Decide Which Customers Get a Human and Which Get a Playbook
Designs a coverage model that matches service level to account value, so your team stops giving every customer the same attention regardless of return. Use it when the team is stretched across too many accounts.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a customer success operations lead. Design a coverage model for my base.
Customers: {{count_and_value_distribution}}
Team: {{how_many_people_and_their_time}}
Current approach: {{how_accounts_are_assigned_now}}
Product complexity: {{self_explanatory_or_needs_help}}
Average contract value and spread: {{acv_range}}
Part 1 — The economics first.
- Cost to serve per account at the current model: fully loaded team cost divided across the base
- That cost as a share of contract value, by segment. The number that matters is where cost to serve exceeds a defensible share of revenue — say what you would consider defensible for a business like mine and why.
- The implicit subsidy: which accounts are currently being served at a loss, and who is paying for it. Usually it is the large accounts, which are consequently under-served — the exact inversion of what you want.
Part 2 — Segment by what actually predicts the return on attention, not by revenue alone:
- Current value, but also growth potential — a small account in a growing company can outrank a large static one
- Complexity of what they bought, and how much help it genuinely needs
- Strategic value: reference-ability, logo, market presence, product feedback
- Risk: what a loss would cost beyond the revenue
Part 3 — Define the tiers concretely enough to staff against. For each: named owner or pooled, contact cadence, what is proactive versus reactive, response time, what they get (QBRs, success plan, health monitoring), and roughly how many accounts one person can carry. Give me a realistic ratio and say what drives it.
Typically: high-touch named ownership at the top, a pooled or shared model in the middle, and a product-and-content-led motion at the bottom — but derive the cut lines from my numbers, not from convention.
Part 4 — Make the low-touch tier genuinely work, because this is where these models fail. Low-touch cannot mean neglected — it means the same outcomes delivered without a person: onboarding built into the product, triggered outreach on health signals, self-serve content, community, and a real path to reach a human when it matters. Tell me what has to exist before I can move accounts down a tier, and what it costs to build.
Part 5 — The transition.
- How to move an account to a lower tier without it reading as abandonment. Give me the actual wording.
- The exceptions worth making, and who approves them, so the model does not erode within a quarter
- What to measure to know whether it worked: retention by tier, cost to serve, and coverage of the accounts that matter