5 App Ideas Reddit Is Begging Someone to Build — November 16, 2026

November 16, 2026

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 Monday's feed covers 70 new conversations from November 12–15, and they share one thesis: the alternative already exists. The missing product is the transition — the migration plan, the measured spec, the migration bridge, the rollout ladder, the trust layer. Each idea below links to the real 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 the November 12–15 window — a 254-comment thread about why Europe still runs on Microsoft, a backpack spreadsheet that turned into a 20-bag comparison project, a Discord-exit thread where every alternative comes with an operations tax, an automation thread that reads like a deployment postmortem, and a matrimonial thread where the first message is a request for a photo. In each case, the "alternative" is not the hard part. Switching is.


1. The M365 Exit Planner — Europe's Problem Isn't Software, It's Migration

Where: r/BuyFromEU (1,166 upvotes, 254 comments) | Thread: Why isn't Europe investing more seriously in European alternatives to Outlook and Office 365?

The pain: The question sounds like a funding debate, and the top reply reframes it in one sentence: "It is individual corporations and businesses in individual countries that chose Microsoft - not Europe." That is the actual buyer. A procurement lead at a mid-sized organization, not a Brussels program. And that buyer has a very rational fear, stated plainly in the thread: "No one in charge of procurement is ever going to get fired for choosing an off-the-shelf solution from the world's most well known and widely used businesses software." The alternative doesn't lose on features. It loses on career risk.

Why it's promising: The comments contain both sides of the market and a complete list of what breaks. A commenter who identifies themselves as IceWarp, one of the alternatives being discussed, says the quiet part: "The options are actually there. Most people just don't know about them, and I think that's the real problem." Then the herd: "Everyone uses M365, so new companies pick it too, because it feels like the safe default and nobody questions it." An enterprise voice cuts through the ideology: "from an enterprise perspective, the office client is arguably the least important part of the Microsoft 365 suite" — meaning the migration is really about identity, mail flow, SharePoint, Teams, retention, and the add-ins nobody documented. A practitioner describes the human wall: "It's REALLY hard to get users and their managers to accept something other than Microsoft Office and Outlook/Microsoft Cloud", because "you want your offer to look identical from your screen to theirs, your old Excel-stuff mostly works." Another lays out the operating plan nobody sells: "You need to develop solutions for all kinds of incompatibilities and edge cases", "run parallel processes during the transition", and "keep everyone on board, even when things sometimes don't work and it's more expensive for a while." The thread even has a cautionary tale: Munich built its own Linux system, ran it for years, and reversed course in weeks after a change in leadership. And the blunt summary of why the default persists: "A lot of it is just companies avoiding friction at all costs." The market is not asking for another list of European software. It is asking for a way to survive the switch without betting a career on it.

The product spec: An M365 exit planner and migration cockpit for public-sector and mid-market IT:

  1. A dependency and difficulty map. Import the tenant and inventory mailboxes, shared mailboxes, distribution lists, SharePoint and OneDrive libraries, Teams channels, Power Automate flows, Outlook add-ins, SSO apps, retention labels, and eDiscovery holds. Score each workload for migration difficulty, so the plan starts with mail and calendars, not with the thing that will stall the project.
  2. A compatibility lab, not a feature matrix. Test the organization's actual documents, templates, macros, shared calendars, and room-booking flows against each candidate stack — openDesk, Nextcloud, Proton, Tuta, OnlyOffice, Thunderbird, Element — and produce a red/yellow/green report per workload. "Your old Excel-stuff mostly works" becomes a measured claim instead of a hope.
  3. A parallel-run transition plan. Coexistence routing, dual calendars, file sync bridges, staged cohorts, a rollback path, and a change-management kit for managers: what changes, what breaks, who supports it, and what the helpdesk should say in week one.
  4. A procurement evidence pack. Data residency, GDPR/NIS2/DORA mapping, subcontractor lists, exit clauses, lock-in scoring, three-year total cost including migration labor, and a public decision log. This is the artifact that lets a procurement lead defend the choice after the next election or reorg.
  5. A vetted integrator marketplace. Fixed-scope quotes from EU-based partners who have done the specific migration before, with references and a standard statement of work. The buyer gets a defensible plan and a supplier they don't have to discover from scratch.

Price the assessment per tenant (a few thousand euros), then a per-seat migration subscription and a marketplace take rate. The wedge is not patriotism. It's the transition plan a risk-averse IT director can put in front of a board.


2. The Under-Seat Bag Database — 20 Bags, One Spreadsheet, No Measured Volume

Where: r/ManyBaggers (126 upvotes, 62 comments) | Thread: I used the Microsoft outage to make a 20-bag spreadsheet for my next backpack purchase. Help a traveling science tech find the perfect under-seat personal item backpack for US airlines!

The pain: A field scientist who travels with spectrophotometer calibration gear and his own pipettes built a 20-bag spreadsheet to answer a question no retailer answers: which personal-item backpack actually fits a 16-inch laptop, more than 22 liters of gear, and the under-seat space on the US airlines he flies. His hard requirements are precise — a 14" x 10" laptop that a "fits most 16-inch" spec does not cover, a bag that is not stuffed, a vertical luggage pass-through wide enough for a TravelPro handle — and the market gives him marketing copy instead of measurements. He even notes that he would assume a bag less than an inch over the 14" x 18" x 8" guidance is fine if it is not fully packed out. That is a specification, not a preference.

Why it's promising: The thread is full of people doing the same unpaid labor. One commenter admits: "I had a very similar Excel Sheet in the past" and says he is now "trying to turn my sheet into a somewhat handy comparison site for my unending bag search." Another points out the limit of every spec sheet: "Comfort is subjective and you haven't used these bags, so I understand why it's not a factor in your rankings." The OP agrees and describes the columns he couldn't fill: "I actually had columns for material type, back/shoulder padding, and other things like chest straps. Because they're so nuanced though and I can't truly experience them, I found it hard to use it as criteria to gauge bags like this." The buying behavior is equally revealing. He wants to try bags in person — "I just wish it were something I could first see locally in a store somewhere" — values "buying secondhand", and gamed the retail funnel on purpose: he signed up for every newsletter and browsed without an ad blocker so that "within 72 hours, my inbox fills with extra offers from Capital One for additional %-off or points-back deals". He is not looking for a review. He is looking for a decision he can trust with $150 and a carry-on.

The product spec: A fit-first bag database with a packing simulator:

  1. Measured dimensions and a real airline matrix. Internal volume measured with standardized packing media, external dimensions as shipped, compressibility, and a per-airline, per-aircraft under-seat fit score with a margin — not the manufacturer's "personal item" claim.
  2. A packing simulator. Enter the actual gear: laptop dimensions, dopp kit, pipette case, layers, cables. See whether it fits, where it fits, and how much bulge it creates. The OP's "stuffed" test becomes a visualization instead of a photo.
  3. Structured owner reports. Strap width, back padding, pass-through width, laptop access, wear at six, twelve, and twenty-four months, and warranty outcomes. Not star ratings — attributes that survive contact with an airport.
  4. Total cost of ownership. Price history, warranty exclusions (PU zipper degradation is a repeated complaint), repairability, resale value, and secondhand listings, because the audience already shops that way.
  5. Deal watch and try-before-buy. Sale alerts, a map of nearby stores with floor models, and return-window tracking. The OP's newsletter-and-cookie strategy becomes a feature instead of a hack.

Revenue: affiliate links, a paid deal-alert tier, and later a retailer/airline data license. Start with personal-item travel backpacks, measure everything by hand, and publish the method.


3. The TTRPG Server That Splits Chat From Canon — Discord's Ephemerality Problem

Where: r/rpg (110 upvotes, 88 comments) | Thread: Alternatives to Discord for online communities.

The pain: A community organizer left Discord because "I really dislike their user data collection and their app is basically spyware" and wants a platform suitable for tabletop RPG groups. The thread immediately splits into a fight about what a community even is. One camp wants the open web: "give me a publicly indexable forum over discord 10 out of 10 times". The other camp wants the room: "You can't do voice chat and live text on a forum, dude". Both are right, and the tools force a choice.

Why it's promising: The comments are an operations manual for the alternative, including the parts nobody advertises. A Matrix host writes the most useful comment in the thread: connecting people "from a bunch of different clients" sounds nice for the techie, but is "a nightmare for the tech support". The "no possibility of data collection" only holds "if you have no public rooms / no federation", "chat and voice" needs some work to set up properly, and a reliable community needs backups and moderation, not just a server. Another commenter names the content problem: "every single conversation becomes completely ephemeral" and "Searching for any type of information in Discord is a total nightmare of disconnected messages of criss-crossed conversations and vibes." A moderator says Discord is "by far the more horrible place to moderate anything though if your server is bigger than 50 people." The privacy camp gets its counterargument too: "Why do people want siloed, difficult to discover communities? Same reason I have a freaking door on my house." And the discovery problem is real on both sides — "the only way to get there is if someone is benevolent enough to provide a link". The named alternatives (Fluxer, Stoat, Signal, Rift, PieFed, IRC) each solve one slice. None solves the split.

The product spec: A TTRPG-native community server that treats live chat and durable canon as two views of the same community:

  1. Two-mode spaces. Session rooms for voice and live text that archive into a structured recap, plus campaign pages that are publicly indexable when the group wants discovery. No more choosing between a forum nobody visits and a chat log nobody can search.
  2. Session-aware search and recap. Messages attach to a session, scene, character, and ruleset. Search "the ruling about grappling" instead of scrolling. Auto-generate recaps with decisions, NPCs, loot, and open threads at the end of each session.
  3. A Discord bridge as the migration on-ramp. Mirror channels both ways so a group can move gradually, keep the players who won't install anything, and flip the primary when the community is ready. The Matrix comment proves bridges are the only realistic adoption path.
  4. Managed hosting with the boring parts solved. Backups, a real report button, mod logs, raid controls, and a browser/mobile client that doesn't require choosing a client. Self-hosting stays available for privacy-maximalist groups, with one-click deploy and managed updates.
  5. TTRPG integrations. Dice, character sheets, time-zone-aware scheduling, LFG boards, safety tools, and creator storefronts for the GMs and small publishers who run the communities.

Charge per server with a free tier for small groups, a creator tier for actual-play shows, and a marketplace take rate on games and supplements. The wedge is the group that already has a wiki, a Discord, and a scheduling spreadsheet — and hates all three.


4. The Shadow-Mode Kit for Team Automations — Nobody Wants to Babysit an Agent

Where: r/automation (36 upvotes, 50 comments) | Thread: How to create an ai agent that actually does stuff for my team?

The pain: A 17-person startup has spent weeks trying to find an automation setup that handles recurring ops without supervision. "Every guide I find is written for developers or solo people." The ask is modest and specific: "something that handles recurring ops stuff without me having to babysit it". The top reply is the bad news: "What you are looking for does not exists. The very efficiency gain of automation is the very nature that makes it brittle." Then the instruction that frames everything below: "Stop searching and self synthesize the solution yourself with your current biggest bottleneck and tackle it one at a time."

Why it's promising: The rest of the comments are a deployment methodology that no vendor sells as a product. Use "a normal workflow tool... with a single LLM step inside it, not an autonomous agent", because "The model only classifies, extracts or drafts; the workflow decides what happens next." Test on "20-30 real past cases (old emails, tickets, invoices)" and read every output before launch. Put "an error alert on every workflow" because "Silent failures are what kill trust, not occasional wrong answers." Keep "a log row per run (input, output, status)". Give each workflow "one named owner on the team, otherwise nobody fixes it when an API key expires or a form field gets renamed". Route "the uncertain cases to a person" instead of approving everything forever. Start read-only, then enable actions one at a time. Put the facts the agent relies on "in a real database or doc, not only in the agent's memory." And the line that should be the category's tagline: "If you need to babysit the agent every day, you've basically hired yourself another employee lol." One commenter admits the failure mode — "building a general agent first and then hunting for jobs to give it" — while another names the unglamorous market: "the stuff with no API: supplier portals, bank or payroll dashboards, government forms, old admin panels." Every piece of this exists as advice. None of it exists as a workflow with guardrails.

The product spec: A shadow-mode deployment kit for internal automations:

  1. A one-task intake. Force the team to name a single recurring task, its trigger, its system of record, its definition of done, and its owner. Reject "do everything" agents at the door — the thread's most expensive mistake is starting with a general agent and hunting for jobs.
  2. Historical replay and shadow mode. Import 20–30 real past cases, run the workflow without side effects, and diff its proposed actions against what staff actually did. The eval set is the team's own history, which is the only benchmark that matters.
  3. A per-action permission ladder. Read-only, then draft-only, then act-with-approval, then autonomous — enabled action by action, with idempotency, timeouts, and a rollback path. Not a global "autopilot" switch.
  4. Confidence routing plus a run ledger. Send missing-field, low-confidence, and unusual-amount cases to a human queue; auto-approve the boring majority. Log every run with input, output, status, latency, and cost, and alert on silent failures — the thing that actually destroys trust.
  5. The handoff kit. Credentials, API-key expiry, a runbook, and a bus-factor checklist so the automation survives the person who built it, plus an expansion gate: two weeks of runs, a measured fix rate, and an owner who isn't getting paged.

Charge per workflow or per seat, and sell to the ops lead at a 10–50 person company. The promise is not autonomy. It's a boring, inspectable automation that a normal employee can own.


5. Wali-in-the-Loop Matrimony — Photo-First DMs Are the Anti-Pattern

Where: r/PakistaniTwenties (17 upvotes, 48 comments) | Thread: How to find significant other while keeping it halal as a girl

The pain: A 28-year-old doctor in Pakistan is midway through specialization exams and planning a move to the UK. She wants a halal route to marriage, and the formal one has failed her: "The formal rishta culture is way too toxic." Her description is specific — "You will tick all the boxes and boy's mother will just reject you over the silliest thing" — and the online alternative was worse. She messaged a man from a Reddit matrimonial community, and "the first thing he asked me to send him was my picture instead of simply asking my name." Her reaction is the product brief: "how could I blindly trust someone and send my picture without knowing who the person is." She is not asking for a dating app. She is asking for a process that doesn't require her to choose between exposure and humiliation.

Why it's promising: The comments contain a design doc from people who have lived the failure. The most useful reply is blunt: "give your wali's number, not yours", and "the app ones like Muzz have wali access built in so he can see the conversation without being in it." On the photo request: "if a guy's first message is 'send a picture' before he's even asked your name, that's not a red flag you have to interpret, it's a man telling you what he values". On timing and geography: "long distance rishta hunting from Karachi to a UK family is the worst version of this process", so "do it after you land, through your own circle there, mosque communities, other registrars, the hospital itself." Multiple commenters recommend "don't upload your pics, give ur wali contact only", and one names an existing app where "people there are more serious and want more of a halal marriage process". But the thread also shows the tension the product must respect: one commenter notes that in proper arranged marriages, "pictures are shared" — you cannot marry someone you have never seen. The answer is not "no photos." It's staged, consented visibility with a guardian in the loop, which no mainstream app has made the default.

The product spec: A wali-in-the-loop matrimonial platform for Muslim professionals and families:

  1. A guardian seat by default. Add a wali or family representative with read access to the conversation from day one, and route the first contact through the guardian's number rather than the woman's. This is the thread's top piece of advice, productized.
  2. Staged photo consent. No public photos. A controlled reveal after mutual interest and guardian visibility, with an audit log of who viewed what and when. The product respects the comment that seeing matters, without making a photo the opening bid.
  3. Verified intent and claims. Profession and education checks (medical council, employer), family references, marital status, relocation plans, and a short video introduction instead of a photo-first DM. Verification is the trust layer the Reddit matrimonial subs lack.
  4. Intent-first matching. Structured profiles on deen practice, family involvement, timeline, relocation, and dealbreakers; a small number of serious introductions per month instead of infinite swiping. The goal is a family conversation, not a dopamine loop.
  5. Safety rails. No unsolicited DMs, scam and catfish detection, guardian notification on reports, a human review queue, and clear community guidelines. The anti-pattern is already documented in the thread; the product's job is to make it impossible.

Revenue from a professional subscription plus a paid verification tier — not from pay-per-photo mechanics, which would recreate the problem. Build with scholars and community organizations, not around them.


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 tree — so the product spec is built from what people actually wrote, not a title. The November 12–15 export contained 70 posts, all new since Friday's edition: zero thread-ID overlap with the November 13 post. None of the threads above appeared in that edition.


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.