Budget Builder and Narrative

A budget without a rationale is just a wish list that gets cut arbitrarily. This skill structures a budget and, crucially, writes the narrative that explains the assumptions behind each line, so the budget is defensible, understood, and more likely to survive review. The narrative is what turns numbers into a plan stakeholders buy into.

1. The period and scope (whole company, department, project).
2. The revenue or funding assumptions.
3. The cost drivers and planned spend by category.
4. Prior actuals, for grounding.
5. The strategic priorities the budget should fund.

1. Anchor to priorities

A budget is strategy expressed in dollars. Tie spend to the priorities it funds, so reviewers see what each line buys, not just what it costs.

2. Make assumptions explicit

Every significant line rests on an assumption (headcount, growth rate, unit cost, timing). State them, because a budget is only as credible as its stated assumptions, and unstated ones invite suspicion.

3. Ground in history where possible

Compare to prior actuals and explain material changes, so the numbers feel evidence-based rather than pulled from air.

4. Build in reality

Flag where estimates are uncertain and where contingency is prudent, rather than presenting false precision.

5. Write the narrative per section

For each major category, a short rationale: what it funds, the key assumption, and why the amount. This is the defensible core.

ALWAYS use:

# Budget: [Scope] | [Period]
## Overview (what this budget funds, top-line totals)
## Revenue / funding assumptions
## Expense plan by category (category | amount | vs prior | key assumption)
## Narrative by section (rationale for each major line)
## Key assumptions summary
## Contingency and areas of uncertainty

• Numbers with no stated assumptions.
• No comparison to prior actuals.
• False precision that hides real uncertainty.
• Spend disconnected from any priority.

This structures figures and assumptions the user provides; it is not financial advice. Never invent figures or assumptions; use placeholders for anything missing and flag it. The user is responsible for the accuracy of the underlying numbers.

A department budget ties each line to a priority, states the headcount and unit-cost assumptions behind the largest categories, compares to last year with explanations for the increases, and flags one uncertain vendor cost with a contingency.