Selecting design partners for the 2027 renewal season
Eligibility verification infrastructure for public benefits
Awbergov pulls income, household, residency and work-activity facts straight from authoritative sources, with the resident’s consent or the agency’s legal authority, and delivers them as signed, reusable evidence to every program that needs them. Eligible people get through faster. Forged documents have nowhere to enter.
For state agencies, data providers, eligibility platforms, navigators and AI-agent builders.
Why now
Every 6 months
Medicaid expansion adults renew twice a year instead of once, for renewals on or after January 1, 2027.
H.R. 1 §71107 · CMS SMD #26-001
80 hrs / month
Work and community-engagement requirements take effect in most expansion states in January 2027, checked at application and renewal.
H.R. 1 §71119 · CBPP
~10%
of the expansion group projected to lose coverage after the first six-month check, much of it for paperwork rather than eligibility.
CBO, October 2025 estimate
$233B–$521B
GAO’s estimate of annual federal fraud losses across government, fiscal years 2018–2022. AI now forges a pay stub in seconds.
GAO-24-105833
The problem
The same system that keeps honest people out lets fraud in. Both failures come from proving eligibility with paper that is re-collected, re-read and easy to fake.
How it works
Awbergov works as a sidecar. Your eligibility system and rules engine stay in place and keep every decision; we supply the verified inputs.
01
The agency’s system asks for the facts its program needs, and nothing more.
02
We check legal authority and consent, then try the most authoritative, lowest-cost source first: state wage and program data, federal hubs, then consented payroll or gig connections.
03
Each result becomes a signed fact with its source, period, confidence and expiry. Conflicting sources are surfaced, never silently resolved.
04
At the next program or the six-month renewal, fresh facts are reused and stale ones refreshed from source, usually without contacting the resident.
Our commitments
We move and attest facts. Raw source data is kept only as long as needed. There is no central dossier on anyone.
Awbergov supplies verified inputs. Your rules engine and caseworkers make every eligibility decision.
An outage, a missing record or an identity mismatch routes to another evidence path or a person, never to adverse action.
Residents see which program receives which fact, and for how long. They can revoke future access in one step.
No endpoint searches people across programs or states. Every read starts from an existing case and an authorized purpose.
Append-only, tamper-evident logs support notices, appeals, disputes and oversight.
Design partners
We are selecting a small group of design partners. Each one shapes the product and gets early, hands-on implementation from our team.
Pilot automated six-month renewals and work-requirement verification on a defined cohort. We bring forward-deployed engineers and integrate alongside your existing eligibility system.
Discuss a pilotPayroll, gig and consented-income platforms, identity providers and state data partners. Become a source in the network and reach every program through one integration.
Explore a data partnershipEligibility-system vendors, system integrators and open-source teams. Add verified, reusable facts to the systems states already run, without replacing them.
Talk integrationHelp residents enroll and stay enrolled through scoped, delegated access to verified facts, never raw records.
Join the assister programThe pilot
Each phase ends at a gate with measurable criteria. If the evidence does not support moving on, we do not move on.
Weeks 1–4
Data agreements, legal basis for each source, baseline metrics and threat model.
Weeks 5–10
Identity binding, consent, policy enforcement, signed fact schema, audit log and the first source connection.
Weeks 11–16
A second source, the verification API, the caseworker exception panel and fact reuse.
Weeks 17–20
The ex parte renewal workflow, dispute and correction, accessibility review and failure-path testing.
Weeks 21–24
A consented cohort with measured outcomes. No production eligibility decision without your sign-off.
Against your own baseline: ex parte renewal rate, procedural denials, caseworker time per case and the rate of upheld disputes.
Medicaid eligibility-system build work can qualify for a 90% federal match, and operations for 75%. We help structure the work to fit.
Procurement, data agreements and security review can take longer than the build. We start them on day one.
Security and compliance
Moderate baseline, with an isolated cell per state and a state-hosted option.
The security and privacy framework for systems connected to Medicaid eligibility.
Federal tax information stays inside the state’s boundary and never enters the network.
IAL2 identity proofing and passkeys, with in-person and assisted paths for people without smartphones.
The state remains the matching party; we operate under its agreements and purposes.
Plain language, multiple languages and low-bandwidth support for the people these programs serve.
Where we stand: Awbergov is in active development and does not yet hold these authorizations. They shape the architecture from the first line of code, and we pursue them alongside our first pilot.
Talk to the founder
Charles Eghobamien, Founder
I build audit-first software, where every fact has a source, every action is logged, and nothing ships without passing a measurable gate. Awbergov brings that discipline to the evidence behind public benefits.