Verified against ChatGPT · 2026-08-11
Map an account expansion plan from usage data and org chart whitespace
Builds a phased expansion plan for an existing account using actual usage data and known org structure, identifying real whitespace to pursue and in what order, instead of a generic 'grow the account' outline.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build an expansion plan for Corvallis Health Systems based on actual usage data and what we know about their org, not a generic 'ways to grow this account' outline. CURRENT FOOTPRINT AND USAGE DATA Deployed in the scheduling team, 45 active users, high daily engagement. ORG STRUCTURE AND KNOWN STAKEHOLDERS Scheduling reports up to Operations; Clinical Ops is a separate, larger department with its own budget and VP. DEPARTMENTS OR TEAMS NOT YET USING THE PRODUCT Clinical Ops, Billing, and a regional satellite office haven't adopted it. TIMELINE PRESSURE, IF ANY Their next fiscal year budget planning starts in ten weeks, which is the real window to get a new line item considered. PHASE 1 — IDENTIFY REAL WHITESPACE Distinguish between whitespace that's actually reachable (a team with a known internal champion or a clear adjacent use case to current usage) and whitespace that's theoretical (a department that could technically use the product but with no identified path in). Rank only the reachable whitespace for the plan; list theoretical whitespace separately as longer-term and not yet actionable. PHASE 2 — SEQUENCE THE EXPANSION Sequence the reachable expansion targets in the order that makes the most sense given dependencies — for example, expanding within a department that already has a strong champion before cold-approaching a department with no internal advocate, since an internal referral changes the whole approach needed. For each step, name what has to be true before moving to the next one. PHASE 3 — NAME THE RISK OF MOVING TOO FAST If pursuing multiple expansion paths simultaneously risks overwhelming the main point of contact or creating internal confusion about who owns the relationship, say so explicitly and recommend a pace, rather than presenting an aggressive multi-track plan as if speed carries no cost. OUTPUT FORMAT 1. Reachable whitespace, ranked, each with the specific reason it's reachable now. 2. Theoretical whitespace, listed separately, with what would need to change to make it reachable. 3. A sequenced plan with dependencies named at each step. 4. A pacing recommendation addressing the risk of moving on too many fronts at once.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Distinguishing reachable from theoretical whitespace targets a specific weakness in AI-generated account plans: without that constraint, a model given an org chart and a list of unused departments will happily generate an expansion idea for every department, because more coverage looks more thorough, but a plan that treats an unreachable department (no champion, no adjacent use case, no known entry point) with the same weight as a genuinely reachable one produces a list of ideas rather than a plan anyone can actually execute against this quarter. Sequencing by dependency rather than listing targets in isolation reflects how account expansion actually works in practice: an internal referral from an existing champion fundamentally changes the sales motion needed compared to a cold approach into a department with no advocate, so treating both as equivalent next steps ignores the single biggest lever available in expansion selling, which is that an existing relationship inside the account is worth more than any external pitch. The explicit instruction to name the risk of moving on too many fronts at once counters a bias toward generating maximally ambitious plans: a model asked to build an 'expansion plan' will often produce an energetic, parallel-track plan because it reads as more valuable output, but overwhelming a single point of contact with multiple simultaneous asks is a known way to create internal confusion about deal ownership and actually slow expansion down rather than speed it up — naming this tradeoff explicitly keeps the plan honest about pace rather than optimizing for the appearance of ambition.
What you get back
Reachable whitespace: Clinical Ops — the scheduling team lead has a standing relationship with their director and has already mentioned interest informally; this is reachable now via warm introduction. Theoretical whitespace: Billing — no known contact, no clear adjacent use case yet; revisit once a use case or contact emerges. Sequenced plan: first, get the warm introduction to Clinical Ops's director before their fiscal planning window opens in ten weeks; only pursue Billing after Clinical Ops shows initial traction, to avoid running two unproven pitches into the same account simultaneously.
Verified against
ChatGPT GPT-5.1 · 2026-08-11
Changelog
- 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
