Why I Think Small Operators Deserve Software Shaped Like Their Business

<p>Since August, a bouldering gym in Ipswich has been running on a platform I built. It's called Gripswich OS, and it's the system behind GRIPswich Bouldering. I'm not going to go through features or numbers here. I want to write about what building it made me think about more broadly: what kind of software small, specific businesses should actually be running on.</p><p>My view is that a lot of small operators end up stuck with tools that were never built around them. The usual approach is to take a booking tool, a payments tool, a spreadsheet, an email platform and maybe a generic CRM, and glue them together. Each one is fine by itself. Put together, the business owner becomes the integration layer. They copy data between systems, they reconcile things by hand, and they bend their processes to fit whatever the tools assume.</p><p>I think that's backwards. The software should fit the business, not the business the software.</p><p><strong>Generic tools optimise for the average customer</strong></p><p>This isn't a criticism of horizontal SaaS. If you're building for thousands of different businesses, you have to design for the middle. That's the right call for those products. But a climbing gym isn't the middle of anything. Neither is a driving school, an engineering consultancy or a trade business quoting jobs. They all have their own vocabulary, their own rhythms and their own edge cases, and generic tools either ignore those or bury them three menus deep.</p><p>So when someone running one of these businesses says the software "sort of works", I hear something specific. It means there's a person in the loop doing the work the software should be doing.</p><p><strong>Why custom used to be the wrong answer</strong></p><p>For most of the history of small-business software, "build something custom" was bad advice. It was expensive, slow and fragile, and once the developer moved on, nobody was left to maintain it. Buying off the shelf won because custom was a trap.</p><p>I think that tradeoff has shifted, and AI is a big part of why. I've written before that I treat AI as infrastructure rather than a feature, and this is where that shows up in practice. Building a focused platform for one business is now within reach of a very small team. Not because the work has become trivial, but because so much of the routine scaffolding can be done with AI as a genuine collaborator. That leaves the human effort for the part that matters: understanding how the business really runs.</p><p><strong>Specific doesn't have to mean one-off</strong></p><p>The obvious objection is that bespoke software doesn't scale. If every business gets its own system, you've built a consultancy, not a product.</p><p>I don't think it's that binary. The way I see it, the right move is to build for one real business properly, then pull out the parts that generalise. That's exactly the path I'm on with AIREP: going from a system built around real operational needs to a multi-tenant product other businesses can use. The specificity comes first and the abstraction comes second. If you do it the other way round, you end up with yet another generic tool that fits nobody very well.</p><p>A real operator using the software every day is the best spec you'll ever get. They don't care about your architecture. They care whether the thing they need to do takes one step or five.</p><p><strong>What I'm optimising for</strong></p><p>When I build for a small business, I want three things. First, the owner should stop being the integration layer. Second, the system should use the business's own language, not a vendor's. Third, it should be honest: no dark patterns, no features designed to lock people in, and no pricing games baked into the UX. Those values aren't a marketing line for me. They're design constraints, and they rule out a lot of the patterns generic platforms rely on.</p><p>I'm not claiming every small business needs a custom platform. Plenty are well served by off-the-shelf tools, and they should use them. But I think the set of businesses that would be better off with software shaped like them is far bigger than it used to be, and it keeps growing as building gets cheaper.</p><p>That's the bet behind a lot of what I'm doing at Intelli AI. Gripswich OS running a real gym every day is the clearest example I have of why I think it's the right one.</p>