Product Line Pricing in SaaS: Ladders, Meters, and Second Products
Priced well, the product line does the selling; priced badly, your products compete with each other. The four patterns from our founder interviews, the design steps, and the signals the line is working.
On this page
Product line pricing is the discipline of pricing a family of products so the family sells more than the products would alone. In SaaS it shows up as the good–better–best ladder, the usage meter layered on the subscription, the free tier that feeds the paid one, and the second product that monetizes the install base the first one built. Priced well, the line does the selling; priced badly, your own products compete with each other.
The four patterns that recur in our interviews
Three to four tiers, each anchored by the one above it. The top tier’s job is partly to sell itself and partly to make the middle tier look reasonable — price anchoring, working quietly.
A usage or transaction meter on top of the seat subscription. Webflow layered hosting onto design subscriptions — and let freelancers resell it — so revenue scaled with customers’ success, not just their seats.
A base product priced to land, with the margin in what it makes necessary. Cloudbeds described the sequence explicitly: property software first, then payments, then the transaction layer — each product priced to make the next one natural.
Build the software business, then sell a second product to the audience it aggregates. beehiiv shipped newsletter SaaS first and an ad network second — the deliberate order, because the ads are worthless without the audience the SaaS accumulated.
Designing the line
- Price the metric before the tiers. Pick the unit that grows when the customer wins — user records, properties, subscribers, seats — and let every product in the line share it. Misaligned meters are why customers downgrade.
- Give every tier one reason to exist. Each step up should unlock a named capability a specific segment needs, not “more of everything.” A tier nobody upgrades into is a discount waiting to be negotiated.
- Set floors, not just prices. Owner.com prices with explicit revenue floors that step up as restaurants grow — a ladder built into a single product’s meter. Floors protect the unit economics the ladder was designed around.
- Let the flagship carry the commodity. When one product in the line is truly differentiated, bundle deliberately: the equity of the strong product lifts the commoditized ones — the exact logic Numerator’s CEO gave for unifying twelve acquired products under one sales force.
The cannibalization test: before shipping a new tier or product, name the customer who will pay less because it exists. If you can’t, you haven’t looked. Sometimes the answer is acceptable — a cheap tier that catches customers who’d otherwise churn to a rival is defense, not loss. But it should be a decision, not a surprise.
The signals it’s working
- Expansion looks organic — net revenue retention above 110% without discount-driven upsell pushes, because the meter and the tiers absorb customer growth on their own.
- ARPU rises inside cohorts — average revenue per user climbing within a signed cohort means the line is monetizing success, not just acquisition.
- Sales stops improvising — when reps quote the list instead of building custom bundles per deal, the line’s logic is doing the negotiation.
Product line pricing is where pricing strategy stops being a launch decision and becomes an architecture: the meter, the ladder, and the product sequence are harder to change than any individual price. Design the line first; the price points are the easy part.
SourcesFounder-described pricing structures from Nathan’s interviews with Webflow, Cloudbeds, beehiiv, Owner.com and Numerator, as published in the GetLatka archive.