The Project That Almost Failed Before It Began: How to Onboard a Web Client Properly
The unglamorous first two weeks that decide whether your website launches on time, on budget, and actually works.
Every web agency has a version of the same story. The kickoff call goes well. Everyone is excited. Then the first design arrives, and the client says it is “not quite what I pictured.” Two weeks later, a login is discovered to be with an ex-employee. A month after that, the client sends a list of new pages that were never in the brief, and the launch date quietly slips into the next quarter.
Almost none of these problems are about design or code. They are about onboarding, the process of getting the client, the agency, and the project onto the same page before any real work starts. Done well, onboarding feels slightly boring. Done badly, it feels like a fire drill that never ends.
This guide walks through what both sides need to prepare, why each step matters, and how to avoid the traps that turn a promising project into a stressful one.
Start with the goal, not the sitemap
Most clients arrive with a list of pages in their head: Home, About, Services, Gallery, Blog, Contact. It feels like a brief, but it is actually a symptom. A list of pages tells you what the site contains. It does not tell you what the site is for.
Ask the question that actually shapes the work: what should a visitor do after they arrive? A clinic may want patients to book appointments. A furniture shop may want online orders. A consultancy may simply need enquiries from the right kind of buyer. Each goal leads to a different structure, different calls to action, and a different homepage.
Write down one primary action and two or three supporting actions. Keep the document short. Every later decision, from the navigation menu to the colour of the button, can be checked against it. When a new request arrives, the question becomes simple: does this help the primary action or distract from it?
If you are unsure how to define that goal, our website development services page explains how we approach discovery for different business types, and it is a useful reference for clients who have never commissioned a site before.
Describe the audience like a person, not a demographic
“Everyone who needs our services” is not an audience. It is a wish. A useful audience description sounds more like a short story. “A homeowner in Ambala who has water pouring through the ceiling and needs a plumber before the evening” tells a designer exactly what the homepage must communicate in the first five seconds.
Describe the people who will visit the site: what they are worried about, what they already know, what they need to see before they trust you, and what would make them leave. This description shapes the headline, the tone of the copy, the order of information on the page, and even the length of the contact form.
Clients often skip this step because it feels soft. It is the opposite. It is the most practical document in the whole project, and it gives both sides a reference point when opinions start to clash.
The accounts list nobody wants to make
Access is the most overlooked part of onboarding, and it is where the most expensive delays happen. Before any build begins, the client should know which accounts the site depends on, and who controls each one.
That list usually includes the domain registrar, the hosting account, the email service, the existing website’s admin login, the Google Business Profile, Search Console, and any analytics property. Many projects stall for weeks because the only person who knows a password has left the company or is on holiday during launch week.
Create one shared, secure document that lists each account, the username, the owner, and who has administrator rights. Add the agency as a user wherever the platform allows it, rather than passing passwords around in messages. Keep the list updated, and treat it as a living part of the project.
Domain and hosting questions are worth clarifying early too. If you are unsure how your domain is set up, the Google Search Console help centre is a good place to verify ownership, which becomes essential once the site is live.
Content is where the real timeline lives
An agency can design a beautiful layout in a week. It cannot write about a business it has never worked in, and it cannot invent testimonials, prices, or team bios. Content is the dependency that causes the most delays, and it is almost always underestimated at the start.
Before the project begins, gather the material the site will need: a company description, service descriptions, team biographies, pricing if you plan to publish it, frequently asked questions, testimonials with permission, and the legal pages such as privacy and terms. If some of it does not exist yet, say so on day one. Some agencies offer copywriting as part of the package, and it is far better to agree that at the start than to discover the gap in week four, when the design is already locked.
Images deserve the same attention. Original photographs of the team, the premises, the products, or completed work make a site feel real. Stock photography can fill gaps, but it rarely builds trust on its own. Supply the highest resolution files you have, and confirm usage rights if a photographer took them. Logos should come as vector files where possible, along with brand colours and any fonts the business already uses.
A timeline that survives contact with reality
A useful onboarding plan splits the project into named stages: discovery, structure and wireframes, visual design, development, content entry, testing, and launch. For each stage, note what the agency will deliver, what the client needs to provide or approve, and the date by which that approval is needed.
Approvals are where projects drift. When feedback arrives scattered across email, WhatsApp, phone calls, and a comment in a shared file, the agency spends its time reconciling conflicting notes instead of building. The fix is simple but needs discipline: nominate one person on the client side who gives consolidated feedback, and agree in writing how many rounds of revisions are included in each stage.
For a broader view of how a well-run project fits together, our guide to why a well-developed website boosts digital marketing results explains why each stage matters beyond the launch day itself.
Define “approved” before anyone sees the design
One of the most common frustrations in web projects is a client who signs off on a homepage, then asks for changes that touch every page. The second is a client who adds new requests after everything appears finished. Both are predictable, and both can be prevented with a single agreement.
Decide what “approved” means before the first design appears. Once a stage is signed off, further changes should be logged as a new request, with a note on any effect on cost or timeline. This is not about being rigid. It protects both sides, keeps the schedule honest, and makes it clear which decisions are being made.
A written sign-off, even a short email confirming that the design is approved for development, saves more arguments than any contract clause.
Plan for life after launch
A website is not finished when it goes live. It is the start of a process that includes renewing the domain, keeping hosting and security current, updating prices and opening hours, and adding new content over time. Projects that skip this conversation often end with a site that is out of date within six months, because nobody knows who is responsible for changing it.
Decide early who will manage content: the client, the agency on a retainer, or a mix of both. Write the answer into the handover documents. If the agency is maintaining the site, a dedicated website maintenance service covers updates, backups, and security monitoring. If the client will handle content, make sure they have been trained on the editing tools before launch, not three weeks after.
Your first meeting checklist
Preparing for the first meeting takes a few hours, and it saves weeks. Bring a clear goal, a short audience description, your accounts list, a content inventory showing what you have and what you still need, and a rough timeline with approval dates. Know who will give feedback and who will sign off.
The agency will still have questions. That is healthy. But when both sides arrive with the right information, the questions are the right ones, and the project starts from firm ground instead of guesswork.
If you are planning a new site and want help structuring onboarding, contact the Pansofic team, and we will walk through it with you before you make any commitments.
FAQs
How long should onboarding take before design starts?
For a typical small business website, one to two weeks is realistic, depending on how quickly the client can gather content and access. Rushing onboarding usually costs more time later than it saves now.
What if I do not have written content or professional photos yet?
Tell the agency on day one. Many can provide copywriting and photography support, or work with placeholder content while you prepare the real material. What matters is that the gap is visible early, not discovered at launch.
Who should own the domain and hosting accounts?
The business should own them, in the business’s name, with administrator access held by at least two trusted people. Agencies can be added as users. Never let a single individual, or an agency, be the only holder of critical accounts.
How many revisions should a project include?
It depends on the scope, but most projects work well with a fixed number of revision rounds per stage, clearly written into the agreement. Additional rounds can be quoted separately. This keeps feedback focused and prevents endless tweaking.
Can onboarding happen remotely?
Yes. Many successful projects run entirely over video calls and shared documents. The critical factor is not location but clarity: a named decision-maker, a shared accounts list, and written approvals at each stage.
Start the project on solid ground
Onboarding is not glamorous, but it is the foundation everything else rests on. Clear goals, a real picture of the audience, secure access, prepared content, and agreed approvals turn a risky project into a predictable one. Give it the attention it deserves in the first two weeks, and the rest of the build tends to run far more smoothly.
Further reading: Pansofic web development services · WordPress vs custom website for Chandigarh businesses · Google Search Console help

Comments
Post a Comment