01The chicken-and-egg of the first price
Pricing advice assumes you have customers to experiment on. Before launch you don’t — and yet you still have to put a number on the page. Picking it by gut, or by marking up your costs, ignores the only thing that matters: what this problem is already worth to the people who have it.
You’re not the first person to charge for solving this, even if your exact product is new. The market has already set reference points; pre-launch pricing is mostly the work of finding them.
02Anchor on what people already pay
The most reliable pre-launch anchor is spend that already exists. People pay for adjacent tools, for partial fixes, for a freelancer or VA to do the job by hand. Each of those is a number the market has validated with real money — far better evidence than any “what would you pay?” answer.
Read enough of these and a band emerges: a floor people clearly accept, a ceiling that triggers complaints, and the gap in between where a new product can land.
03Where to find pre-launch price anchors
The references that come with a real decision attached:
- What they pay for competitors — named tiers people accept (“I’m on the $29 plan”)
- What they pay for workarounds — a VA, a freelancer, a second tool patching the gap
- The price they call too high — “I left when it hit $99” marks your ceiling
- The DIY effort — hours spent on a manual fix, a cost in time you can price against
- “I’d pay X” — useful only as a soft upper bound, since it’s a hypothetical, not a purchase
04From anchors to a starting price
The pipeline turns scattered mentions into a distribution: the willingness-to-pay tiers across the corpus, plus the specific prices named in the verbatim quotes, give you a defensible range rather than a single guess. You set your launch price as a hypothesis inside that band.
Be clear about what this is and isn’t. It gets you a well-grounded first number, not a final one — only a live checkout reveals true willingness to pay. Treat the anchored price as the experiment you start with, then let real purchases correct it.
Read the willingness-to-pay signal
Anchoring a price starts with reading who actually pays — here’s how to find that specifically.
How to find out what customers will pay →05A worked example: triangulating a price from forum signals
Gather what they already pay
You read threads where designers mention current spend. A few say they pay around twenty a month for a general accounting app they barely use; one mentions paying a bookkeeper roughly a hundred a month. That brackets the existing wallet: low-twenties for self-serve software, low-hundreds for done-for-you.
Note what they’ve quit over
Several mention abandoning a rival the moment it jumped past forty a month for a feature they didn’t want. That repeated complaint marks a soft ceiling for self-serve tooling in this niche.
Price the problem in their words
Others describe spending an evening every month chasing late invoices — hours they openly resent. That lost time is a cost you can anchor against, even though no one paid cash for it.
Bracket a starting hypothesis
The floor sits near the twenty-a-month self-serve habit; the ceiling sits below the forty-a-month quit point. A launch price somewhere inside that band — say, the high-twenties — is a defensible first guess. It’s a hypothesis to test at a live checkout, not a final price; only real purchases confirm it.
Frequently asked questions
Anchor on spend that already exists rather than guessing. Read where your target buyers describe what they currently pay for rivals, workarounds, or freelancers, plus the price points they’ve quit over. Those numbers bracket a band — a floor people accept and a ceiling that triggers complaints. Set your launch price as a hypothesis inside that band, then let real purchases correct it.
You triangulate it from three signals: what people already pay for alternatives, the price that made them walk away, and the cost of the problem in their own words — like hours wasted on a manual fix. Together these mark a realistic range. Pick a number inside it as your starting hypothesis; treat it as the experiment you begin with, not a settled answer.
Competitor pages list tiers, but the more useful signal is buyers naming the tier they actually accept — “I’m on the cheaper plan” — and the one they refused. Read discussions where people compare tools and mention real spend. Those lived references tell you which prices stick and which trigger churn, which a pricing page alone never reveals.
Before launch you have no checkout to test, so anchor on existing market evidence instead of gut feel. Collect the prices buyers already pay for adjacent tools and workarounds, the points they’ve abandoned products at, and the cost of the problem they describe. Bracket a starting band from those, launch inside it, and adjust once real purchases give you true willingness-to-pay data.