Defense startup go-to-market: landing your first government contract

Most defense tech startups lose their first year not to bad technology but to a bad mental model of the customer. They assume the path runs from a demo to a deal the way it does in enterprise SaaS: meet the buyer, show the product, negotiate terms, sign. Defense procurement does not work that way. The government buyer who attends your demo is rarely the person who controls the budget, writes the contract, or has the authority to obligate funds. Understanding who those people actually are – and how to reach them before the formal procurement cycle opens – is the first and most important go-to-market skill a defense startup needs.

This guide covers the mechanics of landing a first government contract: the cast of characters in a defense acquisition, the contract vehicles that move at startup speed, the innovation units that exist specifically to onboard new technology companies, and the mistakes that trap capable startups in a permanent pilot cycle without ever converting to paid production.

1. who makes the procurement decision

Defense procurement involves at least four distinct actors, each with different authority and interests. Startups that pitch to the wrong one waste months of relationship capital.

The end user is the warfighter, operator, or analyst who will use the system. Their endorsement is necessary but not sufficient. They can create demand signal – telling their chain of command that a capability is needed – but they cannot authorize a contract or reprogram budget. End-user champions are valuable for requirements shaping and for creating internal advocacy; they are not the signature on the contract.

The program manager (PM) or program executive officer (PEO) controls the funded program that would acquire your technology. They have budget authority and requirements ownership. Reaching the PM directly is the goal of every defense sales motion. They are typically accessible at industry days, conferences, and through formal RFI processes – not through cold email.

The contracting officer (CO) is the government official with legal authority to obligate funds and sign the contract. No one else can. The CO interprets FAR and DFARS regulations, validates your cost proposal, and determines what contract vehicle applies. Building a working relationship with the CO before the formal solicitation is open is a significant competitive advantage – they will tell you what proposal elements they care about and what documentation deficiencies kill bids.

The requirements owner – often in the requirements or capabilities office – writes or validates the formal requirements that a program must meet. They translate operational need into technical specifications. If your technology fits an unmet requirement, engaging the requirements owner early can get your capabilities written into the next requirements document, effectively shaping the RFP before it publishes.

2. the valley of death – and why so many startups fall in

The valley of death is the gap between a successful technology demonstration and a funded production contract. It is where the majority of defense tech startups stall and ultimately fail. The pattern is consistent: a startup wins a $500K to $2M pilot, impresses the end users, gets positive program office feedback, and then waits. And waits. The program office wants to proceed but lacks a funded program line. The requirements are not yet formally documented. The budget cycle has passed. Next year's RDTE request is already submitted. The startup burns through cash waiting for a contract that is "coming."

The valley exists because the US defense budget appropriates money in annual cycles, programs of record take years to stand up, and innovation pilots are funded from discretionary accounts that do not automatically convert to production funding. European procurement faces an equivalent gap between EDF project grants and national program adoption.

Surviving the valley requires three things. First, structure pilots with explicit transition criteria written into the agreement – specific performance thresholds that trigger a defined next step or a formal declination. Second, build a parallel contract pipeline: two or three small contracts across different program offices or allied nations provide a revenue bridge across budget cycles. Third, use non-dilutive funding (SBIR Phase II, DIANA, national grants) to extend runway during transition periods. See our defense fundraising capital stack guide for the full non-dilutive toolkit.

3. the fastest paths to a first contract

Not all contract vehicles move at the same speed. The following mechanisms are specifically designed to onboard new technology companies faster than traditional FAR-based acquisition.

Other Transaction Authority (OTA). OTAs are the fastest government contract vehicle for prototype and production agreements. They are not subject to FAR and DFARS overhead, they can be awarded in 60 to 120 days from solicitation close, and they explicitly encourage non-traditional government contractors – companies without prior federal contract history. DIU, AFWERX, NavalX, Army Applications Lab, and SOCOM TCO all execute primarily through OTAs. A well-scoped OTA prototype agreement typically runs $500K to $5M; follow-on production OTAs can reach $50M to $100M+. The OTA process ends with a production contract if the prototype is successful – it is not a dead end.

SBIR/STTR Phase I and II. Small Business Innovation Research grants are non-dilutive funding with a structured path to production. Phase I (typically $75K to $250K, six months) funds feasibility; Phase II ($750K to $2M, 18 to 24 months) funds prototype development; Phase III is commercialization through a follow-on contract with the sponsoring agency. Conversion from Phase I to Phase II runs around 40 to 50 percent across DoD programs. The entire SBIR stack from first award to Phase III production contract is the cleanest non-dilutive funding path available to a US small business.

Government Purchase Card (GPC). Government purchase cards allow contracting officers to buy commercial products and services up to $10,000 per transaction ($25,000 for some categories) without a formal procurement action. This is the fastest possible first revenue: an operator or program office buys software licenses, data feeds, or short-term consulting directly. It does not require a contract vehicle or competition. GPC purchases do not show up in FPDS award databases, but they generate real revenue and real government customers who can advocate internally for a larger follow-on.

Existing IDIQ and blanket purchase agreements. Getting on an existing Indefinite Delivery Indefinite Quantity (IDIQ) contract or Blanket Purchase Agreement (BPA) as a subcontractor to a prime is a common first-contract path. The prime handles contract compliance; you deliver the capability as a subcontractor. The downside is margin compression and limited direct customer visibility. The upside is fast access to funded work without building contract compliance infrastructure from scratch.

NATO procurement and allied nation agreements. European defense startups and companies with NATO-aligned capabilities can engage through NATO Support and Procurement Agency (NSPA) contracts, bilateral defense cooperation agreements, and national ministry direct-buy mechanisms. Allied nation contracts – UK MOD, Bundeswehr, French DGA, and others – follow national procurement rules that vary but often have faster pathways for innovative small suppliers than US federal acquisition. Dual-track pursuit (US and European) doubles the contract pipeline and reduces single-market risk.

4. how to get meetings with the right people

The innovation unit ecosystem exists to create accessible entry points for companies without established defense relationships. These are the organizations designed to hear from startups.

Defense Innovation Unit (DIU) is the DoD's commercial technology transition organization, headquartered in Mountain View, California. DIU publishes active Solicitations and Commercial Solutions Openings (CSOs) at diu.mil. Responses go directly to DIU program managers with technical backgrounds. DIU's process is structured to respond to proposals within 60 days. The primary vehicle is the OTA. DIU specifically seeks non-traditional contractors – companies without prior DoD contract history are advantaged, not disadvantaged, in the selection process.

AFWERX is the Air Force and Space Force innovation unit. It runs multiple parallel tracks: the SBIR Direct-to-Phase II program (skipping Phase I for companies with demonstrated capability), the AFWERX Challenge (a rapid prototype competition), and the AFWERX Spark Cell network, which embeds innovation nodes at Air Force bases globally. AFWERX is the highest-volume innovation unit in DoD by number of contracts; the competition is intense, but so is the volume of available solicitations.

NavalX connects the naval enterprise – Navy and Marine Corps – to commercial technology. NavalX Tech Bridges operate at universities and innovation hubs globally; local Tech Bridge directors are approachable and will facilitate introductions to relevant program offices in exchange for a clear technical brief on your capability.

SOCOM TCO (Special Operations Command Technical Collection Office) and the broader SOCOM acquisition enterprise moves exceptionally fast. Special operations requirements are often classified but the acquisition process for prototype and fielding is designed for speed. Companies cleared to SECRET or above can engage directly; uncleared companies can engage through the TCO for unclassified capability areas.

NATO DIANA is the alliance's dedicated startup accelerator. For companies building dual-use technology relevant to NATO's challenge areas, DIANA cohorts provide structured introductions to defense ministries across 32 member states, compressed into a six-month engagement. A DIANA graduation is a credential that signals alliance-level validation to European national procurement offices. See our detailed DIANA application guide for selection criteria and timeline.

Brave1 in Ukraine offers the fastest procurement cycle of any national defense innovation program. For companies with combat-relevant technology, Brave1 provides direct access to frontline units for operational testing, grant funding from prototype through production, and a validation signal that no laboratory test can replicate. European and allied companies can engage through Ukrainian subsidiaries. See our Brave1 ecosystem overview for current challenge areas and grant sizes.

5. the pilot trap – structuring pilots to lead to programs

A pilot without a transition mechanism is a demo with a longer runway. Too many defense startups accept pilot terms that provide revenue but no structured path to production. The pilot trap closes when: the pilot contract ends, the end users are satisfied, the program office expresses interest in continuing, and then nothing happens for 18 months because no one has budget authority to take the next step.

Structuring pilots to lead to programs requires negotiating specific language before signing. The ideal pilot agreement includes a defined evaluation period with specific performance criteria; a written statement from the program office of the intended follow-on action if criteria are met; a CLIN (Contract Line Item Number) structure that allows exercising options without re-competing; and a transition funding request already submitted in the program office's budget process before the pilot begins.

If the program office will not commit to any of these elements, the pilot is a research exercise – valuable for learning, worthless for revenue planning. Make the distinction explicit before you sign.

6. pricing mistakes that kill defense startups

Defense contract pricing is fundamentally different from commercial SaaS pricing. Three mistakes destroy otherwise winnable proposals.

Underpricing. Government buyers are not rewarded for finding the cheapest vendor; they are rewarded for delivering capability at reasonable cost. A proposal priced below market signals either that the company does not understand its costs or that it will cut corners on delivery. A convincingly priced, well-justified proposal at market rate wins against an unrealistically cheap proposal from a company that appears naive about contract execution.

Forgetting indirect cost accounting. Government contracts require cost proposals that distinguish direct costs (labor, materials, direct travel directly attributable to the contract) from indirect costs (overhead, G&A, fringe). A startup pricing on a commercial hourly-rate basis without a compliant indirect rate structure will fail a DCAA audit and may be found in violation of cost principles. Build cost accounting into your financial systems before the first proposal.

Ignoring unallowable costs. FAR Part 31 defines specific costs that cannot be billed to government contracts: entertainment, certain legal fees, fines, advertising (with exceptions), excessive executive compensation. Billing unallowable costs to a government contract exposes the company to False Claims Act liability – a company-ending legal risk. Know the list before you price.

7. building a capture team on a startup budget

Traditional defense prime contractors staff capture teams of 10 to 20 people for major bids. A defense startup cannot and should not replicate this model at early stage. The minimum viable capture team for contracts up to $5M is three people: a technical lead, a business development lead, and a contracts specialist.

The technical lead – ideally a founder – writes or directs the technical proposal, responds to questions during evaluation, and presents at oral presentations. Technical credibility in front of a government evaluator is the single highest-value input to a competitive proposal. No BD professional can substitute for a founder who built the technology and understands the operational problem it solves.

The BD lead manages relationships with program offices, tracks solicitation pipelines on SAM.gov and equivalent EU portals, responds to RFIs, and attends industry days. This role requires domain knowledge – a BD person who cannot speak fluently about the capability is a liability in front of a technically sophisticated government customer. Defense-specific BD consultants can be engaged on a fractional basis for specific bids rather than hired full-time before revenue justifies it.

The contracts specialist – again, fractional or outsourced is acceptable at early stage – handles cost proposal preparation, terms and conditions review, and compliance with reporting requirements post-award. Government contract terms are not negotiable the way commercial terms are; expertise in interpreting them prevents costly errors.

For contracts above $5M, especially those requiring cost-plus pricing or classified work, supplement the core team with a cleared facility security officer, a DCAA liaison, and a program manager with government contract execution experience. The complexity of executing a $10M+ government contract is fundamentally different from winning it.

8. the 12-month plan: from first meeting to signed contract

The following timeline is realistic for a well-executed first contract pursuit. It assumes a US-eligible company or a company with a US subsidiary. European-only companies substitute DIANA / national innovation agency engagement for SBIR and DIU/AFWERX steps.

Month 1 to 2. Register on SAM.gov (required for any US government contract). Obtain a CAGE code. Identify one primary innovation unit (DIU, AFWERX, NavalX, or similar) whose active solicitations best match your capability. Respond to one open RFI with a two-page capability brief. Register for the next available industry day.

Month 2 to 4. Attend the industry day. Meet the program manager and contracting officer. Submit a SBIR Phase I proposal to the most relevant active DoD topic. Identify a prime contractor whose IDIQ vehicles cover your capability area; initiate a subcontractor relationship conversation.

Month 4 to 6. Respond to the first open OTA solicitation from your target innovation unit. Set up a DCAA-compatible accounting system. Apply to one national defense innovation program (DIANA, AFWERX SBIR Direct-to-Phase II, or equivalent).

Month 6 to 9. Receive SBIR Phase I award or OTA award (typical timelines: SBIR Phase I results in 4 to 6 months; OTA award in 2 to 4 months from close). Execute the pilot or Phase I work with rigor – the deliverables from this period form the evidence base for every subsequent proposal. Document performance metrics against the stated evaluation criteria.

Month 9 to 12. Submit SBIR Phase II proposal (triggered by Phase I success). Negotiate transition criteria into any ongoing pilot agreement. Initiate the next OTA or direct contract pursuit based on the relationship built with the program office during pilot execution. By month 12, a startup following this plan should have: at minimum one active contract generating revenue, one Phase II proposal submitted or under evaluation, and one prime subcontract relationship in progress.

A signed production contract – as distinct from a pilot or SBIR award – typically requires 18 to 24 months from first contact for a company executing well. The 12-month plan is not designed to produce a program of record on month 12; it is designed to have the relationships, credentials, and pipeline depth that make a production contract inevitable in the following 6 to 12 months.

Frequently asked questions

Does a defense startup need a facility security clearance to win a government contract?

Not necessarily for a first contract. Many OTA agreements, SBIR Phase I and II awards, and innovation unit contracts are unclassified or work at the CUI (Controlled Unclassified Information) level, which does not require a facility clearance (FCL). You will need an FCL if the program requires access to classified information at SECRET or above. Obtaining an FCL takes 6 to 18 months; start the process early through your contracting officer or a cleared prime contractor sponsor – not after contract award.

How long does an OTA contract take from proposal to award?

A typical OTA prototype agreement at DIU, AFWERX, or SOFWERX runs 60 to 120 days from solicitation close to award. Follow-on production OTAs can move in 30 to 60 days once the prototype is validated. Compare this to a traditional FAR acquisition, which averages 12 to 24 months. OTA speed is the primary reason innovation-focused DoD units exist.

What is the minimum viable team to compete for defense contracts?

For an OTA or SBIR at the $1M to $5M level: a technical lead who can write and defend a credible technical proposal, a capture manager or BD lead who understands government contracting, and a finance/contracts person (can be fractional) familiar with cost accounting standards. For contracts above $5M requiring DCAA audit, you need formal cost accounting systems in place. You do not need a traditional BD team of 10 people – depth over breadth.

Can a non-US startup win a US government defense contract?

Yes, with constraints. Non-US companies can receive OTA agreements, but full SBIR eligibility requires a US-incorporated entity with majority US ownership. NATO member companies can engage through NATO-aligned procurement programs, and Five Eyes companies (UK, Canada, Australia, New Zealand) have streamlined paths through bilateral agreements. The practical route for most non-US defense startups is a US LLC or C-corp subsidiary with a US-based BD presence.

What is the valley of death and how do startups survive it?

The valley of death is the gap between a successful pilot demonstration and a funded production contract – often 18 to 36 months of proven capability but no recurring revenue. Survival strategies: structure pilots with explicit transition funding requirements in the OTA agreement; pursue parallel SBIR Phase II awards to bridge the gap; maintain non-dilutive grant funding through NATO DIANA or national programs; and build a pipeline of multiple small contracts across services or allied nations rather than depending on a single program.