The catalog · Hospitality

Waitproof

The queue that texts you

Next.js + SupabaseDifficulty 2/5Suggested $19/moWalk-in restaurants and clinics
Smoke-tested to a running MVP, or we fix it. No card to start.
75
UIQ score
GO
Build Waitproof · free to start, no card
1
Pick a scored ideaEach idea is graded 0 to 100 with the full case that earned the number, so you build on evidence.
2
Build it with your agentA ten-phase kit feeds your coding agent one prompt at a time, from empty folder to a running MVP.
3
Launch and get paidShip it live, then the launch kit helps you land the first users who prove it.

Problem

Twenty people stand outside in the cold waiting for a table. Half leave. The host shouts names into a crowd and loses track. Everyone's evening is slightly worse, including the restaurant's revenue.

Why now

Nothing new. Waitlist apps exist and are priced for chains, and the free option is a clipboard.

Solution

Join the queue, go for a drink, get a text when the table is nearly ready. The host manages a list instead of a crowd, and the people who would have left are still nearby when their table opens.

Who it is for

A walk-in restaurant or clinic losing people to the queue rather than to the service. Twenty stand outside in the cold, half leave, and the host shouts names into a crowd and loses track. Everyone's evening gets slightly worse, including the takings. The waitlist apps that fix it are priced for chains, so the real alternative is a clipboard.

What you could earn from Waitproof

Say you build Waitproof and charge your own customers $19 a month, the price the score suggests. The numbers below are the revenue that would come from them. This is money you earn, never a fee you pay UpgradIQ, and we never take a cut. It is arithmetic off the price, not a promise the customers arrive on their own.

10customers paying you $19/mo$190/moyou earn · $2,280 a year
50customers paying you $19/mo$950/moyou earn · $11,400 a year
100customers paying you $19/mo$1,900/moyou earn · $22,800 a year

See what Waitproof produces

Join the queue, go for a drink, get a text when the table is nearly ready. The host manages a list instead of a crowd, and the people who would have left are still nearby when their table opens.

Waitproof · the queue
PartySizeJoinedWaitStatus
Rivera218:405 minTexted
Chen418:5220 minWaiting
Okafor219:0125 minWaiting
Reid619:1040 minWaiting
14 covers1 table nearly readyA list, not a crowd
Join the queue, get a text when the table is nearly ready · the host manages a listSee the queue

Your build kit for Waitproof

Start the build and the kit opens two steps in, then drip-feeds the rest one phase at a time. Every phase is a copy-paste prompt for your agent with its own verification before the next unlocks, so Waitproof moves from an empty folder to a running MVP without you ever holding the whole plan in your head.

Progress saves across every device, and the workspace always reopens on the exact step you left, so a build that runs over several weeks survives them instead of dying in a browser tab you eventually close.

Idea and stack are already checked, so you open at 2 of 10
10phases to MVP
2/5difficulty
Next.jsprimary stack
Waitproof · build kit
Idea chosenDone
Stack selectedDone
3Scaffold the stackNext up
4Data model and sign-inLocked
5Core feature, end to endLocked
6Monetization wiringLocked
7Test and hardenLocked
8Polish and deployLocked
9Launch-day toolkitLocked
10First 10 usersLocked

How you actually build it

Connect your coding agent once. It pulls the current phase straight from your kit over MCP: the exact prompt, the outcome to aim for, and the check to run before it moves on. You review and ship, it does the typing.

No copy-paste juggling, no thread to lose. The kit stays the single source of truth, and your agent works through it one phase at a time, verifying its own work at each step before the next phase is unlocked.

Start free, run phase 1Free account, no card. The first phase prompt unlocks the moment you start, right in your workspace.
agent · MCP
$ get_current_phase waitproof
Phase 3 of 10: Scaffold the stack
Outcome: The project builds, runs locally, and its health route answers 200.
Check: Run the dev server. `curl` the health route and show the 200. Run the build and show it passing with zero type errors. Confirm `.env` is gitignored: `git status` must not list it.
building · scaffolding Next.js, the data layer, the health check
dev server up · /api/health returns 200 · build passes
$ mark_phase_complete scaffold
Done · 30% complete · next: Data model and sign-in
phase 4 unlocked · the agent asks for the next prompt

Take the context file, free

This is the AGENTS.md that keeps your coding agent on scope for the entire build: what Waitproof is, who it is for, the stack, the non-goals, and the rules it must follow. Copy it into your project now, no account needed, and your agent is briefed before you write a line.

AGENTS.md · waitproof
# Waitproof

The queue that texts you

## What this is
Join the queue, go for a drink, get a text when the table is nearly ready. The host manages a list instead of a crowd, and the people who would have left are still nearby when their table opens.

## The problem it solves
Twenty people stand outside in the cold waiting for a table. Half leave. The host shouts names into a crowd and loses track. Everyone's evening is slightly worse, including the restaurant's revenue.

## Who it is for
A walk-in restaurant or clinic losing people to the queue rather than to the service. Twenty stand outside in the cold, half leave, and the host shouts names into a crowd and loses track. Everyone's evening gets slightly worse, including the takings. The waitlist apps that fix it are priced for chains, so the real alternative is a clipboard.

## Stack
Next.js + Supabase

## Non-goals
Do not build features outside the core job above. This product exists to do one
thing well. Every extra feature is a reason it does not ship.


## Rules for the agent
- Build one phase at a time. Do not run ahead into later phases.
- Validate input at every boundary where data enters.
- Never put a permission or plan check in client code.
- Ask before adding a dependency that a few lines would cover.
- If something is ambiguous, say so rather than inventing a requirement.

---
Context file from UpgradIQ · idea waitproof · prompts kit-v4

Then start free to get the ten-phase kit and run the first prompt.

The path to a running MVP

Phases 1-4

Foundation

Scaffold the stack, then wire the data model and sign-in. It is the skeleton Waitproof stands on, and it goes up in an evening rather than a lost week of config.

Phases 5-6

The product

Build the core feature end to end, then wire how it charges. This is where Waitproof finally turns into something that a stranger will actually pay you for.

Phases 7-10

Ship it

Test and harden, deploy it live, then open the launch-day toolkit that lands the first ten users who prove it.

Is Waitproof for you?

A good fit if
  • You want revenue reasonably soon, not a science project
  • You can give it evenings and a couple of weekends
  • You can reach Walk-in restaurants and clinics
You have read the free case, the hard part4 of 7 sections done

The 3 sections that decide whether you should actually build it, plus the full kit, are one click away.

Pro

3 more sections decide whether you build Waitproof

You have the case and the plan. Pro opens how it makes money, the one risk that kills it, and the build notes, plus the 10-phase kit that takes Waitproof to a running MVP, on this idea and all 200.

How it makes money

Main risk

Build notes

What is free here, and what Pro unlocks

The problem, timing, solution and buyerFree
How it makes money, priced and modelledPro
The full UIQ 75 and all eight sub-scoresFree
The one risk most likely to kill itPro
Stack, difficulty and suggested priceFree
The 10-phase kit to a running MVPPro

Frequently asked

Is Waitproof actually validated?

It scored UIQ 75 with a GO verdict, weighed across eight sub-scores on the same rubric as every idea. GO means 75 and above, so demand and buildability were judged, not guessed.

What stack does it use?

Waitproof is built on Next.js + Supabase, chosen because a coding agent can carry most of it. You are not fighting infrastructure, you are shipping the feature that matters.

How long to a running MVP?

The kit is ten phases, drip-fed one at a time so you always know the single next step. An evening and a weekend for the lighter builds, a few focused weeks for the deeper ones.

What does the $19 a month mean?

It is the price the model suggests Waitproof could charge its own customers, not a fee to us. It is here so the money question is answered before you build, not after.

Which agent do I need?

Any capable coding agent: Claude Code, Cursor, Lovable, or Bolt. Every phase is a copy-paste prompt with its own check, so the agent does the typing and you keep the judgement.

What is free versus Pro?

The whole case above is free: the problem, timing, solution, buyer, and the full score. Pro adds how it makes money, the one risk that could kill it, and the full kit that carries Waitproof from an empty folder to a running MVP.

More like Waitproof

All 6 Hospitality ideas
3 more sections

Build Waitproof, not just read about it

You have the problem, the timing, the solution and the buyer. A plan opens how it makes money, the risk that kills it, and the kit that takes it to a running MVP.

Start building Waitproof
Today's idea is free, no account