Skip to content
Boxed OnlineGary Kellett · Architect · CTO · AI, home
All build notes

5 min readArchitecture

"There must be a better way": how an architect looks at a small business

Enterprise architecture sounds like something for FTSE companies. The same thinking, sized properly, saves small businesses from buying the wrong system.

By Gary Kellett, architect, fractional CTO and chief AI officer

Most owners who call me say some version of the same sentence: there must be a better way to do this, I just don't know what it is.

Enterprise architecture is the discipline of answering that properly. How does the work really flow? Which systems and people touch it? Where does time leak, and where do errors creep in? What are the realistic options, and what does each cost?

In large organisations that work fills a team. In a business of thirty people it fits into a few days, and it often ends somewhere surprising: a process change, a setting in software you already pay for, or one small automation, rather than a new system.

The point is to make the decision on evidence, before a salesperson makes it for you.

Next note

Quoted nine weeks, built in an evening: what actually happened

The plan said 52 to 63 developer-days. The designer shipped the same evening. Here's the process that made that possible, and the parts that still took time.

Newsletter

Get the next note by email

Built this month

One email a month: what I built, what it was quoted at, and what it actually took. No fluff.

Next step

Tell me what's stuck.

In 30 minutes you'll know whether to fix it, buy it, build it or leave it. No pitch deck.

Book a 30-minute callProve a process free

I reply personally within one working day.