Onboarding a new web design client: the first month

The contract is signed, the deposit has landed, and the temptation is to open a design file the same afternoon. Resist it. Onboarding a new web design client properly takes a few days of unglamorous groundwork, and skipping it is the single most common reason the first month of a project drifts: no one has agreed what “done” looks like, nobody can log into the hosting account, and the client is still waiting on you to ask for photos you needed a week ago.

Why the first week decides the next three months

A website project runs on a small number of dependencies that all sit outside your control: the client's logo files, their copy, their domain registrar login, their opinion on three homepage layouts. Every one of those things takes the client time to produce or find, and none of it happens automatically just because the contract is signed. If you wait until you need each item to ask for it, you spend the whole project stalled on someone else's inbox. Asking for everything at once, in the first week, means the waiting happens in parallel with work you can actually start, rather than in a straight line that stretches the timeline every time.

A kickoff call checklist worth actually using

A short kickoff call, ideally within a day or two of signing, does more for a project than any amount of email back and forth. Go into it with a list rather than a general chat, and leave with answers to all of it written down somewhere both of you can see again:

• Who has final sign-off on design and copy decisions, by name.
• Login access to the domain registrar, current hosting (if any), and any existing site builder or CMS.
• Brand assets that already exist: logo files, brand colours, any style guide, existing photography.
• A rough content deadline for copy and images the client is providing, set as a date, not “soon”.
• Which pages or features were actually agreed in the scope, read back from the proposal rather than from memory.
• How and how often you will update each other: a weekly email, a shared document, whatever both sides will actually keep up with.

None of this is complicated, but it is easy to skip when a client is keen to see progress and you are keen to look responsive. The call costs half an hour. Chasing the same information piecemeal over three weeks costs far more than that.

Confirm scope before you confirm colours

Clients often use the kickoff call to introduce new ideas that were never in the original proposal: an extra landing page, a booking system, a blog they had not mentioned before. Write these down and park them rather than agreeing on the spot, and go back to the signed scope before the call ends. This is not about being difficult. It is about making sure the project you deliver matches the project you priced, which is exactly the discipline covered in scope creep in web design. The first week is the cheapest possible moment to have the conversation about a change of scope, because nothing has been built yet. Having it in week six, once half the site exists around the old scope, is far more awkward and far more likely to cost you unpaid hours.

Get access sorted before you need it

Domain and hosting access is the item most likely to stall a project for reasons that have nothing to do with design work. A client who registered their domain through a nephew five years ago, or who has forgotten the login to a hosting account nobody has touched since, can turn a five-minute task into a week of chasing. Ask for this access in the first week specifically so any problems with it surface while you still have plenty of runway, rather than the day you are ready to launch and discover the domain is locked to an account nobody can access anymore.

Set the content deadline, then hold it

Missing content is the other reliable stall point. A client who has not sent final copy or photos by the date you agreed will usually not chase themselves, so build a light nudge into your process rather than waiting for it to become your problem later. A short message a few days before the deadline, and a clear statement that the build timeline shifts if the content does not arrive on time, keeps the responsibility where it belongs without turning into a confrontation. This matters more the busier your own pipeline gets. Once you are running several onboardings at once, a simple pipeline board is a reasonable place to track which client owes you what, rather than trying to hold every open item for every project in your head.

Put the process in writing, once, and reuse it

The value of an onboarding checklist compounds the second time you use it. Write down the questions, the access you need, and the order you ask for things, and reuse that same document for every new client rather than reconstructing it from memory each time. This is one of the small pieces of process that starts to matter as you grow from a solo freelancer into a small agency, because a written process is the only way a second person on your team can run a kickoff call the same way you would, without you sitting in on every one.

Patchscout is built for the prospecting side of this, not the onboarding side, but the two connect: the businesses our system finds for you already have a real audit attached, which means you walk into that first kickoff call already knowing what is wrong with their site rather than discovering it after you have signed the contract.

The three free searches at app.patchscout.co.uk/signup are enough to see how much of that groundwork Patchscout does before you ever get to a kickoff call.