FAILDEX失樂園
中文

REPitchbook

The business, the turning points, and the decisions behind them.

Founded2017
Event year2018

01 / WHAT IT BUILT

What the company did

REPitchbook was a Canadian SaaS product founded in late 2017 by software developer Charlie Reese: it generated customizable, management-consulting-style presentations from real estate market data in seconds, aimed at agents pitching clients, priced at $1,500 per month. Reese built the prototype in six weeks with JavaScript, React, and SQL, and secured a pilot with four agents — then killed the project after six weeks of piloting in 2018, having made $0 in revenue.

02 / REPitchbook FAILURE REASONS

Failure reasons

REPitchbook failed for two reasons its founder named himself. First, a horrible user interface: 100 percent of pilot agents were unable to use the application without in-person instruction, and because it was a tightly coupled single-page application, fixing the UI required a complete rebuild. Second, no email integration: agents did most of their marketing through email, not long-form presentations — Reese had built a printing press for a digital-email market. Underneath both was the classic mistake: he never validated the idea before building, assuming agents wanted professional pitches when almost none did, and piled on half-finished features until nothing felt finished.

03 / EVENT HISTORY

Events in the structured record

  1. Operations ended

    The retained source record identifies the company as having ended operations; the exact event details remain unverified.

04 / CONTEMPORARY REBUILD ASSESSMENT

Difficulty of rebuilding this project today

Material for this section is being gathered and checked. It will appear here once ready.

Rebuild difficultyPending assessmentNot completed
Scoring basisNot completed
ScalabilityPending assessmentNot completed
Scoring basisNot completed

Overall assessment: Not completed

05 / CAUSAL CHAIN

How the factors connect

  1. 01

    Validate before you build: Reese assumed agents wanted consulting-style presentations; almost none did — they wanted email marketing. Six weeks of building could have been six conversations.

  2. 02

    A UI nobody can use without instruction is a failed product: 100 percent of pilot users needed hand-holding, and the verdict was instant.

  3. 03

    Beware the rebuild wall: a tightly coupled SPA meant fixing the design required starting over — architecture choices compound early mistakes.

  4. 04

    Feature creep kills clarity: too many half-complete features left nothing feeling finished; one thing done well beats ten things half done.