Eric Glyman's viral thread: put the US government on Ramp to fix $536B in annual waste
Jan 17, 2025
Key Points
- Ramp CEO Eric Glyman frames $536 billion in annual federal waste as a drag problem solvable through spend visibility and controls that private companies already use.
- Glyman's viral argument positions federal software adoption as inevitable, noting the US government processes timesheets on paper while soldiers use personal Google Maps because procurement infrastructure lags enterprise practice.
- Whether federal agencies actually adopt spend-management software hinges on procurement cycles and bureaucratic resistance that dwarf typical enterprise sales, leaving the policy's real-world impact unresolved.
Summary
Eric Glyman's $536B waste thesis: Government needs Ramp's playbook
$536 billion annually. That's the figure Eric Glyman, CEO of Ramp, uses to quantify federal waste—7.9% of the entire US government budget hemorrhaging through Medicare and Medicaid fraud ($100 billion), SBA loan fraud ($200 billion), and improper payments ($236 billion). The thrust of his argument, delivered via a thread that gained substantial traction, is that the US government has a drag problem, not a revenue problem.
Glyman frames the issue through a physics lens: organizations increase velocity by applying thrust or reducing drag. The drag holding back government performance is lack of visibility and control over spend. Private-sector businesses solved this through two mechanisms that translate directly to government: context (understanding exactly where dollars flow) and control (proactively declining out-of-policy spend before the money moves).
The argument is deliberately calibrated to sound absurd before it lands as logical. Glyman opens by noting that a company losing money for 23 years straight and failing seven audits would fire its CFO. The US government has been running that playbook. Half the federal budget deficit goes to interest payments on debt. Yet the tools to stop the bleeding exist. Ramp customers have been using real-time tracking and automated controls for years. The technical implementation is not speculative—it's proven infrastructure applied to a jurisdiction that still processes timesheets on paper and pen.
The implicit pitch is inevitable: if Ramp can reduce drag for enterprises, it can reduce drag for government. The Kamala campaign already used Ramp. Federal adoption, in this framing, is not a question of if but when.
The thread gained traction in part because it started as a joke—"what if we put the government on Ramp?"—before crystallizing into a coherent policy argument. The joke works because there is a real, measurable gap between how Fortune 500 companies manage spend and how the federal government does. A DOD employee filing a receipt likely has no systematic way to categorize it. Google Maps remains a workaround that soldiers use on personal devices because the government hasn't procured mapping tools. The inefficiencies are not theoretical.
What remains unresolved is whether federal adoption would actually materialize and at what scale. Bringing Ramp into the Pentagon or HHS involves procurement cycles, congressional approval, and bureaucratic resistance that dwarf typical enterprise sales. Glyman positions efficiency as a non-negotiable, but government operates under different constraints than markets. Whether software-driven spend controls can penetrate institutional inertia is the real test.