Most businesses that come to us open with a solution. We need an app. We need a client portal. We need to replace our CRM. It is a perfectly reasonable way to start the conversation, and it is almost never the real problem.
The real problem usually sits further down: a process that takes three people and a day, a spreadsheet somebody is afraid to touch, a stack of subscriptions that do not talk to each other. The app is the shape the frustration took by the time it reached a meeting. Our job is to find the frustration first, and only then decide whether building anything is the right answer.
The request is a symptom
When someone says they need software, what they are describing is a gap between how the work actually happens and what their tools let them do. Sometimes that gap is real and structural. Sometimes it is a setting nobody found, a report nobody configured, or a tool the business already pays for and never fully set up.
So the first thing we do is not design. It is watch. We sit with the people doing the work and follow a single job from start to finish — where the information comes from, where it gets re-typed, where somebody waits, where somebody double-checks something a machine should have checked. The answer to what to build falls out of that far more reliably than out of a feature list.
When off the shelf is the right answer
The honest answer to custom software vs off the shelf is that off the shelf wins most of the time. If what you need is a commodity — email, accounting, payroll, a booking calendar — a good product built by people who do nothing else will beat anything built from scratch, and it will keep improving without you paying for the improvements. Nobody's competitive edge lives in their invoicing tool.
Off the shelf is also right when the tool already fits how you work, or when adapting your process to the tool is genuinely an improvement. Plenty of businesses get better by adopting a well-designed product's way of doing things.
When custom earns its place
Custom starts to make sense in a few recognisable situations. When the way you deliver your work is the thing that sets you apart, and every off-the-shelf option forces you to work like everyone else. When you are paying for a large platform and using a small part of it, while bending your process to fit that part. And when your business runs on several tools that each hold a piece of the picture, so people spend their days carrying data from one to the next.
In those cases the question is less about software and more about who owns the system your business runs on, and whether that system fits the business or the business has been bent to fit the system.
Nobody really needs software. They need the job that takes three people and a day to stop taking three people and a day.
What that looks like in practice
A consulting firm came to us on the premium tier of a very large CRM. The problem was not that the CRM was bad; it was that the team used a small fraction of it, and even that fraction did not match how they actually worked. We rebuilt that fraction around their process — client records with full history, follow-ups triggered by real events, a client portal — and they switched the subscription off.
A therapy and coaching practice was running courses in one place, a media library in another, a community somewhere else, and client intake in a tool that talked to none of them. Every system was an island. We built them as one: one login, one set of member records, where progress, purchases and assessments all land in the same place and nothing is re-entered by hand.
A company that prepares pilots for airline interviews had generic practice tools that could not sound like the airline in the room. We built an interviewer that speaks in the voice of a specific airline, listens to the answer, scores it against a structured method and keeps each candidate's history. The problem there was not efficiency at all; it was that nothing on the market could do the job.
Three very different businesses, and in none of them was the original request the thing we ended up building. You can see more of that work here.
How to tell which one you need
If you are weighing it up, a few honest questions help. Is the thing you want to fix specific to how your business works, or is it a common job every business has? Have you genuinely exhausted the tools you already pay for? Would owning this system matter if the vendor changed its pricing or retired a feature next year? And is the pain big enough that fixing it properly would change how the week feels for the people doing the work?
If most of the answers point towards common and already solved, buy something good and move on — that is the right call, and we will tell you so. If they point towards specific, painful and central to how you operate, that is where a bespoke system earns its keep. It is the same reasoning behind building websites without a database-and-plugin stack. If you recognise your business in any of this, tell us what is hard and we will start there.
