Build a Value-Metric-Based Tier Structure
Objective: Given a new product module and its customer usage data, choose a value metric and build a 3-tier pricing architecture with a clear upgrade trigger for each tier.
You're the product marketer at an email-marketing SaaS company launching 'Automation Studio,' a new workflow-builder module. Leadership wants a pricing recommendation before the module ships.
Given usage data for three customer segments, pick a value metric that scales with customer success, then design Starter/Pro/Enterprise tiers with genuine upgrade triggers, not artificial limits.
Before you start
What you'll need
Free path (everything below is enough to finish)
No account friction, easy to share with leadership for sign-off
The process
2 steps
Step 01 of 02
A value metric is the unit your customer's success scales with, and it is the ideal basis for pricing. Bad value metrics (storage, project count) don't correlate with the outcome the customer is buying.
Automation Studio usage data shows: Segment A runs 40 workflows/month with 3 team members, Segment B runs 200 workflows/month with 3 team members, Segment C runs 40 workflows/month with 15 team members. Seats or workflows run, which value metric actually tracks value delivered?
Procedure
- List the three segments with their workflow-run count and seat count in a Google Sheet
- For each segment, write one sentence describing what 'more value' looks like for that customer
- Circle the metric (seats or workflow runs) that increases in both sentences, not just one
Segment A: 40 runs, 3 seats -> value = automations working Segment B: 200 runs, 3 seats -> value = automations working (seats flat, runs 5x) Segment C: 40 runs, 15 seats -> value = team adoption, not automation depth Decision: workflow runs tracks the module's actual outcome; seats alone would undercharge Segment B and overcharge Segment C.
Healthy
The chosen metric increases for both Segment B (heavy automation, few seats) and any future heavy-usage account, meaning price scales with delivered value in both directions.
Unhealthy
Picking seats as the value metric would charge Segment C 5x more than Segment B despite Segment B extracting far more automation value, an inversion the tier structure would have to work around later.
What this means
When a candidate value metric doesn't move for a customer who is clearly getting more value, it's the wrong metric no matter how easy it is to bill.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A heavy-usage, low-seat account is paying the same as a light-usage account with the same seat count | Re-run the value-metric test on the current pricing model before the next renewal cycle | 30 min |
Step 02 of 02
Most B2B SaaS products converge on three tiers exploiting anchoring and the compromise effect. The starter tier must deliver genuine value; the trigger to upgrade must feel like natural growth, not a wall.
Using workflow runs as the value metric, where do you set the Starter cap so it lets a real small team succeed, but still creates a natural upgrade trigger once they're getting value?
Procedure
- Create three rows: Starter, Pro, Enterprise
- Set a workflow-run cap for Starter that covers Segment A's 40 runs but not Segment B's 200
- Write the specific upgrade trigger for each tier boundary (e.g. 'hits run cap 2 months in a row')
- List one feature reserved for Enterprise only, and justify it as a genuine enterprise need (SSO, SLA, audit log), not an artificial limit
Starter: up to 50 runs/mo, 3 seats — trigger: 2 consecutive months over cap Pro: up to 500 runs/mo, unlimited seats — trigger: needs SSO or audit log Enterprise: unlimited runs, SSO + audit log + SLA — custom pricing
Healthy
Segment A stays comfortably on Starter and Segment B naturally trips the Pro trigger within its first month, both without feeling penalized for normal usage.
Unhealthy
Setting the Starter cap at 30 runs would push Segment A into an upgrade before they've even seen the module deliver value, creating churn risk before adoption.
What this means
A tier boundary set below the value a healthy small customer naturally generates functions as a wall, not a trigger, and reads as bait-and-switch.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| New customers hit the tier cap in their first two weeks, before onboarding is even complete | Raise the Starter cap or delay when the cap starts counting until after a 14-day onboarding window | 5 min |
Final deliverable
A one-page pricing sheet: the chosen value metric with justification, a 3-tier grid (limits, price anchor, features), and the specific upgrade trigger for each tier boundary.
See a reference example
Chewy Autoship Business Tools, tier proposal (excerpt) Value metric: active pet profiles managed (not seats) Starter: up to 25 profiles, 2 seats — trigger: 2 months over cap Pro: up to 250 profiles, unlimited seats — trigger: needs reorder automation Enterprise: unlimited profiles, SLA + dedicated rep — custom pricing
Success criteria
You're done when you can:
- Value metric is justified against at least two customer segments' actual usage
- Each tier boundary has a named upgrade trigger, not just a number
- Enterprise gating is tied to a genuine enterprise need, not an arbitrary limit