Why pricing changes fail without a unit model
Teams raise list prices because competitors did, because a board deck needs a growth story, or because support costs feel high. Those instincts are not wrong, but they are incomplete. A pricing change is really a bet on how acquisition cost, retention, and delivery cost move together. If you do not write that bet down in dollars per customer, you will celebrate a higher average revenue per account while contribution margin shrinks.
Unit economics does not require a full FP&A department. It requires one honest spreadsheet that a founder can explain in five minutes. The goal is not precision to the penny; it is preventing the common failure mode where marketing scales a plan that cannot fund itself after discounts, payment processing, and onboarding labor.
Start with a single “reference customer”: the median new logo in your primary segment last quarter. If mid-market and self-serve behave differently, build two rows—not twelve. Complexity is how unit models die unused.
The five numbers that actually matter
First, net revenue after refunds and contractual credits—not list price. Second, variable cost of serving that customer: hosting attributable to usage, payment fees, third-party APIs billed per seat, and the portion of onboarding that scales with logos. Third, sales and marketing cost to acquire the logo, fully loaded. Fourth, expected gross retention and net retention over twelve months. Fifth, the discount rate or payback threshold your cash position can tolerate.
Contribution margin per customer is net revenue minus variable delivery cost. CAC payback in months is CAC divided by monthly contribution. If payback stretches past your runway comfort—often twelve to eighteen months for bootstrapped teams, shorter if you are cash-tight—raising price only helps if it improves contribution faster than it hurts conversion and retention.
Stress-test the pricing experiment before you ship it
Model three scenarios on the same reference customer: base case, optimistic conversion with mild churn increase, and pessimistic conversion with a larger churn bump. Keep feature packaging fixed so you isolate price. Then model a packaging change separately. Mixing both variables in one launch makes the post-mortem impossible.
Watch the traps that fake good unit economics. Annual prepay improves cash but can hide churn until renewal. Usage minimums look efficient until power users leave. Seat-based pricing that ignores inactive seats inflates ARPU while damaging trust. Put those effects as explicit assumptions, not vibes.
- Discount leakage: Apply your real average discount, not list.
- Support load: If higher tiers include chat SLAs, allocate that labor.
- Expansion: Net retention above 100% can justify longer payback—document why.
- Segment mix: A price that works for enterprise can break self-serve unit math.
Operating cadence that keeps the model honest
Review unit economics monthly with the same definitions. When CAC spikes, ask whether creative fatigue, channel mix, or sales cycle length moved. When churn rises after a price change, split involuntary failures from voluntary cancels. Tie product roadmap items to contribution: reducing onboarding hours or API cost is as real as a price hike.
Before you announce new pricing, write a one-page decision memo: expected lift in contribution, expected conversion hit, kill criteria after thirty and ninety days, and the rollback plan. Share it with sales so discount policy stays aligned. A pricing page that looks “premium” is worthless if reps immediately unwind the change with quiet exceptions.
Good unit economics are boring on purpose. They turn pricing from a branding exercise into a cash-flow experiment you can measure. Do the worksheet first; then change the page.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.
Write the decision criteria down before launch day so the team cannot silently unwind the plan under sales pressure.