What changed
FACT: Google shipped computer-use in a cheap, low-latency Flash tier (Gemini 3.5 Flash), and FACT: schema-defined extraction from arbitrary sites became a single hosted API call (Context.dev, YC S26). HYPOTHESIS: together these make 24/7 automated navigation of login/JS-gated government funding portals economically viable for a solo builder for the first time — the interactive portals that static RSS/HTML scrapers (and therefore most grant databases) never covered.
Why now
Computer-use dropped to a per-action cost cheap enough to poll many portals continuously, and extraction no longer requires per-site parser engineering. FACT: a live, time-boxed access point exists (Nebraska reopened BEAD provider applications with $300M+ unallocated), the kind of gated, state-run window incumbents cover poorly.
Converging signals
Three signals meet: (1) cheap agentic browser control (Gemini 3.5 Flash computer use), (2) one-call structured extraction (Context.dev), (3) a quantified buyer pain — a grant writer calling $124–250/mo databases 'a real buzz kill' for someone starting out. Capability + capability + priced-out buyer.
Customer pain
FACT (one complaint): grant databases cost $124–250/mo and are prohibitive for solo/early grant writers. Underlying deadline/eligibility data is fragmented across free-but-gated state portals; missing a deadline or an eligibility change loses a client a funding round. INFERENCE: municipal/BEAD consultants track a handful of state portals manually and by hand-checking.
Who pays
Grant writers, small nonprofits, and municipal/BEAD/broadband consultants on a monthly subscription. Note the tension: the one documented buyer is complaining that $124/mo is already too expensive — this is a price-sensitive segment, not a forced filer.
Solved today
Paid grant databases (Instrumentl, GrantStation, Candid/Foundation Directory, eCivis for municipal), free federal sources (Grants.gov saved searches + email alerts, SAM.gov), and manual human portal-checking. Gated/interactive state and settlement portals are the gap most incumbents skip.
Why current solutions are bad
Incumbent databases are expensive AND still miss the JS/login-gated interactive portals (opioid-settlement dashboards, state BEAD application systems, some state grant portals) because their pipelines are static scrapers/curation. Free federal tools don't cover state pass-through or settlement portals. Manual checking doesn't scale and misses deltas.
Proposed product
A monitoring/alerts micro-SaaS: a Flash-tier computer-use agent drives each portal's UI (handles login/session), extraction normalizes each rendered page into records, a diff engine detects new/changed deadlines, amounts, and eligibility, and pushes structured alerts (email/Slack/webhook/CSV). Positioned as the 'gated-portal change monitor,' not a full grant-discovery database — a wedge, not a head-on competitor.
MVP version
Pick 10–15 gated portals in ONE vertical where the pain is sharpest and least served (e.g. state BEAD provider portals + opioid-settlement dashboards). Run the computer-use+extraction+diff loop, prove reliable deltas, and deliver alerts to a private list of 5–10 design-partner consultants.
30-day build
Run the embedded kill test first: point the agent at ~20 known gated portals for two weeks; measure yield. Require ≥80% reliable deadline/eligibility deltas without per-site babysitting before spending on product. In parallel, recruit 5–10 design partners from r/grantwriting and BEAD/municipal-consultant circles.
60-day build
Harden auth/session handling and per-portal reliability on the highest-value 15–25 portals; build the alert delivery + a simple dashboard; convert design partners to paid pilots at an intro price; instrument false-positive/missed-delta rates.
90-day revenue plan
Charge for the monitored-portal bundle; expand portal coverage state-by-state. Target: 15–40 paying subscribers. Revenue in the low-thousands/mo is realistic if reliability clears the kill test; deadline-driven urgency (BEAD windows) shortens the sales cycle.
Distribution path
Content + community: r/grantwriting, grant-writer and municipal/broadband-consultant Slack/FB groups, LinkedIn, and free public 'BEAD deadline tracker' pages as SEO/lead magnets. Sell on demonstrated coverage of portals incumbents miss, not relationship sales.
Pricing hypothesis
$49–99/mo per user for a portal bundle (undercuts the $124–250/mo databases the buyer already resents), plus a higher $199–399/mo tier for consultants monitoring many portals/clients and webhook/API access.
Technical difficulty
Medium-high. The core loop is buildable now, but reliable auth/session handling and per-portal drift tuning on interactive portals is the whole ballgame — exactly what the kill test targets. Expect ongoing maintenance as portals change.
Legal / regulatory risk
Low-moderate. Monitoring public funding portals is generally permissible, but automated login to portals with ToS/rate limits, and CAPTCHA/session handling, can breach terms; use portals the customer is entitled to access, respect robots/ToS, and avoid credential-holding where possible. No licensure required.
Platform dependency
Dependency is on the model vendor (Gemini computer-use pricing/availability) and on target portals' UIs — not on an app-store gatekeeper who can deplatform you. Portal UI changes are the recurring operational risk.
Founder fit
Good. It's a public-money data/monitoring product (his primary thesis, monitoring rather than filing layer), a micro-SaaS/data product he prefers, sold on demonstrated value, replicable across 50 states. Weaker than a forced-filer play: buyers here are discretionary and price-sensitive, so it's fit-adjacent rather than the maximal-fit filing shape.
Breakout potential
Moderate. Real expansion path (every state × every program type, plus white-label to associations and per-portal data feeds), but the ~5-month lead before large grant-data vendors bolt computer-use onto their pipelines caps defensibility unless portal coverage and reliability become the moat.
Final recommendation
CONDITIONAL PURSUE — but as a gated-execution bet, not a green light. Do NOT build product first. Spend 2–3 weeks and modest money running the kill test on 20 real gated portals; only proceed if yield clears ~80% reliable deltas without babysitting AND at least 5 design partners commit to pay ~$49–99/mo. If reliability or willingness-to-pay fails, kill it. It ranks below a true forced-filer/per-filing opportunity but is a legitimate public-money monitoring wedge worth the cheap validation.
Next action
Run the embedded kill test: stand up the Flash computer-use + extraction + diff loop against 20 known gated portals (BEAD state portals + opioid-settlement dashboards first) for two weeks and measure the reliable-delta yield; simultaneously DM 10 grant writers/BEAD consultants to confirm they'd pay for gated-portal change-alerts.