The contract, not the proposal — what changes when you win
A Phase I proposal is a pitch. A Phase I contract is a commitment. Once the contract is signed and the kickoff is scheduled, the firm's obligations shift from marketing to delivery, and the things reviewers cared about during proposal evaluation become secondary to what a contracting officer's representative cares about during execution. Founders who mentally stay in proposal mode after award tend to miss the milestones that actually earn Phase II eligibility.
The first concrete change is that a Technical Point of Contact (TPOC) and a Contracting Officer (CO) are now the decision-makers, not the proposal review panel. The TPOC cares about whether the technical work is meeting the statement of work. The CO cares about invoicing, deliverables, and compliance. Both will be asked months from now whether the firm is funding-worthy for Phase II. Both will remember the early interactions vividly.
The second change is the shift from promise to evidence. Phase I proposals make claims; Phase I execution must produce artifacts that back them. An agency that funded a proposal claiming "we can achieve X performance in six months" will expect to see X performance demonstrated, or a credible engineering explanation for why the target has shifted. Waffling on the claim without replacing it with a better one is the failure pattern that kills Phase II prospects.
SBIR Phase I — Execution Calendar
Standard Phase I deliverables
Three deliverables are common across nearly every SBIR Phase I contract. The first is a final technical report documenting the feasibility work. Report length varies by agency — DoD typically expects 30-60 pages, NIH can run longer, NSF tends to run shorter — but the content is consistent: problem restatement, technical approach taken, results with quantitative evidence, lessons learned, and a Phase II plan.
The second is a prototype or feasibility demonstration. The nature of the prototype depends on the topic. For a software/AI Phase I, it is usually a working prototype with documented inference performance on representative data. For a hardware or materials topic, it is a bench-scale demonstration. For an evaluation or methodology topic, it is a documented test harness with results. Agencies vary on whether they want the prototype delivered as a physical artifact, a GitHub repository, or a recorded demonstration.
The third is a commercialization plan. For a Phase I, this is a lightweight document — typically 5 to 15 pages — describing the target market, the path from prototype to commercial product, the federal transition story, and the funding strategy. Many firms under-invest in this deliverable because they treat it as optional; agencies that run Phase II evaluations rely on the commercialization plan to distinguish between firms with a real business and firms treating SBIR as a research grant.
Government interaction cadence
Reporting cadence varies by agency, with DoD generally running the tightest schedule. A typical DoD Phase I contract requires monthly technical status reports (one to two pages), a mid-point technical review around month three with a presentation to the TPOC and sometimes other program office staff, and the final report and demonstration at month six. NIH tends to require less interim reporting but expects a thorough final report. NSF has its own progress report structure tied to its research management portal.
Beyond formal reporting, the productive firms maintain bi-weekly or monthly unstructured contact with the TPOC — a quick email, a short call, a one-slide update. This is not required by the contract. It is required by the political reality that the TPOC will be asked about the firm when Phase II evaluation happens, and TPOCs who have been kept in the loop give better answers than TPOCs who have not heard from the firm in four months.
The third cadence piece is billing and invoicing with the CO. This is mundane but important. Submitting clean, on-time invoices through the agency's payment portal signals operational competence. Firms that screw up invoicing, miss the required documentation, or bill outside the authorized period of performance land on a CO's problem list, which makes every subsequent interaction harder.
Kickoff meeting: what to bring
The kickoff meeting happens within the first two to four weeks of the contract. It is typically a 60 to 90 minute video call with the TPOC, the CO or a contracting specialist, and possibly additional program office staff. The firm should expect to present its technical approach, its proposed schedule, and its team. The government will describe their expectations for reporting, interaction, and final deliverables.
The most common failure mode is a weak kickoff deck. Firms that show up with the same slides used in a proposal pitch signal that they have not thought through execution. Strong firms show a detailed work breakdown structure, a risk register, concrete milestones tied to the technical approach, and a communication plan. The TPOC is watching for whether this firm will be easy or difficult to work with for the next six months — a well-prepared kickoff is the single biggest signal of easy.
Use the kickoff to ask specific questions: what does success look like to the TPOC at mid-point, what evaluation criteria will be applied at the end, is there interest in extending the scope if Phase I completes early, and who else in the program office should be kept in the loop. The answers shape the rest of the engagement.
The Phase II setup: treat Phase I as a setup exercise
A Phase I that only produces a technical report is wasted. A Phase I that produces a technical report plus a warm relationship with the TPOC, a validated Phase II concept, and sponsor interest is a launchpad. The difference is entirely in how the firm spends months three through six.
The practical sequence: at the mid-point review, surface the Phase II concept as a natural extension of the Phase I results. Ask the TPOC what would have to be true for them to support a Phase II application. Ask what other program office stakeholders would need to be involved. Ask whether there are adjacent topics or follow-on opportunities within the same portfolio. Each of these questions signals that the firm is serious about transition, not just about finishing the current contract.
By month four, the firm should have a Phase II concept document that the TPOC has seen and commented on. By month five, a Phase II proposal should be in draft. By month six, the proposal should be ready to submit whenever the Phase II window opens. Firms that wait until after the final report to start Phase II preparation usually miss the Phase II submission window and lose six to twelve months of momentum.
Commercialization plan requirements
Agencies evaluate commercialization plans more rigorously than most first-time proposers realize. SBA requires a commercialization plan for Phase II applications, and the plan's quality influences the Phase II decision. A weak commercialization plan is a common reason for Phase II rejection even when the technical work is strong.
The components agencies look for are the market analysis (who buys this, how big is the market, what is the competitive landscape), the federal transition pathway (which programs of record, which agency customers, which contract vehicles), the funding strategy (next SBIR phase, non-SBIR federal, private capital, revenue), and the intellectual property position. For AI/ML firms, the IP question is particularly important — what is proprietary, what is open-source, and how is the moat defensible.
The tell for a weak commercialization plan is generic language. "The global AI market is expected to grow at 35% CAGR" is a red flag. The market analysis must be specific to the capability being developed and the agency being served. A plan that names the program office, quotes the total obligation authority for the relevant program line, and specifies the transition contract vehicle is much stronger than one that gestures at a large addressable market.
Common execution mistakes that kill Phase II funding
Five failure patterns recur across rejected Phase II applications. First, silence: the firm does not keep the TPOC informed, and the TPOC has nothing to say when asked about the firm. Second, surprise results: the firm discovers mid-contract that the technical approach is not viable and does not tell the TPOC until the final report. Third, scope creep from the firm: the firm decides to expand scope without TPOC concurrence and ends up with an incoherent final report. Fourth, weak commercialization story: the technical work is good but the plan for what comes next is hand-waving. Fifth, poor contract hygiene: late reports, miscoded invoices, confused milestones.
All five are avoidable. All five are more common in first-time awardees than in repeat awardees. The firms that treat Phase I as a fully-structured operational contract — with its own project plan, risk register, and stakeholder engagement cadence — do not fall into these traps. The firms that treat it as a research grant with a due date do.
What the final technical report must contain
The final technical report is the durable artifact of Phase I. It is what the agency will read during Phase II evaluation and what future program offices may read when considering the firm for new opportunities. Its contents should include: an executive summary (one to two pages); a restatement of the problem and Phase I objectives; the technical approach actually taken (which may differ from the proposed approach — note the differences and why); quantitative results with data tables and figures; a discussion of limitations and risks; lessons learned; and the Phase II plan.
The Phase II plan section is the most leveraged part of the report. It should outline the specific technical work Phase II would undertake, the resources required, the transition path, and the proposed budget. A strong Phase II plan in the final report signals to the TPOC that the firm is ready to continue, which makes the Phase II application feel like a continuation rather than a new request.
Bottom line
Phase I is the audition for Phase II. Firms that understand this run the contract as a structured engagement — clear milestones, steady communication, explicit Phase II positioning, rigorous final deliverables. Firms that do not understand this produce a technical report, submit it on time, and wonder why Phase II did not happen. The difference is not luck. It is the same discipline that wins Phase I applied to the ten weeks after the award.
Frequently asked questions
Three items: a final technical report of 30 to 80 pages, a prototype or feasibility demonstration appropriate to the topic, and a commercialization plan. Some agencies add interim status reports and a mid-point briefing. The combination is what gates Phase II eligibility.
Most DoD contracts require monthly one-to-two-page status reports plus a mid-point technical review at month three. NIH and NSF report less frequently but expect thorough final reports. TPOC communication should run bi-weekly to monthly regardless of formal reporting.
Month 4 of a six-month Phase I. That gives two months of parallel work and matches typical Phase II submission windows. Starting later usually means missing the window entirely and losing six to twelve months of momentum.
Tell the TPOC early, document the pivot, and use the Phase I to demonstrate a better approach if one is available. A Phase I that admits a negative result clearly is stronger for Phase II than one that hand-waves the failure.
Yes, most agencies allow no-cost extensions of a few months if the technical work needs more time, subject to CO approval. Scope extensions with additional funds are rarer at Phase I but not unheard of.