Air Force AFWERX

AFWERX is the U.S. Air Force’s way of saying, “We love innovation… and we’d love it even more if it showed up on time, with documentation, and ideally with a test plan.” In plain English, AFWERX is an innovation organization that connects Airmen and Guardians with entrepreneurs, startups, small businesses, academia, and investors to move useful technology from “cool demo” to “real capability” faster than traditional processes typically allow.

If you’ve ever wondered how a commercial drone company, an AI startup, or a scrappy hardware team can end up working with the Department of the Air Force without spending the next decade trapped in an email thread titled “Re: Re: Re: Contracting Question (Final v12),” AFWERX is one of the best answers.

What AFWERX Is (and Isn’t)

AFWERX sits at the intersection of national security needs and the commercial world’s relentless pace. It’s designed to help the Department of the Air Force (DAF) access new technology, new talent, and new funding pathwayswhile giving innovators clearer entry points into defense missions.

AFWERX is not a single magical office that rubber-stamps contracts for any gadget with a futuristic name. It’s a portfolio of programs and pathwayseach with its own purpose, rules, and very real constraints (like budgets, security requirements, and the laws of physics). The goal is to reduce friction, not suspend reality.

The Four “Engines” Under the AFWERX Hood

AFWERX is often described through its major divisions. Think of them as different lanes on the same highwayeach optimized for a specific kind of innovation traffic.

1) Ventures: The Funding & Transition Lane

AFVentures (commonly referred to as the investment arm within AFWERX) is focused on helping the Air Force and Space Force bring in commercially relevant tech and transition it toward operational use. The best-known mechanism here is the SBIR/STTR pipeline (Small Business Innovation Research / Small Business Technology Transfer), which provides non-dilutive funding for R&D and prototypingoften with a strong emphasis on dual-use potential.

Two big ideas show up repeatedly in the Ventures world:

• “Open” vs. “Specific” opportunities: Some pathways invite companies to propose solutions that could help the mission even if they weren’t built for the military originally. Others are tighter, defined problem statements where the government is seeking a narrower solution set.
• Transition planning: In defense, the “prototype” is not the finish line. A strong Ventures project is built with a realistic next step: test, integration, sustainment, scaling, and a customer (or partner) who will actually use it.

Ventures is also where you’ll hear the phrase “Valley of Death”the gap between a successful prototype and a fielded capability. AFWERX invests heavily in bridging that gap through specific programs (more on STRATFI/TACFI below).

2) Spark: Innovation at the Operational Edge

Spark focuses on empowering Airmen and Guardians where the mission happenson bases, in units, in operational teamsby connecting them with innovators and giving them tools to identify problems worth solving. Spark is known for building a network of grassroots innovation communities often referred to as Spark Cells.

In practical terms, Spark helps translate “I deal with this painful workflow every day” into “Here’s a clear problem statement and a path to test a better tool.” It also helps operators get closer to acquisition pathwaysso good ideas aren’t stuck in limbo waiting for the stars to align (and for a meeting invite to load).

3) Prime: Market-Making Programs for Emerging Tech

Prime is about accelerating emerging technology markets by leveraging government resources for risk reduction, learning, and transition. Instead of only funding a single prototype, Prime programs can help create conditions where a whole category of capability can matureby aligning test infrastructure, operational use cases, airworthiness or safety pathways, and partnerships with industry and investors.

A well-known example is Agility Prime, associated with advanced air mobility and electric/hybrid aircraft concepts. Prime’s approach is often collaborative: test, evaluate, reduce regulatory and technical risk, and move toward real use cases rather than endless PowerPoint aerobatics.

4) SpaceWERX: Innovation for Space Missions

SpaceWERX extends AFWERX-style innovation pathways into Space Force priorities. Space missions have distinct constraintsorbital environments, debris, long timelines, unique supply chainsso SpaceWERX creates channels that make sense for the space domain while still leveraging commercial momentum.

One notable space-facing example discussed publicly is Orbital Prime, which has been framed around enabling on-orbit servicing, assembly, manufacturing, and even debris-related capability pathways. The big picture: stimulate a market and transition tech that supports sustainable operations in space.

How AFWERX Turns Ideas into Capabilities

AFWERX is less like a single program and more like a set of “translation layers” between two worlds:

• Commercial innovation: fast iteration, product-market fit, investor timelines, shipping updates weekly.
• Defense capability: mission requirements, safety, cybersecurity, contracting rules, sustainment, and “it must work in the desert at 2 a.m.” constraints.

The core job is to create pathways where these worlds can collaborate without either side losing its mind.

SBIR/STTR: The Front Door for Many Small Businesses

For many startups and small businesses, SBIR/STTR is the first meaningful entry point. It’s structured to fund early-stage R&D and prototypes while encouraging commercialization. In the AFWERX ecosystem, this often comes with additional guidance, topic structures, and transition-focused programs that help connect innovators with real mission partners.

Important timing note: SBIR/STTR policy and authorization can change. For example, AFWERX has publicly noted that as of Oct. 1, 2025, SBIR/STTR authorization expired and certain new activities were paused while ongoing awards remained valid. In other words: always confirm the current status through official channels before building your entire business plan around a deadline you saw on a screenshot.

STRATFI and TACFI: Bridging the “Valley of Death”

STRATFI (Strategic Funding Increase) and TACFI (Tactical Funding Increase) are designed to help scale beyond Phase II-type efforts toward something closer to operational adoption. These programs are especially relevant for companies that have demonstrated technical success and now need resourcesplus committed partnersto move toward real deployment.

A defining feature of STRATFI/TACFI is that they’re built around matching. The logic is simple: if you want to scale, you need more than government enthusiasm. You need committed stakeholdersprogram offices, end users, investors, or other partnerswho will co-invest in getting the thing across the finish line.

In publicly released guidance, STRATFI has been described with funding ranges and matching structures that can require combinations of government and third-party funds. The practical takeaway: STRATFI/TACFI is not “free money.” It’s “shared commitment with receipts.”

AFWERX Challenge: Problem Curation (Because Vague Problems Create Expensive Solutions)

Another visible part of the AFWERX ecosystem is the AFWERX Challenge program, which emphasizes structured collaboration to define problems clearly and match them to potential solutions. Instead of starting with “Here’s a tech,” Challenge efforts often start with “Here’s a mission gap, constraints, and what success looks like.”

Challenge workflows commonly use workshopsoften described publicly as a two-day formatto align stakeholders, narrow the scope, and develop problem statements that can actually be contracted against. This matters because the fastest way to waste money is to fund a solution to a problem nobody agreed on.

Why the Air Force Cares (Beyond the Buzzword Bingo)

AFWERX exists because modern competition moves quicklyand the Air Force needs ways to access technology at commercial speed without sacrificing safety, reliability, or mission fit. A few big reasons it matters:

• Commercial tech cycles are shorter than defense acquisition cycles. Without new pathways, the Air Force risks fielding yesterday’s tools tomorrow.
• The industrial base needs expansion. Defense can’t rely only on traditional primes for every emerging capability, especially in software and fast-evolving domains.
• Transition is the hard part. Prototypes are common; fielded capability is rarer. AFWERX programs put a spotlight on that transition step.
• Talent is a strategic asset. AFWERX creates “on-ramps” for non-traditional innovators and helps Airmen/Guardians become better problem owners and solution evaluators.

Why Startups Care (and Why They Sometimes Get Heartburn Anyway)

From a startup’s perspective, AFWERX can be compelling for a few reasons:

• Non-dilutive capital: Funding that doesn’t require giving up equity can extend runway and validate technical direction.
• Customer discovery with real operators: Few customer interviews are as clarifying as talking to someone whose job depends on the tool working under pressure.
• Credibility and partnerships: A defense customer can unlock additional partnerships, pilots, or investor confidencewhen handled carefully.

But yes, it can come with friction: compliance, cybersecurity expectations, export control sensitivity, contracting timelines, and the requirement that your solution isn’t just “cool,” but usable, supportable, and scalable.

What a Strong AFWERX Pitch Actually Looks Like

Whether you’re approaching a Challenge, a Ventures pathway, or a Prime-style program, the best pitches tend to share the same DNA:

Start with the mission problem (not your features)

• Describe the operational pain clearly, in plain language.
• Define the constraints: environment, connectivity, training time, maintenance burden, safety considerations.
• Explain what “success” looks like in measurable terms.

Show dual-use credibility

• Explain the commercial market traction or pathway (even early signals).
• Clarify why the same tech can reasonably adapt to defense use cases.

Make transition a first-class citizen

• Name the likely adopters or stakeholders (as realistically as possible).
• Outline a test and evaluation plan that produces decision-grade evidence.
• Address integration: data, APIs, cybersecurity, training, sustainment.

Be honest about risks (and how you’ll burn them down)

Defense teams don’t expect zero risk. They expect you to know what the risks areand to have a plan to reduce them without turning the schedule into a museum exhibit.

Specific Examples of AFWERX-Adjacent Innovation in Action

Example: Agility Prime and Advanced Air Mobility

Agility Prime has been publicly described as an Air Force effort to help develop and accelerate an advanced air mobility market, including building a domestic industry and supply chain. That’s bigger than a single prototypeit’s about accelerating a category of capability by aligning test opportunities, use cases, and pathways toward military relevance.

Example: Orbital Prime and Space Sustainability

Orbital Prime has been framed around accelerating capabilities connected to on-orbit servicing and space logistics, with an emphasis on the long-term sustainability of the space domain. That’s a classic Prime-style pattern: create momentum in an emerging market where national security needs and commercial opportunity overlap.

Common Pitfalls (and How to Dodge Them Like a Pro)

Pitfall: “We built a tool. Please find us a mission.”

Solution: Do real customer discovery with operators and mission owners early. Translate your product into a clear operational value proposition.

Pitfall: Overpromising timelines

Solution: Build an incremental plan: pilot → test evidence → integration → scale. Show progress markers you can hit reliably.

Pitfall: Ignoring transition partners

Solution: Identify who would adopt, fund, or sponsor the next step. Programs like STRATFI/TACFI are designed around shared commitmentso you need real partners, not vibes.

Pitfall: Treating cybersecurity as “later”

Solution: Assume you’ll need serious security posture if your solution touches operational data or networks. Bake this into architecture and planning early.

What to Watch Next

AFWERX sits in a dynamic environmenttechnology evolves, missions evolve, policy evolves, and funding authorities evolve. A few trends worth watching:

• Greater emphasis on transition outcomes: The focus is shifting from “how many awards” to “what got adopted.”
• Market-shaping programs: Prime-style efforts often aim to build ecosystems and supply chains, not just fund one-off projects.
• Operationally driven innovation: Spark-style communities continue pushing problem ownership closer to the operational edge.
• Policy and authorization changes: SBIR/STTR and related pathways can be influenced by authorization timelines and legislative actionstay current.

Conclusion

AFWERX is best understood as the Department of the Air Force’s “innovation interface”a set of programs that help translate real operational needs into solvable problems, and translate commercial innovation into usable capabilities. Whether you’re an Airman trying to fix a workflow that’s older than your laptop, or a startup founder hoping to build something that matters beyond quarterly earnings, AFWERX provides pathways designed to move faster, partner smarter, and transition better.

And if you take nothing else away: in the AFWERX world, “innovation” isn’t just invention. It’s invention plus adoptionbecause a brilliant prototype that never ships is just an expensive science fair project.

Field Notes: of AFWERX-Related Experiences (Composite)

These vignettes are composites based on common patterns described publicly across AFWERX-style programsshared to make the process feel real without pretending a single story represents everyone’s experience.

1) The Spark Cell “Aha” Moment: When the Operator Becomes the Product Manager

An NCO walks into a Spark-style session thinking it’ll be another motivational talk with a cool logo and free coffee. Thirty minutes later, they’re standing at a whiteboard explaining a painfully specific problem: a maintenance workflow that requires copying data from one system to another, then “verifying” it by printing it (yes, printing) so someone can sign it, so it can be scanned back into the system. The room goes quietnot because it’s dramatic, but because everyone recognizes the sound of needless pain.

The facilitator doesn’t say, “We’ll build you an app.” Instead, they ask the questions that feel annoyingly basic until you realize they’re the difference between a useful solution and a glittery waste of time: Who uses it? How often? What breaks if it fails? What are the constraints? What does success look like in minutes saved, errors reduced, or readiness improved? By the end, the NCO hasn’t coded anythingbut they’ve done something more rare: they’ve turned a complaint into a problem statement that engineers can actually build against.

2) The Startup Reality Check: “Non-Dilutive” Doesn’t Mean “No Work”

A founder hears “SBIR” and imagines a magical runway extension where the only deliverable is “be brilliant.” Then the first meeting hits: documentation, milestones, security questions, test plans, reporting cadence, and a government teammate who (kindly) asks whether the solution can run in low-connectivity environments because “the cloud” is not always where the mission lives.

The founder learns the AFWERX flavor of customer discovery: a warfighter doesn’t care about your feature list; they care whether it works when they’re tired, under pressure, and operating with constraints you didn’t think to simulate. The best moment comes when an operator says, “This is closeif you change this one thing, it becomes usable.” It’s humbling, and it’s gold. The company ships an iteration, tests again, and suddenly the product roadmap becomes less about “cool” and more about “credible.”

3) STRATFI/TACFI Energy: The Shift from Prototype to Adoption

A small business has a strong prototype and a Phase II-style effort behind it. The tech works. The demos are solid. But everyone keeps asking the same question in different outfits: “Who is paying for this next?” That’s the transition problemthe Valley of Death wearing a business-casual blazer.

In a STRATFI/TACFI-style conversation, the vibe changes. It’s no longer just “prove it works.” It’s “prove it matters enough that multiple stakeholders will match funding and commit.” The company scrambles to align partners: a mission owner who can validate operational need, a program office or unit that can support scaling, and potential outside funding or related commitments. It’s stressfulbecause it forces clarity. But it’s also the moment where a technology stops being a demo and starts acting like a capability in the real world.

4) The Challenge Workshop: Two Days That Save Two Years

In a Challenge-style workshop, people show up with different definitions of the problem. Someone wants speed. Someone wants compliance. Someone wants integration. Someone wants “a dashboard” because dashboards are how grownups cope with complexity. The facilitator pulls the group back to basics: define the mission gap, define constraints, define what success looks like, andcruciallydefine what “good enough to field” means.

By the end, the team leaves with something surprisingly rare: alignment. Not perfect alignment, but enough shared clarity that industry partners can respond with solutions that make senseand government teams can evaluate them without arguing over what they meant in the first place. It’s not glamorous, but it’s the kind of unsexy work that makes innovation real.