The questions founders actually ask.

Consultancy is the closest familiar category — but the role doesn’t stop at recommendation. I get inside the business, find the gap nobody inside it can see, and stay with the problem until that gap is actually closed. Sometimes the fix is insight. Sometimes it’s a change in roles, structure or workflow. Occasionally it’s something that has to be built. I own the problem until the right answer is visible — and when appropriate, Anaptyx can make that answer real.

Because the thing holding a business back rarely announces itself in a spreadsheet or a board meeting. It is usually somewhere more ordinary — the handover everyone works around, the decision that quietly waits for one person, the process that technically exists but nobody actually follows, the founder compensating for a structural gap so effectively that everybody has stopped noticing the gap. You have to get close enough to feel the friction. Distance is useful for seeing assumptions. Proximity is necessary for seeing reality. I need both.

No. Sometimes clarity is sufficient — the gap is named, the sequence is clear, and the business closes it without me. That is a successful outcome, not a lesser one. When the gap lives in roles, ownership, workflow or operating structure and needs more than clarity to close, I stay close enough to redesign the relevant part of the business and help the new way of working take hold. That work is bespoke, and scoped only after The Fix.

Sometimes. But software is never assumed. I don’t sell software — sometimes I discover a business needs software. There is a very big difference. The build happens only when immersion establishes that the business cannot see, coordinate or manage itself properly because the infrastructure it genuinely requires does not exist. Most businesses never reach that stage. That discipline is what makes it credible when one does.

Probably not. The build exists because an investigation determined it was the right answer — never the other way round. If you arrive with a build already decided, the first thing I’d want to test is the decision. That’s not awkwardness. It’s the same discipline that protects every client from being sold something the business doesn’t need.

Sometimes that is exactly what I will recommend — and it’s the cheaper, faster, better answer more often than a builder would like you to believe. A custom build is justified only when existing solutions would force the business into a model that does not fit the way it genuinely needs to operate. The test is honest fit, not commercial appetite.

You do. Outright. Anything Anaptyx builds is designed around how your business actually operates, secure, maintainable, and owned by the client — with no artificial subscription lock-in and nothing designed to keep you dependent.

Absolutely not. For many businesses the engagement ends with the gap named and the sequence clear. Nothing further is sold until the investigation has established that something further is actually required — and if you do not need me afterwards, I will tell you.

Established founder-led businesses with enough history, people and operational complexity to investigate. Real revenue, a team, systems, customers, moving parts — and a problem that keeps not adding up despite several sincere attempts to solve it. If the business is early-stage or pre-revenue, there isn’t enough working reality to get inside yet.

Excellent. You do not need a diagnosis to begin. Most founders arrive with a feeling, not a diagnosis — something is off, something keeps returning, something doesn’t add up. That feeling is usually the most accurate piece of information in the business. Naming the problem is my job, not yours.

Expect that assumption to be tested. Sometimes it survives — and then we know it’s real, which is worth more than believing it. More often, the problem you’re describing turns out to be what the actual problem produces. Either way, the investigation follows the evidence, not the existing theory.