Product Graveyard

Completed Fable 5 Experiment, Not a Commercial Thesis

Lesson · A polished, deployed prototype can successfully validate an AI model's ability to build a coherent game without validating customer demand or creating a reason to operate that game as a commercial product. Portfolio classification should follow the intended experiment and market evidence, not implementation completeness alone.

Completed Fable 5 Experiment Without a Distribution Thesis

Lesson · Deep implementation work can be valuable model evaluation even when it should not become a maintained product. A companion port broadens technical evidence, but it does not create a second commercial product or substitute for validated users, distribution, and willingness to pay.

Insufficient Racing Authority and No Validated Adoption

Lesson · In a high-skill coaching category, curriculum and telemetry concepts do not substitute for trusted domain authority. Validate who customers will accept as an instructor, how that authority will be demonstrated, and whether it creates a credible distribution path before investing in a technically broad training platform.

Workflow Ceremony Overwhelmed Time to Value

Lesson · Review and context-gathering mechanisms should earn their place through better outcomes, not become mandatory product architecture. A skill library can remain useful infrastructure even when the surrounding commercial experience is too heavy to justify continued product investment.

Computer-Use Substitution and No Validated Demand

Lesson · A browserless agent workflow is not a durable product wedge when general computer-use systems can absorb the same task. Validate whether buyers require durable declarative state, review, and drift control—not merely automation—and keep cross-cutting credential infrastructure separate from a vertical wrapper.

No Sustainable Activation Loop

Lesson · Community products need a durable activation loop beyond first-launch excitement. If the founder is not willing and energized to keep recruiting, following up, and creating attendance pull, the community will decay even if the software and event format are solid.

Payment Provider Blocked

Lesson · Validate payment-provider policies before committing to a regulated vertical.

Commodity Economics and Support Burden

Lesson · A technically substantial product is not automatically an economically attractive business. Validate differentiation, willingness to pay, and the support surface before finishing deployment infrastructure in a crowded category with strong free substitutes.

Weak Differentiation and No Validated Demand

Lesson · A feature-rich developer tool is not a business without an urgent workflow, a specific buyer, and evidence that the workflow is valuable enough to displace free notes, Gists, IDE features, or team documentation. Deployment availability must also be reconciled with the canonical product before it is counted as launch evidence.