How to keep a designer going quiet from locking you out

The accounts that should sit in your name from the start

"I'll have it wrapped up by Friday," the designer said. Three Fridays came and went, and the site is still half-built, sitting on somebody else's account.

Freelancers close their businesses. They change careers, get sick, or lose interest in a project that stopped paying enough to hold their attention. It happens in a field built entirely on independent contractors with no employer keeping tabs on them. What protects you when it happens is not a strongly worded email sent afterward. It is what you secured before the silence started.

The core list is short: the domain registrar account, the hosting account, the CMS or website platform login, and any third-party service tied to the site, like email or a booking tool. Every one of those should exist under your name, your email address, and your payment method. Not your designer's.

What to lock down before the first invoice, not after the silence

This gets easier the earlier it happens. Before a deposit changes hands, ask who is registering the domain and under what account. Ask the same question about hosting, in the same conversation, before any work begins.

A designer who plans to build responsibly will register these in your name without hesitation. Some make it a default step in how they work every single time. One who resists, or explains it is simpler to keep everything under their own account "for now," is telling you something worth hearing before you commit any further money.

If the project is already underway and you never asked, it is not too late to fix. Request account access today, in writing, and treat any delay in getting it as information rather than an inconvenience you should just wait out politely.

A short email works fine for this: state plainly that you would like the domain, hosting, and platform accounts set up or transferred into your own name before the project continues, and ask for a timeline on when that will happen. Nothing about that request is confrontational. Any designer worth keeping will treat it as a completely normal part of doing business, not an accusation.

Save the email once it is sent. If this project ever does stall, that single message becomes useful evidence of when you asked and what was said back.

Contract language that still works when nobody answers

A contract cannot force a missing person to respond. Nothing on paper can do that. It can still do useful work in other ways. Terms that specify exactly what gets delivered, and when, give you something concrete to point to if a project stalls and you need a refund, a replacement, or a paper trail for a dispute.

The full checklist of terms worth getting in writing before you pay goes well beyond this one scenario, and it is worth reading before any deposit changes hands, not after.

A clause naming who holds admin access at every stage of the build matters more here than almost any other line in the document. Why admin access specifically is what determines whether a stalled project is recoverable is worth understanding on its own before you sign.

Why holding your own domain and hosting changes the whole situation

A designer who vanishes while you hold the domain and hosting yourself leaves you with an unfinished site and a search for someone new to finish it. That is genuinely inconvenient. It is also recoverable in a reasonable amount of time, usually within days rather than months.

A designer who vanishes while they hold the domain and hosting leaves you locked out of your own business address entirely. You end up dealing with a registrar that will only talk to the account holder on file, not the business that actually depends on the domain. Getting that back can mean proving your identity to a support team that has never heard of you before.

The ownership foundation that decides how recoverable any of this actually is sits underneath the whole situation. The gap between the two scenarios above is the entire reason it matters before a build even starts, not after.

Telling a slow week apart from someone who is actually gone

Freelancers get busy. A slow week, a missed call, or a "sorry, swamped, will get to this Thursday" is not the same thing as being ghosted. Treating every quiet stretch as an emergency will burn a relationship worth keeping over nothing.

A pattern is different from a single gap. Multiple unanswered messages across more than one channel, a business presence that has gone quiet everywhere at once, or a payment that bounces are all worth acting on rather than waiting out politely, hoping it resolves itself.

Two weeks of silence after repeated attempts, across email, phone, and any messaging app you have used before, is a reasonable line to work from. Shorter than that, give it room. Longer than that, start protecting yourself in earnest.

Once it is clear the designer is actually gone, the next steps look different from anything covered here. What to actually do once a builder has gone silent deserves its own walkthrough, step by step.

Requesting a full handover of every file the project produced so far is the first concrete step either way, regardless of what caused the silence. The specific list of files worth asking for, beyond just the live pages is a good place to start that request.

From there, finding someone new to finish or rebuild the site is a decision worth making carefully, not in a panic born out of a stressful week. Rushing into the next contract without checking the same things you should have checked the first time just repeats the risk you are trying to get away from.

More from the blog

All posts