Problem Signals Report, autumn 2026

Published 12 October 2026 · By Daily Product Idea · Our methodology

Key findings

• About 1 in 270 posts became a published idea. 4,939 distinct posts were read between 29 August and 12 October 2026. They produced 360 usable problem signals, 65 problem clusters, 44 opportunity candidates and 18 published researched ideas.
• Where people do the work, they describe problems. Communities of bookkeepers produced 32 usable problem signals per 100 posts. Communities of teachers produced fewer than 1.
• Most problems are already being worked around by hand. 59% of usable signals described a manual workaround, and 25% a spreadsheet specifically. Only 8% showed someone actively looking to buy.
• Easy to build, hard to stand out. Differentiation was the lowest of six scores for 15 of the 18 published ideas (median 32 out of 100), while buildability was the highest (median 75).
• None of the 18 published ideas cleared 61 out of 100. The median opportunity score was 56, and no idea reached the top evidence level.

What this report is

Daily Product Idea publishes one researched product opportunity a day. Behind each one is a pipeline that reads public community posts, picks out people describing a real problem in their own work, groups repeated problems, and researches the strongest. Every published idea shows its sources and scores. This report counts what that pipeline saw across its first six weeks of running daily: what was read, what survived each step, and what the published ideas have in common.

It is a description of one pipeline’s output, not a survey of all businesses. The method and limits section at the end says exactly what was counted and where the numbers should not be stretched.

From 5,193 posts to 18 ideas

Four in five posts never describe a problem at all. They are news, opinions, announcements and questions about something else. Of the problems that were described, a third were rejected at triage, usually because the post only weakly showed a real, specific problem, or because it was promotion dressed as a complaint. Of the 44 candidates researched so far, 4 were rejected after research found more evidence against them than for them.

Where problems surface

The yield of a community, meaning how many usable problem signals it produces per 100 posts read, varied by a factor of more than 80. Communities where people discuss doing the work, such as bookkeepers, restaurant owners and recruiters, produced far more than communities where people discuss their profession more broadly.

The same pattern holds for single communities. r/Bookkeeping turned 21 of 26 posts into usable signals, and r/EtsySellers 14 of 18. r/smallbusiness produced the most signals in total (76) but from 1,075 posts, a yield of 7%. r/Teachers produced 7 from 836. Reddit supplied 239 of the 360 usable signals overall. The guide How to find product ideas on Reddit explains how to read those communities.

Bookkeepers stand out for a reason: they describe the same software tasks repeatedly, in detail, and for clients who pay them by the hour. Five of the 18 published ideas are for bookkeepers, alone or alongside other customers, including LedgerLine, which drew 9 of its signals from r/Bookkeeping.

How people cope today

Each usable signal was tagged with what it shows. A signal can carry several tags, so the shares below add up to more than 100%.

The common problem is not a missing category of software. It is a gap between tools people already pay for, filled by copying, retyping and reconciling by hand. Only 1 signal in 12 shows someone shopping for a fix. That is why every published idea lists the workaround it would replace, and the tests to run before building.

Easy to build, hard to stand out

Each researched idea is scored from 0 to 100 on six points, using only what the evidence shows. The method is explained in Is your product idea worth building?

Differentiation was the lowest score for 15 of the 18 ideas. Of the 20 sourced research findings that weakened a published idea, 18 concerned differentiation: an existing product, a platform feature or a free template that already does most of the job. The problems are real and usually small enough to build for, but someone is usually close to solving them already. Flight Deck scored 20 on differentiation, the lowest. The highest was Clean Exit at 55, still well below its buildability of 78. Deal Floor had the highest buildability of all, 88.

What the evidence looks like

Behind the 18 published ideas are 85 sourced research findings. 53 supported the idea, 20 weakened it and 12 were neutral. Vendor and industry pages made up the largest group (46), followed by job postings that show the work being done by hand (14), product reviews (11) and issue trackers (6). No published idea had search-volume evidence.

Each idea is given an evidence level, from Limited to Direct. 13 of the 18 are Indicative, 4 are Supported, 1 is Limited and none is Direct. Direct needs evidence from customers themselves, such as interviews, sign-ups or pre-orders, which desk research cannot produce. The difference between those levels is explained in How to tell an idea from an opportunity.

The published ideas suggest a median paid tier of £39 a month. Those prices are anchored to what comparable tools charge and are untested with customers, so read them as a starting point, not a finding.

Method and limits

• Period. Posts collected from 29 August to 12 October 2026. Ideas published from 30 August to 12 October 2026. Counts were taken on 12 October 2026.
• Sources. Public posts from Reddit communities, Hacker News, dev.to and GitHub, read through their public interfaces. The communities were chosen by the pipeline’s editor, not sampled at random.
• Screening and extraction. Each post was screened for problem language, and a language model extracted a structured problem signal from the rest: who has the problem, what happens, how they cope and what it costs. Signals were triaged by rules and by hand (323 automatically, 200 by an editor). Tags such as “spreadsheet workaround” come from that extraction.
• Yields are not like-for-like. Some communities were read in full and others through a search phrase, and the mix changed during the period. Treat the differences between community types as large and real, and the exact ratios as indicative.
• Scores are the pipeline’s own. Every score note on a published idea cites the evidence behind it, and the full scoring method is on How ideas are assessed. One idea has dimension scores but no overall opportunity score, so the opportunity-score figures cover 17 ideas.
• Illustrative examples excluded. The site’s three illustrative sample ideas, and one test idea that was withdrawn, are not counted.

Every published idea, with its sources, scores and tests, is in the ideas archive. Please cite this report as: Daily Product Idea, “Problem Signals Report, autumn 2026”, dailyproductidea.com.