Launch essay · 7 min read
Test the Smallest Honest Version of Your Business Idea
A logo and a complex platform can protect an idea from the one thing that would actually tell you whether it works: a customer.
Building as a form of avoidance
There's a quiet trap in early-stage business ideas: the more time you spend building — the branding, the website, the elaborate platform, the perfect pricing tiers — the more it feels like progress, and the less exposed you are to the actual question that matters, which is whether anyone will pay for this. Building feels safe because it's entirely within your control. Selling feels risky because someone else gets to say no.
This is not a character flaw; it's a rational response to an uncomfortable truth. But it means that a great deal of what looks like 'working on the business' is, functionally, a way of delaying contact with the market. The idea stays safe as long as it stays theoretical.
Six honest questions before you build anything
Before building, it's worth answering six questions in plain language, without polish. What is the problem — described the way a real person experiencing it would describe it, not the way you'd put it in a pitch? Who is the customer, specifically enough that you could picture them and, ideally, name a few actual people who fit? What is the offer — the smallest useful version of the thing that solves the problem? What is the price — a real number you could ask for tomorrow? What is the channel — how would this specific customer actually hear about it? And what evidence do you already have, or could gather quickly, that this problem is real and that people would pay to solve it?
None of these require a website. All of them can be answered, at least provisionally, through direct conversation and a bit of honest reflection. If you can't answer them, that's useful information — it tells you what to find out before spending money.
Five conversations, minimal spending
The smallest honest test of most ideas is not a product; it's a conversation. Find five people who genuinely resemble your intended customer, describe the problem you think they have, and listen. Not for validation — for accuracy. Do they recognise the problem? Have they tried to solve it already, and how? Would they pay for what you're describing, and does the number you had in mind survive contact with their actual reaction?
This can be uncomfortable, because it invites disconfirmation in a way that building alone never does. But five honest conversations will tell you more in a week than three months of platform development will tell you in a quarter, and at a fraction of the cost.
What 'minimal spending' actually protects
The instinct to invest heavily upfront often comes from a good place — wanting to be taken seriously, wanting it to look real. But spending is not the same as commitment, and a polished offer built on an untested assumption is not more serious than a rough one built on evidence; it's less serious, because it has skipped the step that would have told you whether it was worth polishing at all.
Minimal spending at this stage protects two things: your money, obviously, but also your willingness to change course. The less you've sunk into a particular version of the idea, the easier it is to adjust it based on what the five conversations actually tell you, rather than defending a decision you've already paid for.
Design your smallest honest test
Write an offer you could test with five conversations and minimal spending.
- Write one sentence describing the problem, in the customer's own likely words.
- Name five real or realistic people who fit your intended customer.
- Write the smallest version of your offer and a real price you could ask for it tomorrow.
- Plan the five conversations: who, when, and the two or three questions you'll actually ask.
Support for turning an idea into a small, honest, testable offer before you spend heavily on it.