The web design client onboarding process, step by step

The two things that actually make projects late

Ask ten freelancers why a build dragged on for four months and you tend to get two answers: we were waiting on content, or the client expected something that was never in the quote.

You will find confident percentages for both of these online. Treat them carefully. The figures that circulate usually come from one firm's audit of its own projects rather than any independent survey, and the honest position is that nobody has measured this properly across the industry. What is consistent in practitioner accounts going back more than twenty years is the direction, not the number: client content arrives late almost regardless of how organised both sides are, and roughly every week of content delay pushes the build back by a week, because the work is content shaped. You cannot lay out a page around text that does not exist yet.

Undocumented scope is the quieter problem and usually the more expensive one. It rarely arrives as a big argument. It arrives as five small requests that each sound reasonable: a second language, a booking form, product filters, a newsletter signup that syncs to their mailing list, one more round of revisions. Each one is a few hours. Together they are the difference between a profitable project and a month you would rather forget, and the awkward invoice conversation at the end is really a conversation about something you never wrote down in week one.

Everything below exists to close those two gaps before any design work starts.

The sequence at a glance

Here is the whole thing in order, with rough days so you can see the shape. Adjust the dates, keep the order.

1. Day 0: enquiry arrives and is logged in one place, with a task to respond within 24 hours.
2. Day 1: intake questionnaire sent, before you quote anything.
3. Day 2 or 3: proposal and scope sent, with exclusions and revision rounds written in.
4. Day 3 or 4: contract signed, deposit invoice issued and paid. No work starts before this.
5. Day 4: welcome message with the asset and credential checklist, plus the dated content deadline.
6. Day 5 to 7: kickoff call, 30 to 45 minutes, with an agenda you send in advance.
7. Day 8 onwards: build starts, automated reminders handle the content chasing, you handle the design.

Seven steps, one week, no heroics. The point of writing it down is that you stop making judgement calls under pressure about whether to start before the deposit lands.

Step 1: an intake questionnaire before you quote

Quoting from a 20 minute phone call is how studios end up pricing a brochure site and building a shop. Send a short form first, and treat refusal to fill it in as information about the project.

Ten questions is usually enough:

• Who signs off the final site, and is that person available during the build?
• What should the site do that the current one does not? Ask for something measurable, such as enquiries per month or bookings taken online.
• Which pages do you need on day one, and which can wait until after launch?
• Who is writing the text: you, us, or nobody yet?
• Do you have professional photography, phone photos, or nothing?
• Do you need to take payments or bookings, and through which provider?
• What has to connect to the site: an email tool, an accounting system, a till, a CRM?
• Is there a launch date, and what is driving it (a trade show, a lease, a campaign)?
• What budget range are you working to?
• Which three sites do you like, and what specifically do you like about them?

The answers change your quote, not just your schedule. A client with no text and no photos is a content project with a website attached, and should be priced that way. If you package your work rather than quoting from scratch each time, it helps to have your web design pricing packages written out already so the questionnaire maps onto a tier instead of a blank page.

Step 2: scope in writing, with the exclusions spelled out

The inclusions list is the easy half and most people write it. The exclusions list is what protects your margin, and most people skip it because it feels negative. It is not negative. It is the kindest thing in the document, because it is the only part that tells the client what they will need to buy separately before they have spent their budget.

Write exclusions as plain sentences, not legal clauses. Typical ones worth naming:

• Copywriting beyond light editing of text you supply.
• Stock photography licences, custom illustration and logo design.
• More than the agreed number of revision rounds (two is a common default, and say what counts as a round).
• Translation or a second language version.
• Data migration beyond a stated number of products, posts or listings.
• Third party plugin or subscription costs, and who pays them after launch.
• Ongoing updates, backups and support after launch, which belong in a separate care plan.
• SEO work beyond basic page titles, descriptions and a sitemap.

Add two mechanics that do more work than any wording: a named approval owner, and a change request process. The change request process can be one line. Anything outside the scope above is quoted as a small written addition before it is built. Clients almost never object to this when they read it on day three. They object when they hear it on day sixty.

While you are writing scope, decide what happens after launch and say it out loud in the proposal, even if you sell it later. Monthly website care plans are far easier to sell as a line on the original document than as a surprise email the week after you hand over.

Step 3: deposit before any work starts

No deposit, no calendar slot. This is the single rule that separates studios with predictable months from studios that are always waiting on something.

There is no universal standard for the amount. Across freelancer guidance and practitioner discussion, most small studios sit between 25% and 50% up front. On smaller projects, 50% on signature and 50% on launch is the common convention. On larger builds, splitting into thirds is more usual, for example 40% to start, 30% at design approval and 30% at launch, so neither side is carrying the whole risk at once. Deposit and refund rules differ by country, and so does what you can call non refundable, so have your terms checked where you actually trade.

Two practical details. First, send the deposit invoice automatically with the signed contract rather than as a separate manual step, because a day of silence here becomes a week. Second, set the payment reminders at the start, not after the invoice is already overdue: one at three days, one at seven, one at fourteen. An invoice that chases itself removes the most uncomfortable message in the whole process from your to do list.

Step 4: collect assets and logins in one place

This is where projects quietly fall apart, because the information arrives in six channels and you end up as the search engine for your own project. Send one checklist, in one place, with one deadline.

What to ask for:

• Brand: logo files (vector if it exists), colours, fonts, any brand guide.
• Content: text for each page, in the page order you agreed, plus product or service details and prices.
• Photos: real photos of the team, premises and work, at full size, not pulled off social media.
• Legal: company registration details, terms, privacy and refund information, VAT or tax numbers where relevant.
• Access: domain registrar, DNS, existing hosting, payment provider, email provider, analytics, Google Business Profile, social accounts.
• People: who receives enquiries, who answers the phone, who gets the invoices.

On access, insist on invitations and roles rather than shared passwords wherever the service supports it. Being added as a user to a domain registrar or payment account is reversible and auditable. A password pasted into a chat thread is neither, and it makes you responsible for something you cannot control. When a client has nothing but a password, change it at handover and document that you did.

One more habit: name the files. A folder called final_final_v3.jpg is a future hour of your life. Ask for a simple convention, such as homepage-hero.jpg or team-sarah.jpg, and the build goes faster.

Step 5: the kickoff call, with an agenda

Keep it to 30 to 45 minutes and send the agenda beforehand, so the call is for decisions rather than discovery. Discovery already happened in the questionnaire.

1. 5 minutes: confirm the goal of the site in one sentence you both repeat back.
2. 10 minutes: walk the page list and the sitemap, and agree what is in phase one.
3. 5 minutes: read the exclusions out loud. Yes, out loud. It takes two minutes and prevents most end of project friction.
4. 10 minutes: content. Who is writing what, by when, and what you will do if it is late.
5. 5 minutes: communication. One channel for decisions (email or the portal), feedback in a single consolidated round rather than daily messages, and a response window on both sides, such as five business days.
6. 5 minutes: the dates. Design review, content deadline, build, launch window.

Send a written summary within the day, listing decisions and owners. That summary, not your memory of the call, is what you refer back to in week six.

Step 6: a dated content deadline with a written consequence

A deadline without a consequence is a wish. The reason content slips is almost never bad faith. It is that writing about your own business is hard, and your client has customers to serve today. So make the default outcome something that keeps your schedule intact.

Wording along these lines, adapted to your terms and checked locally, does the job:

Final text and images for all pages are due by 4 November. If content for a page has not arrived by that date, we will build the page with placeholder content, invoice the completed milestone, and schedule content insertion as a separate task at our current rate. Projects paused for more than 30 days are rescheduled into the next available slot at the rates in force at that time.

The effect is not punitive. It is that the client now has a reason to send three paragraphs this week, and you are not holding an unbillable, half finished project through a quiet month. If you do have to act on the clause, do it calmly and on the date, not two weeks later with an apology. Acting on the date is what makes the clause real next time.

It also helps to ask for content in small pieces rather than one big document. A form with a field per section, one page at a time, gets filled in. A request for the whole site's copy does not.

Let the software do the chasing

Everything above is process, and process delivered by hand quietly turns into a second job: the welcome email, the reminder, the second reminder, the invoice nudge, the note to yourself to check whether the photos arrived. Automate the repetitive parts and keep your attention for the design.

The triggers worth setting up, in roughly this order of payback:

• Enquiry form submitted: create the contact and a deal at the enquiry stage, and a task to reply within 24 hours.
• Proposal sent: a follow up task at day three and day seven if there is no reply.
• Deposit invoice unpaid: automatic reminders at three, seven and fourteen days.
• Deposit paid: send the welcome message, the asset checklist and the calendar link for kickoff.
• Three days before the content deadline: a reminder to the client listing what is still missing, and a task for you.
• Deadline date reached: a task that forces a decision, which is either move the date in writing or apply the placeholder clause.
• Launch date: a task to ask for a review and to open the care plan conversation.

None of this is complicated automation. It is six or seven rules that remove the admin you forget when you are busy, which is exactly when forgetting costs money. If you want the longer version of how a pipeline, stages and follow up rules fit a studio's week, the guide on a CRM for a web design agency covers the setup in more detail.

What the tool stack costs

Most studios assemble onboarding from separate tools, which is fine and often the right call early on. It is worth knowing what the assembled version costs before you decide. Prices below are US list prices at the time of writing (October 2026) and will change.

Two honest observations. A freelancer with three clients a year does not need any of this and should use a form, a folder and a calendar. A studio onboarding two or more clients a month will spend either money on tools or hours on chasing, and the hours are usually dearer.

Running onboarding inside the client's own account

The version that creates least work is when the enquiry, the onboarding tasks, the invoices and the website all sit in one account instead of four tools that do not speak to each other.

With WebNewBiz, an enquiry from a site form lands in the AI CRM as a contact with a deal, where it can be scored, assigned a task and moved through stages. Onboarding steps become tasks and workflow automations that fire on a trigger such as a form submission or a scheduled date, which is what lets the content reminders and the deadline check run without you. Invoices chase themselves, and store buyers or funnel opt ins become contacts automatically rather than arriving as a notification you file somewhere. The CRM starts on the Growth plan at $79 per month, which is worth knowing up front: the cheaper Lite and Starter plans build sites but do not include the CRM, and every plan is $1 for the first month.

For studios building for clients, the white-label website builder side matters more than the feature list. Clients log in to a panel carrying your name, logo and colours, on your own dashboard domain such as app.youragency.com, with invites, emails and invoice PDFs branded as your agency. You create each client account, put it on a plan with limits, and either log in as the client to do the work yourself or let them do it themselves. You sell at your own prices, through your own packages and your own Stripe or PayPal account, so payments come to you. The same arrangement applies on the white-label CRM side for clients who want the pipeline rather than just the site. If you also run campaigns for clients, the email, social and marketing automation tools sit on the higher plans.

Where it is weaker, plainly: WebNewBiz is younger and smaller than Duda, GoHighLevel or Webflow's agency programmes, with a much smaller app ecosystem and community than Wix or Shopify. Agency pricing is not published, so you have to ask, which is a genuine nuisance when you are comparing options on a spreadsheet. Nothing in the platform replaces an e-signature tool, so keep yours for the contract itself. And the AI first draft of a site is a draft: it still needs your edits, your client's real photos and their real facts before anyone sees it.

One thing that fits neatly at the proposal stage: the free AI Website Preview designs a homepage from one sentence about a business. Putting a rough concept in front of an undecided client is often more persuasive than another PDF, and it costs you nothing.

Mistakes worth avoiding

• Starting design before the deposit clears. Every studio does this once for a client who seems certain. The certain ones pay on time anyway.
• Letting feedback arrive in three channels. Decisions made in a chat thread do not exist. One channel, consolidated rounds.
• Writing the site structure before the content exists. You will design a layout for text nobody has written, then redesign it.
• Accepting unlimited revisions to win the job. Say two rounds and define a round. Price the third.
• Having no handover document. List logins, where things live, who owns which account, and what the client is responsible for after launch.
• Onboarding everyone identically regardless of size. A $600 one page site does not need a kickoff call. It needs a form and a deadline.

Quick answers

How long should web design client onboarding take?

Aim for about a week from signed proposal to kickoff call. The questionnaire, contract and deposit can all happen in the first two or three days; the asset and credential collection is usually what stretches, which is why it needs a dated deadline rather than a polite request.

Should I take a deposit before any work starts?

Yes. Small studios commonly take 25% to 50% up front, with 50% on signature and 50% on launch being the usual convention on smaller projects and thirds more common on larger builds. Deposit and refund rules differ by country, so have your terms checked where you trade.

What should the intake questionnaire ask?

Who makes the final decision, what the site must achieve in measurable terms, what pages are needed, who writes the text, whether photography exists, which systems must connect (payments, booking, email), the launch date and the reason behind it, and the budget range.

What do I do when the client never sends the content?

Act on the date you agreed rather than waiting. Build the page with placeholder content, invoice the milestone that is complete, and treat content insertion as a separate scheduled task. This only works if the consequence was written into the scope before you started.

Do I need a client portal for onboarding?

Not for your first few clients. A shared folder, a form and a calendar invite are enough. A portal starts to pay off once you are onboarding two or more clients a month, mostly because it stops credentials and approvals getting lost in email and chat threads.

Can one platform handle onboarding and the website build?

Partly. A platform with a CRM can hold the enquiry, the tasks, the automations, the invoices and the client login, which removes most manual chasing. Contracts and signatures usually still need a dedicated e-signature tool.

Related guides

• How to start a web design agency with AI: a practical playbook
• How to manage multiple client websites

Where to go next

If you want this sequence to live in the same place as the sites you build, the useful first step is a conversation: talk to us about white-label, and we can look at your client mix, the packages you want to sell and whether agency accounts suit the way you work. Agency prices are not published, so asking is the only way to find out.

If you would rather try the product first, the AI website builder is the same tool your clients would use, and you can start for $1 for the first month and run one real onboarding through it before deciding anything. Either way, write your questionnaire and your exclusions list this week. They will do more for your delivery dates than any software.