Teh Air Force’s Software Acquisition Roadblock: Why More Contracts Aren’t the Answer
The Air Force recently issued guidance aiming to streamline software acquisition. However, this well-intentioned effort risks adding more complexity to an already burdened system, potentially hindering the delivery of crucial capabilities to the warfighter. As someone deeply involved in helping companies navigate the federal market, I believe a rollback is necessary.
The core issue isn’t a lack of rules, but an overabundance of them – and a prioritization of process over results. We need to empower those on the ground, not tie their hands with more mandatory contracts.
The Problem with Perpetual Contracting
The current trajectory feels deeply concerning. The idea that achieving desired outcomes requires more contracting actions should be a red flag for every American. As alexis Bonnell points out, constantly adding “just one more form” demonstrates a basic disrespect for the time and dedication of our people.
This isn’t about avoiding accountability; it’s about recognizing the inherent inefficiencies of a system already choked by bureaucracy.
A Smarter Approach to Software Procurement
So, what can be done? Here are three key areas for enhancement:
- Consumption-Based Pricing: A Good Start, But Not the Only Way. Offering consumption-based pricing for Software-as-a-Service (SaaS) is a positive step, and thankfully, it’s already happening. However, it shouldn’t be the only option.
* Some software licenses, like Microsoft Office, offer lasting value without expiration.
* Early-stage pilots often haven’t defined a clear unit of consumption or value.Forcing this prematurely stifles innovation.
* rather, equip contracting and program officers with the tools to choose the right approach based on specific circumstances. Training is paramount.
- Eliminate Software Duplication - Empower, Don’t Restrict. The obligation for avoiding redundant software purchases lies with the requirements owner and program manager. They need the resources to determine if a need already exists within the government’s existing inventory.
* AI-powered tools can significantly simplify this process.
* Focus on equipping these individuals to make informed decisions, rather than limiting them to a narrow range of contracting vehicles.* The guidance likely aims to improve enterprise visibility of existing SaaS products, but mandating contract formats risks recreating the very problems it intends to solve.
- Drop the Progress Prohibition. The current ban on development within contracts is counterproductive. Requiring written approval from the contracting officer’s representative before charging for new features is a reasonable compromise.It provides oversight without stifling agility.
Prioritizing Outcomes Over Process
The Air Force’s aspiration to deliver value through modern software acquisition is commendable. But this guidance, while well-intentioned, threatens to undermine that goal.Adding another layer of mandatory contracts simply introduces more red tape and complexity.
This exemplifies a larger issue: a persistent focus on rigid processes instead of meaningful outcomes. Warfighters, industry partners, and taxpayers deserve better.
An immediate rollback of this guidance is crucial.Let’s empower our teams to deliver the innovative solutions our nation needs, without drowning them in unnecessary bureaucracy.
Noah Sheinbaum is the founder of Frontdoor Defense, a research and advisory company, and STEAM Studio, a media production company. He explores the challenges and triumphs of companies navigating the federal market through his podcast, crossing the Valley.
image: Senior Airman Elizabeth Figueroa via DVIDS