agentleFS
poorvith-mppoorvith-mp/skills-finance/skills/budgeting/SKILL.md

budgeting

Skill1 starsChanged 3 months agoMITView on GitHub

Build the budget, run rolling forecasts, and explain budget-versus-actual variance and expense anomalies. Use when creating annual operating budgets, departmental spend, or variance.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never budget revenue without tying it to pipeline conversion rates and sales headcount productivity caps.

    line 45
  2. Distinctive:

    Every new full-time headcount addition must have an assigned requisition ID and fully-loaded financial model approval.

    line 46
  3. Distinctive:

    NEVER create an annual budget that remains untouched for 12 months despite material market shifts.

    line 57
  4. Distinctive:

    NEVER rely on straight-line revenue growth assumptions without accounting for sales rep ramp time (typically 3–6 months).

    line 58
  5. Distinctive:

    NEVER treat projected cost savings from unhired roles as permanent financial buffer.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Budgeting

Budgeting is resource allocation against strategic hypotheses, not an accounting compliance exercise. Operating budgets must establish departmental spend envelopes, forecast cash runway under variable revenue trajectories, and institute rolling 4+8 and 9+3 variance reviews to catch expense anomalies before they threaten liquidity.

1. Operating Budget Architecture

Deconstruct company expenses into three structural layers:

  • Headcount Costs (typically 70%–80% of tech OpEx): Model fully-loaded payroll (base salary + employer payroll taxes + healthcare + 401(k) match + hardware/SaaS seat stipends). Use a 1.20x–1.25x multiplier on base salaries.
  • Direct Variable COGS: Cloud compute, database storage, payment processing, third-party API token costs. Model directly as a percentage of revenue or active user volume.
  • Fixed & Discretionary OpEx: Office rent, legal/accounting retainers, travel and entertainment (T&E), software tooling.

2. Rolling Forecast Models (4+8, 9+3)

Static annual budgets become obsolete within 90 days. Implement rolling forecasts:

  • 4+8 Forecast: 4 months of closed historical actuals + 8 months of updated forward projections.
  • Scenario Sensitivities:
    • Base Case: Budgeted target revenue growth (e.g. +40% YoY).
    • Conservative Case: Flat net new bookings; headcount freeze; extends runway by 6 months.
    • Downside / Stress Test Case: 20% revenue contraction; immediate elimination of discretionary spend.

3. Budget-vs-Actual (BVA) Variance Analysis

Review departmental performance on the 10th of every month: $$\text{Variance (%)} = \frac{\text{Actual Spend} - \text{Budgeted Spend}}{\text{Budgeted Spend}} \times 100$$

  • Variance Thresholds:
    • Favorable Variance (< 0% for expenses): Spend below budget; verify if due to delayed hiring or efficiency.
    • Unfavorable Variance (> +5% or > $5,000): Requires written department lead variance explanation and corrective remediation plan.

4. Departmental Budget Allocations

DepartmentTypical % of Total OpExPrimary Budget DriversKey Performance Metric
R&D / Engineering45% – 55%Engineering headcount, cloud infrastructure, AI computeFeatures shipped, system uptime, cloud cost/MAU
Sales & Marketing25% – 35%Quota-carrying reps, digital media spend, conferencesCAC, Pipeline generated, Magic Number
G&A (Ops, Legal, Fin)10% – 15%Legal counsel, accounting audit, insurance, executive teamMonth-end close speed, compliance certifications

Critical Rules

  1. Never budget revenue without tying it to pipeline conversion rates and sales headcount productivity caps.
  2. Every new full-time headcount addition must have an assigned requisition ID and fully-loaded financial model approval.
  3. Budget owners are accountable for gross dollar ceilings; savings in one line item cannot be diverted to unapproved software subscriptions without CFO sign-off.

Verification Checklist

  • Fully-loaded headcount multiplier (1.20x–1.25x) applied to all projected salaries.
  • Variable COGS tied dynamically to revenue projections.
  • Monthly BVA variance reports generated with written management explanations.
  • Downside stress-test scenario guarantees minimum 12 months cash runway.
  • Capital expenditure (CapEx) separated from operational expenditure (OpEx).

Anti-Patterns

  • NEVER create an annual budget that remains untouched for 12 months despite material market shifts.
  • NEVER rely on straight-line revenue growth assumptions without accounting for sales rep ramp time (typically 3–6 months).
  • NEVER treat projected cost savings from unhired roles as permanent financial buffer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.