You built something last month that automates 30 hours of a client’s work every week. You billed them $1,500 because it took you three days. The system is now worth somewhere north of $50,000 a year to their business, and you handed it over for the price of a decent laptop.
That gap isn’t a confidence problem. It’s a pricing-method problem. You priced the hours instead of the outcome — and as long as you do that, your income is structurally capped no matter how good you get.
This piece hands over the calculation to fix it. No pep talk. Four steps, one worked example, one worksheet.
The reframe in one sentence
Hours-based pricing sells your time. Outcome-based pricing sells the business result the buyer keeps after you leave.
Hours-based pricing answers the question “what did this cost you to make?” Outcome-based pricing answers the question “what is this worth to me to own?” Those are two completely different numbers, and the buyer only cares about the second one.
Value-based pricing is the same idea stated from the buyer’s side: the price is a fraction of the measurable value the system creates for them, not a markup on your labor.
The shift is simple to state and hard to do, because it means you stop talking about what you built and start talking about what changes in the buyer’s business once you’re done.
Why hours-pricing structurally caps your income
Pricing the hours puts a ceiling on you that has nothing to do with your skill. Get twice as fast at building, and your income halves per project. Get an order of magnitude better at AI tooling, and the same automation that took you two weeks now takes two days — so you charge a tenth as much. The better you get, the less you make.
There’s a second cap. Buyers compare hours-based quotes to other hours-based quotes. Once you’ve named a day rate or a project rate tied to effort, you’re sitting in a market with every other freelance builder and offshore shop, and the only lever you have is going lower.
Outcome pricing breaks both caps. The price is tied to the buyer’s number, not yours. A system that took you a weekend and saves them 1,500 hours a year is priced against the 1,500 hours, not the weekend.
The four-step outcome calculation
Run these in order. Don’t skip step one to get to the number — the number is only defensible if the first three steps are.
Step 1 — Name the business result. What changes in the buyer’s business when this system runs? Pick one of three categories: new revenue created, hours or cost removed, or risk avoided. Write it as a single sentence in the buyer’s language. Not “an AI agent that classifies inbound leads” — “the sales team stops wasting time on leads that won’t close.”
Step 2 — Quantify the result in the buyer’s numbers. Get to a 12-month dollar figure using their inputs, not yours. Ask for the volume (leads per month, hours per week, error rate, deal size). Multiply. If they won’t share numbers, use a defensible mid-range industry figure and show your math. The annual value figure is what you’ll anchor against — call it V.
Step 3 — Locate the value the buyer keeps. The buyer is never going to pay you the full V. They take on the deployment risk, the operating cost, and the opportunity cost of choosing you over an alternative. Your price comes out of a fraction of V that both sides agree the buyer keeps. The rule I use: price between 10% and 25% of the first 12 months of value. Below 10% and you’re underpricing the work. Above 25% and the buyer’s ROI gets thin enough that a smart CFO will say no.
Step 4 — Set the price and write the one-line justification. Pick a number inside that 10–25% band. Round to a clean figure. Write one sentence the buyer can repeat to their boss: “We’re paying [price] for a system that produces [V] in [result] over the next 12 months.” If that sentence doesn’t make sense out loud, the calculation is wrong somewhere — usually step 2.
A fully worked example: $1,500 → $14,000
You built a lead-qualification automation for a B2B services firm. It ingests inbound form fills, enriches each lead from public sources, scores them against the firm’s ideal-customer profile, and routes the top tier to a salesperson with a pre-drafted outreach email. It took you four days. You quoted $1,500 because four days at roughly $375/day felt fair.
Run the four steps.
Step 1 — Business result. The sales team stops spending time on leads that won’t close, and the top-tier leads get contacted within an hour instead of two days. Two effects: hours saved, and revenue captured from leads that would otherwise have gone cold.
Step 2 — Quantify. The firm’s numbers (you asked):
-
Inbound leads per month: 400
-
Time previously spent qualifying each lead: 8 minutes → 53 hours/month → 640 hours/year
-
Loaded cost of the SDR doing that work: $45/hour → $28,800/year saved
-
Top-tier leads previously lost to slow follow-up: estimated 6/month, average deal size $4,000, close rate 25% → $72,000/year recovered
-
V = $100,800/year
Step 3 — Value retained. Buyer keeps 75–90% of V. Your price band is 10–25% of V: $10,080 to $25,200.
Step 4 — Set the number. You price at $14,000. The buyer’s one-line justification: “We’re paying $14,000 for a system that returns roughly $100,000 in saved SDR time and recovered pipeline in year one.” That’s a 7x first-year ROI, which is the kind of number a buyer can defend to anyone.
Same system. Same four days of your time. The price moved from $1,500 to $14,000 because the conversation moved from your hours to their outcome.
Defending the number when the buyer pushes back
The objections are predictable. Here’s the language.
“That seems high for a few days of work.” “The price isn’t tied to the build time — it’s tied to the result. The system returns about $100,000 in year one. We’re asking for $14,000 of that, which is roughly 14%. If we priced this by the day, the math wouldn’t change for you — it would just be a worse deal for me.”
“Can you do it for $5,000?” “I can build a narrower version for $5,000 — one that handles the qualification but not the routing or the outreach drafts. The full system at $14,000 is what produces the $100,000 number. The smaller version produces a smaller result. Happy to scope either.”
“We need to think about it / get other quotes.” “Of course. When you compare, the question to ask each builder is what business result they’re committing to, not what they’re building. If someone quotes lower for the same outcome, that’s a real comparison. If they quote lower for a smaller scope, you’ll want to know what’s missing.”
“How do we know we’ll actually get that result?” “Fair question. We can structure it so the first month is a measurement period — we instrument the system, capture the baseline against the projection, and if the numbers don’t track, we adjust the scope or the price. The result is what you’re buying. I’d rather stand behind it than hide from it.”
Notice what’s missing from those responses: no apology, no discount-as-reflex, no defending the time it took. The price is defended on the buyer’s math, not yours.
The one-page outcome-pricing worksheet
Run this on the next project before you send a number. Filled-in row uses the lead-qualification example above.
Field | Your project | Example (lead qualifier) |
|---|---|---|
1. Buyer & their role | _________ | Head of Sales, 40-person B2B services firm |
2. Business result (one sentence, their language) | _________ | "Stop wasting SDR time on bad leads; stop losing good leads to slow follow-up" |
3. Result category (revenue / hours / risk) | _________ | Hours saved + revenue recovered |
4. Volume input from buyer | _________ | 400 leads/mo, 8 min each, 6 top leads/mo lost |
5. Unit value | _________ | $45/hr loaded SDR cost; $4,000 avg deal × 25% close |
6. Annual value V | _________ | $28,800 saved + $72,000 recovered = $100,800 |
7. Price band (10–25% of V) | _________ | $10,080 – $25,200 |
8. Chosen price | _________ | $14,000 |
9. One-line buyer justification | _________ | "$14K for a system returning ~$100K in year one" |
10. First objection + your one-line response | _________ | "Seems high for a few days' work" → "Price is tied to result, not build time" |
If you can’t fill row 6 with a specific number from the buyer’s business, you’re not ready to price yet — you’re ready to ask two more questions. That’s the whole discipline.
The one line worth remembering
The buyer is not paying for what it cost you to build. They’re paying for what it costs them not to have it.
Every time you sit down to price a system, that line is the test. If your number reflects your effort, you’re leaving money on the table that the buyer would happily have paid. If your number reflects what they keep, you’re running a real business.
Where this fits
Pricing is one leg of the system. The other two are packaging the offer so you stop scoping every project from scratch, and structuring delivery so the math keeps working after the first invoice. Both are covered in companion pieces in this series — one on turning a custom build into a repeatable package buyers can say yes to without a custom proposal, and one on extending the same outcome logic into a retainer once the system is running.
At NextBuild, the outcome-pricing worksheet above is one of the working assets cohort members build alongside the team in week two — applied to a real buyer in their own pipeline, defended in a real sales conversation, and refined until the number holds. The fix isn’t more pricing theory. The fix is running this calculation on a live deal, with someone in the room who’s done it before. Come build it with us at NextBuild.