Good-Better-Best Pricing: The First Principles That Actually Hold

Almost every SaaS founder who has built pricing tiers has done the same thing: opened three or four competitor pricing pages, noted what they charged, and built something that looked roughly similar. It is not irrational. It is fast. But it means your tier structure is built on your competitors' assumptions about buyer behavior, many of which are also wrong.

First-principles pricing starts by asking why three tiers exist at all.

The Financial Exposure

The invisible cost of inherited tier design is that you are optimizing for the wrong outcomes from the beginning.

When you copy a competitor's feature matrix, you adopt their definition of what a "Good" buyer wants versus a "Best" buyer wants. That definition was built for their customer base, their sales motion, and their historical deal data. It is almost certainly wrong for yours.

The most common symptom of misaligned tier design is a distribution problem: too many buyers in the middle tier. In a well-designed three-tier structure, you would expect roughly 20% of revenue in "Good," 45-50% in "Better," and 30-35% in "Best." Most companies have 60-70% of revenue in the middle tier. That is not evidence that the middle tier is the right choice for buyers. It is evidence that the tier boundaries are not creating enough pull toward the top or enough clarity at the bottom to drive self-selection.

Every point of revenue concentration in the middle tier that should be in the top tier represents lost average contract value. For a $25M annual recurring revenue (ARR) business, moving 10% of middle-tier revenue to the top tier is typically worth $800K to $1.2M in incremental ARR at no additional customer acquisition cost.

The Playbook

First-principles tier design follows three questions in sequence.

Step 1: What are the three distinct jobs your buyers hire this product to do? Not features. Jobs. A job is an outcome statement from the buyer's perspective: "I need to reduce time-to-close for my sales team," "I need to provide my leadership team with real-time pipeline visibility," "I need to ensure compliance across 12 jurisdictions." Buyers who hire the product for different jobs have different willingness-to-pay and different support requirements. Those jobs define your tiers.

Step 2: What is the minimum viable feature set to complete each job? Once you have defined three jobs, identify the smallest set of features that actually enables each job to be completed. This is almost always a smaller set than your current tier. Many features in your current "Better" tier are there because a single large customer requested them in year two. They are not structural to the job. They belong in a custom tier or an add-on.

Step 3: What is the economic value of completing each job for a representative buyer? This is the most important step and the one most teams skip. If completing the "Good" job saves a sales team two hours per week, and that team costs $150K per year in fully loaded compensation, the product delivers roughly $7,500 per year in time value per rep. A $2,400 annual price is defensible. A $12,000 annual price requires a different job definition or a different buyer.

The Breakdown

A DevOps SaaS company at $15M ARR had built their tier structure by benchmarking against four competitors. Their "Better" tier at $899/month had 31 features listed on the pricing page. Their "Best" tier at $1,499/month had 47 features. The difference between them was 16 features that had been added over 18 months based on enterprise requests.

Their win rate against their primary competitor was 42% in "Better" and 29% in "Best." Prospects could not articulate why they would choose "Best." Neither could the sales team.

A first-principles audit revealed that their buyers had two distinct jobs, not three: "automate deployments for a single team" and "manage deployments across a multi-team organization with audit requirements." The 47-feature matrix was obscuring a simple two-tier structure with an enterprise add-on for compliance.

After simplifying to two tiers and moving the compliance features to a $400/month add-on, their "Best" equivalent win rate improved to 41% and average contract value increased 28%.

Your Week Ahead

Write down the three jobs your product is hired to do. Not in product language. In buyer language. "Reduce manual reporting time for a revenue operations (RevOps) team" is a job. "Advanced analytics and custom dashboards" is a feature list.

Then check whether your current tiers map to those jobs. If they do not, you are managing a pricing structure built on someone else's customer insight.

Start with the free assessment at assess.fintastiq.com to identify which of your current tiers is most misaligned to buyer jobs. It takes 12 minutes and gives you a prioritized action list.

For more on what happens when first-principles thinking is skipped at the wrong moment, read Before You Scale: SaaS Packaging Prerequisites. For how these principles connect to a testable structure, read A Hypothesis-Led Approach to SaaS Pricing Tiers.