How Much Money Did The Obamacare Website Cost? | True Cost

You’ve probably seen claims all over the map. Some say the site was a $5 billion boondoggle; others cite a lower figure. The truth sits between those poles and depends on what you count. This guide lays out the numbers, the scopes they cover, and how the total grew from launch to the first two years.

How Much Money Did The Obamacare Website Cost? Details By Source

Below, you’ll find the headline numbers used by reporters, lawmakers, and auditors. Each line pairs a dollar figure with the part of the program it covers and a clear date window, so you can match claims to what they actually counted.

Headline Figures By Source And Scope

Use this side-by-side to match a claim to what it counted and when.

Source	What It Counts	Amount & Window
CMS testimony to Senate (Sylvia Mathews Burwell)	CMS marketplace IT contracts and interagency agreements	~$834M through Feb 2014
GAO 2014 review	IT obligations across CMS, IRS, and VA tied to HealthCare.gov	~$946M through Mar 2014
GAO contract detail	FFM task order growth	$56M → >$209M (Sep 2011–Feb 2014)
GAO contract detail	Data hub task order growth	$30M → nearly $85M (Sep 2011–Feb 2014)
Accenture letter contract	Continue FFM development and fixes	$91M start; >$175M by Jun 2014
Bloomberg Government analysis	Broader roll-up incl. call center, paper, later fixes	~$2.1B by Sept 2014
State establishment grants (context)	Grants to states for their own exchanges	~$5B total; not HealthCare.gov

What The Different Price Tags Actually Mean

There isn’t a single invoice for HealthCare.gov. The federal marketplace runs on many contracts, systems, and agencies. Some counts include only the core website build under the Centers for Medicare & Medicaid Services (CMS). Others roll in related systems, other agencies’ work, call-center and paper processing, and post-launch fixes. So the answer to how much money did the obamacare website cost comes down to scope.

Here are the most cited price tags and what each one includes. These figures come from official audits and a well-known industry tally.

Can I Trust The Most Quoted Figures?

Yes. Two anchors are widely used. First, CMS told the Senate in May 2014 it had obligated about $834 million on marketplace IT through February 2014. Second, the GAO’s 2014 review reported total IT obligations of about $946 million across agencies through March 2014. A broader Bloomberg Government analysis pegged the combined build, related systems, call-center work, and later fixes at about $2.1 billion by September 2014. Each number is real; each answers a slightly different question.

How The Bill Grew From Launch To Stabilization

The first build relied on two big task orders: the federally facilitated marketplace (FFM) front end and the federal data services hub. Obligations for the FFM grew from $56 million to more than $209 million by February 2014. The data hub grew from $30 million to nearly $85 million over the same period. After the bad launch, CMS moved to a new prime contractor on a $91 million letter contract in January 2014; by June 2014, that work had risen above $175 million as the team repaired and enhanced the system. Add hosting, identity management, testing, and program management, and the picture starts to match the mid-nine-figure CMS totals and the larger multi-agency tallies.

Close Variation: How Much Did Building The Obamacare Website Cost In Total?

When people ask how much money did the obamacare website cost in total, they usually want the broad number. Using that wide lens—website build, supporting systems, other agencies’ work tied to the site, paper processing, and the early fix-it surge—the best known estimate is about $2.1 billion as of late 2014. If you keep the lens tight on CMS marketplace IT only, the early tally sits near $834–946 million through early 2014. Both answers are accurate within their lanes.

Why Estimates Differ By Billions

Scope: Some counts cover only HealthCare.gov code and core CMS systems. Others include the call center, printing and mail, identity proofing, and more. Timing: Report cutoffs differ. A figure that stops in February 2014 will be lower than one extended to September 2014. Ownership: Several agencies contributed pieces, such as the IRS checks that support subsidy eligibility. Contract Type: Many deals were cost-reimbursement, which pay allowable costs as work evolves, creating swings as requirements shift.

What The Money Bought In Plain Terms

The federal marketplace is more than a website. It validates identity, checks income, pings federal and state data sources, calculates tax credits, shows plan options, handles enrollment files, and runs a large help operation. That means spending on the user interface was only part of the bill. The data hub, identity management, hosting, security, and operations made up a big share. The post-launch tech surge and the switch to a new integrator added more. See the HHS OIG case study for a detailed chronology.

Where The Money Went (High-Level Buckets)

Below is a simple map of major cost buckets to help translate contract jargon into everyday categories.

Area	What It Covered	Notes
FFM Front End	User interface, plan display, application flows	Large rework after launch
Federal Data Services Hub	Data checks with IRS, SSA, DHS and others	Grew with more connections
Identity Management	Account creation, identity proofing	Separate vendors and services
Hosting & Capacity	Servers, scaling, monitoring	Boosted during repair period
Security & Compliance	Assessments, fixes, ongoing monitoring	Continuous spend by design
Operations & Maintenance	Bug fixes, small enhancements	Grows as enrollment rises
Call Center & Mail	Phone support, paper processing	Included in broader $2.1B lens
Program Management	Project control, testing, QA	Multiple vendors

Method, Sources, And Limits

This article relies on federal audits and hearing testimony for the narrow CMS figures and on a respected industry analysis for the broader roll-up. Audits and oversight reports pin down obligations through early 2014. The broader roll-up adds other agencies’ pieces and later fixes through September 2014. Totals past that point keep moving as operations continue year to year, but those two early anchors explain why you see both a near-$900 million figure and a near-$2.1 billion figure in print.

Common Questions, Clear Answers

Was it $5 billion? No. That number often mixes in state grants for separate state-run exchanges. Did HealthCare.gov work after the repair? Yes; enrollments surged in later windows. Was waste avoidable? Some, yes. Better requirements, clear leadership, and tighter oversight would have curbed rework. Did costs only cover a website? No; a big slice funded systems and services behind the scenes.

Takeaways If You’re Quoting The Cost

If you need one line, use the broad late-2014 estimate of about $2.1 billion and name the scope. If you prefer the narrow, early view of CMS marketplace IT, cite the $834–946 million range with dates. Either way, add a short scope tag—what’s in and what’s out—so readers aren’t misled.

Timeline: From Contracts To Fixes

2011: CMS issues task orders to build the federally facilitated marketplace and the federal data services hub. Both start as relatively modest awards under a larger contract vehicle. Requirements are still in flux, which makes estimates soft. 2012–mid-2013: Policy work continues while technical work ramps up. Deadlines don’t move, so teams compress testing and integration. Warnings pile up about readiness. Oct. 2013: Launch stumbles. Users hit errors, long waits, and broken flows. Emergency triage kicks in. A cross-agency tech surge forms to stabilize the site. Jan.–Jun. 2014: CMS brings in a new lead integrator on a short-fuse deal, then extends work as fixes and enhancements roll out. Obligations rise to complete deferred functions and harden the stack. Late 2014–2015: Open enrollment runs smoother. Work shifts from emergency repair to steady improvements, operations, and customer support.

Reading The Sources Correctly

When a source quotes $834 million, it’s pointing to CMS marketplace IT obligations through February 2014. That slice lives inside a wider federal effort. GAO’s $946 million takes a broader IT view across agencies through March 2014. Bloomberg Government used a widest lens—adding paper processing and call-center costs tied to the rollout—and extended the window to September 2014. That’s how it reached about $2.1 billion. Each is a fair count for its scope; the mismatch comes when they’re compared without scopes and dates.

What Drove Overruns

Late requirement changes pushed rework. Cost-reimbursement contracts shifted more risk to the government. Testing time got squeezed. Interfaces to many outside data sources added complexity. After launch, the team reordered work, fixed capacity, and rebuilt release practices. That rapid push wasn’t cheap, but it delivered a working enrollment season while longer fixes landed.

Comparisons: Federal Versus State Sites

States that built their own exchanges also spent large sums, funded by federal establishment grants. Those dollars don’t belong in HealthCare.gov’s total, but they often show up in viral claims. That’s how the wrong $5 billion talking point took off. Several states later moved to the federal platform. Their early spend still sits in state-level totals, not in HealthCare.gov’s bill.

How To Cite The Cost In Your Post Or Paper

If you need precision, pair the number with a scope tag and a date window. Here are two safe templates you can reuse without starting an argument: “CMS marketplace IT obligations: ~$834–946 million through early 2014 (agency and GAO).” “Broader federal marketplace build and rollout: about $2.1 billion by Sept. 2014 (industry analysis).” Add a source link for each. That small context cue stops most debates before they start.

Frequently Misunderstood Line Items

Call-center and mail processing costs weren’t website code, but they were integral to getting people enrolled. Identity proofing often sat with separate vendors. Security work, including third-party assessments, lived under other contracts. Those pieces don’t show up if you count only the front-end build. They do show up in the wider $2.1 billion picture.

What This Teaches Large IT Buyers

Freeze must-have scope early. Stage launches and cut scope fast when deadlines loom. Give the integrator clear authority. Use metrics daily. Keep testing time sacred. When dozens of vendors touch one product, handoffs are where quality dies. One owner, one backlog, and a drumbeat of small releases beat giant all-at-once pushes every time.

Why $2.1 Billion And ~$900 Million Can Both Be Right

Think of it as nested circles. The tight circle is CMS marketplace IT. The next circle adds IT work at IRS and other agencies that enable identity and income checks. The widest circle adds paper and phone support tied to enrollment and the months of post-launch repair. Different circles, different totals. When someone quotes only one number without the circle it came from, readers get confused. Add the circle and the date window, and the debate fades.

Citing Dates Matters

A figure through February 2014 misses costs booked in spring and summer that same year. A figure through September 2014 adds the rebuild. Later totals rise with ongoing operations, hosting, and maintenance. Always pair a date cut with the scope so the number stays anchored.