Design an account-management operating system for my team that is specific enough to run weekly and fair enough to apply consistently. Build it from the facts I provide; do not invent capacity, revenue, customer commitments, performance issues, or tooling capabilities. Business and customer model: [BUSINESS CONTEXT] Account portfolio: [PORTFOLIO DATA] Team structure and capacity: [TEAM STRUCTURE] Customer lifecycle and commitments: [LIFECYCLE AND COMMITMENTS] Current problems and constraints: [CURRENT PROBLEMS] Systems and available data: [TOOLS AND DATA] Produce a management system with these sections: 1. Segmentation and coverage: define account tiers using transparent criteria such as ARR, renewal date, adoption risk, strategic value, and complexity. State the service motion and contact cadence for each tier, plus exceptions and an appeal path. 2. Ownership and handoffs: create a RACI for sales, account management, customer success, support, finance, and leadership. Define trigger points for implementation, escalations, renewals, expansion, payment issues, and executive involvement. 3. Weekly operating rhythm: provide a 30-minute portfolio review agenda, a risk-review agenda, required fields, and a decision log format with owner and due date. 4. Account plan template: include goals, stakeholder map, success measures, adoption signals, risks, next meeting, mutual action plan, and renewal plan. 5. Metrics and guardrails: distinguish leading indicators from lagging outcomes; include coverage, health-data completeness, time-to-first-risk-response, renewal forecast accuracy, retention, and expansion. Explain what each metric should not be used to judge. 6. First 30 days: give a sequenced rollout plan and adoption checks. Before answering, check that every tier has an objective rule, a defined service level, and no hidden reliance on subjective “relationship quality.” Also flag conflicts between proposed cadences and the team capacity provided. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [BUSINESS CONTEXT] | Describe your product, sales motion, contract model, and customer outcomes. | B2B analytics SaaS sold on annual contracts to mid-market operations teams; customers value faster weekly reporting. |
| [PORTFOLIO DATA] | Summarize account count, revenue bands, renewal timing, segments, and known risk patterns. | 180 accounts, ARR from $8k to $120k, 46 renew in the next 120 days, and 18 have declining weekly active users. |
| [TEAM STRUCTURE] | List roles, headcount, geographic coverage, and realistic account capacity. | Three account managers, one CSM, shared support, and one sales director; each AM can actively manage about 55 accounts. |
| [LIFECYCLE AND COMMITMENTS] | Describe onboarding, support, QBR, renewal, and service commitments already made to customers. | 30-day onboarding, email support for all tiers, quarterly business reviews for enterprise plans, renewals begin 120 days before term end. |
| [CURRENT PROBLEMS] | List the operational failures, fairness concerns, or growth constraints the system must address. | Renewal risks are found late, sales promises are not documented, and small accounts receive inconsistent attention. |
| [TOOLS AND DATA] | Name the CRM, support, product-usage, billing, and reporting data your team can actually access. | HubSpot, Zendesk, Stripe, and weekly product-usage exports; no automated health-score platform. |
How to use
- Bring a simple portfolio export with account count, revenue, renewal date, adoption signals, and assigned owner.
- Paste the prompt with current capacity and commitments so the proposed coverage model can be tested against reality.
- Check the tier rules on a small sample of accounts to make sure two managers would classify them the same way.
- Follow up with: “Convert this into a one-page weekly operating review template for our existing HubSpot fields.”
Variations
Renewal risk system
Use this when renewals are slipping because risks surface too late.
Create a renewal-risk system for [PORTFOLIO] using [AVAILABLE SIGNALS] and [RENEWAL TIMELINE]. Define objective risk triggers, severity levels, required evidence, owner, response deadline, and escalation path. Build a 120/90/60/30-day renewal workflow with customer-facing milestones and internal forecast rules. Include a risk register template and metrics for early detection and resolution. Do not label customers “at risk” from intuition alone; flag signals unavailable in [TOOLS].
Change management system
Use this when a new process, tool, or operating model affects a team.
Design a fair change-management system for [CHANGE] affecting [AFFECTED GROUPS] by [TARGET DATE]. Use [CURRENT WORKFLOW], [KNOWN CONSTRAINTS], and [SUCCESS MEASURES]. Produce stakeholder impacts, decision rights, communications by audience, training, pilot criteria, feedback channels, adoption measures, and rollback triggers. Include a weekly decision log with owner and due date. Do not claim buy-in exists without evidence or use adoption metrics as a proxy for individual performance without context.
Executive account plan
Use this for a strategic customer that needs coordinated leadership attention.
Create an executive account plan for [ACCOUNT] based on [ACCOUNT FACTS], [STAKEHOLDERS], [CONTRACT AND RENEWAL], and [OPEN RISKS]. Produce a one-page brief with customer objectives, our value evidence, stakeholder map, relationship gaps, mutual actions, commercial milestones, risks, and asks of executives. Separate verified facts from assumptions and include questions to validate before an executive meeting. Do not invent customer priorities, expansion opportunities, or relationship strength.
Tips
- Segment accounts with rules that can be applied from available CRM and product data, then document how exceptions are approved.
- Start renewal work from the customer’s success evidence and decision process, not only the contract end date.
- Separate health signals from account-manager performance: low usage may reflect implementation delays, product fit, or a customer-side event.
- Give every escalation an owner, a response deadline, and a decision record; vague “visibility” is not an operating mechanism.
FAQ
How many account tiers should we use?
Usually two to four tiers are enough. More tiers can create false precision and make coverage rules difficult to operate consistently.
Should account management own renewals?
It depends on your sales motion, but ownership and handoffs should be explicit. The system should define who runs the customer conversation, pricing approval, forecast, and contract process.
Can AI create a health score for us?
It can propose a draft model from your available signals, but validate it against actual retention outcomes before using it for coverage or forecasting decisions.