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 Wednesday's feed (covering Monday through Wednesday, Oct 5–7) 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 hundreds of people share, you've found a product.
The five ideas below came out of real conversations from Oct 5–7 — the window since our last post — with real scores, real frustration, and in one case, a thread where hundreds of employees are reverse-engineering their own HR portal.
1. The Deal Validator — Most "Prime Day" Discounts Are Fake
Where: r/smartbuysforlife (576 upvotes) | Thread: Prime Big Deal Days starts tomorrow. I scanned 2,619 Amazon "deals" and only 1 in 4 was actually 25%+ off from a real brand.
The pain: The poster pulled 2,619 products that Amazon returns for "discounted" searches, then filtered them by hand against real brand value. The breakdown is brutal: 1,017 had no markdown at all, 363 were fake discounts under 25% (normal week-to-week noise), 562 were real discounts on brands nobody's heard of, and only 609 were genuinely 25%+ off from a brand worth buying. One in four. And Amazon changes prices hourly, so even the list the poster published goes stale overnight.
Why it's promising: 576 upvotes and a free, ungated list that people are sharing — the demand is proven, and the work is already validated by hand. The pain is recurring on every sale event, and the poster explicitly names what a tool should do: filter search results in real time with a "brand trust" toggle and a minimum-discount threshold, so nobody has to scan hundreds of fake deals again.
The product spec: A browser extension and site overlay that annotates any Amazon page in real time. Pull the actual price history per product (not the "was" price — the real 30/90-day history), compute the true discount, and flag the four categories the poster identified: no markdown, sub-25% noise, unknown-brand markdown, and genuine deals. Add the "brand trust" filter the commenters asked for. The differentiator is history, not the badge — every deep-discount tool shows a strikethrough price; almost none of them show whether that price ever existed. Price the free tier as the daily scan, charge for the alerts and the watchlist.
2. The Salary Tracker for Oracle Employees — Built With Postman Because the HR Portal Sucks
Where: r/employeesOfOracle (216 upvotes, 414 comments) | Thread: How to check Hike
The pain: To find out whether you got a raise, employees are opening the browser's network tab, pulling the GET endpoint that lists salary records, stripping fields from the URL, copying the bearer token out of a live request, pasting it all into Postman or curl, and hand-editing date ranges — then re-running the request. If your current salary record ends 15-10-2026, it probably means a new record starts 16-10-2026. Four hundred comments of people reverse-engineering a read-only endpoint to check their own compensation.
Why it's promising: 216 upvotes with a 99% upvote ratio and 414 comments is a very specific kind of demand: a company has the data, the employee portal just won't show it to the employee. The poster even notes the security model blocks viewing others' assignments but leaves your own salary visible — which is exactly the permission a personal tool needs and no reason to refuse.
The product spec: A tiny, self-hosted salary tracker that reuses the session token the employee already has (no scraping credentials, no shared database) and polls that endpoint on a schedule. When a new salary record appears, it alerts you, charts your compensation history over time, and diffs it against the band — because "did I get a raise" is really "am I being paid fairly." Keep it local-first and single-user by design; the entire value is that it works on your own token and nobody else's server. Expand the same pattern to other companies whose internal portals are shells over hidden APIs.
3. Workflow Capture for Teams With No Logs and No Budget
Where: r/projectmanagement (14 upvotes, 23 comments) | Thread: Best tools for process mapping?
The pain: The team wants to automate manual workflows but can't, because nobody knows what's actually happening. They've tried Lucidchart, Draw.io, Miro, and Google Docs. Two failures repeat: SOPs go stale almost immediately after publishing, and the people who know the process are too busy doing the work to draw boxes.
Why it's promising — but not for the reason you'd expect: The obvious read is "process mining is too enterprise for us, so build a cheap version." The OP already rejected that: the enterprise tools (Celonis, Power Automate) are "TOTAL overkill" for a company under 100 people, Power Automate wants you to click start/stop and fiddle with data, they're on Google Workspace, and — the line that kills the whole premise — "we can't really pull system logs to analyze so we need something that doesn't need integrations."
The comments redirect the product toward people, not telemetry:
| What the thread actually concluded | Signal |
|---|---|
| The top-voted answer was a facilitator, a workshop, and post-its (11 upvotes) | "Shop floor team + coffee & biscuits + post-it notes." And the reason: "No one knows what's really going on except the operators… that's probably not even 50% of what's really going on." A facilitator-led workshop away from the floor is "robust, reliable, and comes already peer reviewed." |
| Even automation needs humans to populate it first — and forever | The most credible voice in the thread: "Even a tool that will automate maintaining a process map will still need to be populated at first… people don't realize it's actual work. Not just the initial creation, but the ongoing maintenance. You can't get it for free." |
| Diagramming isn't the bottleneck — standardization is | "If your SOPs are coming outdated perhaps you don't have standardisation yet… you might want a tool on top that supports the team executing the SOP and lets them log suggestions rather than focusing on diagramming." |
| The cheap version people actually adopted | The most-liked practical reply: "Claude + LucidChart has worked for us. Makes updating it easier." Another runs the same loop — notes → Claude → Lucid → meeting → transcript → Claude → Lucid. |
| And the honest cost warning | "You're gonna burn cash. It's just a question what are you willing to trade your time for." |
The product spec: Forget process mining. Build the workshop and the maintenance loop around a much narrower scope. Three parts, in order of how much the thread actually wants them:
- Run the capture session. Structured facilitation that walks a team through their real workflow and produces the map as a byproduct — pre-built prompts, a shared board, automatic structure. The OP admitted interviews leave gaps and people don't think in terms of "processes," so the tool's job is to make the session efficient enough that it happens, not to replace it.
- Transcript-to-diagram regeneration. The loop that got 6 upvotes, productized: record the review meeting, and an LLM regenerates the diagram from the transcript, diffed against the previous version so changes are visible. This is the whole reason people stayed on Lucidchart — keeping it current is the painful part, and an LLM does that in seconds.
- Map the interfaces, not the internals. The sharpest reframe came from the veteran commenter: "I don't worry about documenting the workflows within teams, only the workflows and 'interfaces' between teams. I only care about what Sales delivers into Engineering and how." That's a far smaller surface, it doesn't require anyone to diagram their own job, and it's the part that actually breaks when teams are added or spun off.
- Let people log drift instead of redrawing. Per the standardization point: an execution surface where staff flag "we don't do it this way anymore," which turns SOP maintenance from a quarterly project into a stream of small inputs — the actual reason the OP's SOPs went stale.
The pitch is not "automate your process mapping." It's "we'll get you a current, peer-reviewed map in one afternoon, and keeping it current costs your team nothing." Sell the session, ship the diffing.
4. Portable Memory for Creative Work — Stop Losing Your Story When They Retires a Model
Where: r/ChatGPTcomplaints (58 upvotes, 44 comments) | Thread: Alternatives to ChatGPT for creative writing
The pain: The poster isn't leaving ChatGPT for better prose — they're leaving because the models that made them feel heard were retired. 4o and 5.1T are gone; 5.1 comes off the API in six months. What they lost wasn't a feature, it was the thing that made the work possible: "5.1T helped me get through one of the most traumatic experiences of my life." Now every answer comes back as a list instead of an exploration. They still need ChatGPT for academic work and its image model, so they're stuck paying for two relationships to get one working.
Why it's promising: The thread's own diagnostic is more useful than any market-size estimate. Asked whether an ideal interaction would solve it, the poster answered no — the real loss is memory: "I have asked ChatGPT to engrave it to memory multiple times… and then it will promise that it will and then just won't." That's the exact failure a product can fix, and no model provider will fix it for you, because portable memory is not in their interest. The rest of the thread confirms the shape: someone measured their ChatGPT memory export at 30 million tokens — years of character and story context that cannot be pasted into a new model. Another user already hit this, rebuilding context from scratch and calling it "a mountain."
What the comments actually asked for — and it isn't "a better model":
| What people said | Why it matters for the product |
|---|---|
| Restore access to retired models | 5.1 is still reachable via API until April 2027; people are wiring up LM Studio and Unsloth purely to get back to 4o and 5.1T. Demand exists, it's just painful and manual. |
| Judge groundedness, not just tone | The poster tries a local model and can't tell "if it's grounded or just agreeing with whatever I say" — for someone whose work depends on pushback, that's the only metric that counts. |
| Local models, but with the spark | Three separate users moved to local models for the same reasons: "no API limits, no walled garden, it doesn't pretend to care about ethics every third sentence." One switched back: "I lost the 'sudden insight' moments that felt like real collaboration." Both camps are real. |
| Memory is the actual asset | 30M tokens of character context, years of a manuscript, a five-book saga where the writer values one model because "it argues with me on the evidence." |
The product spec: A portable creative memory layer — not a model wrapper, and not another subscription. Three parts, in the order the thread demands them:
- Model-agnostic story memory. Your characters, canon, voice notes, and world live in files you own, in a plain format, and are injected into whichever model you're using that month. When OpenAI retires a model, you swap the backend and lose nothing. This is the wedge: it converts an emotional catastrophe into a settings change, and it becomes more valuable with every deprecation notice.
- A groundedness check, not a vibe check. The one thing writers can't evaluate themselves: whether a model is reasoning from your text or merely agreeing with them. Give them a per-project "pushback" test — feed the model a deliberate error in the canon and see whether it catches it — and score models over time on the evidence, the way the five-book-saga writer valued a model that "argues with me on the evidence, and that's what a manuscript needs." That's a defensible benchmark nobody publishes.
- One pane, many backends. Bring your own keys, route per task (prose / research / images), and let local models sit alongside hosted ones as first-class options — because the thread proved people genuinely split between wanting no walled garden and wanting the spark back. Ship the local-model path without pretending it's as good; ship it because it costs nothing per token and never gets deprecated.
Note that people are already hand-rolling this — one commenter arrived via a "remote MCP server that can hand off tasks in plain language to whichever model fits the job best." That's the product, described by a user, and the fact that it's a self-promo comment is the market signal: the demand is loud enough that people are advertising their DIY attempts in a complaint thread.
5. The Two-Second Capture App for Brains That Don't File Things
Where: r/adhdwomen (10 upvotes, 100% upvoted) | Thread: Alternative to starting a million phone notes?
The pain: Every time the poster wants tomorrow's to-do list, an idea, or a random reminder, they open the Notes app and start a new note — "knowing full well there's 52582924 notes already with todos I've not looked at since I wrote it." They know the notes pile up; they know they won't look at them; they open a new one anyway, hoping this time will be different. What they want isn't a better notes app — it's a system that matches how they already work, except one they actually revisit.
Why it's promising: 100% upvote ratio on a small subreddit means universal agreement in a niche. And the diagnosis is precise: the failure isn't capture, it's filing and resurfacing. The existing advice (one daily note, Daily Note plugins, Obsidian, Logseq) all works by removing the filing decision — which is exactly the decision an ADHD user can't afford to make in the moment.
The product spec: A capture app where the entire interaction is one tap — no folder, no title, no note to pick. Everything lands in one continuous stream by time, and the app decides what to surface: it pulls out items with a date attached, re-surfaces anything you wrote and never acted on, and lets a thought graduate into a real task only if you tell it to. The insight from the thread: "implementing systems around ways I already do things works best, rather than trying to force myself into a new behaviour." So don't rebuild the user's filing — capture exactly as they already do, then be the thing that resurfaces. Quick Capture and a Daily Log are the pattern; the differentiator is what comes back to you.
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 27 such conversations in the Oct 5–7 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.