Micro SaaS Boutique · Service
Find out if people will pay, before you build.
Most failed software products were built well and wanted by nobody. Validation tests the problem, the customer and the price with real prospects, so the decision to build rests on evidence rather than hope.
Overview
What this covers
An idea feels certain from the inside. You have seen the problem, you can picture the product, and friends say they like it. None of that tells you whether a stranger with the problem will pay to have it solved, which is the only question that matters before you spend on development.
Validation answers that question in the cheapest way available. We talk to people who have the problem, study what they use today and what they pay for it, and put a simple landing page with a price in front of them to see who acts. Each step is designed to produce evidence you can look at, not opinions.
You finish with a written recommendation: build, change the idea, or stop. If the answer is build, you also get a first scope for the MVP, so the next step starts from what customers told us rather than from a feature wish list.
Deliverables
What you get
Interview summary
What prospects said about the problem, how they handle it today and what it costs them, with the patterns pulled out and the raw notes attached.
Competitor teardown
The products and workarounds your customers already use, what they charge, where they fall short and where a focused product could fit.
Landing page test
A simple page that describes the product and its price, with a way for visitors to register interest, set up so you can see who responds.
Pricing signal
What prospects say they would pay and what they did when shown a real price, so the first price is grounded in something.
Recommendation and scope
A plain written verdict of go, change or stop, with the reasons, and a first MVP scope if the answer is go.
Approach
How we run it
- 01
Frame the bet
We write down the problem, the customer and the price you believe in, so we know exactly what the work is testing.
- 02
Talk to prospects
We find people who have the problem and interview them about how they deal with it now, not about your idea.
- 03
Study the alternatives
We review the tools, spreadsheets and services they already pay for, and what those cost in money and time.
- 04
Test with a price
A landing page with a clear offer and price goes in front of the right audience, and we record who acts on it.
- 05
Decide together
We walk you through the evidence and the recommendation, and agree the next step.
Questions
Before you ask.
Do I need a list of contacts to start?
It helps if you have one, but it is not required. Part of the work is finding the people who have the problem, and we agree how we will reach them at the start.
What if the answer is no?
Then the validation did its job. A clear no before development is much cheaper than finding out after launch, and the research often points to a nearby problem that is worth more.
Will you build the product afterwards?
If the answer is go and you want us to, yes. The recommendation includes a first MVP scope, and the build is quoted separately. You are free to take the findings to anyone.
How long does validation take and what does it cost?
Both depend on the idea and how easy the audience is to reach. We agree the scope, timeline and price in the quote before any work begins.
Related
Often paired with
Talk to us about idea validation
Tell us the problem and who has it. We will reply with how we would validate it and what an MVP could look like.
