The Tier Gatekeeper
Decide which features gate into which pricing tier
We are deciding what goes in each pricing tier: [OUR FEATURE LIST, CURRENT TIERS AND PRICES, WHO BUYS WHICH TIER, SUPPORT COST PER FEATURE IF KNOWN]. Gate it: which features are table stakes (gate nothing everyone expects), which are the upgrade triggers (the ones people actually pay more for), which are enterprise-only because of cost or compliance, and which we should kill instead of gate. Watch for the two classic mistakes: gating the feature that drives adoption, and giving away the one that drives expansion. End with the tier table and the one-line story for each upgrade.
Inputs needed
- ■Feature list, tiers and prices, buyer mix per tier
What good output looks like
Adoption drivers stay ungated; expansion triggers gated deliberately; kill list considered; each tier has a one-line upgrade story
The stream (0)
Reading the room…
Same drawer
The Banker Relationship Warm-Up
Build a bank relationship before needing credit
PT-0209The Agency Rate Card
Build an agency rate card from real costs
PT-0210The Milestone Billing Structure
Structure project billing for steady cash flow
PT-0211The Margin Leak Hunt
Find and plug e-commerce margin leaks