Plaid for Government Benefits: what YC wants and how to validate it
Original request by Gustaf Alströmer, Y Combinator. Source: YC Requests for Startups.
The request in plain English
People applying for government benefits prove the same facts again and again to agencies that do not share data. YC wants a consent-based verification layer that pulls income, tax, and residency records from the source, so one verification works across many programs.
What YC's request says
- Caseworkers still check pay stubs by hand, and AI can now forge them convincingly.
- The GAO estimates federal fraud costs up to half a trillion dollars a year.
- From 2027, states must recheck millions of Medicaid enrollees every six months.
Why now
Two pressures are converging. Document-based verification is breaking, because generated pay stubs and statements are now cheap to fake. And verification volume is about to jump, because Medicaid eligibility checks are moving to a six-month cycle for millions of people.
States need a way to verify more people, more often, with more confidence, without hiring armies of caseworkers. Pulling data directly from the source, with the applicant's consent, solves all three at once.
How the business could work
The Plaid comparison is about the shape of the product: connect once to many data sources, expose a clean API, and charge per verification. The buyers are state agencies and the vendors who build their eligibility systems, which means long sales cycles but very sticky contracts.
The applicant side matters too. If verification is fast and respectful, more eligible people complete their applications, which agencies care about as much as stopping fraud.
Three startup ideas to start from
Income verification for Medicaid renewals
Start with the 2027 six-month renewal requirement and sell automated income checks to the states facing it first.
Verification API for eligibility vendors
Sell to the companies that already build state eligibility systems, so you ride their contracts instead of running every procurement yourself.
Applicant-side benefits wallet
Let people hold verified records and share them with any program, cutting repeat paperwork.
How to validate it before you build
- Map which data sources you can actually reach, such as payroll providers, tax records, and state wage databases, and on what legal basis.
- Interview eligibility caseworkers about how long one verification takes today and how often documents are questionable.
- Find the first states implementing six-month renewals and learn their procurement timelines.
- Run a pilot that measures both fraud caught and eligible applicants retained.
The founder trap
Treating government sales like enterprise SaaS. Procurement, security reviews, and data-sharing agreements take a long time. Plan your runway around the first contract, not the first demo.
IdeaCheck's take
Clear timing catalyst and a real fraud problem. The hard part is data access and procurement, so founders with government or fintech infrastructure experience have an edge.
Test your version
Check your idea against Hacker News
Building something in govtech? See what 28,000 Hacker News threads say before you commit.
Your first evaluation is free with Google sign-in.