Ideas our own engine told us not to build

What killed it

• An incumbent can ship this — Cloudflare already provides bot scoring and detection for customers sitting in the request path, and the stated cause of death explicitly acknowledges this incumbent advantage. The product would need defensibility from features Cloudflare won't build, not from dashboards on signals Cloudflare already surfaces.P-1972
• The evidence is too thin to judge — The signal cluster shows operators complaining about bot traffic problems, but none express willingness to pay for a standalone solution or mention trying paid tools that failed. The HN complaints represent awareness, not purchasing intent.S-25S-47S-56S-77S-242
• A free alternative already covers it — The core pain is resource consumption and blocking bad actors, not classification or dashboards. A dashboard that identifies scrapers without actually blocking them or reducing costs leaves the fundamental problem unsolved, while Cloudflare can both detect and mitigate in one step.S-25S-47S-56S-77P-1972

What killed it

• An incumbent can ship this — SimplePractice and Jane both have active products and direct API access to the clinic data, payment rails, and patient records needed to ship the requested features. A third-party cannot offer 'same login' or 'credit cards on file' without those companies granting integration access—which they have no incentive to do if mobile parity becomes table stakes.P-1865P-3035S-1732S-1796
• A regulatory barrier — The stated wedge requires clinic software vendors to expose patient login credentials, payment methods, and appointment history via API to a competitor. No evidence shows SimplePractice or Jane offering this level of access to third parties, and HIPAA compliance would require the clinic to own the patient relationship—eliminating the 'unified login' that differentiates this from yet another booking layer.S-1732S-1796P-1865P-3035
• The evidence is too thin to judge — All three signals come from app store reviews in a 9-month window (Oct 2025–Jun 2026), and all reference existing clinic software apps that are actively maintained. If mobile parity were a structural blocker, we'd see sustained complaint volume across years; instead this reads like a feature gap the incumbents are already working to close.S-1732S-1780S-1796P-1865P-3035

What killed it

• The evidence is too thin to judge — All seven signals are from a single 48-hour window (Aug 6-8, 2026) on one platform (HackerNews), likely representing one viral thread being quoted rather than independent demand. No follow-up complaints exist in the data to suggest this persists beyond the initial discussion.S-32S-87S-104S-106S-108S-114S-140
• A regulatory barrier — Android's security model increasingly restricts background access to motion sensors and lockscreen control, making a third-party app unable to reliably detect 'run mode' or suppress theft alerts without requiring intrusive permissions that would block Play Store distribution.S-106
• An incumbent can ship this — Google already owns the theft-detection feature being complained about and can ship a native workout exception or sensitivity toggle in a single OS update, eliminating the problem before a third-party solution gains distribution. The stated cause of death explicitly predicts this.S-106

What killed it

• The evidence is too thin to judge — All complaint signals come from end users, not vendors. There is zero evidence that SMB SaaS companies are searching for, spending on, or expressing intent to purchase escalation tooling. The market evidence shows pain exists but not that the stated buyer — the software vendor — recognizes it as a problem worth outsourcing.S-1729S-1776S-1986S-2031
• The unit economics do not close — Wave — the primary example in the evidence — is an active product whose users are complaining about *lack* of human escalation, yet Wave has not purchased this solution. If the need is acute enough to generate multiple complaint signals, but the vendor experiencing the complaints has not bought or built an obvious fix, this suggests vendors do not prioritize solving this problem at a price point a third party could charge.P-530S-1729S-1776
• An incumbent can ship this — The only spend signal in the evidence is for Telegram-specific support triage with automatic handoff, indicating that buyers want platform-native solutions integrated into their existing stack, not a generic drop-in layer. This reinforces the stated cause of death: vendors will build this themselves as a routing rule rather than pay for a third-party add-on.S-2839

What killed it

• An incumbent can ship this — Anthropic and OpenAI own the config schemas and have direct retention incentive to ship native workspace-level sync. The stated cause of death identifies this as the most likely outcome within a release cycle, and no evidence shows demand for agent-agnostic sync that would differentiate from the native solution.P-482P-486
• A free alternative already covers it — Git submodules or symlinks already solve config sync across repos for free, and developers coordinating multi-agent work are explicitly managing git worktrees and tracking context per project. A paid CLI that only syncs configs adds no value over existing version control primitives.S-2301
• The evidence is too thin to judge — Only one signal directly describes the core problem of config drift across repos. The rest describe multi-agent coordination, testing infrastructure, or environment setup — adjacent problems but not validation that developers will pay specifically for config sync tooling.S-193

What killed it

• An incumbent can ship this — Microsoft already owns the natural distribution channel (M365 admin console) and the primary AI coding tool in this market (Copilot), making a third-party dashboard structurally disadvantaged. Organizations are already defaulting to built-in Microsoft options over more capable standalone tools, and the cluster shows no signals of buyers specifically seeking cross-vendor dashboards.S-432P-508P-509
• The unit economics do not close — The target buyers are explicitly cost-sensitive about incremental AI seat licenses, yet this product asks them to pay for a separate seat-based dashboard on top of the AI tools themselves. The evidence shows organizations questioning whether to buy Copilot for employees who won't use it fully, not willingness to add another layer of tooling cost.S-154

What killed it

• An incumbent can ship this — Offline sync is a standard mobile engineering pattern, not a defensible technology moat. The incumbent already has the harder problems solved—payroll integration, dispatch workflow, customer data—and adding offline mode is a feature sprint, not a platform rebuild.S-1725S-1726S-1811
• An incumbent can ship this — The complaints clearly identify Housecall Pro as the incumbent, and these are paying customers trapped by switching costs who explicitly say 'switching to another platform is not a simple process once you're invested'. They are complaining, not churning, which means the pain threshold for departure is high.S-1700S-1735
• The evidence is too thin to judge — The signal set is extremely thin for validating a standalone business: 9 complaints over 14 months, all from app stores, with no evidence of search volume, willingness to pay for a solution, or businesses actively seeking alternatives. One mention of operational losses is immediately followed by acknowledgment that switching is too hard.S-1735S-1725S-1726