How to Price Your Product When You've Never Sold Anything
Value-based pricing is a method for setting product prices that uses the economic outcome the buyer receives — not the effort the seller expends — as the starting point.
TL;DR: Price based on what the outcome is worth to the buyer, not what the work cost you to produce. Run the value calculation first: what does the buyer's current problem cost them per year? Price at 10–20% of that figure. Say the number out loud until it stops feeling embarrassing, and always present at least two price points so the top tier makes the one you want them to choose feel reasonable. If the number does not make you slightly nervous, it is probably too low.
The cost-plus trap
Cost-plus pricing anchors your fee to your own effort, which disconnects the number from any value the buyer actually receives — and consistently produces prices that are too low.
Here is how it plays out in practice. A developer builds a lead-tracking dashboard. It takes 40 hours. They charge $75/hour, round up, and quote $3,200. The buyer is a solo agency owner who closes three extra deals per month using better data — each worth $4,000. The developer just sold $144,000 of annual value for $3,200. They will also be the cheapest option the buyer ever finds, which trains the buyer to expect that price point and makes upselling harder later.
The problem is not that $3,200 is a bad number in isolation. The problem is that it was derived from the wrong direction — from effort, not outcome.
The real driver of low prices is rarely logic. It is fear. Fear that saying the real number will end the conversation before it starts. That fear is worth examining directly, because the cost of acting on it is compounding.
The value-based method
Value-based pricing works by calculating what the problem costs the buyer per year, then pricing at 10–20% of that figure — the range where the ROI is obvious and internal justification for the purchase is easy.
Four questions get you to the right number:
- What problem does this solve? Be specific. "Saves time" is not specific. "Eliminates the 3-hour weekly manual export their ops manager currently does" is specific.
- What does that problem cost the buyer right now? Convert it to dollars. Time multiplied by their hourly rate, missed revenue, or a recurring penalty they are currently absorbing.
- What is the outcome worth to them over 12 months? Multiply the weekly saving by 52, or the monthly revenue uplift by 12.
- Price at 10–20% of that annual value. At this range, the buyer's ROI is clear and the purchase requires minimal justification internally.
For a product saving someone $2,000/month ($24,000/year), value-based pricing points to $2,400–$4,800 per year, or $200–$400/month. That is the zone to work in — not a single number, but a defensible range built from real data about the buyer's situation.
Pricing approach comparison
| Method | Starting point | Common outcome | Risk |
|---|---|---|---|
| Cost-plus | Your hourly rate × hours | Chronic undercharging | Trains buyers to expect low prices |
| Competitor anchor | Their published price | Race to the bottom | Ignores your actual value |
| Gut feel | What feels safe | Unpredictable, usually low | No rationale to defend under pressure |
| Value-based | Buyer's annual problem cost | Defensible, often 3–5x higher | Requires discovery conversation |
The table makes the choice clear: value-based pricing is harder upfront because it requires a discovery conversation before you can produce a number. Every other method trades that difficulty for a number that consistently underserves you.
The "say it out loud" test
Before you publish a price or say it on a call, say it out loud to yourself. This test surfaces calibration errors that spreadsheets cannot.
$97/month. $297/month. $997/month.
The one that makes you slightly uncomfortable — the one where you instinctively want to add a caveat or offer a discount before the prospect even reacts — is usually the right one. The one that feels safe is almost always too low.
This is not about being aggressive. It is about calibration. If a price does not require a moment of internal courage to state, you have almost certainly anchored it to your own effort rather than the buyer's outcome. The discomfort is a useful signal. Do not eliminate it by choosing the safer number.
Anchoring: never show one number alone
Never present a single price. Without a reference point, buyers assess absolute value poorly — they need at least two options to judge what is reasonable.
The top-tier option does one specific job: it makes your middle option feel moderate. A buyer who sees $1,200/month next to $497/month will process the $497 as reasonable, even if they would have balked at $497 presented in isolation. This is not manipulation — it is how human valuation works. Buyers do not assess absolute value well. They assess relative value.
The structure that works consistently:
| Tier | Role | Pricing principle |
|---|---|---|
| Starter | Credible entry point | Enough value to be real, low enough to reduce friction |
| Growth | The option you want most buyers to choose | Positioned as the obvious middle ground |
| Scale | Anchor for the Growth tier | 2–3x the Growth price; makes Growth feel moderate |
Even if you only want to sell one thing, build the tier above it before you pitch. The Scale tier's job is not to sell — it is to make the number you actually want to close feel like the reasonable choice.
Before and after: the same product, priced two ways
BEFORE (cost-plus):
A developer builds an API integration that pulls inventory data from a supplier and syncs it to a client's Shopify store. It takes 30 hours. They charge $85/hour and quote $2,550 as a one-time fee. The client accepts immediately — which is a signal the price was too low.
AFTER (value-based):
Same integration. The developer asks what the manual process currently costs. The client's VA spends 6 hours per week doing it manually at $25/hour — $7,800 per year. Stock errors from lag cause roughly $1,200/year in cancelled orders. Total problem cost: $9,000/year. The developer prices the integration at $1,500 setup plus $199/month (year-one total: $3,888 — well under 50% of the problem cost). The client pauses, thinks, and says yes.
The second conversation also repositions the developer from "person who builds things" to "person who understands the business." That reframe matters for every sale that follows.
When the prospect asks how you came up with the number
Tell them exactly how you calculated it. Walking a prospect through the value estimate turns a price objection into an ROI conversation.
"I looked at what this problem currently costs you. You told me your team spends about eight hours a week on manual reconciliation. At your billing rate, that is around $400/week — roughly $20,000 a year. I am pricing this at $4,800 for the year. If it saves what we calculated, that is a 4x return."
A prospect who understands how the price was built is significantly easier to close than one who received a number without context. The calculation also creates a shared frame: if they want to negotiate, they have to engage with the value estimate, not just push back on the number. That forces a more honest conversation about what the outcome is actually worth.
One additional benefit: walking through the calculation publicly signals that you understand their business. That signal is valuable independent of whether they buy — it sets the tone for every conversation that follows.
How to read pricing resistance
A prospect's first reaction to your price is data, not a verdict. Understanding what different types of resistance signal helps you respond without defaulting to a discount.
"That's more than I expected" — usually a value gap, not a budget constraint. Ask what they expected and why. The answer will tell you whether you failed to communicate the outcome clearly or whether the problem is genuinely smaller than you estimated.
"We don't have budget right now" — sometimes true, but often a polite objection to an outcome they are not yet convinced is real. Walk back to the value calculation. If they cannot see the ROI clearly, no budget discussion will resolve the objection.
"Can you do it for less?" — the most useful signal is when this arrives without any further justification. A buyer who pushes back with "can you do it for less?" and nothing else often has room in their budget but wants to test whether you will move. If you have done the value calculation, you have a defence. Use it.
"Let me think about it" — the hardest to read because it is the most polite. The right response is a concrete next step, not open-ended follow-up. "What would help you decide?" is more productive than a week of silence followed by a check-in email.
Actionable takeaways
- Calculate the buyer's current cost or missed value before you build your price
- Price at 10–20% of the annual value the outcome delivers
- Say the number out loud before any call; if it does not make you slightly nervous, recalculate
- Always show at least two price points — use the top tier to anchor the one you want them to choose
- When questioned on price, explain the value calculation rather than defending your time
- Treat the first reaction to your price as data — diagnose before you move
If you want a free teardown of your current pricing structure — including a value calculation and where the number likely needs to move — book a session at closewright.com/book.
FAQ
How do I price something if I have no customers yet and no benchmark data?
Start with a proxy. Find a similar problem solved elsewhere — a competing tool, an agency charging for comparable work, a case study in an adjacent industry. Use it as your floor, not your ceiling. If no proxy exists, run a value estimate with hypothetical numbers and validate it in your first three conversations. Early pricing is a hypothesis, not a commitment.
What if a prospect pushes back hard on the price?
First check whether you established the value clearly before stating the number. Most pricing objections are value objections in disguise — the prospect has not yet seen what they are paying for. Walk back through the outcome calculation before considering any price movement. If they push back after a thorough value conversation, that signals a fit issue, not a problem a discount solves.
Should I discount to close my first few customers faster?
Avoid blanket discounts — they compress perceived value and attract the wrong segment. Use a different lever instead: a limited-scope beta offer with a clear reason for the lower price, a time-limited incentive with a hard date, or a payment structure adjustment. Frame it as a different product configuration, not a markdown on the main offer.
When should I raise my price?
Raise when your close rate exceeds 60% and prospects accept with minimal pushback — both together indicate you have room to move. Increase by 20–30% on new enquiries and measure resistance before touching existing customers. If referrals describe your pricing as 'surprisingly reasonable,' that is a direct signal you are undercharging relative to perceived value.
What if my competitor charges significantly less than me?
Being more expensive than a competitor is defensible if you can articulate what the buyer receives that the cheaper option does not. Identify the specific gap — a feature, a guarantee, a result — and tie it to a dollar value. 'Our integration eliminates a manual step theirs requires' is a sentence; add a number and it becomes a justification.
Bring your outreach. Get it torn down.
Get your outreach torn down →