All articles
Go-to-market

Willingness to pay is a research question, not a guess

Pricing isn't a number you pick in a spreadsheet. Four ways to surface what your beachhead will actually pay before you launch.

GTM · pricingStop guessing the price.

Ask most early-stage founders how they arrived at their price, and you'll often get one of two answers: "we looked at what competitors charge and picked something close," or "we picked a number that felt right and we'll adjust later." Both are guesses dressed up as decisions.

Willingness to pay is knowable before you launch — but you have to go looking for it the same way you'd research any other part of your positioning.

Why "competitor pricing" isn't enough

Competitor pricing tells you what the market has been willing to accept for a different product, sold by a different team, to a possibly different segment. It's a useful data point, not an answer. Anchoring entirely on it means you inherit someone else's assumptions about value — including assumptions that might be wrong for your beachhead specifically.

Four ways to find the real number

1. Ask about budget, not price

Don't ask "what would you pay for this?" — people are notoriously bad at answering hypothetically, and tend to lowball. Instead, ask: "is there a budget today for solving this problem, and roughly what's allocated to it?" This anchors the conversation in something real: money that's already moving.

2. Find the cost of the status quo

What does the problem cost your buyer today — in time, in tools they're already paying for, in mistakes that happen because of it? A product that demonstrably saves $2,000/month of wasted time has a natural ceiling well above a token monthly fee, and your buyer will often do this math for you if you ask the right questions.

3. Run a real pricing page, even pre-launch

A landing page with actual prices on it — even before the product fully exists — generates real signal. Track where people drop off. A spike in abandonment right at the pricing tier tells you something a survey never will.

2-3x

In our review of early pricing experiments, founders who tested a real price on a landing page before launch ended up charging, on average, two to three times more than their original spreadsheet estimate.

4. Ask "what else have you paid for this?"

If your buyer has previously hired a freelancer, bought a different tool, or built an internal workaround to solve this problem, that spend is one of the strongest signals available — it's not hypothetical, it's a number they've already approved.

Worked example · pricing research
Series A–B eng teams, 50–200 developers
Status quo cost~6 eng-hours/week on stale docs
Budget signalExisting line item for dev tooling
Starting priceAnchored above the freelancer rate they currently pay

Where to start this week

Pick three people in your beachhead segment and ask them one question: "what, if anything, are you currently spending — in money or time — to deal with this problem?" The answer is the start of your pricing model, not a survey result to file away.

PositioningBeachheadCustomer researchGo-to-market
DP
Devin Park
Go-to-market lead, FounderMast

Devin has run more first GTM experiments than he can count. He writes about channels, beachheads, and the unglamorous work of finding your first ten real customers.

Put it into practice

Find your beachhead before Friday.

Paste a one-line description of your startup. Five minutes later, walk away knowing exactly who to target and what to do next.

No credit card · Your description stays private