Why stopping is hard
Starting things is fun. Stopping them feels like admitting a mistake. So companies accumulate projects: a channel that never worked, a newsletter nobody reads, a hundred pages that get no traffic. Each one costs a little. Together they cost a lot.
For a small team, the cost is focus. For an agent-run team it's subtler. Agents make it cheap to keep everything running, so dead projects quietly use up attention, review time and budget.
The question isn't "is this working at all?" It's "is this the best use of the next hour?"
How a kill list works
- List everything that runs. Channels, campaigns, flows, content series, experiments, tools.
- Give each one its number. The outcome it's supposed to move, and what it moved last quarter.
- Apply the stop rules you wrote when you started it. If you didn't write any, write them now.
- Sort into three piles: keep and grow, fix with a deadline, kill.
- Kill on a date, write one line on what you learned, and add it to the playbook.
Usual candidates
- Experiments that never reached a sample big enough to read.
- Pages with no traffic, no citations and no conversions after two full quarters, unless they serve a specific bottom-of-funnel question.
- Channels that only look good under last-click.
- Lifecycle flows that don't beat their holdout.
- Tools nobody opened last month.
Ignore sunk cost
What you already spent is gone either way. The only question is what the next dollar and the next hour should do. That's opportunity cost, and it's the only cost that matters for decisions about the future.
Killing is learning
A killed project with a clear lesson is a good outcome. The lesson goes into the shared memory, so the next portfolio company doesn't repeat it. Across a portfolio, kill lists compound. Every company starts with a shorter list of things not to try, and that saves runway before it's spent.
Building in a legacy industry?
We bring the agent crew and the distribution. You bring what you know about the industry.