The Eleven-Listener Podcast Problem: Seven Things Founders Build That Nobody Asked For
Photo: empty office whiteboard sticky notes startup founder unused projects, via images.fineartamerica.com
There is a particular kind of silence in a small business. It is the silence of a podcast episode that has been live for three weeks and has eleven plays, two of which were you, checking the edit. It is the silence of a customer dashboard whose last login was your co-founder in February. It is the silence of a loyalty scheme with printed cards in a drawer.
Nobody in UK SMEs talks about this shelf honestly. We talk about launches, not about the quiet things we keep funding because admitting otherwise would mean admitting we were wrong.
The graveyard, itemised
Seven specimens, all of which I have seen real firms pay for.
The branded podcast. Twelve episodes, a decent microphone, a jingle. No distribution plan, no idea who it was for, and a guest list drawn from the founder's networking breakfast. Cost: roughly a day a fortnight plus editing.
The custom customer dashboard. Built because one client asked a vague question about reporting. Now it is a login nobody uses and a support burden that arrives every time a browser updates.
The loyalty scheme. Designed around what the founder would like as a customer, not what these customers do. Zero sign-ups is not a failure of promotion; it is an answer.
The app. A native app for a business whose customers buy twice a year, when a decent mobile web page would have done the job and cost a tenth as much.
The community Slack or Facebook group. Set up to 'build the tribe'. Two hundred members, four active, all of them complaining about delivery times.
The annual conference. A lovely room, a decent panel, and a net cost that would have funded a full-time hire for a quarter.
The bespoke internal CRM. Built to avoid a £30-a-month subscription. It has one user, no export function, and the person who wrote it has left.
Why we keep doing it anyway
Four honest reasons, none of them stupid.
We mistake activity for progress. A launch feels like growth in a way that a pricing change does not, and launches are more fun to talk about at a networking event.
We are solving for the founder's boredom. After two years of the same operation, building something new is the most appealing way to avoid fixing something boring that actually matters.
We skip the evidence step. The question 'has anyone asked for this?' feels rude to ask in a room full of enthusiasm, so it does not get asked until eighteen months and several thousand pounds later.
And sometimes we build for a customer who is not our customer — the one sophisticated client, the one investor, the one voice on LinkedIn — rather than the twenty who actually pay the invoices.
The kill-or-keep test: behaviour, not gut feel
Gut feel is useless here, because gut feel built the thing in the first place. Use evidence instead. Six questions, and if a project fails four of them, it goes.
- Is it used by anyone who was not involved in making it? Not 'anyone', specifically. Named people.
- Has usage grown, held, or quietly declined over the last two quarters? Flat is a no.
- Can you trace revenue to it? Not a feeling of goodwill — a renewal, an upsell, a deal that would have been lost.
- Has a customer mentioned it unprompted in the last ninety days? Support tickets asking for it count. Silence does not.
- What does it cost to keep alive? Include your own hours at a real day rate. This is where most projects die.
- What actually breaks if you switch it off? If the honest answer is 'nothing, and one person might mention it', you have your answer.
The trap to avoid is the sunk-cost defence: 'we have spent £20,000 on it, we cannot stop now.' The £20,000 is gone either way. The only question is whether you spend another £20,000.
The quarterly pruning ritual
Book one Friday afternoon a quarter. Put a recurring calendar block in and treat it as immovable as a client meeting, because otherwise it will never happen.
Before the meeting, list everything the business runs that is not core delivery: side projects, subscriptions, campaigns, channels, memberships. Add four columns — annual cost including your time, the named person who last used it, the last date it produced anything measurable, and the owner.
In the meeting, sort into three piles. Kill: no evidence, no owner, no traceable money. Park: promising but unproven, with a date to revisit in one quarter. Keep: demonstrable, defended by a person who can cite the numbers.
Then do the unglamorous bit. Sunset things properly — tell the eleven listeners, export the data, cancel the subscription before renewal, redirect the URL. Killing something badly, with a broken login and a customer wondering where their history went, costs you more goodwill than the thing ever earned you.
Where the reclaimed time goes
This is the part that gets skipped. If the ritual only produces a list of cancellations, it is just tidying. The point is that the podcast hours and the CRM maintenance budget go somewhere with a pulse.
Split what you free up in three. Take a third and spend it on the customers who already pay you — a faster quote, a better handover, a phone call that is not a complaint. Put a third into the one activity your existing customers already respond to. And keep a third genuinely free, because the reason founders build graveyard projects is that they have no slack, and no slack means no thinking.
At a junction, half the skill is knowing which roads to stop driving down. The other half is noticing you were on the wrong one long before the fuel light came on.