A pragmatic tech-stack scaling assessment

Orbit Partners runs a deliberately simple stack: Salesforce and the Microsoft suite. That simplicity is a strength, with fewer moving parts and fewer dependencies that can hold back growth. They asked me to assess it with an eye on scaling.

Rather than recommend change for its own sake, I focused on the questions a growing business should get ahead of. On Salesforce, that meant the usual scaling pressure points: storage and data management, the cost of maintaining heavy customisation, API limits on integrations, performance as usage grows, and some basic governance and monitoring so problems get caught early rather than after they bite. The main recommendation was simple but important: get a clear, current picture of usage, like storage, API calls and response times, so growth can be planned for rather than reacted to. Where deeper, product-specific expertise was needed, I drew on specialists in my network rather than overclaiming.

The most interesting opportunity was about knowledge, not infrastructure. As in many firms, valuable material from past projects is spread across documents and slides, and there is real value in making it easier to surface to the people who need it, so good work gets reused rather than rediscovered. I flagged this as the most promising thing to explore together next.