Account plans
AuraScore 81/100

Municipal Agency Cross-Department Expansion Plan

Build a structured SLED account plan to expand technology or service footprint across municipal departments ahead of budget cutoff.

Use this template when planning expansion within an existing state, local, or municipal government account. It aligns cross-departmental stakeholder priorities with strict public sector procurement calendars and funding mechanisms.

Template

Role: Senior Public Sector Key Account Director specializing in state and local government (SLED) technology growth.

Context

  • Target Public Entity: {{agency_name}}
  • Existing Footprint & Scope: {{current_contract_scope}}
  • Budgetary & Fiscal Schedule: {{fiscal_year_cycle}}
  • Expansion Target Departments: {{target_departments}}
  • Qualified Procurement Channels: {{procurement_vehicle}}
  • Grant & Public Funding Levers: {{funding_sources}}

Task

Develop a comprehensive multi-department account growth plan that outlines strategic priorities, department-specific value cases, procurement vehicles, and a phased execution roadmap to secure contract expansion before the fiscal year deadline.

Method

  1. Analyze the institutional priorities and stated public mandates of {{agency_name}} across the targeted departments.
  2. Audit current performance and adoption metrics in {{current_contract_scope}} to establish referenceable internal proof points.
  3. Map key buyer personas, elected officials, and civil service department heads within {{target_departments}}.
  4. Align target department initiatives with available funding allocations under {{funding_sources}}.
  5. Select the lowest-friction procurement pathway utilizing {{procurement_vehicle}} to avoid procurement delays.
  6. Sequence relationship-building and committee briefings against the critical milestones in {{fiscal_year_cycle}}.
  7. Detail specific multi-department business cases showing shared operational efficiencies and cost avoidance.
  8. Formulate a risk mitigation matrix addressing election cycles, public scrutiny, and compliance requirements.

Constraints

  • MUST align all engagement milestones explicitly to {{fiscal_year_cycle}}.
  • MUST utilize solely compliant purchasing routes defined in {{procurement_vehicle}}.
  • MUST NOT recommend sole-source approaches unless legally justified within SLED guidelines.
  • Do not include speculative cost numbers; restrict financials to structural budget allocation percentages.
  • Keep department value narratives focused on civic impact, citizen service levels, and inter-agency collaboration.

Output format

Provide the plan across four structured sections:

  1. Executive Context & Baseline Audit (max 200 words)
  2. Inter-Department Stakeholder & Funding Matrix (table: Department, Key Sponsor, Funding Lever, Strategic Driver)
  3. Procurement & Vehicle Strategy (bulleted tactical steps)
  4. 90-Day Fiscal Alignment Action Plan (chronological table with Week, Action, Owner, and Milestones)

Self-review

  • Verify that every department in {{target_departments}} is mapped to a funding source in {{funding_sources}}.
  • Ensure all timeline gates correlate directly with {{fiscal_year_cycle}} deadlines.
  • Check that compliance with {{procurement_vehicle}} terms is rigorously preserved.
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 engineering12/12 · Strong

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
public-sector-nonprofit
sled
public sector
government sales