Founder pricing

Purpose

Turn pricing from a guess or webpage exercise into a founder-led learning system that aligns customer value, buying motion, company economics, and expansion.

Give the founder a decision, the evidence behind it, the strongest contrary case, and the smallest executable next step. Do not produce generic encouragement or a long menu of tactics.

When to Trigger

Use this skill according to the frontmatter description. If the stated issue is a symptom of an earlier broken link, say so and route to founder-debugger or the owning retained skill.

Inputs Needed

• Specific user, buyer, champion, and economic buyer
• Painful job and current alternative
• Quantified value: revenue gained, cost removed, time saved, risk reduced, or capability unlocked
• Current model, metric, packages, list price, realized price, and discounts
• Win/loss reasons and price objections in the buyer's exact words
• Activation, retention, expansion, and support burden by segment
• Gross margin and variable cost by unit of value
• Procurement, budgeting, contract, and bill-predictability constraints

Ask only for missing inputs capable of changing the decision. For reversible actions, make assumptions explicit and propose a bounded test instead of blocking on perfect data.

Questions to Ask

• Who receives value, who pays, and who approves?
• What changes economically or operationally after the product works?
• What does the buyer pay or sacrifice today?
• Which unit increases as customer value increases?
• Can the buyer understand and forecast the bill?
• Does the metric discourage the behavior the product needs?
• Are lost deals truly price losses, or weak value, trust, timing, authority, or fit?
• What would happen to conversion, revenue, margin, and support if price doubled?
• Which customers are underpriced because they capture disproportionate value?

Mental Models

• Price is segmentation.
• Value metric before price point.
• Willingness to pay is behavior, not survey intent.
• Packaging is a growth path.
• Price determines sales motion.
• Discounts are data and debt.
• Usage pricing trades entry friction for bill uncertainty.
• Price changes are experiments with trust guardrails.

Use these models as competing lenses. Select the one that best explains the observed behavior, state what evidence would falsify it, and convert it into a decision rather than repeating it as a slogan.

YC Principles

• Charge earlier than feels comfortable; payment is stronger evidence than enthusiasm.
• Start with a simple price and learn through founder-led sales rather than optimizing a pricing page in isolation.
• For B2B, anchor the conversation in business value and ask directly for the sale.
• Do not hire a sales organization before founders understand why customers buy and what objections mean.
• Use price to select customers who have the problem intensely enough to be useful learning partners.

Paul Graham Principles

• A deep initial well matters more than broad mild interest; price helps reveal depth.
• Do unscalable work to understand each early buyer's value and approval process.
• Revenue and ramen profitability create strategic freedom, but charging cannot rescue a product users do not want.

Garry Tan Principles

• Keep the founder close to pricing because it exposes product truth, positioning, and customer quality.
• Use AI for scenario modeling and analysis, not to invent willingness-to-pay evidence.
• Prefer clear, fair, legible pricing over cleverness that damages trust.

Decision Frameworks

Pricing sequence

1. Define the segment and valuable outcome.
2. Quantify the current alternative and economic value range.
3. Choose a value metric that is understandable, aligned, hard to game, and measurable.
4. Choose model: flat, seat, tiered, usage, outcome, transaction, or hybrid.
5. Package only around real segment or value differences.
6. Set a price hypothesis and explicit learning goal.
7. Ask real buyers; record decisions and objections.
8. Model realized price, usage, margin, expansion, and downside.
9. Ship, observe cohorts, and revise.

Model selector

1. Use flat pricing when value and use are similar and simplicity matters most.
2. Use per-seat when collaboration and organizational adoption create value.
3. Use usage pricing when consumption closely tracks value and the bill can remain predictable.
4. Use outcome or transaction pricing when attribution is trusted and results are legible.
5. Use tiering when distinct segments need meaningfully different solutions.
6. Use hybrid pricing when a base platform has durable value plus variable consumption.

Objection diagnosis

1. If qualified buyers do not understand the outcome, fix positioning.
2. If they value it but cannot justify the amount, improve ROI proof or adjust price.
3. If the budget owner differs from the user, redesign the buying path.
4. If usage creates bill fear, add caps, alerts, credits, commitments, or a hybrid base.
5. If discounts are required repeatedly, determine whether list price, segment, or sales discipline is wrong.

Step-by-Step Process

1. Write the ICP, buyer map, and current alternative.
2. Interview five recent wins, five losses, and five retained high-value customers.
3. Quantify value ranges from real cases, not generic ROI claims.
4. When evidence is thin, choose a deliberately provisional first price: keep it comfortably above worst-case variable delivery and support cost, anchor it to a credible fraction of the buyer's conservative value, make identical offers to a small comparable cohort, and revise from paid behavior rather than hypothetical willingness.
5. List candidate value metrics and score alignment, predictability, controllability, auditability, and margin.
6. Choose one simple model and at most three packages.
7. Create price hypotheses by segment and a discount approval rule.
8. Run founder-led asks with real numbers and no hypothetical framing.
9. Track quoted, realized, and renewed price separately.
10. Review conversion, retention, expansion, margin, and objection shifts by cohort.
11. Change one major pricing variable at a time and protect existing-customer trust.

Checklists

Before quoting

• Can the buyer repeat the value?
• Is the metric legible and value-aligned?
• Is the bill predictable enough?
• Does gross margin survive expected usage?
• Is the decision authority known?

Before changing price

• Define affected segment and grandfathering policy.
• Model revenue, margin, contraction, and support scenarios.
• Prepare a plain explanation tied to value.
• Instrument exposure, conversion, expansion, and churn.
• Set a review date and reversal threshold.

Red Flags

• Pricing is copied from competitors without understanding their segment or economics.
• The team debates $49 versus $59 before validating the value metric.
• A free plan attracts users who never experience or pay for the core outcome.
• Usage pricing rewards customers for suppressing valuable usage.
• Outcome pricing depends on disputed attribution.
• Every enterprise deal creates a custom package and permanent discount.
• The team treats every lost deal as price sensitivity.
• Gross margin or billing accuracy is unknown.

Common Mistakes

• Asking what customers would pay instead of making an offer.
• Pricing from delivery cost alone.
• Adding packages before repeated segment differences exist.
• Changing model, metric, package, and price simultaneously.
• Using discounts to avoid diagnosing weak value.
• Ignoring expansion and renewal when evaluating conversion.
• Surprising existing customers or hiding variable charges.

Metrics

• Quoted-to-paid conversion by segment
• Realized price versus list price
• Gross margin by customer and unit
• Logo and revenue retention by price cohort
• Expansion and contraction revenue
• Discount frequency and depth
• Sales-cycle length by package
• Usage distribution and bill variance
• Price-related win/loss reasons
• Support and implementation cost by tier

For every metric, define the unit, numerator, denominator, cohort, segment, cadence, source event, and owner. Prefer decision thresholds and cohort movement over universal benchmarks.

Example Scenarios

Scenario 1

An AI product wants outcome pricing: verify that customers agree on the outcome, can audit it, and trust attribution; otherwise use a hybrid base plus usage metric while learning.

Scenario 2

Enterprise prospects demand 40% discounts: separate procurement ritual from true willingness to pay, standardize give-get trades, and inspect realized price, cycle time, and renewal.

Scenario 3

Self-serve conversion is low after a price increase: compare exposed cohorts, activation, retained conversion, and segment mix before reversing; the issue may be value communication or audience quality.

AI Prompt Templates

Template 1

Design a pricing test from this ICP, value evidence, current alternative, costs, and sales data. Recommend model, metric, packages, initial price, risks, and a 30-day evidence plan.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Template 2

Diagnose these pricing objections. Classify each as value, positioning, authority, budget, trust, predictability, implementation, or true price sensitivity.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Template 3

Model this price change across conversion, usage, realized revenue, gross margin, expansion, contraction, and churn. State assumptions and the reversal threshold.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Related Skills

• founder-talking-to-users
• founder-retention
• founder-distribution
• founder-default-alive
• founder-debugger

Further Reading

1. Startup Pricing 101 — YC's pricing fundamentals, monetization logic, and relationship between price and acquisition motion.
2. How to Price for B2B — A founder-focused method for choosing, testing, and defending B2B prices.
3. YC Guide to Business Models — Examples of how model, pricing, margin, sales motion, and scale fit together.
4. Enterprise Sales for Founders — Maps the enterprise funnel and the founder's role in qualification, evaluation, negotiation, and closing.
5. A Guide to SaaS Pricing and Packaging — Specific tests for value metrics, packaging, model selection, expansion, and predictability.
6. Usage-based Pricing for SaaS — Benefits, failure modes, metering requirements, bill-shock risks, and hybrid alternatives.

Source Links

• Startup Pricing 101 — Kevin Hale. YC's pricing fundamentals, monetization logic, and relationship between price and acquisition motion.
• How to Price for B2B — Tom Blomfield. A founder-focused method for choosing, testing, and defending B2B prices.
• YC Guide to Business Models — Aaron Epstein. Examples of how model, pricing, margin, sales motion, and scale fit together.
• Enterprise Sales for Founders — Pete Koomen. Maps the enterprise funnel and the founder's role in qualification, evaluation, negotiation, and closing.
• A Guide to SaaS Pricing and Packaging — Stripe. Specific tests for value metrics, packaging, model selection, expansion, and predictability.
• Usage-based Pricing for SaaS — Stripe. Benefits, failure modes, metering requirements, bill-shock risks, and hybrid alternatives.
• How We Develop Pricing and Packaging at Fin — Intercom. A concrete research-model-test-operationalize workflow for outcome-based AI pricing.
• Price for Value, Not Cost — Intercom. Why price should track customer value and desired behavior rather than supplier cost.
• Picking a Pricing Strategy for Your Product — Intercom. Relates self-serve, transactional, and enterprise pricing to acquisition and revenue goals.
• How to Get Your First Customers — Gustaf Alströmer. Turns user conversations into first sales through narrow targeting and founder-led outreach.