Mapping the players who actually run a public sector market

2. Challengers. Newer entrants or smaller specialist firms trying to unseat incumbents, often on cost, technology, or user experience. Think Deloitte-adjacent boutique consultancies, or newer platform players like Softheon or CareJourney, that pitch modern cloud-based alternatives to legacy mainframe systems. Challengers rarely win the whole contract; they win pieces, then expand.

3. Systems integrators (SIs). Firms that stitch together multiple vendors' software, data, and hardware into one working system. Accenture, IBM, and Deloitte again play this role. The SI role matters because Medicaid IT is never one product, it's dozens of modules (eligibility, pharmacy benefits, provider enrollment) that must talk to each other. Whoever holds the SI contract has outsized influence over which sub-vendors even get considered.

4. Suppliers and subcontractors. Smaller specialist firms providing a slice: a data analytics module, a call center, a cybersecurity layer. They depend entirely on being selected by the prime contractor (the company holding the direct contract with government). Margins here are thinner and relationships more fragile.

5. Oversight bodies and regulators. In US Medicaid IT, this means the Centers for Medicare & Medicaid Services (CMS), the federal agency that co-funds and approves state Medicaid systems, state legislatures that appropriate budgets, state procurement offices that run the bidding rules, and inspectors general who audit for fraud or waste. CMS enforces the Medicaid Information Technology Architecture (MITA) framework, which sets technical standards states must meet to get federal matching funds. This is the single most powerful lever in the whole ecosystem: CMS can withhold funding approval and freeze a project entirely.

Why incumbents usually win, even when they underperform

This is the counterintuitive part non-technical audiences often miss: performance and contract renewal are only loosely connected in public sector markets.

Three structural reasons:

• Switching cost. Ripping out a Medicaid eligibility system that touches millions of beneficiaries is riskier than tolerating a mediocre one. Agencies fear a botched transition more than they value an upgrade. This is the same logic that kept Californias' vendor entrenched for years despite visible failures.
• Procurement complexity. Public RFPs can take 12 to 24 months to draft, bid, and award. Only firms with dedicated proposal-writing teams and past-performance references can realistically compete. That filters out most challengers before technical merit is even scored.
• Relationship capital. Incumbent staff often sit inside agency buildings, attend budget meetings, and shape how the next RFP's requirements get written. That is not corruption, it is standard practice, but it means incumbents frequently help draft the specifications they will later bid on.

Challengers break in mainly through three doors: a highly visible incumbent failure (like California's), a legislative mandate for modernization, or a federal push (CMS has, for instance, pushed states toward modular, cloud-based procurement instead of one giant monolithic contract, which lowers the entry barrier for smaller firms).

Where the margin actually sits

Value in this chain is distributed unevenly, and it maps directly to risk-bearing and switching cost, not to who does the most technical work.

| Player | Typical role in value chain | Margin position |

|---|---|---|

| Prime contractor / SI | Owns client relationship, contract risk | Highest, captures markup on subcontractor work |

| Incumbent software vendor | Licensing, maintenance fees | High, recurring revenue, low churn |

| Specialist subcontractor | Delivers a module or service | Thin, competitive, replaceable |

| Staffing/labor subcontractor | Provides bodies (developers, call center staff) | Lowest, commodity pricing |

| Oversight body | Sets rules, approves funding | Captures no margin, but controls the gate |

The prime contractor's advantage is structural: they hold the contract vehicle (the legal mechanism through which government buys), so every subcontractor's invoice runs through them, often with a markup of 10 to 20% for management overhead (this is a commonly cited industry range, treat it as an estimate, actual rates are negotiated per contract and rarely disclosed publicly).

Competitive dynamics: it's not a market, it's a relationship system

In private markets, competitors fight on price and features continuously. In public sector markets, competition is episodic: it happens at the RFP moment, then goes dormant for the 5 to 10 year life of the contract.

This changes strategy completely. Firms don't compete for market sharemarket shareThe percentage of total industry sales your company captures in a given period. It measures competitive position relative to rivals in a defined market.Voir la définition complète → day to day, they compete to:

1. Shape requirements before the RFP is published (via industry days, requests for information, informal agency briefings).

2. Win the incumbency, because incumbency itself becomes the strongest asset for the next cycle.

3. Position as the "safe" bidder for risk-averse procurement officers, who are personally and professionally exposed if a project fails publicly.

This is why so much of public sector business development budget goes into relationship building and past-performance documentation rather than product innovation. A firm's SAM.gov registration and past contract record (the federal government's central vendor database) often matters more to winning than a superior technical solution.

🎬 [VIDEO: "How Government Contracts Actually Work" - https://www.youtube.com/results?search_query=how+government+contracts+work - search for explainer content on federal/state procurement mechanics, useful as a visual companion to RFP and contract vehicle concepts]

Reading the power mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.Voir la définition complète → for any public sector deal

When you're assessing a new market, whether it's Medicaid IT, transit signaling, or school lunch procurement, ask five questions in order:

1. Who holds incumbency now, and how long is left on their contract? Contract expiration dates are usually public record in state procurement portals.

2. Who controls the RFP drafting process? Look for "requests for information" (RFIs) issued months before the RFP, they signal who's shaping requirements.

3. What does the oversight body require? For Medicaid, check whether CMS has flagged the state's system for MITA compliance gaps, that is where mandated change originates.

4. Where does the money actually flow? Look at the prime/subcontractor structure in the awarded contract (often published as part of transparency requirements) to see who captures margin.

5. What triggered the last vendor change, if any? A pattern of failure-driven switches (like California's) tells you the market only opens episodically, not continuously.

Key Takeaways

• Public sector markets have five recurring player types: incumbents, challengers, systems integrators, suppliers/subcontractors, and oversight bodies (like CMS for Medicaid). The names change by sector, the structure doesn't.
• Incumbents win renewal far more often than performance alone would predict, because switching costs, procurement timelines, and embedded relationships favor them structurally.
• Margin concentrates with the prime contractor/systems integrator, who captures markup on subcontracted work; specialist and staffing subcontractors operate on thin, commodity-like margins.
• Competition is episodic, not continuous: it flares at the RFP moment and then goes dormant for years, so real strategy happens in shaping requirements before the bid, not in the bid itself.
• Oversight bodies hold no margin but control the gate: agencies like CMS can freeze funding and force modernization, making them the most underrated power center in the whole chain.