SBIR/STTR Phase I: Getting Started with Innovation Funding

Intermediate

sbir sttr innovation funding small-business

SBIR/STTR Phase I: Getting Started with Innovation Funding

Let me be blunt. Most small businesses treat SBIR Phase I like a lottery ticket. They browse topics, throw together a proposal highlighting their cool technology, and pray the government picks them. That’s amateur hour, and after 25 years in Air Force acquisition, I’ve watched that approach waste millions in taxpayer dollars and crush promising companies.

Phase I isn’t a grant. It’s an audition for a strategic partnership. If you approach this tactically—chasing money instead of solving validated warfighter problems—you’ll win occasionally, but you’ll lose systematically. Let me show you how to do this right.

Strategic Foundations (Think): Understanding the Valley of Death

Before you write one word of a proposal, you need to understand why these programs exist. Congress mandated SBIR/STTR because the Department of Defense faces a structural problem called the “Valley of Death”—the gap between basic research (6.1 funding) and operational weapon systems (6.4 and beyond). Brilliant ideas die in this gap because program offices need mature technology, but researchers lack resources to mature it.

Strategic Patience is non-negotiable here. A Phase I award is not a payday; it’s the first step in a three-phased march toward operational capability. Phase I proves feasibility ($50K–$250K, typically 6–12 months). Phase II develops prototypes ($750K–$1.5M, typically 24 months). Phase III is transition to actual programs of record—where real money and longevity exist.

This requires Innovation Within Constraints. Unlike venture capital, where you pitch disruptive solutions to ambiguous problems, SBIR topics derive from validated capability gaps. When AFRL (Air Force Research Laboratory) or NAVSEA issues a topic, it’s not a suggestion—it’s a translation of warfighter pain into technical requirements. Your innovation must fit inside that validated need, not redefine it.

The fundamental truth: SBIR exists to derisk technology for program offices, not to fund your business plan. Keep that distinction razor-sharp.

Operational Leadership (Lead): Partners, Not Products

Here’s what happens inside the acquisition shop. The SBIR Technical Director manages a portfolio of topics derived from actual requiring activities—program offices flying the jets, maintaining the satellites, or defending the networks. They don’t need vendors; they need partners who understand the operational context sufficiently to navigate the Byzantine transition pathways from lab to battlefield.

Buyers Perspective: When I reviewed Phase I proposals at AFRL, I wasn’t evaluating technology—I was assessing transition feasibility. Could this team actually deliver? Did they understand the difference between a laboratory demonstration and an operational prototype? Most importantly, did they treat this as a transactional sale or a capability partnership?

The companies that won consistently—and more importantly, advanced to Phase II and Phase III—understood Partners Not Products. They engaged during the “Phase 0” period before solicitations dropped. They called the technical points of contact listed in the topic descriptions. They asked questions like: “What does success look like for your program office?” not “How do I win this contract?”

This is Operational Leadership—positioning yourself not as a bidder but as a capability extension of the government team. It means understanding that your AFRL technical monitor has annual performance objectives tied to technology transition. Your Phase I success directly impacts their evaluation. Act accordingly.

For STTR specifically, this operational dynamic shifts. You’re not just partnering with the government; you’re contractually marrying a research institution (university, FFRDC, or nonprofit). The government wants to see IP arrangements that enable rapid commercialization, not academic papers. Negotiate these relationships before the solicitation drops, not during proposal writing.

Tactical Execution (Do): Writing to Win

Now we get to the mechanics. This is where most guides start, but without the strategic and operational framework above, you’re building a house on sand.

Step 1: Intelligence Gathering (90 Days Pre-Solicitation)

Don’t wait for the announcement. SBIR topics appear in the DoD SBIR/STTR Prediction system (DSIP) months before formal release. Identify your target topics and conduct Technical Reconnaissance:

  • Call the Technical Point of Contact (TPOC) listed in the topic
  • Attend industry days and “Outreach” events (Air Force, Army, Navy, DARPA)
  • Review the FYDP (Future Years Defense Program) to understand budget realities
  • Map the topic to specific program offices and acquisition strategies

Tactical Note: When you call that TPOC, don’t pitch. Ask diagnostic questions: “What triggered this topic? What barriers prevented previous approaches? What’s the threshold for Phase II invitation?” You’re conducting battlefield reconnaissance, not telemarketing.

Step 2: Architecture of the Winning Proposal

Phase I proposals typically have three components: Technical Approach (10-20 pages), Commercialization Strategy (5 pages), and Cost/Price Volume. Here’s how to execute each:

Technical Approach: This isn’t a research paper. It’s an engineering plan. Structure it as:

  1. Problem Validation: Prove you understand the operational context (use the TPOC’s language)
  2. Technical Baseline: Current state of the art and its limitations
  3. Innovation: Your technical concept with measurable objectives (quantify success metrics)
  4. Feasibility Justification: Why Phase I duration/funding is sufficient to derisk the approach
  5. Phase II Transition Path: Explicit linkage to a program office or operational user

Critical Error to Avoid: Writing about what you want to research instead of what the topic requires. Innovation within constraints means coloring inside the lines while demonstrating technical creativity.

Commercialization Strategy: The government secretly fears “SBIR mills”—companies that live off Phase I/II awards with no intention of fielding capabilities. Your commercialization plan must demonstrate dual-use potential (military and civilian markets) and identify specific transition partners. Name the program office. Name the prime contractor. Name the end user. Vague assertions about “future military sales” signal inexperience.

Cost Volume: Phase I budgets are fixed or analyzed, depending on the agency. Submit realistic costs that reflect adequate effort to achieve objectives, but avoid “gold plating.” Government evaluators know what technical labor costs. If you’re proposing $150K for six months of algorithm development, your labor rates better reflect actual PhD-level engineering, not inflated overhead.

Step 3: STTR-Specific Mechanics

If pursuing STTR, your proposal must document the cooperative research agreement with your Research Institution (RI). The RI must perform 30–60% of the work in Phase I. Tactical Execution Tip: Negotiate IP rights before proposal submission. The government wants clear pathways to data rights; academic institutions want publication rights. Resolve this tension proactively or risk Phase II delays.

Step 4: Review and Red Team

Before submission, conduct a Red Team Review using actual Source Selection Evaluation Board (SSEB) criteria:

  • Technical Merit and Innovation (40-50%)
  • Qualifications of Personnel (20-30%)
  • Commercialization Potential (20-30%)

Have someone outside your technical team—preferably with government acquisition experience—review for “colorful language.” Scientists love words like “novel,” “revolutionary,” and “disruptive.” Acquisition officers see red flags. Use measured, evidence-based language. “Demonstrated feasibility” beats “paradigm-shifting innovation” every time.

Step 5: Post-Submission Engagement

The moment you hit submit, begin Phase I Preparation. If awarded, you have approximately 45 days to negotiate and start. Use this time to:

  • Establish accounting systems compliant with DFARS 252.242-7006 (Cost Accounting Standards)
  • Identify your contracting officer’s technical representative (COTR) relationship
  • Prepare for the Kickoff Meeting (this is your first operational test—fail it, and you’ve lost credibility)

Strategic Takeaways: The Craftsman’s Path

SBIR Phase I success isn’t about grant writing; it’s about strategic positioning within the defense innovation ecosystem. You’ve moved through three tiers to get here:

You Thought strategically about the Valley of Death, recognizing that Phase I is the entry fee to a multi-year capability partnership, not a revenue event.

You Led operationally by engaging as a partner rather than vendor, understanding that your technical monitor’s success metrics align with your transition potential, not your patent portfolio.

You Executed tactically by writing proposals that solve validated warfighter problems within constrained requirements, building the commercialization bridge while maintaining Values-Based Decisions regarding realistic technical approaches and honest market assessment.

Remember: The Air Force doesn’t buy technology; it buys capabilities delivered by trusted partners. Your Phase I proposal is evidence that you understand this distinction. Execute with strategic patience, recognizing that the companies dominating Phase III today endured five years of Phase I and II iterations to become indispensable.

Get out of the lottery mindset. Get into the partnership business. The warfighter is waiting.

Dr. Jesse W. Johnson
Founder, Craftsman Leadership
Doctorate in Strategic Leadership, Regent University
25+ Years, Air Force Acquisition and Innovation