How to Automate Your Web Design Client Onboarding: From Enquiry to Project Kick-Off
From the outside, your web design client onboarding probably looks great. Your client receives a proposal, signs the contract, pays the invoice and gets a welcome email telling them exactly what happens next.
Behind the scenes, though, there's usually far more going on than they realise. You're setting up their Google Drive folders, creating a new project in your project management tool, adding deadlines, sending links, checking whether their website copy has arrived and trying to remember what needs to happen before the kick-off call.
None of it is difficult, it's just that you have to do it all again every single time somebody books, and that adds up fast.
Good client onboarding for a web designer isn't only about a welcome email that looks nice It's about a joined-up process that takes someone from their first enquiry to a project that's properly prepared, and then carries them all the way through your review rounds to a final handover.
For a lot of web designers, that means Dubsado looks after the client-facing side, a project management tool such as Notion looks after the project itself and Zapier passes the right information between the two. I'll walk you through how that can work.
What should a web design client onboarding process include?
Onboarding starts well before the welcome pack. It begins the moment a potential client gets in touch and carries on until you've delivered their website and said a proper goodbye.
For most web designers, the journey looks something like this:
A potential client submits an enquiry form
You review the enquiry and decide how you'd like to reply
They book a discovery call or receive an email response
You send a proposal, contract and initial invoice
They sign and pay to secure their project
They receive their welcome information and next steps
You collect their website copy, branding, images and other assets
You prepare the project internally and kick things off
The client reviews your designs in one or two rounds
You deliver the finished website and ask for feedback
When this works well, your client always knows what's happening, what you need from them and what comes next. You also have the files and information you need without hunting through old email threads.
The tricky part is that the whole journey rarely happens inside one platform.
Where Dubsado fits into a web designer's workflow
Dubsado is great as the client-facing side of your workflow. It can look after everything from the first enquiry through to final delivery, including:
Capturing leads through an enquiry form
Sending an instant acknowledgement so they know their enquiry has landed
Sending discovery call invites with confirmation and reminder emails
Following up on enquiries and proposals that haven't had a reply
Sending the proposal, contract and invoice as one smooth flow
Sending welcome information and onboarding questionnaires
Updating project statuses so you can see where every client is at a glance
Attaching a review workflow for each round of feedback
Sending sub-agreements so clients can sign off drafts
Sending your delivery and offboarding emails
Giving clients a portal for their contracts and invoices
Instead of building every project from scratch, you can create workflows based on the service somebody has chosen. A website-in-a-week client needs a very different sequence from someone booking a fully custom site, with different payment plans, prep time and deadlines, and your workflows can reflect that rather than pushing everyone through one generic process.
You can automate the repeatable parts and still keep the personal touchpoints exactly where you want them. The aim isn't to remove you from the client experience, it's to make sure the essential steps happen consistently, so you have more time and headspace for the work that genuinely needs you.
Why Dubsado doesn't need to manage the entire project
One of the biggest mistakes I see in people's systems is expecting one platform to do absolutely everything.
Dubsado is fantastic for leads, contracts, invoices, forms and client communication, but it doesn't need to hold every task involved in designing and building a website. That's where a project management tool such as Notion comes in, holding the internal side of each project, like your design process, tasks, deadlines and who is responsible for what.
This gives you a really useful separation between the client journey and the work happening behind the scenes. Dubsado manages the relationship and the commercial side, your project tool manages how the work gets delivered and Google Drive stores the files. Every platform has a clear job, so you're not saving the same information in three slightly different places.
The Dubsado portal works best in the same spirit. I like to switch it on during onboarding as a central hub for contracts and invoices, and I let clients know it's there for their paperwork rather than for managing the project.
How Zapier connects Dubsado, Google Drive and Notion
Using several platforms can create even more admin if you have to update each one by hand, which is where Zapier earns its place.
Zapier can watch for things happening in Dubsado, such as a signed contract, a payment or a change of project status, and then trigger actions in your other platforms. It can also filter by project type, so a web design booking triggers a different set of actions from any other service you offer.
Once a client has signed and paid their first invoice, for example, an automation could:
Create a folder for them in Google Drive
Create a matching project in Notion, or whichever project tool you use
Let you know their project space is ready
By the time you open your project tool, the foundations are already there. You haven't had to set up folders and a new project by hand, and you haven't had the chance to forget a step in the middle of a busy week.
The exact automation depends on the tools you use and how you like to work. A solo designer needs something quite different from a studio with a copywriter, a developer and a designer involved, which is why I always start with the process before I choose any automation.
An example onboarding workflow for a web designer
Here's what the full journey could look like from start to finish.
1. The enquiry arrives
The potential client completes your Dubsado enquiry form. I like to add a question asking whether they'd prefer a call or an email, because more and more people would rather start with a message than book a discovery call.
Dubsado creates the lead, updates the project status and sends an acknowledgement, which can suggest they browse your portfolio while they wait to hear from you within a day or two.
2. You review and choose the next step
Everything pauses here on purpose. You read the enquiry yourself and attach either your call invite workflow or your email workflow, which means no automation fires before you've decided how you want to respond.
My top tip is to give every workflow a consistent name that includes the service and the phase, so it's obvious what each one does when you have several running.
3. The conversation, and a gentle chase
For clients who want a call, the workflow sends a scheduler link. I name the scheduler something like "Discovery Call with [Your Business Name]" so it's clearly labelled in their calendar, and a confirmation, a 24-hour reminder and a 1-hour reminder help cut down on no-shows. The project status moves along as they request and then book their call.
If they haven't booked after a few days, an automatic follow-up email goes out inviting them to grab a time on your scheduler, so there's no nudging needed on your side at all. As soon as they book, a pause workflow stops the chasing, which means nobody gets a reminder about something they've already done.
Email enquiries work a little differently, because there's no scheduler to keep track of. A few days after your reply, the workflow adds a to-do task to your inbox asking whether you need to chase, and if you do, you simply attach the follow-up workflow yourself. I like a to-do for this because it gives you a clear instruction to act on rather than an approval notification you might miss.
4. Proposal, contract and invoice in one flow
Instead of three separate emails, the client chooses their package, signs the contract and pays the initial invoice in one smooth sequence. Dubsado can't automatically switch to a different payment plan based on what someone picks, so I create a separate package for each payment option, and the right first payment lands on the invoice. I also put the payment plan details in the package description rather than relying on a total amount in the contract.
Follow-up emails go out if the proposal or contract hasn't been completed, and each one includes a link to the invoice in case they leave part way through. An expiry email after a set time, such as 10 days, invites them to get back in touch if they're still interested.
5. Welcome, preparation and content
Once the contract is signed and the first payment is made, the status changes to onboarded and a welcome email goes out with a general welcome guide. The guide covers your deadlines, payment schedule and review process, which cuts down the back and forth no end!
This is also where Zapier prepares your internal systems. I still like a manual check in the middle, so a to-do task reminds you to add the folder and project links to the next email, and that email only sends once you've ticked the task off. Reminders then go out ahead of your content deadline so you can see what's arrived and what's still missing before the project begins.
6. Review rounds
When your first draft is ready, you attach a first look workflow, and when the next round is ready, you attach a second look workflow. Nothing starts until you're ready for it, which means there's no pressure on your side, and I build these workflows to run from the moment you attach them rather than tying them to project dates.
Each round includes a sub-agreement with a simple checklist. The client can say they're happy to accept the design, that they'd like some refinements or that they want to start again, and the wording makes it clear what any extra rounds or a restart would cost. That formalises the sign-off, gives you somewhere to capture further edits and helps prevent scope creep or clients going back on an approval. An automated email confirms as soon as they complete it, so they know their feedback has arrived.
7. Delivery
When the final files are ready, you attach a delivery workflow that sends everything over. Rather than recording a new video for every client, record your how-to videos once, such as a walkthrough of editing their new site, and reuse them every time.
8. Offboarding and feedback
When you're happy that a project is truly finished, you tick a task. Two weeks later, the offboarding workflow sends a feedback request and a Google review link, then archives the project.
What should you automate, and what should stay personal?
Automation works best when it supports the client experience instead of trying to replace it.
Good things to automate include:
Enquiry acknowledgements
Scheduling links and reminders
Proposal, contract and invoice follow-ups
Standard onboarding instructions
Content deadline reminders
Review round acknowledgements
Creating folders and internal projects
Feedback requests and archiving
The parts that usually benefit from you being personally involved are:
Deciding how to respond to a new enquiry
Discovery and strategy calls
Understanding unusual project requirements
Creative direction and feedback
Deciding when each review round starts
Handling concerns or changes
Deciding when a project is finished
You really don't have to choose between an efficient process and a personal one. The right systems give you more capacity to be fully present at the moments where your expertise and judgement matter most.
Signs your web design onboarding process needs attention
Your process probably worked perfectly well when you were booking the occasional project. As your business grows, the gaps tend to become much more noticeable.
It might be time to review your systems if:
You create the same folders and documents by hand for every project
Your onboarding emails are copied and pasted from old threads
Clients regularly ask what they need to do next
Website copy or images arrive late because the deadlines weren't clear
Clients keep requesting changes after they've approved a design
Important information is scattered across emails, forms and notes
You keep entering the same client details into several platforms
You forget internal prep tasks when several projects overlap
Every project is onboarded slightly differently depending on how busy you are
You have several useful platforms that don't talk to each other
Too much of the process lives only in your head
None of this necessarily means you need more software. More often, the platforms you already use just need clearer roles and better connections between them.
Start with the process, not the automation
It's tempting to begin with a list of everything Zapier can do. Automating a messy or unclear process usually just gives you a faster version of the same mess, so it's worth pausing before you build anything to work out:
What should happen at each stage of the client journey
What information you need from the client
Which platform should hold that information
What has to happen before the next stage can begin
Where you want to make a personal decision
Which actions are repeated in every project
Which parts change depending on the service booked
What the client sees and what stays internal
Once you've made those decisions, the technology becomes so much easier to set up. Your Dubsado workflows, project template and Zapier automations should all follow one considered process, rather than acting like separate systems you have to remember to keep in sync.
A smoother client experience starts behind the scenes
Your clients may never know that Zapier created their folders or that your project tool was ready the moment they booked. What they will notice is that your emails arrive when they're expected, your instructions are clear, your review process feels fair and their project moves along without a last-minute scramble for missing information.
That's the real purpose of your web design client onboarding process. It isn't automation for the sake of it, it's a reliable structure that supports your clients and the way you deliver your work.
If your client journey looks polished from the outside but still leaves a trail of manual admin behind the scenes, I'd love to help you look at the whole picture. Together we can map how your client experience and internal operations should work, decide what belongs in Dubsado and your other platforms, and build the workflows and Zapier integrations that connect everything properly.