Understanding AFWERX and Air Force Innovation Ecosystem

Intermediate

afwerx innovation air-force sbir accelerators

Understanding AFWERX and the Air Force Innovation Ecosystem

*Strategic Tier: Tactical Difficulty: Intermediate*

Let me cut through the buzzwords for you.

AFWERX is not a venture capital firm. It’s not a charity for startups. And it’s certainly not a shortcut around acquisition regulations. What AFWERX represents—along with the broader Air Force innovation ecosystem—is a fundamental shift in how the Department of the Air Force identifies, validates, and scales solutions to warfighter problems.

After 25 years in Air Force acquisition, I’ve watched this ecosystem evolve from the fringe “let’s try new things” experiments into a legitimate pathway that moves at the speed of relevance. But here’s what most contractors get wrong: they see dollar signs and program names without understanding the strategic architecture underneath. They treat this like a vending machine—insert pitch deck, receive contract—rather than what it actually is: a relationship-driven pipeline that demands patience, alignment, and genuine partnership.

If you’re approaching AFWERX tactically without understanding the strategic intent, you’re building on sand. Let’s fix that.

Strategic Foundations (Think)

The Philosophy of Innovation Within Constraints

Traditional defense acquisition operates on a “requirements first, solution second” model. Someone identifies a gap, writes a requirement document, funds it through the Program Objective Memorandum (POM) process, and three to seven years later, fielding begins. This works for stealth bombers and nuclear command systems. It fails miserably for software, AI, and technologies evolving faster than the contracting cycle.

AFWERX emerged from a simple, uncomfortable truth: our adversaries don’t wait for our bureaucratic processes to catch up. The Strategic Foundations here rest on three pillars that should guide your tactical approach:

1. Dual-Use Technology Doctrine The Air Force finally recognized that commercial markets often outpace military R&D. The ecosystem isn’t about building bespoke military tech from scratch—it’s about finding what’s already working in commercial markets and adapting it for defense applications. This is “innovation within constraints” in action: leveraging private capital and commercial velocity while applying mission assurance and security requirements.

2. Risk-Tolerance Stratification Understand the difference between AFWERX (experimental, high-risk/high-reward) and traditional Program Offices (low-risk, validated requirements). AFWERX funds failure. Program Offices fund reliability. If you’re bringing unproven technology, you’re talking to AFWERX. If you’re offering incremental improvements to fielded systems, you’re talking to the Program Office. Knowing which ecosystem strand fits your maturity level prevents wasted effort and damaged relationships.

3. The Partner-Not-Product Paradigm This is where values-based decision making enters. The Air Force isn’t buying your widget; they’re buying your team’s capability to solve evolving problems. AFWERX evaluates “team, technology, and transition path”—in that order. If you’re just trying to sell a product, you’ll be frustrated by the constant pivot requirements and user feedback loops. If you’re building a partnership, you’ll see these as force multipliers.

The Ecosystem Architecture Think of the innovation ecosystem not as a single program, but as a funnel with guardrails:

  • Top of Funnel: Spark Cells (grassroots ideation), AFVentures (capital injection), Commercial Solutions Opening (CSO) for rapid requirements
  • Middle: SBIR/STTR Phase I/II (feasibility and prototype), STRATFI/TACFI (Strategic/Tactical Funding Increases)
  • Bottom: Program Office transition, Phase III SBIR, or direct commercial adoption

Each layer filters based on technical merit, mission alignment, and transition probability. Your tactical job is understanding where you fit in this flow and how to move downward through the funnel without falling out.

Operational Leadership (Lead)

Navigating the Web Without Getting Stuck

As an operator in this space—whether you’re a government lead or industry partner—you need to understand the human terrain. AFWERX works because it removes some friction, but it doesn’t remove accountability.

Understand the Buyer’s Dilemma From my time on the government side, here’s the reality: Program Managers (PMs) are evaluated on delivering capability on time and on budget to the warfighter. AFWERX projects are inherently risky. A PM who transitions your SBIR Phase II project into their program carries that risk on their evaluation.

Your operational challenge isn’t technical—it’s risk mitigation. You must prove not just that your technology works, but that transitioning it into a Program of Record (POR) reduces rather than increases program risk. This means:

  • Documenting cybersecurity compliance early (Authority to Operate pathways)
  • Proving integration doesn’t destabilize existing architectures
  • Demonstrating supply chain security (CMMC compliance, domestic sourcing)

The Art of Strategic Patience I see too many companies chase the Phase I check, treat Phase II as a payday, and wonder why they never reach Phase III. This is tactical thinking that kills strategic opportunities.

Strategic patience in this ecosystem means:

  • 18-Month Horizon Planning: If you’re entering an SBIR Open Topic, plan for 18 months minimum before meaningful revenue, and 24-36 months before scale.
  • Relationship Capital: Invest in relationships with both the AFWERX team (who control the funding spigots) and the operational users (who validate the requirement). The former gets you the contract; the latter gets you the transition.
  • Pivot Discipline: When the Air Force user tells you they’re solving a different problem than the one you’re pitching, listen. Operational leaders adapt their technology to the mission, not the mission to their technology.

Managing the AFVentures Relationship AFVentures—the investment arm—isn’t Silicon Valley. They use Other Transaction Authorities (OTAs) and Small Business Innovation Research (SBIR) funding strategically to fill capability gaps, not to generate venture returns. When engaging with AFVentures:

  • Lead with the mission impact, not the market opportunity
  • Understand that dilution concerns are secondary to delivery concerns
  • Recognize that “strategic investment” here means fielding velocity, not equity growth

Leadership Principle: Transparency as Currency In traditional contracting, information asymmetry creates advantage. In the innovation ecosystem, transparency creates trust. When you hit technical roadblocks—and you will—raise the flag early. The organizations that survive Phase II and reach Phase III are those that treated the government as partners in problem-solving, not adversaries in negotiation.

Tactical Execution (Do)

The Step-by-Step Playbook

Enough philosophy. Here’s how you actually execute within this ecosystem.

Step 1: Intelligence Preparation of the Battlefield Before writing a single word of a proposal:

  • Monitor the AFVentures Open Topics (released quarterly). These aren’t generic “we want AI” statements—they’re specific operational deficiencies identified by MAJCOMs.
  • Engage with AFWERX Events (Engage phase). Attend BEYOND, the Virtual Pitch Days, and specific technology area showcases. Your goal isn’t to pitch; it’s to listen. Understand the language operators use to describe their pain points.
  • Map the Customer: Identify the Specific Operational Force (SOF) or MAJCOM (Major Command) associated with your technology area. Build a stakeholder map before you build a slide deck.

Step 2: The Entry Strategy You have three tactical entry points:

Option A: Open Topic SBIR

  • Pros: Broad solicitation, high flexibility, quick turnaround (typically 90 days from submission to award)
  • Cons: Highly competitive (5-10% selection rate), limited funding ($50K Phase I)
  • Execution: Craft your technical volume around the “triple helix”—technical feasibility, operational impact, and transition probability. Use quantitative metrics for impact (hours saved, maintenance reduction, sortie generation improvement).

Option B: Direct to Phase II (D2P2)

  • Pros: Skip Phase I, larger funding ($750K-$3M range)
  • Cons: Requires existing technical foundation (usually previous government funding or significant commercial traction)
  • Execution: You need data. Not projections—actual data from commercial applications or other government work. D2P2 is for derisked technologies entering the military domain.

Option C: STRATFI/TACFI

  • Pros: Scale funding ($3M-$15M+), direct alignment with Program Offices
  • Cons: Requires Phase II completion and validated transition partner
  • Execution: You need a written transition agreement with a Program Office before applying. Start those conversations during Phase II, not after.

Step 3: The Proposal Architecture Don’t write traditional government proposals. AFWERX uses commercial review criteria with military precision.

Your proposal must answer:

  1. The Problem: Quote the user, don’t define it theoretically. “Master Sergeant Johnson at Tinker AFB spends 12 hours manually reconciling…”
  2. The Solution: Show, don’t tell. Videos, prototypes, demonstrations carry more weight than technical jargon.
  3. The Team: Demonstrate past performance in austere environments. Military experience on your team isn’t just nice-to-have; it’s risk mitigation.
  4. The Business: Clear path to scale. How do you survive post-SBIR? Do you have other customers? Can you serve the joint force, or just the Air Force?

Step 4: Execution Discipline (Post-Award) Winning the contract is when the real work starts. Tactical execution here separates the tourists from the craftsmen:

  • Month 1-3: Establish technical performance metrics with your government point of contact. Get specific. “Improve maintenance” becomes “Reduce F-35 ALIS false positive rate by 15%.”
  • Month 4-6: Conduct mid-term reviews with brutal honesty. If you’re behind, say so. If the requirement changed because the warfighter learned something new, adapt.
  • Month 9-12: Build the transition bridge. Start drafting your Phase III strategy. Identify the specific Program Office, the specific funding line, and the specific contracting vehicle (OTAs, FAR-based, etc.).

Step 5: The Cybersecurity Reality You cannot execute tactically in this space without understanding cybersecurity compliance. If your solution touches a network (and they all do), you need:

  • An active NIST SP 800-171 self-assessment
  • A path to CMMC certification (Level 2 minimum for most, Level 3 for CUI)
  • Authority to Operate (ATO) strategy: Platform One, Cloud One, or specific weapon system integration

Failure here kills more innovation contracts than technical failure. Treat cyber compliance as a design constraint, not an afterthought.

Strategic Takeaways

The Craftsman’s Perspective

AFWERX and the innovation ecosystem represent the Air Force’s admission that we cannot out-innovate our adversaries through hierarchy alone. But this system only works when participants understand that innovation is not the absence of discipline—it is discipline applied differently.

Remember these principles:

1. Partners Not Products Your successful navigation of this ecosystem depends on relationships that outlast single contracts. The companies that thrive here are those that embed themselves in operational units, understand that “fail fast” means “learn fast” not “give up fast,” and treat taxpayer dollars with the reverence they deserve.

2. Strategic Patience is a Competitive Advantage The contractors who win Phase III and become “program of record” providers aren’t necessarily the ones with the best technology—they’re the ones who survived the Valley of Death because they planned for 36-month runways, not 6-month sprints. Build your financial and operational models for endurance, not speed.

3. Innovation Within Constraints The regulations haven’t disappeared; they’ve been streamlined. Authority to Operate, export control, fiscal law, and acquisition integrity remain non-negotiable. The craftsmen here are those who innovate within these guardrails, treating constraints as creative forcing functions rather than obstacles to ignore.

4. Values-Based Decisions In a system designed to move fast and break things (or at least bend them), your integrity is your navigation system. Don’t pitch technology you can’t deliver. Don’t promise transition paths you haven’t validated. Don’t treat SBIR as “free money”—treat it as seed capital for national security impact.

AFWERX is a tool, not a solution. The Air Force innovation ecosystem is a pathway, not a destination. Your job is to bring operational discipline to innovative potential, transforming good ideas into fielded capabilities that protect the nation.

Execute with precision. Partner with purpose. And remember: the warfighter at the edge doesn’t need your innovation—they need your solution. Make sure you know the difference.

Dr. Jesse W. Johnson, DSL, MAOM Founder, Craftsman Leadership