GovCon Bid and Proposal Insights
GovCon Bid and Proposal Insights
Hybrid Architecture and Development for Experimental Systems (HADES)
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode, we break down the $300M HADES Single-Award IDIQ and what the latest Draft RFP update means for offerors. We cover the newly added Task Order PWSs, notional staffing plans aligned to Sections L & M, and the clarified engagement and Q&A process. You’ll also learn why early feedback to the POCs is critical, as the Draft RFP will be updated on a rolling basis ahead of the Spring 2026 release. If you’re tracking Air Force or Space Systems Command opportunities, this episode gives you the key insights you need without the noise.
Listen now to understand the HADES opportunity and position early.
Contact ProposalHelper at sales@proposalhelper.com to find similar opportunities and help you build a realistic and winning pipeline.
Welcome back to the deep dive. Today we are looking at something that honestly has one of the most intense cinematic names I have ever seen in a government document.
SPEAKER_00:Oh yeah.
SPEAKER_01:It sounds like something pulled straight out of a Marvel movie or a, I don't know, a Greek mythology textbook. We are talking about Hades.
SPEAKER_00:It really is a dramatic acronym, isn't it? Hades. It just conjures up images of the underworld, you know, fire, brimstone.
SPEAKER_01:A free-headed dog.
SPEAKER_00:Maybe a three-headed dog guarding the gates, exactly. Trevor Burrus, Jr. Right.
SPEAKER_01:You hear Hades and you think, okay, this is some kind of doomsday weapon. But then you open the documents, specifically the draft solicitation from the Space Force, and you realize, no, it's actually about infrastructure. Trevor Burrus, Jr.
SPEAKER_00:But incredibly expensive, complex infrastructure. Right. The name actually stands for hybrid architecture and development for experimental systems. And while it's not a doomsday device, it is a massive$300 million effort to completely overhaul how the Space Force handles its ground systems for RD.
SPEAKER_01:Aaron Powell$300 million. That is the ceiling we're looking at here.
SPEAKER_00:Aaron Ross Powell That's the ceiling. It's an indefinite delivery, indefinite quantity contract, an IDIQ.
SPEAKER_01:So a hunting license, basically.
SPEAKER_00:It's a hunting license. The government guarantees they'll spend at least$3 million, but the potential goes all the way up to$300 million.
SPEAKER_01:And the location for all this mythological drama.
SPEAKER_00:Kirtland Air Force Base in New Mexico. That's the heart of the action here. Specifically supporting the innovation and prototyping Delta.
SPEAKER_01:Aaron Powell Okay, so we have the setting New Mexico. We have the stakes$300 million. We have the cool name. But let's unpack the actual what of this. When I see hybrid architecture, my brain immediately goes to like hybrid cars. You know, a little bit of gas, a little bit of battery. Is that what we're talking about here?
SPEAKER_00:Aaron Powell It's actually a really good analogy. But instead of gas and battery, think heavy metal and cloud.
SPEAKER_01:Okay.
SPEAKER_00:The hybrid in Hades, it refers to that friction point between the physical world and the virtual world.
SPEAKER_01:Aaron Powell So blending old school hardware with modern software.
SPEAKER_00:Aaron Ross Powell Exactly. You have the ground system enterprise or GSE. This includes things like big antennas, dishes, physical servers, they call them common user elements. That's the hardware. Right. But the Space Force wants to move the actual control systems, the brains of the operation, into a fully virtualized environment. The source documents describe it as two instances of physical infrastructure hosting fully virtualized instances of ground system software.
SPEAKER_01:Wow. That sounds incredibly complicated to manage. You're trying to run cutting-edge, you know, cloud native software on top of what I assume is some legacy hardware.
SPEAKER_00:Aaron Powell That is the core technical challenge. And they aren't just doing this to keep the lights on. They explicitly want this system to be a test bed. The whole mission is to support the research and development space and missile operations program-RDSMO. They want a partner who can operate the system today, but also use it to test the concepts of tomorrow.
SPEAKER_01:So they want a playground and a fortress at the same time.
SPEAKER_00:Precisely. They want to drive down operations costs, obviously. But they also want to be the viable choice for all new ground command and control programs. They want Hades to be the standard.
SPEAKER_01:Aaron Powell Okay, so that's the big picture. But I want to get into the specific work because when you look at the draft solicitation, they don't just say go build it. They break it down into these task orders.
SPEAKER_00:Right.
SPEAKER_01:And these task orders give us a real glimpse into the day-to-day life of whoever wins this.
SPEAKER_00:Right. With an IDIQ contract, you win the right to compete for work, but the task orders are where the actual work happens. And they've defined the first three right out of the gate. Task order one is pretty standard. Ground control.
SPEAKER_01:The meat and potatoes.
SPEAKER_00:It is. Mission support, travel, paying for other direct costs. It's just the baseline administrative and operational layer.
SPEAKER_01:Okay.
SPEAKER_00:Then you have task order two, which I gotta say has the second coolest name in the document after Hades.
SPEAKER_01:Jaguar.
SPEAKER_00:Jaguar. It just sounds fast, doesn't it?
SPEAKER_01:It really does. We need you to support Jaguar.
SPEAKER_00:It stands for a specific mission support function. We don't have all the classified details from these sources, but it's clearly a distinct, high priority mission. And then task order three is ground support.
SPEAKER_01:Aaron Powell So far, so standard. You've got your admin, your special mission, your support. But then we get to the part of the document that made me stop and actually reread it. It's in section L, the instructions to offerers.
SPEAKER_00:Oh, this part.
SPEAKER_01:The emerging requirements scenario.
SPEAKER_00:Aaron Powell This is so fascinating. This is where the government stops being polite and uh starts playing war games with the contractors.
SPEAKER_01:Aaron Powell It really feels like a simulation. I mean, usually a proposal is just tell us how you'll do the work we listed. But here they are asking you to role-play a crisis.
SPEAKER_00:Exactly. They ask the offerers to simulate a scenario where 12 months into the contract, so you're a year in, you're comfortable, you've got your rhythm, and suddenly a completely new development activity just pops up. A phantom fourth task order.
SPEAKER_01:Surprise mission.
SPEAKER_00:A surprise mission. They call it an emerging requirement. And they don't just want you to say, sure, we'll hire more people. They want a detailed narrative. They want to know exactly how you pivot your staffing. How do you pull engineers off Jaguar without breaking Jaguar?
SPEAKER_01:Aaron Powell And where do you find new people with top seeker clearances in this labor market?
SPEAKER_00:Aaron Powell That's the million-dollar question, isn't it?
SPEAKER_01:Aaron Powell It's a stress test. They are basically asking, what happens when we change our minds?
SPEAKER_00:Aaron Powell It's a test of agility. And just think about what that implies. It implies that the Space Force expects the mission to change. They know the threat landscape in 2027 or 2028 is going to look different than it does today.
SPEAKER_01:Aaron Powell So they don't want a contractor who is rigid.
SPEAKER_00:No, they want a partner who can turn the ship on a dime. And they are judging you heavily on this. It's not a throwaway question. Not at all. No, it's central to the evaluation. If you can't show that you have the processes to handle that pop-up requirement, you aren't winning this contract, period.
SPEAKER_01:Aaron Powell Speaking of winning, let's talk about the proposal itself. Because if I'm a company trying to grab this, you know,$300 million ring, I have to jump through some very specific hoops. And the first one is the page limit.
SPEAKER_00:The 45-page limit on the technical volume.
SPEAKER_01:Aaron Powell That seems incredibly short. I mean, we're talking about a massive hybrid cloud architecture, three distinct task orders, a transition plan, and this emerging requirement simulation. And you have to fit it all into 45 pages.
SPEAKER_00:It is brutally short. And that's by design. The government is tired of reading these 200-page novels full of marketing fluff. They want brevity. They want precision.
SPEAKER_01:It forces you to be disciplined.
SPEAKER_00:Incredibly disciplined. You have to blinkest your own solution, you know, just get to the point.
SPEAKER_01:And it's not just the text. I noticed a very specific and kind of nerdy requirement for how you present your data.
SPEAKER_00:Oh, I love this bar.
SPEAKER_01:They don't just say show us a staffing plan. They demand stacked area charts.
SPEAKER_00:I love this detail. It's in Section L. They specifically require stacked area charts produced in Excel.
SPEAKER_01:Why that specific chart? I mean, why not a bar chart? Why not a table?
SPEAKER_00:Well, think about what a stacked area chart visualizes. It shows layers of volume over time. The x-axis is time months one through 12. The y-axis is total labor hours, and the stacks are the different task orders.
SPEAKER_01:So you can see the geology of your workforce.
SPEAKER_00:That's a perfect way to put it. They want to see the layers. At the bottom, you have the steady hum of task order one, ground control. Then layered on top is Jaguar. And then, and this is the key, they want to see that emerging requirement wedge itself in at month 12.
SPEAKER_01:They want to see the bulge in the chart.
SPEAKER_00:They want to see the surge. If your chart is just a flat line or if the new layer appears without affecting the total height of the chart, they know you're faking it. They want to visually see the ebb and flow of the workforce. It's a lie detector test in Excel format.
SPEAKER_01:That is wild. It really forces you to prove you understand the workload dynamics, and you have to do all this while also explaining how you're going to take over from the incumbent contractor.
SPEAKER_00:The transition plan. Yeah, that's another huge hurdle. You aren't building this from scratch. Someone is running these systems right now. Right. You have to explain how you're going to walk in, take the keys, transfer the passwords, and probably hire a lot of the incumbent staff, all without dropping a single packet of data.
SPEAKER_01:Aaron Powell And the transition period is from fixed price, right?
SPEAKER_00:It is. Which means the risk is entirely on you. If the transition takes longer than you thought or costs more, that comes out of your profit. The government writes one check for the transition and that is it.
SPEAKER_01:And we can't ignore the security aspect here. I mean, we are talking about work ranging from unclassified all the way up to top secret SCI.
SPEAKER_00:That is the biggest bottleneck in the defense industry right now. Clearances. You can have the most brilliant cloud architect in the world, but if they don't have a TSSCI clearance, they can't touch the Hadeus network. Right. Your proposal needs a viable plan for recruiting and retaining these people. And retaining is the key word. Once you have a cleared engineer, everyone else wants to poach them.
SPEAKER_01:Aaron Powell So you've got your stacked area charts, your 45 pages of brilliant pros, your transition plan, and your security strategy. How do they actually grade you? I was looking at Section M, the evaluation criteria, and it seems like they are. They're flipping the usual script on cost.
SPEAKER_00:Aaron Powell They are. This is a best value source selection. And the hierarchy of importance is very telling. Factor one is technical. Factor two is cost price. And the solicitation explicitly states that the technical factor is significantly more important than cost.
SPEAKER_01:Aaron Powell So you can't just be the Walmart of space contract. You can't just come in with the lowest price and expect to win.
SPEAKER_00:In fact, coming in with the lowest price might actually hurt you. It might signal that you don't understand the complexity of the work. The government is signaling they're willing to pay a premium, you know, extra taxpayer dollars for a superior technical approach.
SPEAKER_01:Aaron Powell Let's talk about how they grade that technical approach. They use a color-coded system, right?
SPEAKER_00:Aaron Powell They do. It's the standard Department of Defense palette, but it's worth breaking it down. You have blue, which is outstanding. That means an exceptional approach, multiple strengths, no weaknesses. It's the dream. The dream. Then purple is good, thorough approach, at least one strength. Green is acceptable, yellow is marginal, and red is unacceptable.
SPEAKER_01:And red is basically game over.
SPEAKER_00:It's immediate disqualification. If you get a red in any subfactor, you are unawardable. You don't pass go, you don't collect$300 million.
SPEAKER_01:But there's a nuance here that I think is really important for people to understand. You can have a blue idea, a brilliant idea, and still lose because of risk.
SPEAKER_00:This is the paradox of government contracting. Technical capability and technical risk are graded separately.
SPEAKER_01:Walk me through that. How can I be outstanding and high risk at the same time?
SPEAKER_00:Okay. So imagine you propose a solution for the virtualization that uses some brand new cutting-edge AI coding assistant. It promises to do the work in half the time. It's revolutionary.
SPEAKER_01:Capability-wise, that sounds blue. It's amazing.
SPEAKER_00:Exactly. The evaluators look at it and say, wow, this is an outstanding approach. So you get a blue for capability. But then they look closer. Maybe that software hasn't been security vetted yet. Maybe it relies on a vendor that just started up last week. So they say, we love the idea, but we think there's a high chance it will cause a schedule delay or a security breach. So they slap you with a high risk rating.
SPEAKER_01:And high risk is bad.
SPEAKER_00:It's toxic. You want the golden ticket. Blue capability, low risk. That means we love your idea and we are totally confident you can pull it off without drama.
SPEAKER_01:It seems like that low risk factor is heavily tied to program management. I noticed something interesting in the weighting within the technical factor. Program management is actually weighted higher than systems engineering.
SPEAKER_00:That caught my eye too. Subfactor two, program management, is more important than subfactor one, systems engineering.
SPEAKER_01:That seems backwards for a technical contract. Why would you value the managers over the engineers?
SPEAKER_00:I think it goes back to that emerging requirements scenario. The Space Force is confident that there are plenty of smart engineers out there who can write code. They are not confident that there are partners who can manage the chaos of a shifting mission. They are worried about the coordination, the staffing surges, the agility. They are valuing the conductor more than the violinists.
SPEAKER_01:That is a massive insight. If you spend 40 of your 45 pages talking about how great your code is and only five pages on how you hire and manage people, you're answering the wrong question.
SPEAKER_00:You're missing the point of Hades. Hades isn't just about building a system, it's about managing an evolving enterprise.
SPEAKER_01:Okay, let's shift gears to the financials. We know the ceiling is$300 million, but how does the contractor actually make a profit? It's not a simple fee-for-service model.
SPEAKER_00:No, it's largely a cost plus award fee contract or CTF. This is a very specific structure. In a normal cost plus contract, you get reimbursed for your costs and you get a fixed fee, say 6% profit on top.
SPEAKER_01:But not here.
SPEAKER_00:Not here. In CPF, there is no base fee allowed, zero guaranteed profit.
SPEAKER_01:So you could do the work, get your costs covered, and make zero dollars in profit.
SPEAKER_00:Theoretically, yes. Your entire profit margin comes from the award fee pool. At the end of every evaluation period, the government grades your performance. If you did great, you get a big slice of the pool. If you were mediocre, you get crumbs. And if you failed, you get nothing. It puts a tremendous amount of pressure on performance. It aligns the contractor's bank account directly with the government's happiness.
SPEAKER_01:It prevents the lazy incumbent syndrome.
SPEAKER_00:You have to sing for your supper every single period.
SPEAKER_01:Now there are a few other gotchas in the sort of material, these little logistical hurdles that could trip you up. One of them is the small business requirement.
SPEAKER_00:The 25% rule. This is a hard metric.
SPEAKER_01:That seems like a big chunk. The contract mandates a 25% small business participation requirement.
SPEAKER_00:And it's calculated in a specific way. It's based on the total small business expenditures divided by total labor costs on the labor CLINs.
SPEAKER_01:Z-line ends being contract line item numbers.
SPEAKER_00:Right. So they are looking at the labor bill. They want to ensure that a quarter of that labor value is going to small businesses. And this is crucial. The government explicitly warns against pass-throughs.
SPEAKER_01:What's a pass-through?
SPEAKER_00:That's where you hire a small business just to put their name on the paper, but they don't do any real work. You know, maybe they just print the manuals or do the jitorial services. Got it. Hades says no. They want the work to have complexity and variety. They want small businesses doing the actual engineering.
SPEAKER_01:Which connects back to the innovation goal. Small businesses are often where the risky, cool ideas come from.
SPEAKER_00:Exactly. If Hades is a test bed, you want those hungry startups in the mix. But if you're a big prime contractor, finding small partners who have cleared staff and can handle the technical work, that is a logistical nightmare.
SPEAKER_01:And if you miss that 25% target, it's a pass failgate.
SPEAKER_00:Section M says the criterion is met or not met. If you are not met, you are ineligible for the award.
SPEAKER_01:Brutal. Okay, here's another logistical hurdle that made me laugh just because of how specific it is. The New Mexico twist.
SPEAKER_00:Ugh, the tax clause. This is a classic trap for contractors who aren't from the Southwest.
SPEAKER_01:Usually military bases are federal land, so state sales tax doesn't apply to services.
SPEAKER_00:Usually. But New Mexico is special. They have a gross receipts tax that applies to services, not just goods. And because of the specific jurisdiction of Critland AFB, the solicitation includes a clause requiring the contractor to register with the New Mexico Taxation and Revenue Department.
SPEAKER_01:I can just imagine a proposal manager in Washington, D.C. glossing over that, submitting a price without the tax, and then realizing their profit margin just evaporated.
SPEAKER_00:Or worse, they bill the government incorrectly and trigger an audit. It's a hyper-specific detail, but Section I makes a point to include it. It's another test. Do you actually understand the operating environment?
SPEAKER_01:Aaron Powell And speaking of liability and money, there's one more clause that caught my eye. The high value end item clause.
SPEAKER_00:FAR 52.24624 alternate I.
SPEAKER_01:You know we're deep in the weeds when we're citing FAR clauses, but this one defines a high value end item as anything worth more than$10,000.
SPEAKER_00:Which, in the world of space systems, is basically a toaster.
SPEAKER_01:Right. A single server blade, a specialized switch, a high-end laptop, almost everything they touch is going to be over$10,000.
SPEAKER_00:Exactly. And the clause dictates who pays if that equipment gets broken. Since the contractor is managing common user equipment and government furnished property, they are going to be handling millions of dollars of hardware. If they drop a server rack or if a virtual update bricks a physical antenna controller, the government wants to know who is writing the check.
SPEAKER_01:So bringing this all together, we have a$300 million contract, we have a requirement to blend the cloud with heavy metal. We have to simulate a surprise mission, draw it in Excel with layers, manage a transition, pay New Mexico taxes, and make sure we don't break the expensive toasters.
SPEAKER_00:That sums it up pretty well. Hades is looking for a partner, not just a vendor. They want someone who can handle the technical complexity of virtualization, but also the management complexity of a shifting mission.
SPEAKER_01:It really feels like they are trying to future-proof this enterprise.
SPEAKER_00:They are. The documents repeatedly mention sustainment alongside development. They don't just want to build a new system. They want a system that can evolve. The emphasis on the hybrid concept is key here. They know the future isn't just big iron servers in a basement. It's distributed, it's virtual, it's flexible.
SPEAKER_01:And I think that brings us to the big so what of this entire deep dive. Why does the Space Force care so much about this? Why structure the contract this way?
SPEAKER_00:I think the answer lies in that emerging requirements scenario we talked about. Oh, so look at the waiting again. Technical is more important than cost. Program management is more important than systems engineering. And the core test of program management is how do you handle a surprise mission?
SPEAKER_01:They're buying an insurance policy for the unknown.
SPEAKER_00:Exactly. They know the technology will change, they know the threats will change, they don't know how yet. So they aren't looking for a vendor who can build the system they want today. They are looking for a partner who can build the system they haven't even thought of yet.
SPEAKER_01:That is a powerful thought. If the technical factor is so much more important than cost, they are essentially saying that agility is the single most valuable currency in modern space operations.
SPEAKER_00:It is. In modern space ops, the hardware is almost secondary. The winner is the side that can update their software and reconfigure their ground systems faster than the other guy. Hades is the infrastructure that allows that adaptation to happen.
SPEAKER_01:It's a philosophy of operations disguised as an IDIQ contract.
SPEAKER_00:That is the perfect way to put it.
SPEAKER_01:Well, there you have it. Yeah. From the underworld of Greek mythology to the high stakes, high tech future of Space Force ground systems, Hades is definitely a program to watch.
SPEAKER_00:Absolutely. And remember, if you're writing a proposal, don't forget the stacked area charts.
SPEAKER_01:And pay your New Mexico taxes.
SPEAKER_00:Always.
SPEAKER_01:Thanks for joining us on this deep dive. We'll catch you on the next one.