The anchor
Use-case anchor, not price anchor
The Pro tier's $20/user/mo is not designed to look reasonable next to a higher tier. The anchor is the commercial-use restriction on Hobby: any project that earns revenue must upgrade to Pro. This converts the anchor mechanic from a price-comparison nudge into a binary structural requirement, which is more reliable than psychological anchoring.
The upgrade trigger
Commercial-use boundary
The trigger fires the moment a project transitions from hobby to revenue. This is a structural trigger that fires exactly when willingness-to-pay materializes (the project is now generating money) and exactly when continued use on the free tier becomes a TOS violation. Two-sided alignment.
What works
- • Commercial-use boundary as upgrade trigger converts free users at the exact moment they generate revenue.
- • Per-user base plus metered usage scales pricing with customer success, which lowers commitment friction.
- • Hobby tier is generous enough that developers ship real projects on it before committing, which builds product habit.
- • Pro tier price is round and memorable ($20/user/mo) rather than a comparison-shoppable odd number.
- • Custom Enterprise tier hides infrastructure pricing from competitors while serving the largest deals.
- • Usage overages metered per resource (bandwidth, function invocations, builds) so the bill maps to specific product behavior the customer can optimize.
What to copy
- • Use a structural upgrade trigger (commercial use, team formation, scale threshold) rather than a feature gate when possible. Structural triggers fire predictably at value moments.
- • If your product has clear hobby vs commercial use cases, use the boundary as the free-to-paid trigger. The TOS line backs up the price line.
- • Meter usage per specific resource so the customer can optimize their bill, not just absorb it.
What to avoid
- • Do not free commercial use if your competitive position depends on revenue from small commercial users. Hobby-tier free works because Vercel monetizes the moment revenue starts.
- • Do not adopt per-user base plus usage pricing if your customer cannot predict their usage. Bill-shock is the biggest churn driver in usage-billed SaaS.
- • Do not gate features behind tier upgrades if usage metering achieves the same revenue. Feature gates fight the buyer; usage metering aligns with them.
Trial behaviour
Hobby tier IS the trial. The commercial-use restriction is the structural trigger to Pro.
Apply this to your own idea
Run your product through the Pricing Fit Calculator to see where your intended price lands against frontend cloud and hosting benchmarks, then validate whether the market supports it.
Source: unlocksaas.com — indie-saas-teardowns (CC BY 4.0). Pricing page https://vercel.com/pricing. Verified 2026-05-17.