How to build a technology stack that scales

A scalable stack is boring in the best sense. Each system has a job. The jobs do not overlap more than they must. When something happens in the business a new customer, a finished job, an invoice, an exception the information knows where to go.

That does not require exotic software. It requires decisions. What is the system of record for the customer? For the work? For the money? What is allowed to be a satellite? What will we refuse to add until the core is connected?

Scale also requires a path for exceptions. Real businesses are not linear. The architecture has to hold the messy cases without sending them back to a hero in the inbox.

I prefer fewer, better-connected tools over a large estate of specialist products that do not speak. Breadth is useful. Coherence is more useful.

If you are choosing software without a picture of the operating system, you are decorating. Start with the picture.