Every day, Engaggit scans Reddit for conversations where people describe exactly the app they wish existed — not in a survey, but in the middle of a real problem. This Friday's feed (covering Wednesday through Friday, Nov 4–6) surfaced five gaps so clearly defined that "build this" is already implied. Each idea below links to the actual thread, so you can read the full context before you commit a weekend to it.
This isn't a list of trends. Trends are what everyone already sees. This is a list of threads where someone hit a wall, looked for a tool, and discovered nothing quite fits. When you find a wall that thousands of people share, you've found a product.
The five ideas below came out of real conversations from Nov 4–6 — the window since our last post — with real scores, real frustration, and in one case, a thread where a 1,088-upvote argument about a $30k raise accidentally specced a migration product.
1. Legacy-System Archaeology — The $30k Handover Nobody Can Document
Where: r/careerguidance (1,088 upvotes, 441 comments) | Thread: Company offered me a $30k raise to take over a job nobody else knows how to do. Is this a trap?
The pain: A 28-year-old in operations at a regional logistics company is being offered $30k more to inherit an inventory system a retiring coworker built himself in the early 2000s — with two months to learn it, "barely any documentation, no outside support," and a previous replacement migration that failed so badly the company abandoned it. His director keeps calling it "a huge opportunity" because he'd become indispensable. He's not sure whether that's leverage or a trap.
Why it's promising: This is the sequel to the knowledge-handoff problem we covered in October — that thread was about a person leaving; this one is about the system they leave behind, and the comments can't even agree on what the job is. The top answer (397 upvotes) says outright: "being the expert in a one-off hand-built proprietary system is a dead-end career move… The way to turn this into a good career move is for you to be the agent for modernization." A 226-upvote reply disagrees: "Take it, learn everything. Then ask for another 30k." A 62-upvote reply advises "document everything, don't share that documentation with anyone." Meanwhile a 40-upvote commenter diagnoses why the last migration died: the incumbent "mostly sandbagged the whole process." The disagreement is the market — the same two-month window produces either a dead end or a career-making migration, and which one depends entirely on what gets captured while the builder is still there. Two comments even name the product before we do: "put the software into an AI and have it tell you how it works and write an instruction manual" and "get outside quotes… put a cost and scope to the problem."
The product spec: An AI-assisted legacy system succession kit, aimed at the exact two-month window the thread describes:
- System ingestion → operating manual. Feed the codebase, database schemas, cron jobs, and integration configs into a model that produces a business-logic map and a plain-language manual — the thread's "put the software into an AI" idea, made systematic instead of improvised.
- Start with the failed migration's post-mortem. One comment's practical advice: obtain "any post-mortem report of failed efforts from the past." Ingest those first, then plan version two around why version one died — plus a sandboxed dry-run of the data migration.
- Structured capture of the retiring expert. Automate the debrief the comments insist on: record the interviews, transcribe them, map each answer to the system area it explains, and produce a coverage report showing what still lives only in one person's head. Then help negotiate the 6-month consulting bridge another commenter recommends.
- The leverage package. Generate the outside-consultant quote comparison and scope document the thread says to demand — turning "you'll be indispensable" into a budget line, and giving the modernizer the evidence to lead the change rather than babysit the relic.
The buyer sits on both sides: the person who just got the offer, and the company that would otherwise pay a consultant $500k for the same work. Deadline-driven, budget-lined, and recurring every time someone retires.
2. The Household Audio Filter — Auto-Skip Anything, Anywhere in Your Home
Where: r/homeassistant (486 upvotes, 98 comments) | Thread: How to set up Home Assistant to detect and auto-skip Mariah Carey's "All I Want for Christmas is you"?
The pain: "I hate this song. It infiltrates my home in so many ways." The poster wants Home Assistant to hear the song and skip it, replace it, or — his preferred fallback — "kill the power to what's paying it… I would rather shut off power to the entire house than hear this god damn song one more time." Written as comedy, but the complaint is precise: the song arrives through sources he can't individually control — radio, streaming playlists, holiday stations — and no single switch stops all of them.
Why it's promising: The comments are a complete requirements doc, ordered by engineering effort. The 84-upvote answer is the easy path: trigger on media-player state change, match media_title, call media_next_track — but that only works where the source exposes metadata. The 6-upvote reply covers the rest: "sanitize inputs… most radio stations publish their schedule online" — import it and mute during the scheduled offense. The 5-upvote reply is the universal one: "a script that adds a ten second delay to audio streams, then matches the recorded waveform… play something else. This is a complicated solution to a dumb problem and I love it." There's even a 36-upvote fantasy about phase-inverted anti-sound. Under the jokes, a real gap: platforms let you block a song inside one app, but nothing provides source-agnostic, content-level control across every speaker in a house. And beyond Christmas songs, the same primitive serves every household that has ever wanted one specific piece of audio gone — an ex's voice on a playlist, a specific ad on radio, a toddler's forty-eighth replay.
The product spec: A universal audio content filter for the smart home:
- Fingerprint matching, not just metadata. Adopt the delay-buffer waveform approach from the thread as the core: a 10-second lookahead that recognizes the audio itself, so it works on radio streams, podcasts, and any source that hides its titles.
- An actions ladder straight from the comments. Skip, replace with a chosen track, mute, or apply schedule-based sanitization (import station schedules and mute during known windows) — the user picks the response per rule.
- Per-person, per-room blocklists. The 19-upvote reply — "I did precisely this for my girlfriend" — is the real use case: everyone in the household has their own bans, scoped to their rooms and speakers.
- Seasonal packs. One tap blocks the ten most overplayed holiday songs until January. The seasonal search spike is the acquisition moment; the year-round blocklist is the retention.
Sonos can mute and streaming apps can block within their own walls. Nothing skips by identity across all of them — and this thread proves people will configure an entire home automation system just to try.
3. Taper-Based Addiction Recovery for Students — The Blueprint Is Already in the Comments
Where: r/JEENEETards (290 upvotes, 212 comments) | Thread: (pls hear me out ) 🙏🙏Anyone who knows how to quit gooning addiction and pornograpy
The pain: A student in 11th grade — using since he was 12 — writes that his "brain is functioning like fuck," with "poor concentration and focus… I can't focus on a thing during lectures, my mind wanders off to past memories or regrets or future tension." He already meditates daily. He's four days clean and asking strangers for a method. This is not a fringe post: 290 upvotes in a college-prep subreddit, 212 comments, 0.98 upvote ratio.
Why it's promising: The most-upvoted replies are jokes — which tells you how this cohort copes with a topic it can't discuss seriously — but buried beneath them are two substantive answers that agree with each other and contradict the entire existing product category. A 74-upvote comment: "Don't criminalise it. Don't treat yourself as a piece of shit for it… Don't try to quit at once. It never works. Reduce the frequency. Once every day? Try and make it once every 2 days… a controlled dosage is way better than all out." A 22-upvote comment distills it: "just one blueprint… Get busy in life, it should be interesting. Don't try to quit at once… try to remove the cues as much as possible." Every mainstream quit-app is built on streaks — relapse resets the counter to zero, shame does the rest. This thread's own community says the opposite: taper, treat relapse as data, remove the cues, fill the recovered hours. The demand is enormous and the advice on offer is better than what the apps implement.
The product spec: A taper-first recovery and focus tool built on the thread's blueprint instead of the streak:
- Taper scheduler, not a streak counter. Encode the 74-upvote protocol directly: a personalized reduction cadence (2/day → 1/day → every other day → every 3 days), where a relapse is a data point that adjusts the schedule — never a reset to day zero.
- Cue-removal audit. The second half of the 22-upvote blueprint. Have users identify their patterns — time, place, device, being alone, being in bed — and break them with environment rules: scoped app blockers, grayscale, scheduled wind-down, device-out-of-bedroom prompts.
- "Get busy" as a feature, not advice. The recovered hours need somewhere to go: focus sessions, study sprints, workout plans. For this audience specifically, that means exam-prep integration — the thread is from a competitive-exam sub where focus is the product.
- A shame-free voice. The community's top votes are jokes for a reason. Coach tone should be the 74-upvote comment — matter-of-fact, humorous, never moralizing — because the stern streak app is exactly what makes users quit the app too.
Existing apps sell shame and call it accountability. This thread's top advice says taper, don't criminalize yourself, and stay busy — that's a product spec the incumbents are ignoring.
4. The Team Token Governor — Corporate Claude Accounts Die in Week One
Where: r/developersIndia (254 upvotes, 96 comments) | Thread: How to manage Claude's heavy token consumption? Please read body text
The pain: A senior dev describes the real state of enterprise AI adoption: his company provides a $20 monthly limit per seat. He already routes 70% of his work to Haiku and the rest to Sonnet, and the limit still dies "in a week or two, max" — two weeks only when he's "being super conservative." Meanwhile, he notes, "Cursor has given me much better quality output without hitting the limit ever." He tried the viral community skills (ponytail, caveman, superpowers) for token savings: "slight improvement though" — not enough.
Why it's promising: This is what AI budgeting looks like without a product: a hard per-seat allowance, manual model mixing done by gut feel, prompt-trick folklore with unmeasured returns, and a competitor's tool quietly proving that unbilled usage is the real benchmark. The thread exposes three unsolved layers at once — nobody can see burn-down before day seven, nobody governs which model touches which task, and nobody can answer "did that skill actually save anything?" IT buys the seats; velocity dies on day eight; the engineering manager finds out from a Slack message. The token-cost problem we covered in October was about sessions; this one is about organizations, and it has a budget owner with a credit card.
The product spec: A per-team AI budget governor that sits on top of the provider accounts the company already pays for:
- Burn-down telemetry per seat, per model. Show every user their remaining budget as a 30-day curve with a projected exhaustion date — the difference between discovering the limit on day 7 and preventing it.
- Model routing as policy. The OP already sends 70% of traffic to Haiku by instinct; encode that as rules — task type → model, with quality gates — so the cheap model does the bulk and Sonnet/Opus only touches what genuinely needs them.
- A/B measurement for workflow changes. The skills experiment is begging for instrumentation: tokens-per-task before and after each prompt pack, so "slight improvement" becomes a number a manager can approve or reject.
- Budget-aware agents. Agents that know the remaining allowance and degrade gracefully — cheaper model, tighter context — instead of dying mid-sprint, plus a per-ticket cost report so "how much did this bug fix cost" has an answer.
The wedge is the person who gets blamed when the team runs dry: sell the dashboard to the manager who currently learns about it from an angry developer.
5. Browser Playbooks — 216 Agent Runs, One Script, and the Missing Experiment
Where: r/AI_Agents (7 upvotes, 17 comments) | Thread: I ran the same browser job 216 times with Claude Code and Codex. A script beat every agent run, and the best browser tool depended on the agent
The pain: The quietest thread on this list is also the most rigorously measured. One builder ran the same browser job — pick a department, open a 500-row report, read it, save it, close the tab, return to start — 216 times: Claude Code and Codex against agent-browser, Playwright, and Chrome DevTools, each via CLI-with-skill, CLI-without-skill, and MCP, split across macOS, WSL, and Windows. All 216 runs passed, so the deciding metrics became cost and speed, and they varied wildly: a Claude Code run over MCP hit 1.59M input tokens / $1.02 while the same tool over CLI without a skill ran 304K / $0.28 — a 3.5× tax for the wrong connection mode.
Why it's promising: The comments are what turn a benchmark into a product spec, because they identify exactly what the experiment didn't measure. The sharpest critique (quoted by the OP in reply): "216/216 passed. With zero failures, the experiment ranks setups on cost and speed but stays silent on the axis that decides a real deployment — which setup degrades best when the app changes. Tool choice barely matters while everything works; it matters the day the report moves or the department picker gets renamed." The OP concedes the point: "The script story is an anecdote: I broke the script, not the app." A second commenter names the failure mode that actually hurts: "The breaks that cost me the most were not crashes… The expensive ones were scripts that finished and reported the wrong thing. One read a sign-in page" instead of the data. And despite the disagreement, the thread converges on one architecture from every direction — "let the agent figure out the selectors once and then just run the code until the UI inevitably changes," or as another commenter put it: scripts for repeats, agent for breakage. One participant even described the product already existing in open source: agent works the flow once in your logged-in Chrome, you save it as a playbook, and it reruns with no model in the loop.
The product spec: A playbook layer between agents and browsers:
- Record once, replay forever. An agent drives the flow in your authenticated session; you approve and save it as a deterministic script that runs daily with zero token cost — the architecture the whole thread converged on.
- Drift detection as the headline feature. Productize the missing experiment: run playbooks in verification mode and flag UI changes before they become silent failures. The
matched N elementsambiguity another commenter hit — fixed by scoping actions to a container — gets handled at record time. - Silent-failure sentinels. Assert output sanity on every run: were the 500 rows actually read, or was it a sign-in page? Crash detection is table stakes; wrong-answer detection is the moat.
- Connection-mode cost routing. Bake in the benchmark's clearest number: the same job costs 3.5× over MCP. Choose CLI, skill, or MCP per run based on the budget, not habit.
Seven upvotes, but it's the most complete piece of evidence we've pulled: a full 216-run benchmark plus a comments section that tells you which experiment to run next — and every answer to it is a feature.
How These Were Found
This list comes from a daily feed: Engaggit scans a set of subreddits, scores every matching post by relevance, and drafts a summary connecting what people said to what they need. No surveys, no echo chambers — just people describing real problems in their own words, scored and surfaced while the conversation is still fresh.
For every idea that made the list, we pull the full thread — post body, score, upvote ratio, and comment count — so the product spec is built from what people actually wrote, not a title. There were 86 such conversations in the Nov 4–6 window.
More App Ideas
Looking for more ideas like these? We post a new batch every Monday, Wednesday, and Friday — explore all of today's app ideas at app ideas 2026.
Track These Yourself
These five ideas were pulled from conversations Engaggit surfaced automatically — but they're only the tip of the iceberg. Every day, Reddit is full of people describing the exact problems your future users have.
Download Engaggit (https://engaggit.com/) and track Reddit posts yourself, adapting the feed to your specific needs. Set up interests around your niche, get relevant conversations scored on your machine, and read real problems in your market's own words — before anyone else does.
Engaggit is a privacy-first, AI-powered Reddit lead generation app. It runs on your machine, keeps your data to yourself, and helps you never miss a relevant conversation again.