Building is the expensive part of a startup. Testing an idea is cheap, as long as you do it before the build and not after. Two focused weeks can tell you a lot about whether people want what you plan to make.
This is the plan we walk founders through. You don't need a designer, a developer or a budget. You need a notebook, a phone and the discipline to listen.
Days 1–2: Write down your riskiest assumption
Every idea rests on a stack of assumptions. Some are safe. One or two could sink the whole thing.
Start by writing the idea as one sentence: who it's for, what problem it solves, and how you'll make money. Then list everything that has to be true for it to work. For example:
- People with this problem exist, and you can reach them.
- The problem hurts enough that they already try to solve it.
- Your solution is clearly better than what they do today.
- They will pay a price that covers your costs.
Now circle the one that, if it's wrong, makes everything else pointless. That's your riskiest assumption. Usually it isn't “can we build it?” It's “does anyone care enough to change what they do?”
Write it as a statement you can prove wrong: “Small restaurant owners in our city will pay a monthly fee for a tool that handles WhatsApp orders.” If you can't imagine evidence that would make you drop it, it isn't specific enough yet.
While you're at it, write down what result on day 14 would make you build. For example, “at least five people pay a deposit.” Deciding this now stops you moving the goalposts later, once you're attached to the idea.
Days 3–7: Talk to 10–15 potential customers
This is the most important part of the two weeks, and the part founders most often skip.
Who to talk to
Pick people who match the “who” in your sentence. Not friends, not family, not people who want to be nice to you. Find them where they already gather: industry WhatsApp groups, LinkedIn, local business associations, Facebook groups, the shop down the street. Ask for 20 minutes to learn how they work, not to pitch.
Ten to fifteen conversations is enough to hear patterns. When you start hearing the same stories again, you can stop.
Ask about the past, not opinions
People are bad at predicting what they'll do, and kind when you ask what they think of your idea. “Would you use this?” almost always gets a yes. That yes is worth nothing.
Instead, ask about what they actually did. Past behaviour is evidence. Future intentions are guesses. Questions that work:
- “Tell me about the last time this problem came up. What happened?”
- “What did you do to solve it?”
- “What does it cost you today, in money or time?”
- “Have you looked for a better way? What did you try?”
- “Why didn't that work for you?”
- “Who else is involved when you deal with this?”
Questions to avoid:
- “Would you use an app that…?”
- “How much would you pay for…?”
- “Do you think this is a good idea?”
Don't describe your solution until the end, if at all. Take notes in their words. If someone says “it's annoying, but we manage,” write it down. It often means the problem isn't painful enough to pay for.
Say you're planning a booking app for hair salons. If five salon owners tell you their paper diary works fine, that's a signal. If they tell you they lose clients every week to missed calls and have already tried three apps, that's a very different signal.
Days 8–13: Run a small test
Conversations tell you about the problem. A test tells you whether people will act. Pick one of these.
A one-page landing test
Build a single page that explains the offer in plain words: who it's for, what it does, the price, and one clear action. That action should cost the visitor something: leaving their phone number for a call, joining a paid waiting list, or putting down a small deposit.
Send people to it from the communities you found in week one, or with a small ad budget you're ready to lose. Watch what visitors do, not how many arrive.
A manual “concierge” version
Or skip software entirely and deliver the result by hand to a handful of customers. Say your idea is an app that plans weekly meals for families. Plan the meals yourself, over WhatsApp, for five families for one week. Charge something, even a little.
The concierge version teaches you things a landing page can't: what customers actually ask for, where they get stuck, and whether they come back. It's also the cheapest prototype there is.
Real signals vs polite interest
By now you'll have plenty of reactions. The hard part is being honest about which ones count.
Real signals cost the person something:
- A pre-order or a paid deposit.
- Someone paying for the concierge version, then asking for more.
- People giving you time: a second meeting, or an introduction to their manager or a colleague with the same problem.
- Someone sharing their data or documents so you can help them.
- A customer chasing you to ask when it's ready.
Polite interest costs nothing:
- “Great idea, I'd definitely use it.”
- Likes and comments on a post.
- Email sign-ups that never open anything you send.
- “Let me know when it launches.”
Polite interest feels good and tells you very little. One person paying a deposit is worth more than a hundred compliments.
Day 14: Build, change or stop
Lay out your notes and go back to the assumption and the threshold you wrote on day one. Then make one of three calls.
Build
You heard the same painful problem again and again. People already spend money or time on it. Some of them gave you money, a deposit or serious time. Now build the smallest version that delivers the result, and nothing more. Keep the people who paid close. They're your first users.
Change
The problem is real, but your solution or your customer was off. Maybe accountants care and restaurant owners don't. Maybe people want a service, not software. Rewrite your sentence, pick the new riskiest assumption, and run another two weeks. This isn't failure. It's the cheapest kind of learning.
Stop
Nobody described the problem without you prompting them. Nobody paid, and nobody chased you. That's a hard answer, but it's a good one. You found out in two weeks, not after a year and your savings.
Where we come in
This is the kind of thinking behind two of our workshops: the Design Thinking Sprint and Startup Fundamentals, two days each, for teams and founders who want to test ideas before they spend on them.
If you've run your two weeks and want a second opinion on what you found, or you're not sure where to start, book a free 30-minute call. We'll look at your idea with you, and if there's work we can do together, you'll get a fixed quote within 48 hours.