The Keys to the Kingdom, Please: How One Fan Forum Survived Its Founders Moving On

Every friend-built website has a moment nobody plans for: the day the people who made it want to step away.

For the crew behind ThreadCount — a fan forum for a long-running TV drama that's outlived three network rebrands — that moment arrived last spring. Twelve years of inside jokes, episode breakdowns, and an annual fantasy-draft league were sitting on a $14-a-month hosting plan, and the two founding admins were deep in new jobs, new cities, and, in one case, a new baby. The site wasn't failing. It was just... theirs, and they were leaving.

What happened next is a masterclass in something almost nobody writes about: succession planning for casual internet projects. No legal team, no board of directors. Just friends trying to pass a baton without dropping it.

The Problem With Everything Living in One Guy's Head

The first audit the ThreadCount founders ran was sobering. The hosting account? Under Marcus's personal email. The domain registrar? Marcus again. The moderation playbook? It existed entirely as vibes and a decade of muscle memory. The password to the original Twitter account that drove half the traffic? Nobody knew. Not even Marcus.

This is the default state of almost every friend-built site. When you start something with your buddies, you don't document — you just know. And that knowledge has a shelf life.

Their fix was unglamorous but effective:

• A shared password vault (they went with Bitwarden, set up a dedicated organization, and every credential moved in within a weekend)
• A registrar transfer to an account owned by the project, not a person — with two trusted people as recovery contacts
• A single Google Doc, brutally titled "If We Get Hit by a Bus," listing every account, renewal date, and monthly cost

The bus doc sounds morbid. It's actually the opposite. It's what let the founders relax.

Documentation That Outlives the Inside Jokes

Here's where most handovers die: the wiki page that says "run the usual cleanup script." The usual one? From 2019? The one referenced in a Discord thread that's been deleted?

The ThreadCount crew rewrote their docs with a simple rule: assume the reader is smart but wasn't there. No "the usual way," no acronyms from the group chat, no steps that start at step three. Where an inside joke was load-bearing — like why the spam filter auto-flags any post containing the word "cryptic" — they explained the history in one sentence and kept the rule anyway. Culture survives when it's explained, not when it's gatekept.

They also wrote down the things that feel too obvious to write down: what tone the mod team uses in disagreements, why they never lock threads before 48 hours, the fact that the community voted in 2016 to keep the off-topic subforum even though it's 80% chili cook-off talk.

Mentoring Without Hovering

The incoming admins were three contributors in their early twenties who'd been the most active members for two years. The founders' instinct was to stay close, answer every question, review every change. Their better instinct — after one awkward month — was to set office hours instead.

One hour, every other Sunday, on a voice call. New admins bring questions; founders bring stories. Everything else, the new crew handles solo, including the mistakes. When they briefly broke the search function during a plugin update, the founders heard about it at the next office hour, along with the fix the new team had already shipped.

That's the whole trick, honestly. You have to let the site break a little under new management. A forum that never stumbles under new admins is a forum whose admins are still the old ones.

What the Founders Kept

Marcus kept exactly one thing: a lifetime achievement flair and read-only access. He visits maybe once a month now. The annual fantasy draft still runs — new crew, same trophy, a slightly different scoring system that the founders learned about from a pinned post like everyone else.

The site's traffic dipped maybe 10% during the transition, then recovered. More telling: the new admins have since added a Discord bridge and a mobile-friendly theme the founders had talked about for six years and never built.

If you've got a group project aging alongside you, the ThreadCount playbook boils down to this: move every credential into shared ownership, write docs for a smart stranger, name successors who are already showing up, and then — the hardest part — actually get out of the way.

The site was never the code. It was the fact that people kept showing up. All you have to do is make sure they can keep the lights on when you go.