J.R. MullisMost companies treat the Department of War (DoW, formerly DoD) budget like weather: something that happens to them. Then they wonder why every opportunity feels like a fire drill and every December feels dead.
The budget isn’t weather. It’s a machine with a published schedule. Learn the schedule and you stop reacting; you start showing up exactly when decisions get made. That’s the whole game.
Three budgets at once
Here’s the part nobody explains to industry: at any given moment, the Department is working three fiscal years simultaneously.
It’s executing this year’s money; that’s what you can sell into right now. It’s defending next year’s request on the Hill, and the justification books that go with it are public documents that name programs, quantities, and dollars. Free intelligence, sitting on the internet, that most of your competitors never read. And it’s building the year after that through the POM: the internal process where program offices fight for their share.
Why you should care: if you wait for a solicitation, you’re shopping in the “executing” budget: money that was locked in two years ago, shaped by whoever was in the room then. If you want to be in a budget, you engage during “building.” That means the requirement you influence today funds in roughly two years. Plan accordingly.
Colors of money, and why your pitch dies without them
Appropriations aren’t interchangeable. RDT&E (the 3600 accounts) funds development and prototypes. Procurement accounts buy fielded systems at scale. O&M (3400) pays for operations, services, and sustainment. It expires after one year, which is why it moves fast and why so much of it gets obligated in Q4.
A program office can love your product and still be unable to buy it, because they hold the wrong color of money. We watch this kill deals constantly. The fix is simple: before you pitch, know which appropriation your offering maps to, and ask early whether the office you’re courting actually controls that money. If they don’t, find out who does. That’s a question, not a mystery.
Demand, funding, and a contracting vehicle. The budget cycle is the “funding” leg, and it tells you the timing of the other two. An office with validated demand but FY28 money is a relationship to build, not a deal to close this quarter. Treat it that way.
The calendar that should drive your BD plan
- Oct–Dec (Q1): New fiscal year starts, usually under a continuing resolution, which freezes new starts. Slow quarter for awards; perfect quarter for relationship building and shaping.
- Jan–Mar (Q2): Appropriations typically land; obligations pick up. The President’s Budget request drops. Read the J-Books for every program adjacent to your tech. This is your map for the next 18 months.
- Apr–Jun (Q3): Execution at full speed; POM deliberations heat up inside the Department. Mid-year reviews shake loose unspent money. Your white papers and demos need to be in front of decision-makers now.
- Jul–Sep (Q4): Use-it-or-lose-it season. Offices race to obligate expiring funds. If you’re already known, already qualified, and already on a vehicle, this is harvest. If you’re introducing yourself in August, see you next year.
What to do with all this
Three moves, starting this week. One: pull the public J-Books for your top two target programs and read the line items; you’ll know their funded priorities better than half their own building does. Two: tag every opportunity in your pipeline with its color of money and fiscal-year timing, and watch your forecast get honest fast. Three: build your engagement calendar around the Department’s calendar, not your own quarter-ends.
The budget cycle rewards companies that respect it and punishes everyone else. We’ve spent careers inside this machine; navigating it for clients is the part we handle. We don’t guess at the cycle, we work it. And we’re damn good at it.
Want your pipeline mapped against the FY27 and FY28 cycles? Let’s talk.