Step 11: Map the Budget Cycle

The step in one sentence

Replace the classic playbook's "map the process to acquire a paying customer" with a literal, dated calendar of how money moves through your beachhead country's defence budget, because in defence, the sales process is not a funnel you drive; it is a train timetable you either catch or miss.

1. Why this step is different in defence

In the classic entrepreneurial playbook, Step 11 asks you to map the sequence of actions that turn a lead into a paying customer. The founder controls the tempo: more calls, better demos, shorter cycles.

In defence, tempo is exogenous. The buyer cannot buy outside the budget cycle even when they love you. A ministry program officer with genuine urgency and a validated requirement still cannot sign until:

1. the requirement exists in a planning document,
2. the money exists in an approved budget line,
3. a legal contracting vehicle exists to move that money to you.

These three conditions mature on a government calendar, not on yours. The startup that treats defence sales as a funnel optimizes activities that do not matter. The startup that treats it as a timetable schedules its product milestones, hiring, and, critically, its fundraising against the dates when the three conditions align.

The reframe: you are not "shortening the sales cycle." You are positioning yourself at the station before the train arrives.

This is also the step that explains the sector's fundraising barbell (our deal data: defence companies that graduate seed to Series A do it in a median of 11.5 months versus 17.3 for the market, but very few graduate). The graduates are not better sellers. They are companies whose proof-points landed in phase with a budget cycle, so contract news and round news compounded. The stalled majority are out of phase: real traction, wrong year.

2. The three clocks

Every beachhead procurement path runs on three overlapping clocks. Your map must show all three.

Clock 1, The planning clock (24 to 48 months out). Where requirements are born: defence white papers, capability reviews, NATO defence planning targets, EDF work programmes. If your capability is not represented in a planning document, there will be no budget line to catch later. The work at this horizon is requirement-shaping: briefing armaments directorates, contributing to industry consultations, getting your capability gap named in the documents that program officers will later cite.

Clock 2, The budget clock (12 to 24 months out). Where money is authorized: the annual national budget process, ministry draft, government approval, parliamentary vote, appropriation. Each country has fixed dates. Miss the insertion window and the earliest money moves a full year later. This clock is public, predictable, and almost universally ignored by first-time founders.

Clock 3, The contracting clock (0 to 12 months out). Where money becomes revenue: tender publication (TED in the EU), framework call-offs, urgent operational requirements, innovation-unit contracts. This is the only clock most startups watch, and by the time a tender publishes, the requirement was shaped (Clock 1) and funded (Clock 2) long ago, usually around someone else's product. Capture literature has a rule of thumb: if you first learn of a tender when it publishes, you are the price check, not the winner.

The founder's job in Step 11: for one beachhead path (chosen in Step 2), write down all three clocks with real dates for the next 36 months.

3. Building the map: the method

3.1. Choose the single path. One country, one buyer mechanism (from Step 2). A map of "European defence budgets" is a poster; a map of "German Sondervermögen line X via BAAINBw framework Y" is a plan.

3.2. Assemble the source stack.

• Planning: national defence review, NATO capability targets, EDF work programme, service-branch modernization plans.
• Budget: ministry budget submission dates, parliamentary defence committee calendar, published budget annexes with program lines.
• Contracting: TED alerts for your CPV codes, the buyer's framework agreements and their renewal dates, innovation-unit call calendars (DIANA cycles, DASA themed calls, AID challenges).

3.3. Draw the timetable. A single horizontal 36-month timeline with three swim lanes (one per clock). Mark: document publication dates, budget insertion deadlines, votes, tender windows, framework renewals, and the innovation-unit calls you'll use as assumption tests (Step 15).

3.4. Mark your insertion points. An insertion point is any dated event where an action by you changes what happens downstream: an industry-day comment that shapes a requirement, a pilot that a program officer can cite in a budget justification, a challenge win timed so its result lands during budget drafting.

3.5. Fuse it with the gate sequence. Overlay your planned funding rounds. The discipline rule of the whole methodology, never pitch gate N+1 with gate N−1 proof, becomes schedulable here: the round opens after the proof-point event on the timetable, ideally within 90 days, while the news is hot. (Observed pattern in our data: Comand AI announced Saab's strategic investment at Eurosatory, proof-point and capital event fused into a single calendar moment.)

4. The worksheet

For the beachhead path chosen in Step 2:

1. Which planning document names (or should name) your capability gap? Next revision date?
2. What are the three key national budget dates this year (ministry draft / government approval / parliamentary vote)?
3. Which budget line can legally pay you? Who "owns" it? (Cross-reference Step 3's program officer.)
4. What contracting vehicle moves that money, tender, framework, UOR, innovation contract? When does it next open?
5. What are your five insertion points in the next 36 months, with dates?
6. Which proof-point lands within 90 days before your next planned raise?
7. What is your Plan B vehicle if the primary window slips a year? (There is always slippage. A map with one train is a prayer.)
8. Which prime's program calendar could serve as your fourth lane, and what is its next design freeze or upgrade window? (See Section 5.)

An answer of "we don't know" to any of these is a Step 15 key assumption, schedule its test.

5. The fourth lane: riding someone else's timetable

The three clocks describe the direct path, earning your own place in a nation's budget. There is a second path that skips Clocks 1 and 2 entirely: entering a prime integrator's program of record.

Primes (Rheinmetall, Thales, Saab, Leonardo, BAE, KNDS) hold the multi-decade contracts to deliver complete systems. Their trains have already left the station, requirement shaped, budget voted, contract signed. If your subsystem is designed into an existing program, you reach production revenue on the prime's timetable, not the ministry's. This is budget-cycle arbitrage, and it is why the deal data shows primes investing before they buy: Saab's strategic stake in Comand AI and Rheinmetall's participation in Kraken's Series B each formalized a design-in decision.

The prime lane has its own clock. Add a fourth swim lane to the timetable, populated not with parliamentary dates but with:

• Design freeze dates, the moment a program's configuration locks. Miss it and the next entry point may be years away. A design freeze is exactly as hard a deadline as a budget vote.
• Mid-life upgrade (MLU) windows, scheduled modernization points where new subsystems are competed in.
• Obsolescence replacement cycles, components aging out create recurring insertion points for drop-in-plus-better offerings.
• The prime's own capture calendar, the tenders the prime is bidding, where your capability can strengthen their offer (you join their team during proposal, not after award).

What the lane costs. The map must be drawn with open eyes:

• Margin compression, subcontractor pricing while the prime keeps system margin.
• IP and dependency risk, design-in can become design-around, or leverage for acquisition at a discount.
• Channel concentration, one corporate buyer replacing one government buyer.
• Brand invisibility, the ministry learns the prime's name, not yours, which weakens the gate-4 consensus story unless actively managed.

The dual-lane doctrine. The strongest observed trajectories run both paths at once: prime subcontracts generate revenue and production credibility while the company shapes its own direct program on Clocks 1 to 3. Kraken exemplifies the pattern, Rheinmetall in the round and sovereign backers (NIF, NSSIF) on the cap table, two channels feeding one company. On the timetable this means insertion points in all four lanes, with the prime lane funding the patience the direct lanes demand.

Dataset: prime CVC activity by category; prime program-ownership map; MLU and design-freeze calendars per program.

6. Failure modes

The demo-day fallacy. Optimizing operator enthusiasm (Clock 3 energy) while no requirement or budget line exists upstream. Symptom: many "successful pilots," zero production contracts. This is the grant-farming trajectory investors price at zero.

The published-tender trap. Building the pipeline from TED alerts. Everything you can see there was shaped by others 18 to 36 months earlier.

The out-of-phase raise. Raising when the runway dictates rather than when the timetable delivers a proof-point, the single most common cause of the "valley of death" between prototype and program. The valley is not a market failure; it is usually a scheduling failure that was visible 24 months earlier on a map nobody drew.

The single-train map. One country, one tender, no fallback. Slippage of a single parliamentary vote becomes an existential company event.

The captive-supplier drift. Living entirely in the fourth lane: prime revenue is real, but no direct-path work happens, margins stay thin, and the company matures into an acquisition target priced by its one customer rather than a franchise priced by the market.

7. Case slot (to be developed from data)

Reverse-engineer one company's actual timetable: for each of its funding rounds (from the deal dataset), identify the procurement event announced within the preceding 6 months, and reconstruct the clocks it was riding. Candidate: Stark Defence's 2025 to 26 sequence (seed with sovereign participation to contract news to €500M round at €3.5B) for the direct path, and Kraken Technology (Rheinmetall + NIF/NSSIF) for the dual-lane doctrine.

8. Exit criterion

You have completed Step 11 when you possess a one-page, dated, four-lane timetable for your beachhead path, three government clocks plus the prime lane, with five insertion points, your next raise positioned within 90 days after a scheduled proof-point, and a named Plan B vehicle. This document, not your pitch deck, is what separates a fundable defence company from a hopeful one, and it becomes the spine of the Gate Plan in Step 18.