When Your Web Company Shuts Down (or Locks You Out)

The ghosting story everybody knows is the dramatic version: deposit paid, project half-built, designer gone dark. The quieter version is often worse, because it happens years later, after a successful project, when everything was fine.

Your designer retires. Or the agency downsizes and your project's developer was the one let go. Or the "web company" was always one person, and that person's life moved on. Or — the most common modern variant — the company is still in business but has decided your $49/month plan is now $249/month, and moving off their platform means rebuilding from scratch.

Nothing about your site broke. Everything about your control over it did. This piece is about that day, and about the audit that would have prevented it.

First: what you actually control today

The recovery process starts with a ten-minute inventory. Answer these questions now, ideally today, while everything is calm:

The domain. WHOIS lookup — is the registrant you or your business? If it's your designer's name, your domain is an asset inside someone else's account, and its fate is now tied to theirs.

The hosting. Whose account is the site hosted in? Can you log in to the hosting control panel? If the answer is "the company handles all that," you have no hosting — you have an arrangement.

The site files. Do you have a complete, current copy of the site — code, database, images — in your possession? Not "they have backups." A backup you can't reach is a hope.

The analytics. Is your Google Analytics property in your Google account? Your Search Console? Who really owns your website covers why these four answers determine everything about your options.

Score yourself: four yeses means a shutdown is an inconvenience. Three or fewer means a shutdown is a crisis — and the fix is a conversation to have now, while the company is still answering.

If they've already shut down

The recovery path, in order:

The domain first. The domain is the crown jewel — without it, the site doesn't matter because nothing points to it. If the registrar account is the designer's, contact the registrar with proof of business ownership: invoices showing the domain was purchased for your business, correspondence, business registration. Registrars have recovery processes for exactly this situation; they're slow, and they work more often than people expect. If the domain is in your name but the designer held the login, this is a password reset, not a crisis.

Then the site. If hosting was in your name, move the site to any host — any competent developer can handle a migration if you have the files. If you don't have the files, partial recovery is possible: the Internet Archive's Wayback Machine often holds complete copies of public pages, and a rebuild can start from there. Content you own (text, photos, your logo) usually survives somewhere — in your email, in drafts, on social media.

Then the rebuild. The honest part: if you control neither the domain nor the files, the site is probably gone, and the task is a rebuild, not a recovery. The silver lining is that the rebuild is faster and cheaper than the original — the decisions are made, the content exists, the photos exist. And this time you build it under the ownership rules in the pieces above.

The lock-out that isn't a shutdown

The most common version of this story isn't a company folding — it's a company that's very much alive, changing the terms. The monthly-fee site that was $299 is now $399. The "unlimited edits" plan now bills edits hourly. The platform company gets acquired, and the new owners have different ideas about pricing.

None of these are breaches of contract — they're exactly the kind of change the contract permitted. The protection isn't legal; it's architectural: if your site is portable, a price increase is a negotiation, because your alternative is real. If it isn't, a price increase is a ransom. That's the entire argument of the real math on "$299/month" websites: the monthly number matters less than whether the asset is yours to walk away with.

Why one-person shops deserve a fair hearing

This is the part where the internet's usual advice goes wrong. The conclusion people jump to — never hire a solo operator, they might disappear — is the wrong lesson, and it's worth saying why.

Small studios and solo designers retire, get sick, and change careers. So do the senior developers at large agencies — you just don't hear about it, because the account manager who answers your email was never the person who knew your site anyway. The scale of the shop predicts almost nothing about continuity. What predicts it is whether the arrangement survives the person: your accounts, your files, your logins, your data.

The right question isn't "how big is your company?" It's "if you weren't available next month, what would I still control?" A solo operator who can answer that question well — client-owned everything, documented handoff, a peer network — is a safer bet than a 40-person agency whose platform you can't leave.

We're a single-operator studio ourselves, and we think that question is the single fairest thing a client can ask. The answer should be structural: you own the code, the domain, the hosting, the accounts. Our process is built so that "what if something happens to Travis" has a boring answer.

The audit, again, because it's the whole article

If you take one thing from this piece: spend ten minutes this week answering the four questions — domain, hosting, files, analytics. Every shut-down horror story is a story about someone who didn't, and every smooth recovery is a story about someone who did. The audit is free, the fixes are cheap while the relationship is good, and both prices rise steeply after the goodbye email bounces.

And if you're choosing your next designer, the full protection stack is already written: ownership, the launch handoff, and the contract terms that make all of it binding.

Questions about what you'd control if your situation changed tomorrow? We answer every enquiry personally, within one business day.