When the leak is not in the software.

Sometimes the answer is not to build. It is to fix the pricing, the channel, or the team. How a two-week Strategy engagement tells you which one — and why this is often the cheapest, most valuable thing we do.

Most owners who come to us asking for software actually need something else first. The conversation usually starts with "we want to build X." It ends, more often than we expect, with "the leak is not in X. The leak is in your pricing, your channel, or the way your team is structured. Software will not close it."

This is the work that the Strategy & Advisory engagement exists for. Two weeks. Fixed fee. A written memo. The memo says whether the problem you have is a software problem, and if it is not, what it actually is.

The most common categories of non-software leaks are these. First: a pricing model that has not been updated since the company was much smaller, and is now leaving twenty per cent of revenue on the table. Second: a channel strategy that depends on the founder’s personal network, with no plan for what happens when the network stops introducing. Third: a team structure where the wrong people are doing the most important work, usually because the founder has not yet replaced themselves in two key roles. Fourth: a positioning that no longer matches the customer the business actually sells to.

None of these are solved by building software. Some of them are made worse by building software. A new product launched on a broken pricing model is just a broken pricing model running on more code.

What a Strategy engagement does. Week one, we read what the business has — financials, customer data, the existing pitch deck, the team structure, the operating cadence. We interview the founder and four to six people on the team. We look at the metrics that the founder watches, and at the metrics they would watch if they had more time.

Week two, we write. The memo has three parts: what we read, what we think it means, and what we recommend. The recommendation might be to build software. It might be to fix the pricing first. It might be to hire a head of marketing before anything else. The reasoning is on the page. The owner can disagree, and we have explicitly written the engagement so the owner can disagree productively.

Why this is often the most valuable work. A two-week engagement that prevents a year of building the wrong thing has paid for itself many times over. The same is true if the engagement is the thing that gets a stalled business unstuck — sometimes the answer is one obvious change that the team can implement without us.

Why this is the cheapest engagement we offer. We do not need to staff a build team. We do not need to commit to a multi-month commitment. We need the founder’s time, our reading time, and the discipline to write the memo without padding.

The wrong reason to take a Strategy engagement is to confirm a decision you have already made. We will not do that. The right reason is to find out which version of the problem you actually have, and which intervention closes the gap. If the answer is software, we will tell you. If it is not, we will tell you that too.

→ If the leak is not where you think it is, the Discovery is two weeks well spent. Book one.