Ten of 764 needs worth a first look.

Each memo below links to its full evidence page. Browse all documented needs →

This is a screening record, not an industry report. Each of the ten below ran the same six questions: who signs the cheque, why now, what you sell first, where the ceiling is, what compounds, and what result would make you stop. The other 754 are not rejects — they are where these ten came from, they stay published, and you can check our judgement against them.

SourceTraced to the original thread, continuously updated Inventory764 needs, every one published This issue10 businesses · 2 fundable · 5 cash flow · 3 not a company

Summary

Three conclusions. Each of them changes a build decision, which is why they come before the ten.

  1. 01
    Discussion volume is not revenue. The three most-discussed needs in the inventory — directory submission, blocking AI content, a calendar that bends to flow — are the three hardest to monetise of the ten. Heat measures how much a complaint hurts; it does not say whether anyone will pay to stop it.
  2. 02
    Six of them are already being paid for, step by step. 01, 02, 03, 04, 05 and 07 — the buyer is already spending today: contact data, model bills, compliance audits, quote gaps, character production, sales collateral. These are not new customers waiting to be convinced; they already pay for the adjacent step, so the product replaces a line item instead of creating one.
  3. 03
    Only two have a clear window. One is a competitor shutting down — GummySearch stopped new signups in November 2025 and shuts down on 1 December 2026; the other is tokens moving from R&D spend to cost of goods, a turn happening in the next year or two. The other eight are not wrong, they are untimed: doable this year, still doable in five.

The portfolio on one page

Ceilings are bottom-up: reachable accounts × monthly price × 12, with the account count labelled wherever it is an assumption. Not TAM, and not a valuation.

#BusinessBuyerPriceCeilingCall
01A daily lead list from public comment threadsOutbound shops, GTM consultants$99/mo$4.8MFUND
02Flag the AI customers you lose money onSaaS teams already shipping AI$49/mo$8.0MFUND · CATCH
03SOC 2 in six weeks, fixed price1–3 person company closing a first enterprise deal$4,900 flat$0.3MCASH
04Defend a quote instead of discounting itIndependent developers, small studios$29/mo$12MCASH
05Keep multi-persona canon consistentStreamers running more than one character$12/mo$2.9MCASH · SMALL
06Hand over a one-person businessSolo founders whose clients depend on them$19/mo$1.2MCASH · HARD SALE
07White-label audits studios resellWeb and WordPress studios$49/mo$6.0MCASH
08Submit to 80 live directories in 48 hoursFounders in launch week$149 once$0.3MQUICK CASH
09Move the calendar around flowRemote workers, personally$8/mo$0.6MNOT A COMPANY
10Block AI content where you actually readOrdinary readers$3 once$0.09MNOT A COMPANY

764 needs, one square eachthe rust squares are the ten in this issue

754 still in the inventory, carried to the next issue 10 taken into this memo

Six questions, before anyone spends

The same six, in the same order, on every memo below. If you read only two, read the first and the last: who pays, and what would make you quit.

#QuestionWhat a usable answer looks like
01Who signs the chequeNot "who has this problem" but who is allowed to spend money on it, and which line it comes out of. Replacing an existing line is a sale; creating a new line is a campaign.
02Why nowThe thing that changed in the last eighteen months: a price, an API, a shutdown, a rule, a model getting cheap. If nothing changed, the need has sat there for a decade and nobody bought.
03The wedge, then the expansionThe smallest thing you can charge for this month, and what it opens. A wedge is not a small MVP — it is a complete answer to one narrow question.
04The ceiling, bottom-upReachable accounts × price × 12. Not TAM. Every memo prints the arithmetic so you can argue with the input instead of the conclusion.
05What compoundsIn twelve months, what do you own that a competitor cannot copy in a weekend? Data, distribution, trust, switching cost. If the answer is "a nicer interface", you have a feature.
06The falsification testA specific spend, a specific window, a specific result that means stop — written down before you start, because after three months of work every founder can find a reason to continue.

Ten memos

Ordered by what each should become, not by how interesting the problem is: venture-backable first, businesses that pay one person in the middle, tools and services last. All ten are real; they differ only in which form fits — and each memo ends by naming that form, and the result that would make us stop.

Limits, and what this memo is not

Not an investment recommendation

No cheque has been written against any of these ten. The calls — FUND, CASH, NOT A COMPANY — describe what each should become: a company, a cash-flow business, or a one-off service. Not what we would pay for it. That distinction is the body of the memo, not a footnote.

The other 754 are not rejects

A need that is real and cannot be sold is still a real need. The only difference between them and these ten is whether someone is already paying for it. They stay published and carry into the next issue — the ten are ten because the other 754 were read first.

Every number is an assumption, and it says so

Each ceiling is reachable accounts × monthly price × 12, with the account count stated or labelled as an assumption. Several are probably wrong by a factor of two. They are printed anyway, so the disagreement happens at the input instead of at the conclusion.

No receipts, and a source that is better at pain than at budgets

Nobody in the inventory posted an invoice: what the 764 contain is hours lost, quotes rejected, bills nobody understood, clients who left. That proves the pain; it does not prove anyone will pay, which is why every memo ends with the conditions that would produce that evidence. About seven in ten of what the library collects comes from developer sources — Hacker News, DEV.to and GitHub — so it is a strong instrument for what builders complain about and a weak one for budgets. No heat score appears on any memo: that number is internal to the pipeline and not comparable across days.

Snapshot, not a standing claim. The GummySearch shutdown lands on 1 December; a directory index decays monthly; platform labelling ships on the platform's own schedule. Re-read the dated claims before acting on them, and treat every ceiling as a hypothesis you can bet against.