Testing pricing, lifetime deals, and building for your best customers

Executive overview

Most founders lack the traffic volume for true A/B price testing. Pricing changes are calculated bets, not controlled experiments. Lifetime deals undermine the core advantage of SaaS recurring revenue. Retention requires building everything for a specific someone, not something for everyone.

Picking the right ICP and pricing model is more consequential than optimising either once chosen.

Testing pricing in practice

• Low-touch funnel: change the pricing page and track conversion rate over one to four weeks — a "poor person's split test."
• True split testing requires high traffic volume; almost no SaaS companies have it.
• High-touch / demo sales: unpublish pricing, quote higher numbers, and watch for resistance — double the price until you get pushback.
• Existing customers: separate entirely from new-customer testing; only change after high confidence.
• Before any pricing change, consult a co-founder, advisor, or mastermind peer, then factor in gut feel.
• Aspirational pricing — setting a price you want to grow into — can work if you commit to building features that justify it.
• Testing price drops is rare; almost all testing is upward pressure on price elasticity.

Why one-time and lifetime deals are dangerous

• SaaS recurring revenue is the "cheat code" that every other business model wants but doesn't have.
• Lifetime deal customers generate no ongoing revenue but require ongoing server, maintenance, and support costs.
• If lifetime sales stop, you're paying running costs out of old earnings — structurally similar to a Ponzi dynamic.
• Annual recurring revenue is already easy to misread: $6,000 collected in six annual payments looks like $6,000 MRR but is $500 MRR.
• One-time revenue is another order of magnitude more fragile than annual.
• Treat AppSumo / lifetime buyers as freemium users you happened to get paid for once (Ruben Gámez's framing).
• Lifetime deal customers become a liability at acquisition — they must be serviced with no ongoing revenue attached.
• Verdict: not a never, but a strong default against unless you can articulate every ramification.

Acquisition vs retention: choosing your ICP

• Des Traynor's framing: "Having something for everyone gets you acquisition. Having everything for someone gets you retention."
• A horizontal product still requires hard decisions about which use cases to prioritise; you cannot avoid it.
• Identify best customers by lowest churn, lowest price sensitivity, highest value extracted, and referral behaviour.
• Drip example: SaaS founders and bloggers/creators were core ICPs; WordPress plugin developers churned quickly; e-commerce emerged organically at 15% of the base without any marketing to them.
• Bloggers were high-churn and price-sensitive — a warning that a segment's size doesn't make it the right ICP.
• A single tight vertical (e.g., HR reps at construction firms) makes ICP decisions simpler and product decisions easier.
• Once you tap out a vertical's total addressable market, decide: adjacent vertical, second product, horizontal expansion, or price increase.

Making useful recommendations

• A good recommendation includes why the thing is worth the time, not just the name.
• Distinguish universal-appeal works (Shoe Dog, Masters of Doom) from ones that need prior context (Sid Meier memoir, Doom Guy).
• Qualify caveats up front: which third of a book is worth reading, what's dated, and what the core payoff is.
• This framing lets the recipient self-select out if the recommendation doesn't fit their goal.
• Mismatched recommendations (e.g., suggesting Shoe Dog when asked for SaaS marketing tactics) waste the recipient's time and signal you didn't internalise the question.