New startup ideas · AI for people who run the AI themselves · What vibe coders need after the demo
startup concept
Spendgate
Meter, cap and route the AI spend inside apps vibe coders shipped
Spendgate is a proxy key for the LLM calls inside a shipped vibe-coded app: per-user metering, hard monthly caps, automatic fallback to cheaper models when a budget nears, and alerts before the bill surprises the owner.
- Infrastructure and APIs
- Consumer
- $200-a-month seats for heavy users
0
similar startups, last 2 years (0 all-time)
no
no public money matching the concept's terms
Test it before you build it
$600 · 3 weeks · 30 prospects
For $600 and 3 weeks, prove that builders burned by a surprise API bill will pay a $49 reservation and route production LLM traffic through a stranger's proxy key, before the proxy is productized.
Riskiest assumption · An owner whose shipped app just produced a surprise API bill will route production LLM traffic through a third party's proxy key and pay 3% of spend, rather than settle for the free project budget limits already in the OpenAI and Anthropic dashboards.
1Focus group: who and where
A solo builder whose shipped Lovable or bitrig app has a live AI chat feature that produced a triple-digit OpenAI or Anthropic bill in a single weekend - the invoice email is in their inbox this month and the app earns little or nothing against it.
where to find 30 · The OpenAI Developer Forum (community.openai.com) and r/LLMDevs, searched for surprise-bill and rate-limit threads from the last 90 days (communities where the exact pain is posted with usernames attached), the Lovable Launched showcase filtered for apps with visible chat features (a directory of exposed owners), and X #buildinpublic, where makers post bill screenshots (a channel with public DMs).
2Sell first, build later
A founding pilot sold before the product exists: per-user spend caps, a live cost dashboard and bill alerts on the buyer's production key within 7 days of reserving, via a one-variable key swap they can revert instantly.
the ask · $49 refundable reservation now; free up to $50 of routed spend per month, then 3% of managed spend
a real yes · A real yes is a $49 card charge followed by a completed key swap on production traffic and written acceptance of the 3% terms. 'I'd try the free tier', dashboard compliments, and swaps on test keys that never see real users do not count.
3Small experiments
The first one attacks the riskiest assumption; each ends with a number that says whether to run the next.
1. Bill-scare outreach and reservation pitch
$100 · 10 days
Collect 30 prospects: authors of surprise-bill posts from the last 90 days plus owners of chat-feature apps on Lovable Launched. DM each the outreach script, book 12 calls, and on each call review their actual last invoice line by line, then ask for the $49 refundable founding-pilot reservation on the spot.
keep going if · 12 of 30 reply, 10 become calls, and 5 of 12 calls end with a $49 reservation charged
2. Priced reservation landing
$200 · 7 days
Publish the landing copy with a card-charging reservation and post it as a reply in the surprise-bill threads already found, plus in every DM follow-up. This tests whether the pain converts without a call.
keep going if · 3 or more $49 reservations from roughly 120 visitors, counted separately from call-driven reservations
3. Key-swap pilot on a hosted proxy
$300 · 14 days
Stand up an open-source LLM proxy (LiteLLM) on a $10-a-month server, configure per-user metering and a hard monthly cap for the first 5 reservers, and have each swap one environment variable to route production traffic through it. Track for 14 days whether they keep routing - this attacks both the trust objection and the latency version of the platform risk.
keep going if · 4 of 5 pilots still route 100% of production traffic after 14 days and accept written 3%-of-managed-spend terms
4Collect a deposit up front
Tesla took $1,000 refundable reservations for the Model 3 and $100 for the Cybertruck before building either: the deposit is the measurement, not the revenue.
$49
per prospect, refundable
how · A refundable card reservation at checkout - the right instrument because this is a consumer-priced buyer who pays OpenAI by card already, and the card's free-tier wedge means only money moved up front distinguishes real demand from free-tier tourists; the founder sends the link on the call and confirms the charge before scheduling the key swap. set up: Stripe Checkout ↗
what it reserves · One of 10 founding pilot slots, the key swap and cap configured within 7 days, and 0% fees on the first $500 of managed spend
refund · Refunded in full any time before the key swap, or automatically if measured added latency exceeds 200 milliseconds in the first week.
target · 8 reservations from 30 prospects within 21 days, with the first 5 swapped onto the proxy
Go: build it if
8 of 30 prospects pay the $49 reservation and 4 of the first 5 pilots still route all production traffic after 14 days and sign the 3% terms - build the product.
Kill: stop if
Fewer than 3 reservations from 30 bill-scare conversations, or 2 or more pilots revert the key within a week citing latency or the free budget limits in the OpenAI and Anthropic dashboards - the native-tooling risk is confirmed, stop.
5 Scripts to run itoutreach message, landing copy, deposit terms · click to open
outreach message
Saw your post about the surprise OpenAI bill - that weekend spike is the most common way shipped vibe-coded apps bleed money. I'm building a drop-in key that caps what each of your users can spend, falls back to cheaper models near the limit, and alerts you before the invoice does. You swap one environment variable and can revert instantly. I'm taking 10 founding pilots at a $49 refundable reservation. Got 20 minutes this week to go through your last invoice together?
landing page
Cap what your app's users can spend on AI $49 refundable reservation: per-user caps, live cost dashboard and bill alerts within 7 days; free to $50 of routed spend a month, then 3%. Reserve one of 10 founding pilot slots - refunded if we add over 200ms of latency.
deposit terms
You pay $49 today to reserve one of 10 founding pilot slots with 0% fees on your first $500 of managed spend. Your key swap, per-user caps and dashboard go live within 7 days. Full refund any time before the swap, and automatic refund if added latency exceeds 200 milliseconds in your first week.
Would you run this test?
One tap. The yes-share feeds the Demand pillar of this idea's score; nobody sees who answered.
Budgets are out-of-pocket estimates for a team of one to three, US market. Size the deposit to the deal, and check the terms before taking money in a regulated line.
Scorecard
Ranked against every idea in the catalog: trend, demand and 100x potential from the corpus, competition relative to the other ideas. A generated concept has no judges or swipes yet, so its pillars use the data signals only.
39
Idea Score, 0-100 (partial) · raw 24.4 x 1.61
Open
competition: more crowded than 12% of ideas · headwind x0.94
+0.0
government priorities, secondary (0 matching grants)
Trend
24
Is the wave forming now? 2025-26 entrants vs 2023-24, rounds since 2025, the sector's live-batch direction, the 2026 trend analyst.
- Entrants 2025-26 vs 2023-24 (similar companies)21
- Rounds announced 2025+ in the sector0
- Sector direction (live batch)50
Demand
15
Does anyone want it? YC's current RFS, companies already paid for something similar, the operator judge, founders' yes-rate in decks, readers who would run the test.
- YC asks for it (current RFS: idea / sector)30
- Someone already pays (similar companies, recent / all-time)0
100x potential
50
Can it return a fund? The venture judge (double weight), market-size and moat axes, neighbours still alive, the technologist judge.
- no signal yet, taken as 50
Score = 100 x cbrt(Trend x Demand x 100x) x (1 - 0.5 x crowding) + government bonus (max 5), calibrated so the 95th-percentile idea scores 90 (order never changes). A geometric mean: a weak pillar cannot be papered over. Percentiles are among the 382 ideas in the catalog; the terms matched were meter, cap, route, spend, apps, vibe, coders, proxy.
The concept in full
- What
- Spendgate is a proxy key for the LLM calls inside a shipped vibe-coded app: per-user metering, hard monthly caps, automatic fallback to cheaper models when a budget nears, and alerts before the bill surprises the owner. First hour: swap the app's OpenAI or Anthropic key for a Spendgate key, set a monthly cap, and watch live per-feature cost on a dashboard.
- Grounded in (2025-2026 signals)
- Claude Max launched 'on April 9, 2025 at $100 and $200 a month'; Woz (yc W25) is a 'Claude Code plugin that reduces token consumption and cost by 50%', proof the 2025 cohort pays for token cost control; Cursor's run from '$100 million in January 2025' to 'about $4 billion by May 2026' annualized shows usage-based AI exposure compounding; the collection brief names cost control as one of the unbuilt layers.
- What it rides
- $200-a-month seats for heavy users: the Claude Max tier launched April 9, 2025 priced individual heavy usage, but the AI features inside a builder's own shipped app have no such ceiling, and Spendgate gives the owner the cost controls the platforms give themselves.
- Why now
- Builders who shipped AI features in the 2025 wave are now carrying open-ended inference bills against apps that may earn nothing, in a market where Menlo's June 26, 2025 survey found only 3% of consumers pay for AI; the gap between capped platform pricing and uncapped in-app usage opened within the last twelve months.
- Wedge: first customer and entry point
- A Lovable or bitrig builder whose app's chat feature produced a triple-digit API bill in one weekend; free up to $50 of routed spend per month, then 3% of managed spend, adopted by changing one environment variable.
- Closest real companies, as the generator saw them
- Woz (yc W25) cuts token cost inside Claude Code for the developer's own sessions; Spendgate governs production spend of a shipped app's end users, a different bill paid by a different person. Prism (yc X25) deploys agents via API but does not manage their cost.
- Main risk
- OpenAI and Anthropic ship native per-key budgets and routing good enough that a proxy adds only latency.
Similar startups in the directory
Companies whose pitch matches most of the concept's terms (meter, cap, route, spend, apps, vibe, coders, proxy).
Nothing in the directory matches this concept's terms.
Public money in this direction
US federal grants and open opportunities matched to the concept's terms.
No matching grants or programs tracked; 19 startup-relevant grants exist in Horizontal AI assistants overall.
Other concepts in this collection
- SkillproofRegression testing for the Agent Skills you actually depend on
- ProvenaryScan third-party skills and MCP servers before you let them touch your data
- LedgerkitVersioned skill packs that make a solo CPA's assistant work like a tax practice
- VendfoldLicensing, signing and auto-update infrastructure for people who sell Agent Skills
- PackroomOne shared skill library for a team where everyone runs their own agent
- TokentabPer-skill cost, routing and drift telemetry for the person who runs AI all day
- ThreadkeepA memory vault you own that every assistant you run can read
- RelayfileHand a running task from Claude Code to Codex without losing state
- MeterhouseOne budget, meter and kill switch for every agent you run
- AttestlyAudit trail and approval inbox for the agents you run at work
- SkillvaneVersion control and regression tests for the skills your agents load
- CrewlineA shared board where each teammate's agents pick up each other's work
- WardkeySecurity scanner that finds and fixes exposed keys in vibe-coded apps
- StillupUptime and error monitoring that answers in fix prompts, not stack traces
- CopystoneAutomatic backups and one-click restore for apps built without engineers
- GroundskeepMonthly maintenance for shipped vibe-coded apps, applied as reviewable patches
- TillhousePayments, sales tax and refunds as one drop-in for non-developer founders
- DryloopRehearsal mode for the automations a small business owner builds alone
- MeterlyOne metered key with spend caps for every AI step you run
- FlowmedicWatches your automations, explains failures in plain English, proposes the fix
- ScrubdeckA data-cleaning step any workflow can call, with rules the owner keeps
- OpshandTurns your written SOPs into versioned Agent Skills with tests included
- CrewtraceShared visibility when five people at one business each run their own automations
- VeraciteCitation verification and AI work records for solo attorneys who draft with Claude
- TickstoneTurns a solo CPA's AI sessions into reviewable workpapers with tickmarks and source trails
- ChartproofA verification layer for physicians who use AI on clinical notes under their own license
- CoverlensPolicy-form verification for independent insurance agents who quote with AI
- MethodkitSolo consultants package their methodology as versioned Agent Skills they own and resell
- AttestrailTamper-evident logs of every AI action, built for licensed professionals' liability files
- ScrublineLocal redaction proxy that makes your personal AI accounts safe for work data
- StipendlyTurn personal Claude Max and ChatGPT Pro seats into managed employer stipends
- TollgateA policy gateway between your assistant and every MCP server it touches
- SkillvetScan, pin and approve Agent Skills before they touch company data
- DaylightSelf-serve shadow AI registry and policy for companies with no security team
- LedgerlineRightsizing dashboard for everyone paying for AI out of their own pocket
- SwitchyardOne metered endpoint with routing, fallback and per-person caps for tiny teams
- HearthmeterUsage budgets and one bill for the household that shares AI plans
- SeatcaseMeasures who on your team earns a Max seat and who wastes one
- TokencairnProfiler that shows what each installed skill and MCP server really costs
- FusegateBudget caps, fallback and kill switches for automations you run yourself
- SkillbenchRegression testing for Agent Skills before every model and skill update
- CitelockVerifies every citation in AI-drafted work before a licensed professional signs it
- MiddlegateA local gateway where you set the rules for what your MCP servers can do
- DriftwatchCatches output drift in the automations small operators wired themselves
- ShipcheckPre-launch review gates non-technical builders run on their own vibe-coded apps
- TracelineA claim-level provenance trail for every number in an AI-assisted report
- DrillyardScored practice repos where you learn to drive coding agents well
- PassrateA proctored AI operation exam scored from your real agent transcripts
- PatchcraftDebugging drills that teach non-technical builders to maintain what they vibe coded
- SkillsmithA workshop for writing, testing and versioning Agent Skills that actually hold up
- TickmarkSynthetic client caseloads where CPAs drill AI-assisted work before trying it on real clients
- PostgameAn MCP server that scores your own agent sessions and drills your weakest habits
- CitegridEvery number in your published research links to a source snapshot you verified
- MnemosYour research corpus as a private MCP server every assistant can query
- MeterlineModel routing and cost accounting for one person's AI research pipeline
- SkillcaskVersion, test, and sell your expertise as licensed Agent Skills
- StackfeedA personal data pipeline that repairs itself when sources change
- ClaimboardA shared evidence ledger for small teams where everyone runs their own agent
Fictional concept generated 2026-08-26 by claude-fable-5 from the collection's brief and MarkosWeb data. Treat it as a research prompt, not a plan.