Permission is two things: someone official agreeing in writing the need is real, and money set aside.
Everything below is how those get made — and who can take them back.
Three movements describe where the money comes from. Eight seats describe who can stop it. Permission is the thing they're both about.
Two questions decide everything below. Does permission exist? And will it hold?
Most of what is sold as Defense strategy is a place in a queue.
The standard engagement: log into a portal, find a solicitation that already exists, and write a response competing against a field that was assembled before you saw the document, for money that is already spoken for. That isn't strategy. It's standing in line, and being charged for the privilege.
You're not missing context. The document is. It was written for people already in the conversation.
The work is in the chapters before the conclusion gets written: where the funding originates, how requirements are generated at each level from authorization to obligation, and which lever actually moves value toward you and toward your customer at the same time. Do that and the question changes. You stop asking which solicitation to answer and start asking whose requirement you are going to be the obvious answer to.
You want to create a market, not chase it. By the time a solicitation publishes, the market should already have your shape.
What's missing has a name.
Your strongest advocate is usually the one person who can't buy anything. The people who can buy don't know you exist, and their budgets were settled two years ago. So the enthusiasm is real, the meetings are real, and none of it is funded.
Permission is two things at once: someone official has agreed, in writing, that the gap you fill is real — and there is money set aside for it, of the right kind, in the right year. Hold both and somebody over there is finally allowed to buy what you built. Hold one, and you have a pilot program with a ceiling on it.
Then it can be taken back. Congress cuts the line. A program is restructured, deferred, or quietly raided to pay for something louder. The contract isn't the finish line — it's the midpoint, and the second half is the half everyone stopped watching.
So there are only two questions here worth paying anyone to answer. Does permission exist? And will it hold? The first has a one-time answer. The second has a standing one.
Where permission comes from.
Federal money travels a long, deliberate path before it becomes a contract. Most consultants have memorized the acronyms without ever seeing the inside of the system they claim to navigate. The path has three movements, and permission is manufactured somewhere in each of them.
The trace, in three movements:
-
Where authorizations and appropriations (and the occasional reconciliation) are written, and how the language that governs your market gets made.
-
How authorized intent becomes requirements, programs, and budget lines inside the Pentagon and the services.
-
How requirements become solicitations, vehicles, and obligated dollars — and how a technology gets positioned to be the answer that pathway was built to buy.
I have generated requirements at every one of these levels, inside Defense Acquisition and then from a company that had to win Programs of Record to make payroll.
———
That's where permission comes from. Now the harder half — who can withhold it.
Acquisition, in Defense, isn't M&A. It's the government's word for how it decides what to buy, from whom, and with which year's money.
Acquisition is not a document. It's eight people who all have to say yes.
"Acquisition" gets used as if it means contracting — the solicitation, the response, the award. Contracting is one of seven functional areas the government trains its acquisition workforce in, across eight certification tracks: auditing, business financial management, business cost estimating, contracting, engineering and technical management, life cycle logistics, program management, and test and evaluation.
Each seat asks a different question. Is there a program, with a decision authority who can actually buy this. Is there money, in the right appropriation, in the right year. Does the independent cost estimate close at fleet scale rather than prototype scale. Will it integrate into a technical baseline you don't control. Can it be proven against endpoints you didn't write, and sometimes couldn't have. Can someone who isn't you sustain it for twenty years. Will your books survive the audit that arrives with growth.
Contracting turns all of it into a lawful instrument — and it goes last. So when a solicitation reaches you, seven other functions have already decided what a winning answer looks like, and you are being invited to the end of a process to argue with its conclusion.
If acquisition were arbitrary, a good meeting could fix it. It isn't, and it can't. A bad decision that seven offices took two years to reach is harder to move than a whim, not easier. Slow is not the same as random.
The award is the midpoint. Almost everyone treats it as the finish line.
The same seven functions that had to say yes can take it back, and none of them will call you first. Congress cuts the line in conference. A program is restructured and your scope moves to a follow-on that hasn't been funded. An office moves the money to cover a shortfall somewhere louder than you. Your requirement is superseded by a broader one written around a capability you don't have. The champion who carried it rotates in two to three years — and the civilians holding the money largely don't rotate at all, which cuts both ways: the enthusiasm leaves, and the people who told you no are still there.
None of that shows up in your pipeline. It shows up in a budget document, months before it shows up in your revenue, and it is legible the whole time to anyone who reads those documents for a living.
That is the second question, and it is the one your board will not think to ask until the year it matters.
You're not underwriting whether it works. You're underwriting whether anyone is authorized to buy it.
Defense-tech diligence routinely prices the wrong risk. The deck says technical risk and competitive risk; the company dies of acquisition risk. A portfolio company can hold validated technology, an enthusiastic user community and three SBIR Phase IIs and still be unfundable by its own customer — because no program owns the requirement, or the earliest new money is two budget years out and the decision creating it is being made now without them, or the price doesn't survive fleet scale, or nobody has worked out who maintains it for twenty years and who owns the drawings.
None of that surfaces in technical diligence. All of it is knowable before the check.
After the check, the exposure inverts. The most expensive thing a Defense-tech board does is set a commercial revenue target on a company whose buyer has no approved budget until 2029 — and then read the result as an execution problem. That is preventable with a memo, and the memo is cheaper than the down round.
Two numbers change the model. Time to obligated dollar — the day money legally becomes yours, which is not the day you win and is emphatically not the day someone expresses "funding interest." And transition probability: the odds a prototype becomes a funded program, conditioned on how many of the eight seats currently have a written answer.
Permission is also the only thing anyone will pay for your company.
Large Defense companies do not buy technology. They buy backlog they can underwrite — a quantity and a unit price across a number of years, or a sustainment tail that renews, printed in a budget exhibit the government has already committed to. A development contract isn't that. A services contract isn't that. Being "eligible" on a vehicle that ten other vendors are also eligible on isn't that. Eligible is not programmed.
This is why the best-funded venture-backed Defense companies don't get bought. It isn't that the primes can't afford them. It's that there is nothing on the page a prime can price — and when the capability is software, the prime can license it instead. The government is deliberately building its systems so that no single vendor is ever a must-buy.
Is there money behind this that comes back every year?
If yes, the company has an exit. If no, it has a customer relationship — and that relationship is worth what's remaining on the contract
That is the same question a corporate development team asks, and the same question a fund should have asked before the check. It is also the one question in this business that is answerable from documents you can open yourself.
One limit, stated plainly: some government buying is classified and never appears in the public exhibits. When the trail goes dark, you'll be told it went dark, not told it isn't there.
Two questions. Two engagements.
Does permission exist? And will it hold? The first has a one-time answer. The second has a standing one.
Engagements are structured, not hourly guesswork. Most clients enter with the Assessment and grow into the Retainer — and some get an answer from the Assessment that means they shouldn't continue into the standing relationship.
Most often the fund pays. The engagement letter names your company as the beneficiary, and there isn't a founder version and a fund version — you both read the same thing.
The Permission Assessment
Fixed scope, one time. Does permission exist for what you've built, and if not, can it be made to? You get a written verdict traced to documents you can open yourself: which program could own the requirement, whether a line exists and in what year, whether the price survives being multiplied by the whole fleet, which of the eight seats currently has no answer at all — and whether there is a budget line behind the research money that comes back every year, and which kind: a program of your own, a modification into someone else's, or the money that sustains what's already fielded. That is the question an acquirer will ask about you one day whether or not you asked it first.
It can end in no. That is not the failure case — it is the cheapest thing I do. Winning the wrong market costs more than losing the right one: a year and six figures of engineering aimed at a customer who lacks the authority to buy.
The Permission Retainer
Standing, monthly. Permission you already hold is the asset most likely to be taken back while you are busy delivering. Every period ends in a dated artifact: what moved against your program since the last one, and the documents it moved in. Cuts made during Congressional review, money moved to another program, work pushed into a later budget year, requirements rewritten, a competitor's line appearing where yours used to be.
If nothing moved, the report says so and names what was checked. Vigilance is not a deliverable.
Six reasons people hire a Defense strategist. None of them are the real job.
Six things Defense strategists routinely sell that don't move a funding decision or set conditions for persistent differential returns.
Access isn't the job. I'll make an introduction when both sides consent and both sides gain. What isn't for sale is the address book — an introduction doesn't survive a budget decision, so buying one buys you the wrong thing.
The proposal isn't the job. I'll review yours, and I'll write the section where my judgment changes the outcome. What I won't take is the engagement where writing the response is the plan. By then the decision has usually already gone the other way.
Taking work they can't move isn't the job. When that's the answer, I say so and name someone who can help instead. The referral is the deliverable in that case.
Trading on what they know about other companies isn't the job. Method travels between engagements; information never does. What I learn inside your company stays there — and that's the same commitment every other client has, which is the only reason it's worth anything to you.
Taking credit isn't the job. I don't claim an outcome I can't trace to a document. You should be able to check everything I tell you against something you can open yourself.
And covering every seat isn't the job either — nobody covers eight. What I'll do is tell you which ones will kill your line of business this year, what a written answer to those looks like, and in what order to get them.
Frequently Asked Questions
-
I shape the conditions that make a solicitation winnable — or unnecessary. The proposal treadmill keeps you competing inside a queue; my job is to get you off it. Pen should go to paper only when your strategy and the government's line up.
-
Eventually. Not first.
A BD hire is optimized for demand that already exists — who to call, who hasn't answered, what demo is next. That's real work, and it's the right work once you know which program office, which funding line, and which requirement you're aiming at. Hire before you know that and you've bought twelve months of someone learning the acquisition system on your payroll, well into six figures loaded, to find out whether there was a market at all.
There's also an incentive problem nobody mentions in the interview. A BD hire is measured in meetings booked and white papers submitted. They are structurally incapable of telling you there's nothing here. That conclusion ends their job. It's one of the answers my assessment is built to produce.
The order that works: find out whether there's a funded path, then hire the person to run it. You stop asking a new employee to "go find us some defense business" and start handing them a market, a customer, a funding mechanism, and a pathway. That's a dramatically easier job — and a cheaper hire, because you're not paying that person to learn what you already know.
-
It's necessary and it isn't sufficient. A champion has a requirement and no checkbook; the person with the checkbook has a portfolio and no urgency. Your uniformed champion rotates in two to three years. The civilians controlling the money largely don't rotate at all — so the enthusiasm leaves and the institution stays. Enthusiasm that never became a written requirement and a programmed line leaves with the champion who held it.
-
Other Transaction Authority — contracting outside the standard federal rules — genuinely widened the entrance, and contracting officers have real speed on the instrument now. Two caveats. GAO reported in September 2025 that DoD doesn't track the data needed to assess whether OTAs are working as intended, and that of eighteen sampled prototype efforts, ten reverted to FAR contracts for production — so the outcome claim isn't available yet. And the FAR overhaul is still mid-rulemaking, running largely on agency deviations. None of it programs money into Fiscal Year +2, closes a cost estimate at fleet scale, writes a test strategy or creates a sustainment tail. Streamlining the last gate makes the first seven more decisive, not less.
-
No, and most companies that become durable never get one. They end up inside someone else's — a modification kit, a spare, a sustainment contract — with their name nowhere on the budget line and their revenue in it every year. That money gets less scrutiny than development money and outlives most programs. It doesn't make a headline, and it is a position an acquirer likes. The Assessment tells you which of those doors is open to you, and whether the one you're walking toward is the slow one.
-
Software compresses engineering and shortens test. It doesn't touch what kind of money can buy you, the budget calendar, the security accreditation you need before anything runs on a network, or the fact that someone has to own and fund your product after the pilot. Software got its own appropriation pilot — BA-08 — precisely because the kind-of-money rules were breaking software programs. That's an admission the problem is real, not evidence you've skipped it. And BA-08 doesn't cover most of you.
-
No. Paying a consultant a contingent fee to obtain a federal contract raises serious compliance problems under the FAR. I structure engagements as fixed fees and retainers.
-
For early-stage firms, yes — as part of a cash-plus-equity structure, tailored per company.
It exists so that a company short on cash can still buy the answer.
-
Companies building for a defense customer, venture-backed or not, and the funds and boards behind them. A profitable company funding its own R&D has the same permission problem as a Series A company — it just has more time to solve it. Structure scales with stage.
-
With a free conversation, then a Permission Assessment if there's a fit. The Assessment is fixed scope and fixed fee, agreed in writing before it begins.
-
Yes — when both parties consent and both stand to gain. What isn't on offer is access as a product. The person who is enthusiastic about your technology and the person with the authority to fund it are usually different people in different organizations, so an introduction to the first doesn't move the second. Selling you one would be selling you something that doesn't work.
-
Yes. I review them, and I write the sections where my judgment changes the outcome — a technical approach that has to survive someone who owns a baseline you don't control, or a past-performance narrative aimed at the evaluator's actual criteria rather than the ones you'd prefer they used. What I won't take is the engagement where the solicitation response is the strategy. If the first time you engaged with that requirement was the day it posted, better writing isn't the variable.
-
8.
Because the work is judgment, and judgment doesn't scale by adding staff to it. Publishing the number is what stops me saying yes to a ninth — which is the only reason the eight get what they're paying for.
-
You're not being asked to. Switching off the money that keeps your lights on would be malpractice — and it isn't the play.
The grants stay on and we aim them. Every award you chase from here gets chosen and shaped to build toward one thing: a program that outlives that one grant. The same revenue you already win — pointed at an exit from the treadmill instead of another lap on it.
The faucet keeps running while we dig the well. The goal is not to turn the faucet off — it is to get you to the well it draws from.
And the part nobody says out loud: staying on the treadmill isn't the safe choice. Topics change, programs sunset, and a company that always wins and transitions nothing is one budget cycle from the lights going out with nothing behind them. Crossing over is what makes the money durable.
-
Then I tell you — and that's the most valuable answer you can get.
Winning the wrong market costs more than losing the right one: a year and six figures of engineering aimed at a customer who lacks the authority to buy. The Permission Assessment is built to catch that before you spend it. A clear "no" early is worth more than a hopeful "maybe" three years in.
-
The bureaucrat adds gates. I remove the ones you'd have walked into blind.
Schedule an engagement.
An hour now might save you more than a year of discovery learning.
A few questions first — they help me show up to our conversation prepared. Wherever you are in your journey, even if you are still in ideation, share your context and you'll get my calendar to book a time. I read every inquiry myself.

