Chaque idée devait montrer un acheteur prêt à payer, des preuves tirées de la discussion et un vrai manque, puis survivre à une red team chargée de l'abattre.
Articles passés en revue
25
Lus en détail
3
Idées proposées
7
Retenues
1/7
1 idée retenue
| # | Note | Idée | Type | Catégorie | Douleur | Payer | Timing | Manque | Défense | Faisable |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 6.5 | Agent de revue de jugement avant dépôt pour cabinets d'expertise comptableUne couche QA agentique qui compare les brouillons de déclarations aux fichiers sources clients, souvent désordonnés, et signale les problèmes importants avant le dépôt par le cabinet. | Venture | SaaS B2B | 7 | 7 | 7 | 6 | 6 | 5 |
Écartées · 6 · sous la ligne de 6.0
| 5.6 | Independent token-efficient coding agent harness | Quoted the discussion instead of paraphrasing. |
| 5.4 | Independent Second-Opinion Review for Prepared Tax Returns | The red team found a fatal weakness. |
| 5.1 | Spend observability for agentic coding harnesses | This is a near-duplicate of the recently published per-developer AI coding spend control idea, and the underlying telemetry gap is something Anthropic/OpenAI will close natively in their own dashboards before a third party builds a moat. |
| 4.1 | Maintained Federal Income Tax Rules Engine API | Column Tax already sells a commercial tax-calculation API, PolicyEngine is a free open-source rules engine, and the long-tail builder market that supposedly falls between them is too small and too price-sensitive to sustain a maintained rules corpus. |
| 3.8 | Prompt-layer privacy and config guard for coding agents | A business premised on patching a vendor's precompiled weekly-updating binary is a feature request to Anthropic (stop leaking email in headers) plus generic DLP proxies, and the vendor can kill it with one config change or one privacy fix. |
Voir 1 idées écartées de plus
| 3.6 | Self-hosted synced slide presenting for regulated teams | The actual job — show slides to a remote audience without a third party seeing the deck — is already solved by screen sharing in any self-hosted or approved meeting tool (and BigBlueButton covers the self-hosted case), so a standalone single-purpose presenting server has no budget line and no pull. |