Lenss to verify pricing

Verify a pricing change before customers verify it for you.

Usage-based transitions, tier redesigns and discounting, checked against how your customers actually use the product.

Works on: Pricing memos · Packaging and tier redesigns · Usage-based billing proposals

How the audit runs

  1. 01

    Pin the revenue goal

    What the change must hold or grow, and for which customers.

  2. 02

    Quote the typical-customer claim

    The sentence that stands one customer in for the whole base.

  3. 03

    Apply the distribution you state

    Your own figures on usage concentration, applied to every segment, not the median.

  4. 04

    Compute the neutral price

    The price point at which revenue holds, and who pays the difference.

Typical findings

Skewed usage

A median that hides the accounts carrying most of the usage.

Bill shock

The segment whose bill multiplies at a forced renewal.

Cannibalisation

A new tier that moves revenue down instead of customers up.

Worked example

Stakes$147,000 MRR · 3,000 accountsAdversarial Review · 3/4

Source draft

467 chars

Memo: moving from flat $49 to usage-based pricing

Head of Growth · for exec review

Today. 3,000 customers pay a flat $49 per month, which is $147,000 MRR. Customers make 3.6 million API calls per month in total, and the top 10% of customers make 70% of all calls. Proposal. Replace the flat plan with a $19 platform fee plus $0.02 per API call. The typical customer makes 1,500 calls a month (median of our top 500 accounts), so the typical bill stays at $49 and revenue holds. Rollout. Migrate every account at the next renewal. No grandfathering.

Adversarial review

pinned · quoted · computed
01

Pinned objective

Move to usage pricing without losing revenue or the accounts that carry it.

Underneath: Revenue is set by total calls across all 3,000 accounts, not by a typical one.

02

Hidden assumption

The top-500 median stands for every customer. MRR is the platform fee times all accounts plus the price per call times all calls, and the memo states both totals.

“The typical customer makes 1,500 calls a month (median of our top 500 accounts), so the typical bill stays at $49 and revenue holds.”
verbatim · highlighted in source

If it’s wrong: MRR falls 12.2% on day one, while bills for the top 10%, who make 70% of calls, rise from $49 to $187 at a forced renewal.

03

Flip threshold

Price per call at which MRR holds at $147,000

$0.025memo proposes $0.020
Figures behind the threshold
Platform fees: 3,000 × $19$57,000
Usage at $0.02 × 3.6M calls$72,000
New MRR vs $147,000 today$129,000 (−12.2%)
Top-10% bill: 8,400 calls avg$49 → $187

At $0.02 the memo cuts revenue by $18,000 a month before any churn, and concentrates the increase on the accounts that matter most.

Cheapest test: Re-price last month's actual invoices under the new model, account by account, and read the top-300 bills before the exec review.

Used most by Product managers · Founders & growth

Audit your own draft now.

Paste up to 24,000 characters. You get the objective, every quoted assumption, the tensions, the flip threshold and a hardened rewrite.

Audit your draft