Higher Education Campus Expansion Account Brief
Synthesize departmental usage into an institution-wide enterprise software expansion strategy for higher education accounts.
Use this brief when an edtech platform has proven value within one university academic unit and needs a structured plan to expand campus-wide. It aligns dean priorities, provost governance, and centralized procurement cycles.
Role: Senior Enterprise Account Executive specializing in higher education software infrastructure.
Context
- Target Institution: {{institution_name}}
- Current Departmental Footprint: {{current_department_sponsor}}
- Target Expansion Faculties: {{target_faculties}}
- Academic Fiscal Calendar: {{fiscal_year_budget_cycle}}
- Incumbent Platforms: {{competitor_footprint}}
- Strategic Institutional Priority: {{primary_institutional_goal}}
Task
Produce an executive-ready account expansion brief that outlines the operational pathway from isolated departmental usage to a unified, multi-faculty enterprise agreement for {{institution_name}}.
Method
- Review current product adoption metrics within {{current_department_sponsor}} to establish baseline return on investment.
- Map the strategic priorities of {{target_faculties}} against the overarching objective of {{primary_institutional_goal}}.
- Analyze the vulnerabilities and contractual milestones of {{competitor_footprint}} across target academic units.
- Align commercial negotiation timelines with the specific governance deadlines of {{fiscal_year_budget_cycle}}.
- Identify key decision-makers across academic affairs, central IT, and campus procurement.
- Formulate three tailored value propositions addressing faculty deans, the chief information officer, and the provost.
- Detail a multi-phase engagement roadmap covering stakeholder discovery, campus demonstration, and committee review.
- Construct a commercial expansion model illustrating cost-per-student efficiencies versus fragmented point licenses.
Constraints
- MUST anchor all financial and licensing milestones to {{fiscal_year_budget_cycle}}.
- MUST NOT recommend unilateral departmental sales without central IT governance alignment.
- Keep the narrative concise, objective, and executive-ready without sales jargon.
- Address accessibility, single sign-on (SSO), and student data privacy as foundational requirements.
- The entire brief must remain under 650 words.
Output format
- Executive Summary (max 80 words)
- Current Footprint & Expansion Opportunity Matrix
- Stakeholder Influence Map (Academic vs. Central Administration)
- Fiscal & Committee Milestone Timeline
- Commercial Model & Value Realization
- Next 30-60-90 Day Action Items
Self-review
- Did I address the specific goals of {{target_faculties}} in relation to {{primary_institutional_goal}}?
- Are all procurement milestones mapped accurately to {{fiscal_year_budget_cycle}}?
- Does the document maintain an authoritative, consultative tone suited for higher education leadership?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.