Structure · Pricing & Packaging

Design a Value-Based Pricing Model

Move a service from hourly or cost-plus pricing to a value-based model tied to client outcomes and willingness to pay.

founderAdvancedA full pricing strategy session
When to use
Use this when you suspect you're under-pricing because you're anchored to hours or cost-plus, and the client value of your work is meaningfully higher. Best for services with measurable outcomes (revenue, leads, rankings). Run it once per high-leverage service line before your next pricing refresh.
The prompt
You are a pricing strategist who has helped digital marketing agencies move from hourly and cost-plus pricing to value-based pricing models.

Agency: [AGENCY_NAME] | Service: [SERVICE_LINE]
Current pricing model: [CURRENT_MODEL] (e.g., hours x rate, cost-plus, flat retainer)
Current average fee: [CURRENT_FEE]
Measurable client outcomes from this service: [OUTCOMES]
Dollar value of those outcomes (avg + range): [OUTCOME_VALUE]
Proof / case study data we can cite: [PROOF_POINTS]
Client size we serve: [CLIENT_SIZE]
Willingness-to-pay signals from past deals: [WTP_SIGNALS]
Cost basis: [COST_BASIS]
Margin floor: [MARGIN_FLOOR]

Design a value-based pricing structure for this service. Define the value metric, the value-to-price ratio, the price points for 2-3 customer segments by size or outcome potential, and the proof needed to defend the price.

- Anchor price to a client value metric (revenue influenced, qualified leads, conversion lift, etc.) — not hours.
- Show the value-to-price ratio (we capture X% of value created).
- Price must clear [MARGIN_FLOOR] given [COST_BASIS] — show the floor check.
- Use only [PROOF_POINTS] I provided; don't invent case studies.
- Include a script for explaining the pricing on a sales call (4-6 lines).

1. Value metric definition
2. Value-to-price ratio (with rationale)
3. Segment pricing table: Segment | Outcome Range | Price | Value Captured % | Margin Check
4. Proof points to cite per segment
5. Sales call script (4-6 lines)
6. Migration plan for existing clients (3 bullets)
Variables
  • [AGENCY_NAME] — Your agency
  • [SERVICE_LINE] — Service you're repricing
  • [CURRENT_MODEL] — How you price today
  • [CURRENT_FEE] — Current avg fee for this service
  • [OUTCOMES] — Outcomes you reliably drive
  • [OUTCOME_VALUE] — $ value of those outcomes
  • [PROOF_POINTS] — Case studies / data you can show
  • [CLIENT_SIZE] — Client size you serve
  • [WTP_SIGNALS] — What past clients have paid / pushed back on
  • [COST_BASIS] — Internal delivery cost
  • [MARGIN_FLOOR] — Lowest acceptable margin
Example input
AGENCY_NAME: Northbound | SERVICE_LINE: B2B SaaS demand gen retainer | CURRENT_MODEL: Flat retainer $8k/mo | CURRENT_FEE: $8,000 | OUTCOMES: SQLs delivered to sales | OUTCOME_VALUE: Avg SQL worth $4,500 in pipeline, 22% close rate, $35k ACV | PROOF_POINTS: 3 case studies showing 40-80 SQLs/mo within 6 months | CLIENT_SIZE: $5M-$30M SaaS | WTP_SIGNALS: Clients have paid $15k/mo when SQLs were the metric | COST_BASIS: $3,200/mo delivery | MARGIN_FLOOR: 55%
Example output
Value metric: Qualified SQLs delivered per month (SLA defined jointly).
Value-to-price ratio: We capture ~12% of pipeline value created.

| Segment | SQL Range | Price | Value Captured | Margin Check |
|---|---|---|---|---|
| Foundation | 15-25 SQLs/mo | $9,500/mo | ~11% | 66% ✓ |
| Growth | 25-50 SQLs/mo | $14,000/mo | ~12% | 77% ✓ |
| Scale | 50+ SQLs/mo | $19,500/mo | ~10% | 84% ✓ |

Proof: 3 SaaS case studies showing 40-80 SQLs/mo within 6 months at 22% close rate.

Script: "Your average SQL is worth roughly $X in pipeline. At 40 SQLs a month, that's $X in monthly pipeline contribution. Our fee is roughly 12% of the pipeline we generate — meaning if we don't hit the SQL band, we're not earning it."

Migration: 1) Grandfather existing clients for 6 months. 2) Offer them new model with a 10% loyalty discount for year 1. 3) New deals go on value-based pricing starting next quarter.
Pro tips
  • Don't move to value pricing until you can prove outcomes with at least 3 case studies.
  • Define the value metric jointly with the client in onboarding — it kills disputes later.
  • Hold a margin floor — value pricing isn't an excuse to over-promise and lose money.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts