Why removing the price does not remove the reason people stay put.
Ten people described your problem in their own words before you ever mentioned you were building something. You gave all ten free access. Two created an account. One started setup. None finished.
The instinct is to rewrite the landing page. That instinct is almost always wrong, and it is wrong in a specific way worth understanding, because the same mistake shows up long before a product exists.
Why does a free offer fail if the problem is real?
Because a free offer removes exactly one of the three costs a person pays to switch, and it is the smallest one.
The three costs are money, effort and exposure. Money is the price. Effort is the thirty minutes of setup, the reconfiguration, the data that has to move. Exposure is the part nobody talks about: if the new thing breaks, the person who championed it owns the breakage.
Free deletes the money. It leaves effort untouched and it makes exposure slightly worse, because a free tool is easier for a colleague to dismiss as unserious. A founder reading zero adoption as a pricing failure is reading the one variable they changed and ignoring the two they did not.
Why do people only ever complain about price?
Because price is the only objection that makes the person saying it look reasonable.
Telling a founder this is too expensive positions the buyer as prudent. Telling them you cannot be bothered to spend half an hour on it positions you as lazy, and telling them you do not want to be the person who broke the reporting workflow positions you as scared. Nobody volunteers either of those to someone who is visibly hoping for a yes.
So price absorbs every other objection. It is the socially acceptable container. Founders then optimise the container and wonder why the contents did not change.
What is the real competitor?
Not another product. The janky thing they already have.
The workaround people complain about in public is usually annoying enough to mention and functional enough to keep. That combination is far more durable than it looks. A spreadsheet maintained by hand for two years has a property no new product has: everyone already knows what it does when it goes wrong.
This is why we have no competitors is one of the least useful sentences in a pitch. There is always an incumbent. Sometimes the incumbent is a person doing it manually on a Friday afternoon.
How do you test switching cost before you build?
You look for evidence that somebody already paid something to make the problem smaller.
Not that they said it was painful. That they did something. Built a spreadsheet. Paid a freelancer. Wrote a script. Maintained a workaround. Any of those means the problem crossed the threshold where effort became worth spending, which is the only threshold that matters.
If nobody in your sample has ever spent an hour or a euro on a bad version of the solution, the problem is real and dormant. Real and dormant is a legitimate finding. It is also a completely different business than real and urgent, and it needs a different plan and a longer runway.
The question to run through your last ten conversations is short. What did they do about it the last time it happened? Not what they would do. What they did, when, and whether anyone else got involved.
Key takeaways
- Free removes money, not effort and not personal exposure, and the last two are usually larger.
- Price is the objection people are socially permitted to give, so it absorbs every other objection.
- Your competitor is the tolerable workaround, and tolerable is stronger than it looks because its failure modes are known.
- Evidence of prior effort, meaning a spreadsheet, a freelancer or a script, is the cheapest available proxy for switching willingness.
- A problem can be real and dormant. That is a finding, not a failure, but it changes the plan.
FAQ
Does a free trial ever validate demand?
It validates curiosity. Completed setup by someone who had no relationship with you validates something closer to demand, because setup is where effort gets spent.
If ten people confirm a problem and none adopt, was the research wrong?
The research was probably right about the problem and silent about urgency. Confirming a problem exists and establishing that it outranks everything else on someone's list are two separate questions, and most interviews only ask the first.
How do you ask about switching cost without leading the answer?
Do not ask about switching at all. Ask what they currently do, how long it takes, and what happened the last time it went wrong. Switching cost is what you infer from the answer, not what they report.
Is doing the setup yourself a good idea?
It is a good way to get usage and a bad way to get a reading. It works, and it hides the signal, so track hand-held users separately from self-serve ones from the first day.
What if the workaround is genuinely terrible and people still keep it?
Then it is not terrible enough to beat the risk of change. Terrible and known outperforms better and unknown far more often than founders expect.