← All notes

Series · The three questions · 1 / 3

Does the problem exist? The difference between an annoyance and a budget line

The first question in our filter looks the simplest. An annoyance gets worked around, a problem already has a budget: here is how we tell them apart.

Our filter fits in three questions, asked in this order. The first one looks the simplest, and yet it is where many projects stop: does the problem exist?

The question is not about the technology, nor about the quality of the team. It is about the organisation you are selling to. Does it already have a problem, in the sense that it pays for it today, or does it live with an annoyance?

Annoyance or problem

An annoyance is a real irritant that everyone acknowledges in a meeting and nobody funds. People work around it: a spreadsheet, a macro, half a day a month that an analyst spends on it without it showing up anywhere. Users love having it taken away. The organisation has no reason to buy.

A problem is a spend. It already has a budget line, even a badly spent one: a tool that disappoints, a contractor renewed for lack of anything better, identified person-days, a penalty, an insured risk. Someone in the organisation already has to justify what this problem costs.

The difference does not show in a demo. It shows in the budget.

The budget line test

In a meeting, we ask a very concrete question: today, how much does your customer spend on this problem, and on which line?

“Nothing, that is exactly the opportunity” is the answer that worries us most. If nobody spends anything on a problem, the first thing to ask is why, before asking how much it could earn.

“They do it by hand, three people, two days a month” is an interesting answer, on one condition: that those days are visible to someone who holds a budget. A cost nobody sees is not a problem yet, it is an annoyance waiting to be measured.

“They already pay a contractor, or a tool they want to replace” is the best answer. The budget exists, it has already been allocated once to this problem, and your product does not create a spend: it replaces one.

When the budget sits elsewhere

Sometimes the problem is real and the budget is held by a different function from the one that suffers it. This is common in cybersecurity and in industry: the operational team lives with the problem, while finance, compliance or the insurer carries its cost.

That does not disqualify a project; it is often where the best ones are. But it moves the conversation to the second question of the filter, who pays for it, which is the subject of the next note in this series.

What we ask for in a meeting

Not a market study. One sentence: which existing spend your product replaces, or which already-measured cost it reduces, and for which function. If you have that sentence, the rest of the conversation moves fast.

If you do not have it yet, it is not a final no. It is the first customer meeting to get, before ours. And once you have it, run your project through the filter: the guided form drafts your first message from your answers.

Does your project pass the filter?

Three questions, a few minutes: the guided form drafts your first message, and you review it before sending.

Run the filter →

↑ ↓ navigate↵ openesc close