agentsclimarketplace

Budget planning

Skill Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/budget-planning

A curated pack of custom Claude Code skills for developers — installable as a Claude Code plugin marketplace.

Install
npx -y skills add Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack --skill budget-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

When to activate: annual budgeting, zero-based budgeting, rolling forecasts, budget variance analysis, headcount planning, capex vs opex, financial planning and analysis

SKILL.md

7.8 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it

Budget Planning

Annual Budget Process

Timeline (Reverse Calendar)

DateMilestone
Oct 1CFO issues budget guidelines and macro assumptions
Oct 15Department heads submit headcount plans
Oct 31Department heads submit expense budgets
Nov 15Finance consolidates, identifies gaps vs. plan
Nov 30Executive review and negotiation
Dec 15Board approval
Jan 1Budget locked — new fiscal year begins

Macro Assumptions to Align Early

  • Revenue growth target (top-down or bottoms-up)
  • Headcount growth % by function
  • Inflation assumption for salary increases
  • Capital markets / fundraising assumptions
  • Key risk scenarios: bull / base / bear case

Budget Approaches

Top-Down

  • Executive sets targets → departments fill in how to achieve
  • Fast, aligned to strategic priorities
  • Risk: unrealistic targets disconnected from operational reality

Bottoms-Up

  • Departments build from detailed plans → consolidate to company total
  • More accurate, builds ownership
  • Risk: empire building, everyone asks for more than needed

Zero-Based Budgeting (ZBB)

Every line item must be justified from zero — prior year spend provides no entitlement.

ZBB Process:

  1. List all activities performed by the team
  2. For each activity: what is the output? What does it cost to deliver?
  3. Rank activities by strategic value
  4. Allocate budget from highest to lowest priority until budget cap is hit
  5. Document what is cut and the business impact of each cut

Best for: Cost-heavy functions (G&A, marketing ops), post-acquisition cost rationalization

Rolling Forecast

  • Re-forecast full year every quarter (or monthly for fast-moving companies)
  • Replace static annual budget with living projection
  • Formula: Actuals YTD + updated forecast for remaining months

Department Budget Template

Department: [Name]
Budget owner: [Name / Role]
Fiscal year: YYYY

HEADCOUNT
  Current HC:     N FTEs
  Planned hires:  +N FTEs (list by role + planned start date)
  Planned exits:  -N FTEs (attrition assumption)
  Year-end HC:    N FTEs

  Salary & benefits:     $X
  (loaded cost per employee: base + benefits + payroll tax ≈ 1.25× base)

DIRECT EXPENSES
  Software / SaaS:          $X
    [Tool 1]:               $X/year ([N] seats × $X/seat)
    [Tool 2]:               $X/year
  Contractors / agencies:   $X
  Travel & entertainment:   $X
  Training & development:   $X
  Conferences:              $X
  Other:                    $X

ALLOCATED EXPENSES (from shared services)
  IT:          $X
  Facilities:  $X
  HR:          $X

TOTAL DEPARTMENT OPEX:  $X

CAPEX (if applicable)
  [Equipment / infrastructure investment]:  $X
  Useful life: N years → annual depreciation: $X/year

TOTAL BUDGET: $X
YoY change vs. prior year: +/-X%

Headcount Planning

Headcount Model Inputs

InputOwnerNotes
Revenue planFinanceDrives sales / CS HC
Product roadmapProductDrives engineering HC
Support volume forecastSupportDrives support HC
Target ratiosExecutivee.g., 1 CSM per $Xm ARR
BackfillsHRTrack separately from growth hires

Function-to-Revenue Ratios (SaaS benchmarks)

FunctionBenchmark ratio
Sales (AE)1 AE per $1–2M quota
CS1 CSM per $1–3M managed ARR
Support1 agent per X tickets/month (varies by complexity)
Engineering1 eng per $200–400K ARR (scales with maturity)
Marketing10–15% of revenue (varies by motion)
G&A10–15% of revenue at Series B/C

Ramp Cost Calculation

New hire total cost (first year) =
  Annual salary × 1.25 (loaded)
  × ramp factor (typically 0.5 for partial year + ramp)
  + recruiting cost ($X per hire)
  + equipment ($X)
  + onboarding overhead ($X in manager / team time)

Capex vs. Opex Decision

FactorCapexOpex
Upfront paymentCapitalized, depreciated over useful lifeExpensed immediately
Cash flow impactLarge upfront, smaller P&L hit per yearImmediate P&L hit
Tax treatmentDepreciation deduction over timeFull deduction in year incurred
FlexibilityLower (committed asset)Higher (cancel subscription)
Balance sheetIncreases assetsNo balance sheet impact
Best forLong-lived assets (servers, IP, equipment)SaaS, services, recurring costs

Cloud Infrastructure Decision Framework

  • If predictable, high-volume workload: reserved instances (capex-like commitment, opex accounting) = lower cost
  • If variable, unpredictable: on-demand (pure opex) = flexibility
  • If exploratory: spot / preemptible = cheapest, interruption risk

Budget Variance Analysis

Monthly Variance Report Template

[Month] Budget vs. Actuals — [Department]

                    Budget      Actual      Variance    Variance %
Salaries & Benefits $X          $X          $(X) fav    -X%
Software / SaaS     $X          $X          $X unfav    +X%
T&E                 $X          $X          $X unfav    +X%
Contractors         $X          $X          $(X) fav    -X%
Other               $X          $X          $X          X%
--------------------------------------------------------------------
TOTAL               $X          $X          $X          X%

YTD:
                    Budget YTD  Actual YTD  Variance    Variance %
TOTAL               $X          $X          $X          X%

Key explanations:
1. Software overage ($X): [Root cause — e.g., "price increase on Salesforce, not budgeted"]
2. Contractor favorability ($X): [Root cause — e.g., "project delayed to Q3"]

Reforecast for full year:
  Prior full-year budget:    $X
  Revised full-year forecast: $X
  Change:                    $X (+/-X%)

Variance Materiality Thresholds

ThresholdAction
< $10K or < 5%Note in monthly report, no escalation needed
$10–50K or 5–15%Explain in variance report, reforecast line item
> $50K or > 15%Escalate to CFO, budget amendment may be required

Budget Request Template (Mid-Year)

Budget Request — [Description]
Submitted by: [Name / Department]
Date: YYYY-MM-DD
Amount requested: $X (one-time) / $X per [month/year] (recurring)

Business case:
  Problem: [What situation requires this spend?]
  Solution: [What will this purchase or investment accomplish?]
  
Expected benefits (quantified where possible):
  - [Outcome 1]: saves X hours/month = $X/year
  - [Outcome 2]: enables $X revenue
  - [Outcome 3]: reduces risk of $X loss

Alternatives considered:
  - [Alternative 1]: rejected because [reason]
  - [Alternative 2]: rejected because [reason]

Timeline: [When is budget needed? What are the milestones?]

Risk of not approving: [What happens if this is declined?]

Approval required from: [Finance + relevant exec]

Budget Governance

Budget Amendment Policy

  • Reallocation within department (same total): manager approval
  • Reallocation across departments: CFO approval
  • New spend > budget total: exec + CFO + board notification above threshold
  • Emergency spend: CEO authority up to $X, then board

Forecast Cadence

Company stageForecast frequency
Seed / Series AMonthly
Series B+Monthly (detailed) + rolling 12-month
Pre-IPOWeekly during planning; monthly ongoing
PublicQuarterly guidance + monthly internal

Gives 0 of the 12 instructions most plan spec skills give in ~1.9k tokens

Counted across 1,100 of the 1,860 authors here whose files we hold, read 2026-08-06

  • ask one question at a timein 46 of 1100, across 38 files
  • Break plans into vertical slicesin 28 of 1100, across 10 files
  • Publish issues in dependency orderin 27 of 1100, across 9 files
  • Iterate until user approves the breakdownin 24 of 1100, across 6 files
  • Explore the repository to understand the codebase statein 24 of 1100, across 7 files
  • Use domain glossary vocabularyin 23 of 1100, across 5 files
  • Apply correct triage labels to published issuesin 23 of 1100, across 5 files
  • Write failing tests before implementation codein 23 of 1100, across 18 files
  • Prefer AFK slices over HITLin 22 of 1100, across 7 files
  • ask clarifying questions until requirements are concretein 21 of 1100, across 13 files
  • Respect existing architecture decision recordsin 20 of 1100, across 5 files
  • write a specification before writing any codein 20 of 1100, across 12 files

Said here and by no other author read

  • align macro assumptions early
  • justify every line item from zero
  • rank activities by strategic value
  • document business impact of cuts
  • calculate loaded headcount costs
  • classify spend as capex or opex

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.