Account plans
AuraScore 81/100

University Research Account Expansion Framework

Map academic faculty buying centers and grant funding timelines to scale software across research institutions.

Use this template when expanding a departmental pilot into a campus-wide research software license. It aligns procurement milestones with academic grant cycles and faculty stakeholder priorities.

Template

Role: Senior Strategic Account Executive for Research Software Solutions

Context

  • Institution: {{institution_name}}
  • Current Department Sponsor: {{current_department_sponsor}}
  • Target Expansion Faculties: {{target_faculties}}
  • Grant Funding Cycle: {{annual_grant_cycle_dates}}
  • Current Contract Value: {{current_contract_value}}
  • Primary Software Tool: {{primary_research_tool}}

Task

Develop a structured institutional expansion framework to transition {{institution_name}} from a single-department contract into an enterprise-wide research agreement across target faculties.

Method

  1. Audit the baseline usage, seat density, and demonstrated outcomes within {{current_department_sponsor}}.
  2. Identify overlapping research workflows and publication requirements across {{target_faculties}}.
  3. Align contract renewal milestones with {{annual_grant_cycle_dates}} to identify departmental co-funding opportunities.
  4. Map internal champions, faculty deans, and centralized research administration budget holders.
  5. Formulate a multi-tier licensing framework that demonstrates cost efficiencies compared to {{current_contract_value}}.
  6. Define mutual milestones for technical data integration, campus security approval, and faculty onboarding.
  7. Establish a quarterly executive cadence to review inter-departmental research impact and citation velocity.

Constraints

  • MUST prioritize decentralized faculty autonomy alongside central IT governance requirements.
  • MUST NOT propose pricing models that fail to account for multi-grant cost allocation rules.
  • Milestones must anchor directly to {{annual_grant_cycle_dates}}.
  • Keep strategic action tables concise and limited to high-priority deliverables.

Output format

Provide a 4-part structured account framework:

  1. Account Overview & Pilot Baseline (1 paragraph summary)
  2. Faculty Penetration Matrix (Markdown table: Faculty, Research Use Case, Budget Sponsor, Priority Tier)
  3. Grant-Aligned Expansion Roadmap (Chronological milestone list across 4 quarters)
  4. Risk & Governance Mitigation Table (Markdown table: Risk, Impact, Owner, Countermeasure)

Self-review

  • Confirm all 6 context variables are actively integrated into the framework.
  • Verify that the procurement milestones align with the grant calendar.
  • Check that the output format adheres strictly to the 4 requested sections.
AuraScore breakdown
81/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 efficiency7/10 · Adequate

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
research-productivity-operations
research
higher-ed
account-expansion