Agile Budgeting
Agile Budgeting replaces the traditional annual budget cycle — where every product, team, and project is funded for 12 months based on assumptions made 14-18 months before delivery — with a continuous funding model: persistent funding for product teams (not projects), quarterly outcome reviews, and dynamic reallocation based on what is actually working. Variants include Beyond Budgeting (Bjarte Bogsnes / Statoil), bet-based funding (used at Spotify and ING), and rolling forecasts. KnowMBA POV: agile budgeting decisively outperforms annual planning when product release velocity exceeds one release per quarter — at higher velocities, annual budgets become fiction within months. Below that velocity, traditional annual budgeting may still be appropriate. The mistake is applying agile budgeting universally; the correct frame is 'velocity-matched funding.'
The Trap
The trap is keeping agile delivery practices on top of an annual budget cycle. Teams ship every two weeks, but funding decisions happen once a year — so the annual decision becomes a bet on what teams will need 14 months later, which it cannot be. The result: teams either underspend (saving for unknowns) or overshoot (because there's no mechanism to adjust). The other trap: declaring agile budgeting and then secretly reverting to annual processes for the politically sensitive decisions (headcount, vendor contracts, major capex). Half-agile budgeting is worse than honest annual budgeting because it adds overhead without changing decisions.
What to Do
Move to agile budgeting in three structural shifts: (1) Fund teams persistently, not projects annually — each persistent product team gets a continuous baseline, with quarterly review for trim or expansion. (2) Reserve a discretionary pool (typically 15-25% of digital spend) for quarterly reallocation to emerging bets. (3) Replace the annual planning ceremony with quarterly portfolio reviews where bets are evaluated on outcomes, not status. Critical structural enabler: finance must change its closure rhythm and approval workflows — agile budgeting fails if every reallocation requires a 6-week finance approval cycle. Spotify, ING, and Statoil all rebuilt the finance function in parallel with the budgeting model. Measure success on (a) % of spend reallocated quarterly, (b) time from outcome signal to spend change, (c) % of teams persistently funded vs project-funded.
Formula
In Practice
Spotify has publicly described its 'bets' funding model — leadership commits to a small number of company-level bets each cycle (typically 6-month horizons), with persistent squad funding underneath. Squads can be re-pointed quickly because the funding follows the bet, not the project. ING Bank's 2015-2018 transformation explicitly converted from annual project budgeting to quarterly portfolio reviews and persistent product funding; ING's CIO Peter Jacobs publicly identified the funding-model change as the most consequential element of the transformation. Statoil (now Equinor) pioneered Beyond Budgeting in the early 2000s under Bjarte Bogsnes — running for over 20 years without a traditional annual budget — and his book 'Implementing Beyond Budgeting' documents the multi-year change journey including the finance function redesign.
Pro Tips
- 01
Don't promise agile budgeting until finance has redesigned its approval workflows. The bottleneck is almost always finance process speed, not commitment to the model.
- 02
Hold a discretionary reallocation pool. 15-25% of total digital spend kept available for quarterly reallocation is the most common pattern — enough to fund emerging bets, small enough not to threaten existing teams.
- 03
Replace 'business case' with 'outcome thesis + kill criteria.' Agile budgeting depends on being willing to stop investments that aren't working — which requires explicit kill criteria set up front, not after-the-fact rationalization.
Myth vs Reality
Myth
“Agile budgeting means no budget”
Reality
Agile budgeting still has total spend constraints and team baselines. The difference is reallocation cadence and decision granularity — quarterly and team-level rather than annual and project-level. Statoil's Beyond Budgeting still has spend ceilings and accountability.
Myth
“Agile budgeting works for everything”
Reality
Agile budgeting outperforms annual planning when product release velocity exceeds ~1 release/quarter. Below that velocity, the overhead of quarterly reallocation outweighs the benefit. Multi-year capex projects (data center builds, ERP rollouts) are rarely well-suited to fully agile funding.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
An enterprise has adopted agile delivery (every team ships every 2 weeks) but kept annual budgeting. By month 8, what is the most likely symptom?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Quarterly Reallocation Volume (% of Digital Spend)
% of total digital spend reallocated between teams/bets per quarter, mature agile-budgeting orgsBeyond Budgeting Mature (Statoil-class)
> 25%
Strong Agile Budgeting (ING-class)
15-25%
Developing
5-15%
Annual Budget with Light Variance
1-5%
Locked Annual
< 1%
Source: Beyond Budgeting Roundtable / ING Agile Transformation Disclosures
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Spotify
2010-Present
Spotify publicly described its 'bets' funding model — leadership commits to a small number of company-level bets each cycle (typically 6-month horizons), with persistent squad funding underneath. Squads can be re-pointed quickly because funding follows the bet, not the project. The structure has evolved over years (the original 'Spotify model' has been revised multiple times) but the underlying agile funding pattern has persisted because it matches Spotify's high product velocity.
Funding Horizon
~6-month bets
Squad Funding
Persistent, re-pointable
Annual Budget Role
Total ceiling, not allocation
Pattern Longevity
10+ years (with evolution)
Spotify proved that agile budgeting can scale to a multi-thousand-engineer org if funding follows persistent teams and time-boxed bets, not projects.
ING Bank
2015-2018
ING's transformation moved 350 squads onto persistent product funding with quarterly portfolio reviews replacing annual project budgeting. CIO Peter Jacobs publicly identified the funding-model change as the most consequential element — harder than the org-chart change and more enduring. Reported outcomes included 30% faster time-to-market and double-digit employee engagement gains. ING's case is the clearest large-bank reference for agile budgeting paired with squad-based delivery.
Squads on Persistent Funding
350
Tribes (Product Groupings)
13
Time-to-Market Improvement
~30%
Funding Cycle
Annual → Quarterly
Funding model change is harder and more consequential than org chart change. ING is unusual in publicly emphasizing this and providing a reference implementation.
Decision scenario
The Funding Cadence Decision
You are CFO of a $3B financial-services firm. The CTO is requesting a move from annual project budgeting to quarterly persistent product funding. Your team is anxious — finance approval workflows are built around annual cycles. The CTO promises 25-30% throughput improvement.
Annual Digital Spend
$180M
Current Funding Cadence
Annual project budgets
Finance Approval Avg Cycle
5-7 weeks
Product Release Cadence
Bi-weekly
Decision 1
Choose your approach.
Approve quarterly product funding immediately; redesign finance workflows in parallelReveal
Spend Q1 redesigning finance workflows to match quarterly cadence; pilot agile budgeting on 3 product teams in Q2; full rollout in Q3-Q4✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Agile Budgeting into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Agile Budgeting into a live operating decision.
Use Agile Budgeting as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.