gp0540

The go-to-market motion in one picture

Most commercial GTM playbooks assume a buyer with discretionary budget, a short evaluation, and a signature that converts to revenue in the same quarter. Defense inverts all three. The money is appropriated by Congress two years before it is spent, the buyer is split across a program office that owns the contract, a requirements sponsor that owns the need, and an operational unit that owns the pain, and the "signature" is a contracting officer's action that can be blocked by a compliance gate no salesperson ever sees. A playbook that ignores that structure produces expensive activity and no bookings.

The motion that actually works in 2027 runs in six stages, and each stage has a different owner and a different definition of done. Stage one is signal detection: reading budget justification books, Broad Agency Announcements, SBIR topic releases, and industry-day slides to find a need before it hardens into a solicitation. Stage two is shaping: getting in front of the requirements owner while the requirement is still a paragraph, so the eventual solicitation describes an architecture your product already satisfies. Stage three is entry: winning a small, fast vehicle — an OTA prototype agreement, a SBIR Phase II, a DIU Commercial Solutions Opening — that puts your technology in a government user's hands with a real contract number attached. Stage four is proof: running the prototype in an operational environment and instrumenting it so the output is data, not slides. Stage five is transition: converting that prototype into a production or sustainment vehicle riding a real appropriations line. Stage six is scale: adding scope, additional users, or additional services on top of an established contractual relationship.

The single most useful mental discipline is to stop calling stages three through five "the deal." They are three separate deals with three separate buyers and three separate funding colors. Research, development, test and evaluation dollars fund the prototype; procurement dollars fund the fielded system; operations and maintenance dollars fund sustainment. A capture plan that does not name which appropriation pays for each stage is a plan that will stall at the boundary between them — the widely documented "valley of death" between a successful prototype and a fielded capability. The valley is not a technology problem. It is a funding-and-sponsorship problem, and it is solved in stage two, not stage five.

The loop back from the valley to requirement shaping is the important edge. Firms that stall at transition almost always discover that no one inside the government owned the need in a way that could carry a budget request. The fix is upstream, and the second attempt is cheaper only if you kept the operational data from the first.

Who owns what across the revenue org

Defense contractors routinely staff business development with retired senior officers and call it a go-to-market function. Access is genuinely valuable — a retired flag officer who can get a meeting with a combatant command staff is a real asset — but access is one input among six, and organizing the entire revenue org around it produces a pipeline that no one can forecast.

Capture lead. Owns the pursuit end to end and owns the bid/no-bid recommendation. This is the closest analog to an enterprise account executive, but the job is longer and more analytical. The capture lead builds the customer map (program office, requirements sponsor, user unit, resource sponsor, contracting officer), maintains the competitive assessment including incumbent strength, and owns the price-to-win analysis. One capture lead can realistically carry three to five active pursuits of meaningful size; more than that and the shaping work degrades into proposal response.

Technical solutions lead. Owns the architecture story and the demonstration. In a market that increasingly mandates modular open systems approaches, this person must be able to describe your interfaces, not just your features, and defend why integrating your component reduces rather than increases the integrator's risk. They own the prototype instrumentation plan — deciding before the pilot what will be measured and how it will be captured.

Proposal and contracts. Owns compliance with the solicitation instructions, the cost volume, and the contract type negotiation. Under FAR-based competition this function is decisive and unglamorous: proposals are routinely eliminated for administrative non-compliance before anyone reads the technical volume. Under OTAs the burden shifts from page-count compliance to negotiating data rights and intellectual property terms, which is a different and arguably harder skill.

Compliance and security. Owns CMMC posture, facility clearances, personnel clearances, export-control review under ITAR, and software supply-chain artifacts including software bills of materials. Treat this as a revenue function with a seat in pursuit reviews, not a back-office cost center, because it gates which opportunities you are even eligible to pursue.

Marketing and demand. Owns the digital surface: technical content that names the mission problem, past-performance pages a program office can actually find, conference presence at the events where your customer set congregates, and the credibility artifacts a skeptical government engineer reads before taking a meeting. In defense the goal is not lead volume — it is being discoverable and credible at the moment a government team is writing a market research memo.

Program delivery. Owns the follow-on. In this market the most reliable source of new revenue is an existing contract executed well, because past performance is scored, referenced, and gossiped about. Delivery leaders should be measured partly on organic growth within their programs.

The interface that breaks most often is capture-to-delivery. A capture team wins on an aggressive technical promise, hands it to a delivery team that was not in the room, and the resulting schedule slip costs the company its most valuable asset in this market: the reputation for doing exactly what it said it would. Force delivery leadership to sign the technical approach before submission, and give them an explicit veto.

Metrics, targets, and realistic ranges

The commercial SaaS metric stack does not survive contact with defense procurement. Monthly recurring revenue, sales-accepted leads, and 90-day sales cycles describe nothing here. What replaces them is a smaller set of pipeline-health and efficiency measures adapted to multi-year capture.

Pipeline coverage against a multi-year horizon. Because awards land irregularly, coverage must be measured against the year the revenue would be recognized, not against a rolling quarter. A pursuit that awards in the fourth quarter of next fiscal year belongs in next year's coverage, and a business that shows healthy total pipeline but nothing awarding in the next four quarters has a bookings cliff that the aggregate number hides. Build the coverage view by award-year buckets.

Probability of win, honestly maintained. Assign a win probability at each gate and force it to move only on evidence: customer access achieved, requirement language shaped, prototype accepted, incumbent weakened. The failure mode is optimism inflation — every pursuit sitting at fifty percent forever. A useful discipline is to require a written justification for any probability above fifty percent that names the specific advantage, and to treat an unshaped requirement on a recompete against an entrenched incumbent as a low-probability pursuit regardless of how much the customer likes you.

Bid-and-proposal cost as a percentage of the resulting award. This is the defense analog of customer acquisition cost, and it is the number that most directly protects the business. Track the fully loaded cost of each pursuit — capture labor, proposal labor, prototype investment, travel, consultants — against the value of what it won, and track it separately for FAR competitions versus OTA and SBIR entries. The two pathways have very different cost structures: a full FAR proposal on a large program can consume a substantial team for months, while a Commercial Solutions Opening response may be a short paper plus a demonstration. If your no-bid rate is near zero, your B&P efficiency is almost certainly poor, because you are funding pursuits you cannot win.

Prototype-to-production conversion rate. For any firm entering through OTAs or SBIR, this is the single most diagnostic metric in the business. Count how many prototypes you completed and how many produced a follow-on contract with a named appropriation behind it. A low conversion rate is not a signal to run more prototypes; it is a signal that transition planning is missing from the front of the motion. Track the reason for each non-conversion — no sponsor, no budget line, technical shortfall, competitor displacement — because the distribution tells you which pillar to fix.

Time from first substantive customer contact to first contract action. Measure this by pathway. It will be materially shorter through prototype and other-transaction vehicles than through full FAR-based source selection, and quantifying that gap in your own historical data is what justifies concentrating effort on the faster pathways.

Compliance readiness as a gating metric. Report the share of your addressable pipeline you are currently eligible to bid given your certification posture, clearance level, and facility status. When that number is well below one hundred percent, the highest-return investment in the company may be a compliance program rather than another capture hire.

Past-performance density. Count contracts completed with documented performance ratings by mission area. This is the asset that compounds, and a deliberate strategy of taking smaller, adjacent work to build a citable record in a new mission area is often better revenue strategy than chasing one large program with no relevant record.

Set targets by pathway rather than in aggregate. A reasonable internal construction is a high no-bid rate on FAR competitions where you lack access, a much higher pursuit rate on prototype vehicles where entry cost is low, and an explicit annual budget for speculative prototype investment treated as marketing spend rather than as pipeline. Publish those targets, review them monthly, and force the pipeline review to talk about evidence rather than optimism.

Where the motion breaks down

Five failure modes account for most of the wasted effort in this market, and every one of them is diagnosable before it becomes expensive.

Proposal-first pursuit. The most common and most costly error is discovering the opportunity when the solicitation posts. By that point the requirement reflects someone's architecture, the incumbent has years of relationship and data, and the evaluation criteria were written with a specific answer in mind. Responding anyway feels like activity and burns real money. The test is simple: if you cannot name the person inside the government who owns the requirement and describe a conversation you had with them before the draft solicitation, you are responding, not capturing, and your probability should reflect that.

Compliance discovered late. Commercial firms entering defense repeatedly build a great product and then find they cannot handle controlled unclassified information, cannot pass a supply-chain review, cannot obtain an authority to operate on the network the customer actually uses, or cannot staff the program because clearance processing takes longer than the period of performance. Each of these is a months-long remediation discovered at the worst possible moment. Run a compliance gate at qualification, not at proposal: what information will we touch, what certification does that require, what network does it run on, what clearances do the delivery staff need, and what export-control review applies.

The pilot with no transition path. A prototype that no one is obligated to fund at the end is a demonstration you paid for. Before signing the agreement, name the program of record or budget line the capability could ride into, name the sponsor who could carry a requirement forward, and understand where you sit in the appropriations timeline. If none of those exist, either build them during the prototype or price the prototype as marketing and expect nothing.

Undifferentiated integration story. With open-architecture mandates spreading, integrators are actively avoiding lock-in. A vendor whose value proposition is a closed end-to-end system is now the risky choice. Firms that publish clean interfaces, conform to the relevant open architecture standards, and make themselves trivially easy to integrate become the low-risk component in someone else's system of systems — and, paradoxically, become very hard to remove once the kill chain depends on them.

Overpromise on schedule. Trust in this market compounds slowly and evaporates instantly. A missed delivery date or a security control that was represented as in place and was not does more damage than losing the competition would have. The structural fix is the delivery veto described above, plus a rule that no capture team may commit to a schedule the delivery organization has not costed.

A sixth, quieter failure mode deserves mention: treating the Department of Defense as one customer. The services, the combatant commands, the defense agencies, the innovation organizations, and the individual software factories buy differently, fund differently, and care about different outcomes. A message tuned to an operational commander focused on time-to-effect and decision advantage will land flat with an acquisition executive whose personal risk is schedule and cost variance. Segment by mission and by buying role, and maintain two translations of the same technical differentiator — one in warfighter language, one in acquisition-risk language.

How to sequence the build

If you are standing up or rebuilding this function, the order matters more than the total investment. Building demand generation before compliance readiness produces interest you cannot legally serve. Hiring capture leads before you have a qualification discipline produces expensive pursuits of unwinnable programs.

The first quarter is foundational and internal. Establish the compliance baseline — determine what information you will handle, what certification level that implies, what export-control exposure exists, and what facility and personnel clearances the work requires — and get an honest remediation estimate. In parallel, build the customer map: which services, commands, agencies, and program offices have a mission problem your capability addresses, and who inside each one owns the requirement, the budget, and the contract. Nothing else in the playbook works without that map.

The second phase is entry-vehicle competence. Assign named ownership for monitoring SAM.gov, Defense Innovation Unit solicitations, SBIR and STTR topic releases, and the consortium vehicles relevant to your mission areas. Write two or three responses even if you expect to lose them, because the organizational muscle for fast, concise, technically specific submissions is built by doing, not by planning. Simultaneously stand up the instrumentation capability: decide how you will capture performance data during an exercise, who owns the data, and how you will secure operator endorsements.

The third phase is proof and evidence. Run one prototype well rather than three badly. Enter it with a written transition thesis, capture quantitative performance data against a realistic mission thread, and collect qualitative endorsement from the operators who used the system — a short recorded account from a user describing how the tool shortened a decision cycle frequently carries more weight with a resource sponsor than any compliance matrix. Package the result as a reusable evidence artifact, not a one-off report.

The fourth phase is ecosystem and scale. Formalize teaming: subcontract relationships with primes that give you access to existing contract vehicles, mentor-protégé arrangements if you qualify, and membership in the consortia through which other-transaction work flows. Participate in the standards and working groups that shape future interface requirements, because influence over an interface specification is durable market advantage. Only now does broad marketing investment pay off, because you finally have past performance and evidence worth being discovered for.

Two sequencing traps are worth naming. The first is hiring senior relationship talent in phase one, before there is anything credible to sell; expensive access burns out quickly when the meetings produce nothing actionable. The second is deferring the instrumentation decision until the prototype is underway, at which point you will produce anecdotes instead of evidence and the transition conversation will be unwinnable.

Related questions

Should a commercial software company pursue defense at all?

Only if it can fund a two-to-three-year runway to first meaningful revenue and absorb compliance investment before any award. The market rewards patience and punishes tourism. Firms that dabble typically spend a year, win a small prototype, and stall at transition.

What is the fastest realistic entry point?

SBIR Phase I or II, a Defense Innovation Unit Commercial Solutions Opening, or an other-transaction prototype agreement through a consortium. All three are faster than full FAR-based source selection and are explicitly designed to lower barriers for non-traditional firms.

How much should we budget for compliance before our first award?

Scope it against what you will handle: controlled unclassified information triggers a materially higher certification burden than public data, and classified work adds facility and personnel clearance timelines measured in many months. Get an assessor's estimate before committing to a pursuit.

Do we need a former government executive on the team?

Access helps but does not substitute for evidence and compliance posture. Hire for it after you have a credible offering and an entry vehicle, not before, and pair the relationship capital with an analytical capture process.

How do we avoid the valley of death?

Name the transition target before the prototype starts: the program of record or budget line, the sponsor who can carry the requirement, and the appropriation that would fund production. If none exist, treat the prototype as marketing spend.

FAQ

How do I find defense contract opportunities before the RFP posts?

Mine budget justification documents, Broad Agency Announcements, SBIR and STTR topic releases, and industry-day materials, then pair that scanning with in-person presence at the conferences where your specific customer set gathers. The signal you want is a mission problem described by a person who owns it, months before a contracting officer formalizes it. Assign named ownership for this monitoring or it will not happen consistently.

What certifications actually gate our ability to bid?

The Cybersecurity Maturity Model Certification program is the central gate for contracts involving covered defense information, with the required level driven by the sensitivity of the information you handle. Quality standards such as ISO 9001 and the aerospace-specific AS9100 are commonly expected in hardware work, and ITAR and broader export-control compliance governs anything with international exposure. Determine your required level before you pursue, not after you win.

Can a small startup realistically win defense work?

Yes, and the on-ramps are well established: SBIR and STTR awards, other-transaction prototype agreements, Commercial Solutions Openings, and subcontracting under a prime that already holds the vehicle. The realistic path is a narrow technical differentiator in an area where incumbents are weak, proven in a prototype, then transitioned. The risk is not winning the first award — it is failing to convert it.

How long does a defense deal take to close?

It varies enormously by pathway and program. Prototype and other-transaction vehicles move substantially faster than full FAR competitions, and a successful pilot can shorten the path to a follow-on award. But the appropriations cycle sets an outer bound: procurement money is requested roughly two years before it is available, so a capability with no existing budget line faces that timeline regardless of how fast the contracting action moves.

How should we price for the Department of Defense?

Match contract type to risk. Cost-reimbursement structures fit high-uncertainty research where the scope will move; firm-fixed-price fits well-defined production where you control the variables. Ground pricing in your actual cost basis, be explicit about assumptions, and frame value as total cost of ownership and mission outcome rather than unit price — but expect cost realism scrutiny, and never bid a price your delivery organization has not costed.

What is the biggest mistake defense contractors make?

Treating compliance as an afterthought and the pilot as the finish line. Both errors have the same root: optimizing for the visible milestone rather than the contractual and budgetary machinery that converts a demonstration into fielded, funded revenue. The second most common is overpromising on schedule, which costs the one asset that cannot be rebuilt quickly in this market — trust.

Sources

• https://www.acq.osd.mil/ — Office of the Under Secretary of Defense for Acquisition and Sustainment
• https://www.diu.mil/ — Defense Innovation Unit
• https://www.acquisition.gov/ — Federal Acquisition Regulation and DFARS
• https://dodcio.defense.gov/CMMC/ — Cybersecurity Maturity Model Certification program
• https://www.sbir.gov/ — SBIR and STTR program portal
• https://sam.gov/ — System for Award Management, official contract opportunities
• https://www.ndia.org/ — National Defense Industrial Association
• https://comptroller.defense.gov/Budget-Materials/ — DoD budget justification materials
• https://www.gao.gov/ — Government Accountability Office reports on defense acquisition
• https://www.pmddtc.state.gov/ — Directorate of Defense Trade Controls (ITAR)

Related on PULSE

• [Inbound demand-capture GTM playbook in 2027](/knowledge/gp0511)
• [Sales-assisted PLG for mid-market in 2027](/knowledge/gp0510)
• [Reseller and VAR channel GTM playbook in 2027](/knowledge/gp0509)
• [International and geo-expansion GTM playbook in 2027](/knowledge/gp0508)
• [Vertical SaaS go-to-market playbook for healthcare in 2027](/knowledge/gp0507)