The Life and Death of Direct File [pdf]

Original Article ↗ Hacker News Discussion ↗

A detailed post-mortem of the IRS’s Direct File pilot sparks debate over whether government should run free tax-filing services or leave them to private vendors like TurboTax. Commenters argue about the program’s apparent success versus its high per-return pilot costs, the political and lobbying pressures that helped kill it, and the broader “buy vs. build” bias in U.S. federal IT. Underneath is a deeper clash over trust: some see a conflict of interest in the tax collector also preparing returns, while others view reliance on profit-driven intermediaries as more exploitative and less efficient.

Perceived success and demise of Direct File

  • Several commenters see Direct File as a clear success: rare example of competent government software, good UX, and strong user satisfaction.
  • Others argue “there isn’t much to study” because it was killed for political reasons unrelated to merit.
  • Strong sentiment that it was ended due to lobbying from tax-prep companies or political actors threatened by its success.
  • A minority view argues its termination was appropriate because it exceeded what Congress actually authorized.

Legal authority, process, and “nation of laws”

  • Congress authorized a study, not a full production system; critics say allowing real taxpayers to use it violated statutory limits and budget intent.
  • Supporters counter that focusing on process over outcome ignores that the government demonstrably can deliver valuable services.
  • Multiple examples are cited where congressionally mandated programs were later gutted or ignored, suggesting legal mandates alone don’t protect projects.

Costs, scale, and economics

  • One analysis claims ~$226 per filing vs ~$40 via private software, arguing Direct File cost more taxpayer money than it saved.
  • Others respond this is a pilot artifact: one-time build costs dominate; per-filing cost would drop sharply at scale.
  • Some note additional 2025 spending and limited user counts, arguing the metrics don’t yet “sell” the project and that politics dominate perception.

Government vs. private provision

  • One camp: government shouldn’t run digital services; contract everything out to competitive vendors to control costs.
  • Opposing camp: contracting often leads to inflated bills, perverse incentives, and worse outcomes; government can and does run major infrastructure well.
  • Examples raised on both sides: healthcare.gov failures, mega‑project successes, contractor overbilling, municipal services, and public transit.

Trust, conflict of interest, and user autonomy

  • Critics worry about conflict of interest: the tax collector also preparing your return, potentially nudging unfavored groups into higher liabilities or missed credits.
  • Supporters argue private tax-prep firms have an even clearer profit motive and have lobbied to keep filing complex.
  • Some see prefilled or direct filing as especially valuable for low-income filers who otherwise lose a significant share of refunds to preparer fees.
  • General split between deep distrust of the IRS/government and those who see that distrust as excessive and exceptional compared to other countries.