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:

———

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.

KICK THE TIRES ON MY BACKGROUND

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

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.