Decision Memo

Benefit check bot

Record the team verdict, rationale, and reviewer leans locally, then print or share a source-anchored memo.

Markdown export

Agent and email version.

# Decision Memo: Benefit check bot

Full report: https://ideanavigatorai.com/ideas/benefit-check-bot/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Research (51/100)
- Confidence: 55%
- Recommendation: Keep this parked until the team has evidence for the next validation step: Recruit 5-10 benefits navigators at FQHCs or community nonprofits in two states to run the bot on 100+ real client intakes over 4-6 weeks. Measure whether it cuts average screening time versus their current process, the share of clients identified as likely eligible for at least one program they were not already enrolled in, and navigator-rated accuracy against a manual check. Target a willingness-to-pay signal: at least 3 orgs agreeing to a paid pilot.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies
- Market: Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC
- Problem: Over $100B in benefits low-income families qualify for goes unclaimed each year because eligibility rules are fragmented across federal, state, and county programs, applications are long and document-heavy, and frontline navigators screen clients manually one program at a time. Caseworkers at clinics and nonprofits lack a fast, accurate way to tell a client in minutes which of dozens of programs they likely qualify for and how much money is on the table.
- Thesis: Benefit check bot should be tested as a narrow first-win workflow for Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies.
- Source: https://codeforamerica.org/news/eitc-with-getctc/
- Source: https://www.irs.gov/pub/irs-soi/24rpeitcunderclaims.pdf
- Source: https://frac.org/blog/the-snap-gap-a-state-by-state-glance
- Source: https://www.pew.org/en/about/news-room/opinion/2024/08/06/benefits-data-trusts-closure-should-prompt-us-to-rebuild-the-flawed-public-benefits-system
- Source: https://aspe.hhs.gov/reports/web-based-benefit-access-tools-mitigating-barriers-special-needs-populations-0

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 5.9/10 (24% weight)
Demand looks thin because the report has 5 source-backed signal(s), an editorial confidence of 55/100, and a defined buyer in Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC.

- More than $100B in government benefits available to low-income families goes unclaimed annually, including $15B+ in SNAP and $10B+ in EITC (Code for America / Frontdoor reporting).
- Target buyer: Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies

### Problem severity - 6.3/10 (22% weight)
Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

- Over $100B in benefits low-income families qualify for goes unclaimed each year because eligibility rules are fragmented across federal, state, and county programs, applications are long and document-heavy, and frontline navigators screen clients manually one program at a time. Caseworkers at clinics and nonprofits lack a fast, accurate way to tell a client in minutes which of dozens of programs they likely qualify for and how much money is on the table.
- More than $100B in government benefits available to low-income families goes unclaimed annually, including $15B+ in SNAP and $10B+ in EITC (Code for America / Frontdoor reporting).

### Willingness to pay - 5/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- B2B2C SaaS: per-seat or per-screening subscriptions for clinics, health systems, and nonprofits; tiered pricing by program coverage and volume; white-label API licensing; and outcome-based contracts with health plans/Medicaid MCOs that benefit from members staying enrolled
- Recruit 5-10 benefits navigators at FQHCs or community nonprofits in two states to run the bot on 100+ real client intakes over 4-6 weeks. Measure whether it cuts average screening time versus their current process, the share of clients identified as likely eligible for at least one program they were not already enrolled in, and navigator-rated accuracy against a manual check. Target a willingness-to-pay signal: at least 3 orgs agreeing to a paid pilot.

### Competitive saturation - 3.9/10 (18% weight)
Competitive room is reduced by 3 recorded alternative(s); the wedge must stay narrow and differentiated.

- Recorded alternative: mRelief — SNAP screening and application assistance
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 4/10 (16% weight)
Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.

- Recruit 5-10 benefits navigators at FQHCs or community nonprofits in two states to run the bot on 100+ real client intakes over 4-6 weeks. Measure whether it cuts average screening time versus their current process, the share of clients identified as likely eligible for at least one program they were not already enrolled in, and navigator-rated accuracy against a manual check. Target a willingness-to-pay signal: at least 3 orgs agreeing to a paid pilot.
- Eligibility rules vary by state, county, and program and change frequently; maintaining accurate, to-the-dollar rules engines across jurisdictions is costly and a liability if estimates are wrong.

## Market gap
Underserved segments:
- Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Promising enough to test, not strong enough to build broadly.

Blind spots:
- Eligibility rules vary by state, county, and program and change frequently; maintaining accurate, to-the-dollar rules engines across jurisdictions is costly and a liability if estimates are wrong.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Benefit Check Bot checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: Benefit check bot focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.

Print-ready memo

Decision Memo: Benefit check bot

Team verdict: Park
Validation verdict: Research / 51/100
Confidence: 55%
Recorded: Not recorded

Recommendation

Keep this parked until the team has evidence for the next validation step: Recruit 5-10 benefits navigators at FQHCs or community nonprofits in two states to run the bot on 100+ real client intakes over 4-6 weeks. Measure whether it cuts average screening time versus their current process, the share of clients identified as likely eligible for at least one program they were not already enrolled in, and navigator-rated accuracy against a manual check. Target a willingness-to-pay signal: at least 3 orgs agreeing to a paid pilot.

Team rationale

No team rationale recorded yet.

Reviewers

No named reviewers recorded.

Source anchors

Buyer: Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies
Market: Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC
Problem: Over $100B in benefits low-income families qualify for goes unclaimed each year because eligibility rules are fragmented across federal, state, and county programs, applications are long and document-heavy, and frontline navigators screen clients manually one program at a time. Caseworkers at clinics and nonprofits lack a fast, accurate way to tell a client in minutes which of dozens of programs they likely qualify for and how much money is on the table.
Thesis: Benefit check bot should be tested as a narrow first-win workflow for Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies.

Validation rubric

Demand signal

24% weight

5.9/10

Demand looks thin because the report has 5 source-backed signal(s), an editorial confidence of 55/100, and a defined buyer in Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC.

Problem severity

22% weight

6.3/10

Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

Willingness to pay

20% weight

5/10

Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

Competitive saturation

18% weight

3.9/10

Competitive room is reduced by 3 recorded alternative(s); the wedge must stay narrow and differentiated.

Feasibility

16% weight

4/10

Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.

Market gap

Underserved segments

Healthcare systems, FQHCs/clinics, community-based nonprofits, and benefits navigators that screen low-income clients (B2B2C SaaS), plus aligned state/county agencies who still run the workflow in spreadsheets, generic docs, email, or chat threads.
Small teams in Public-benefits access and social-care technology (SDOH) for safety-net programs like SNAP, Medicaid, and the EITC that feel the pain weekly but are too narrow for broad incumbents.
New adopters who need guided proof before committing to a larger platform.

Feature gaps

A narrow workflow that reaches value without configuration-heavy onboarding.
A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
A handoff path from manual concierge service to repeatable software.

Differentiation levers

Use specificity as the wedge: one buyer, one workflow, one measurable result.
Show proof earlier than broad competitors with before-and-after examples and small pilot data.
Keep implementation lighter than incumbent suites or generic AI assistants.

Roast and risks

Promising enough to test, not strong enough to build broadly.

Blind spots

Eligibility rules vary by state, county, and program and change frequently; maintaining accurate, to-the-dollar rules engines across jurisdictions is costly and a liability if estimates are wrong.
A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
The first release can become a generic dashboard if the job is not named tightly.

Hard questions

Who wakes up already trying to solve this?
What do they stop paying for or stop doing when this works?
What proof would make a skeptical buyer trust it in one screen?
What is the smallest paid version of this idea?

Kill criteria

Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
No buyer can name a current cost in time, money, risk, or reputation.
The first demo does not produce a clear next step, paid pilot, or specific objection.

Offer ladder

Lead magnet