At a glance
WHAT IT’S REALLY ABOUT
Identify and eliminate startup “terrorists” who hijack progress and value
- A “terrorist customer” is one that consumes disproportionate time and resources, dictates the roadmap, and creates negative value—often because the founder feels hostage to the revenue or attention.
- Founders must distinguish between valuable-but-difficult relationships (positive net impact) and truly destructive ones that hijack execution and continuously escalate demands.
- Even good customers can make “terrorist requests” (money-losing projects or irrelevant features), and blindly fulfilling requests is a leaky strategy because users often can’t articulate what truly drives success.
- The same destructive dynamic appears internally via “terrorist recruits/employees,” where founders rationalize endless special demands and the relationship stays net-negative over time.
- Investors can also behave like “terrorists” by monopolizing founder time with endless questions or by projecting pessimism that erodes founder confidence; good advice requires candor plus genuine belief in the founder.
IDEAS WORTH REMEMBERING
5 ideasA terrorist is defined by net-negative value and hijacked attention.
They don’t merely create friction; they dominate the roadmap/time budget and still don’t produce proportional progress or value. The tell is a “cloud of problems,” not a single issue.
Revenue quality matters more than revenue quantity.
Early startups can become trapped by a “shiny logo” that pays but forces custom work, margin loss, and constant fire drills. Founders are often shocked, but sometimes the correct move is to stop servicing that revenue.
Treat “terrorist requests” as a separate category from “bad customers.”
A generally good customer can ask for money-losing work or irrelevant features; the founder’s job is to say no (or re-scope) and stay aligned to what actually improves the customer’s outcomes.
Don’t assume customers know what to ask for—synthesize signals instead.
Users often request literal features that don’t address the real driver (e.g., Facebook’s early “best feature” was having all friends on it—growth that wouldn’t appear in user research; Twitch streamers didn’t ask “pay us,” but clues showed monetization was the need).
Escalating concessions are an anti-pattern—saying yes invites more asks.
These dynamics rarely resolve through negotiation or “finessing.” Once you demonstrate pliability, the request stream grows, and the startup loses compounding time needed for product and growth.
WORDS WORTH SAVING
5 quotesIt's like, this customer is a terrorist. Like, they are actively bombing your startup.
— Michael Seibel
We're supposed to be doing this mutual exchange where we both improve. We're not supposed to be doing this exchange where I die.
— Michael Seibel
The thing about terrorist employees, like when you do the PNL, the cost benefit analysis, it is always negative with potential.
— Michael Seibel
Blindly following feature requests, it's a, it's a leaky bucket. There's a hole in the bucket, and you will never fill it if you're just blindly following feature requests.
— Dalton Caldwell
You don't deserve terrorists. This is hard enough without terrorists.
— Michael Seibel
High quality AI-generated summary created from speaker-labeled transcript.
