다운그레이드를 막는 가치 울타리가 있는 가격 티어

Role: You are a pricing strategist who has restructured plans and tiers for 30 software and service companies with revenue between 200,000 and 30 million dollars, and has seen more revenue lost to leaky fences than to prices set too high.
Context: We sell [productService] to [targetMarket]; our core promise is [valueProposition]. What we know about our segments, their usage and what they pay today: [segmentNotes]. Current pricing: [currentPricing]. The owner will redesign the pricing page next month and must defend each price in one sentence.
Task: Design three tiers with a value metric, price points and fences, where each fence is a capability a larger customer needs and a smaller one does not, so customers self-select upward instead of downgrading.
Inputs:
- [productService], [targetMarket], [valueProposition]: what we sell, to whom, and the value it creates.
- [segmentNotes]: the customer groups we see, their size, usage and willingness to pay. If only one segment is described, propose two more from typical patterns in this market, labeled as hypotheses.
- [currentPricing]: current plans and prices, or "none yet". Anchor the middle tier on it unless the notes show it is clearly wrong.
Constraints:
- Pick one value metric (seats, usage, outcomes) and justify it in two sentences; prices scale with it.
- Exactly three tiers; the middle one is designed to be chosen by 50 to 60 percent of customers.
- Each fence reflects a real need of the next segment up, not an artificial limit; name its type (feature, usage, service, or who may use it).
- State the anchoring logic and expected revenue mix in plain numbers, labeled as estimates.
- Before answering, check that no feature in a lower tier makes the next tier unnecessary for its target segment.
Output format:
1. Value metric: two sentences on the metric and why it tracks value.
2. Tier table with exactly 3 rows and these columns: Tier name, Price and billing unit, Built for, Included, Fenced out, Why they upgrade.
3. Fences: a table with exactly 4 rows and these columns: Fence, Type, Separates which tiers, Customer need it reflects.
4. Who buys what: a table with 3 rows and these columns: Segment, Tier chosen, Why, Estimated share.
5. Risks: a bullet list of 3 ways this could backfire and the signal to watch.
6. Next step: one sentence on what to test with 5 customers before publishing.