/Catalogue/Prompt/cbrock84/cbrock84-headcount-budgeting-and-forecasting

Origin: github

budgeting-and-forecasting

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.

by cbrock84 · updated 7d ago · imported from GitHub

Installs0+0/7d
Security score100/100
Retention 14d0%
GitHub stars1.7K

Skill logic

Execution graph
User message
Prompt rewrites behaviour
Response

SKILL.md

View on GitHub ↗

Budgeting and forecasting

The budget is a commitment, the forecast is a belief

Keep them separate. A budget re-cut every month is not a commitment; a forecast held to the original budget is not a belief. Both failures make the numbers useless for different reasons.

Running the cycle

  1. Set the frame first — targets, headcount envelope, and the assumptions everyone builds on (pricing, attrition, timing). Distributed teams building on different assumptions produces a consolidation that cannot be reconciled.
  2. Collect in a fixed template. Free-form submissions cost more to normalize than to build.
  3. Challenge the inputs, specifically: what is the volume driver, what is this per unit, what happens if it comes in at half. Budget submissions are negotiating positions and should be treated as such without hostility.
  4. Consolidate and find the gap between bottom-up and top-down. There always is one. Close it explicitly by cutting something named, not by proportional trimming — proportional cuts damage the highest-return line as much as the lowest.
  5. Publish what was not funded and why. This prevents the same request arriving three times.

Rolling forecast

Re-forecast on a fixed cadence over a constant horizon. Update only what has changed and say what changed and why. A re-forecast with no narrative is a new set of numbers with no information in it.

Variance analysis

Variance is only useful decomposed. For each material variance, separate:

  • Volume — did we do more or less of it?
  • Rate — did each unit cost or earn a different amount?
  • Timing — did it move between periods, or is it gone?
  • Mix — did the composition shift?

Timing variances need no action and are constantly mistaken for performance. Rate variances on recurring costs compound and are constantly under-reacted to.

Explain the top few by value, not every line. A variance report covering everything gets read as nothing.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Planning: Anaplan, Pigment, Workday Adaptive Planning, Vena, Cube, and similar. A well-built spreadsheet on a clean chart of accounts beats a planning tool nobody has been staffed to maintain; move when budget owners outnumber the people who can hold the model in their head.

Driver data comes from the ledger, the CRM, and the HRIS. The planning tool is only ever as current as those connections.

Never

  • Present a forecast without saying what changed since the last one.
  • Let a department own an assumption that drives another department's numbers.
  • Report accuracy without measuring it. Track forecast error over time — it improves quickly once visible and never improves while unmeasured.

Discussion

No comments yet — start the thread.

Sign in to join the discussion.

/More from cbrock84/headcount

cbrock84· 7d agoCommunity
chief-strategy-officer

Prompts · Markdown · v0.1.0

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.

#agent-marketplace#chatgpt-plugin#chatgpt-skills

0 1.7K
cbrock84· 7d agoCommunity
market-entry

Prompts · Markdown · v0.1.0

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop. Use this to evaluate a new geography, segment or vertical, pressure-test an entry plan, or work out why a launched market never reached scale.

#agent-marketplace#chatgpt-plugin#chatgpt-skills

0 1.7K
cbrock84· 7d agoCommunity
mergers-and-acquisitions

Prompts · Markdown · v0.1.0

Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.

#agent-marketplace#chatgpt-plugin#chatgpt-skills

0 1.7K
cbrock84· 7d agoCommunity
portfolio-strategy

Prompts · Markdown · v0.1.0

Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide whether to exit one, structure a portfolio review, or when several initiatives compete for the same limited investment.

#agent-marketplace#chatgpt-plugin#chatgpt-skills

0 1.7K