173 ideas you can
build with Next.js
The default for a web product a coding agent can carry end to end. Every one below is scored 0 to 100 on the same rubric, with the reasoning behind the number on the page, so you are picking on evidence rather than on a title that sounded good.
What the scores actually look like
A catalog where everything scores well is a catalog with no rubric behind it. This is the real spread across the 173 ideas on Next.js, and it includes the ones rated CAUTION, published with the reason they are risky.
Anything under 55 never publishes at all, which is why the bottom band is empty rather than flattering.
How the rubric worksNext.js shows up in 3 stacks here
Each one has its own page with the full list. This page is the view across all of them.
What it costs to run
The number people overestimate most. Below is the monthly bill at a thousand users on each Next.js combination, from the same model behind the cost tool. Every one of them is still free at that scale.
Ranges, not promises: your bill moves with real traffic. Run your own numbers.
The six strongest on Next.js
Ranked by UIQ, out of 173Expecta
Product safety, scanned
Marklight
Prove what your AI made
Billable
The hours you forgot to bill
Accesspass
The accessibility fix, not the score
Allerline
The allergen answer that is written down
Casetimer
The deadline you cannot miss
The kit is written for Next.js
Every idea here ships with a 10-phase build kit whose prompts name your stack, not a generic one. Your agent gets the commands that actually apply, so the first evening goes on the product instead of on setup.
The first two phases are already done when you open it: the idea is chosen and the stack is picked, so you start at 2 of 10 rather than at nothing.
Is Next.js the right call here?
- One codebase for the pages and the API
- Agents know it, so less of your evening goes on scaffolding
- Deploys free and scales without a rewrite
It is a web framework, so anything that has to live on a phone home screen or work offline is the wrong fit. Reach for Expo there instead.
Browse every stackFrequently asked
Do I have to use Next.js?
No. The stack is a recommendation the score already accounts for, and the kit adapts if you swap it. It is here because picking a stack you already know is the single biggest thing that decides whether a solo build gets finished.
Are these ideas Next.js-specific?
The idea is not, the kit is. Each of the 173 above ships with prompts written against Next.js, so your agent gets commands that run rather than ones it has to adapt first.
How were the 173 scored?
On the same rubric as every other idea in the catalog: eight weighted sub-scores, each shown with its reasoning. The average here is 77 and 141 came out GO, which leaves 32 that did not.
Which one should I start with?
If you want the shortest path to something running, one of the 84 rated difficulty 2 or under. If you want the strongest case, start at the top of the six above and read the risk section before you commit an evening.
What does it cost to run?
Nothing at launch on every combination listed above, and a modest monthly bill once real usage arrives. The table above shows the bands, and the cost tool lets you put your own numbers in.
Is any of this generated at runtime?
No. Every score, plan and kit is produced offline and reviewed before it publishes. Nothing on this site calls a model while you are reading it, so nothing here can invent an idea that was never scored.
Pick one and start tonight
The idea of the week is unlocked in full, free, with no account. Read a complete one before you decide anything.