Account plans
AuraScore 79/100

Enterprise Client Expansion Architecture

Formulate a multi-practice cross-sell growth specification for an established professional services client.

Use this specification when an existing enterprise client relationship is concentrated in a single practice area and needs a structured multi-year expansion blueprint. It guides client partners in mapping cross-practice opportunities, executive buying centers, and commercial packaging.

Template

Role: Senior Managing Director & Global Client Partner in professional services.

Context

  • Target account: {{client_name}}
  • Current anchoring practice area: {{current_practice_area}}
  • Target cross-sell practice areas: {{target_expansion_practices}}
  • Current annual contract value: {{annual_contract_value}}
  • Executive sponsor network: {{key_executive_sponsors}}
  • Incumbent competitors across adjacent domains: {{competitive_incumbents}}

Task

Develop a comprehensive account expansion specification that establishes a multi-year growth trajectory, mapping cross-practice professional services offerings to strategic client priorities while dislodging entrenched incumbent competitors.

Method

  1. Analyze current relationship capital, delivery performance, and revenue baseline within {{current_practice_area}} at {{client_name}}.
  2. Map strategic enterprise imperatives across unserved business units against capabilities in {{target_expansion_practices}}.
  3. Profile decision-making dynamics, personal incentives, and relationship strength for {{key_executive_sponsors}} and adjacent budget holders.
  4. Evaluate competitive positioning against {{competitive_incumbents}}, identifying service gaps, delivery blind spots, and pricing vulnerabilities.
  5. Design distinct multi-practice value propositions that bundle cross-functional advisory, technical delivery, and managed services.
  6. Structure commercial engagement pathways including pilot propositions, gain-share models, and enterprise master services agreement revisions.
  7. Establish a multi-quarter pursuit roadmap detailing relationship development cadences, thought leadership seeding, and proposal milestones.
  8. Formulate account governance protocols including partner-level sponsorship, executive steering cadences, and early warning health indicators.

Constraints

  • MUST anchor all cross-practice proposals directly to measurable business outcomes for {{client_name}}.
  • MUST NOT propose generic service catalogs; every solution module must reflect the specific context of {{current_practice_area}}.
  • Prioritize opportunities that protect and elevate current {{annual_contract_value}} margins.
  • Include explicit displacement plays for each identified entity in {{competitive_incumbents}}.

Output format

  1. Executive Growth Hypothesis (max 250 words)
  2. Stakeholder & Buying Center Grid (markdown table: Stakeholder, Domain, Engagement Strategy, Sponsor Alignment)
  3. Cross-Practice Opportunity Architecture (3 detailed modular initiatives with projected value)
  4. Competitive Displacement Playbook (tactics targeted at {{competitive_incumbents}})
  5. 12-Month Pursuit & Governance Milestones (quarterly breakdown)

Self-review

  • Confirm all 6 context variables are deeply integrated into the expansion mechanics.
  • Verify that commercial pathways account for the baseline {{annual_contract_value}}.
  • Ensure clear differentiation between anchoring work in {{current_practice_area}} and new offerings.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-account-plans
professional-services
account-growth
cross-sell
enterprise-sales