Client Onboarding for WordPress Projects: A Process for Agencies
The first two weeks of a WordPress project set the tone for everything after. Rush onboarding and the same things go wrong every time: content that never arrives, decisions nobody made, passwords nobody can find, and a client who isn’t sure anyone is in charge. Get it right and the project moves faster, and the client trusts you from the start.
What follows is the onboarding we’d recommend, ending with the handover to your developers or a white label partner.
1. A focused kickoff call
The kickoff is where expectations get set. Talk through the goals and how you’ll know the project worked. Find out who decides things on the client side and who signs off designs and content. Walk through the timeline, the milestones and what you’ll need from the client at each one. Agree how you’ll communicate and how quickly each side replies.
Send a short written summary the same day. Weeks later, when someone says “I thought we agreed…”, that summary settles it.
2. All the access, at once
Missing logins hold up more projects than you’d expect. Send one checklist and ask the client to share credentials through a password manager. You’ll typically need the domain registrar and DNS, the hosting, the current WordPress admin if there’s an existing site, Search Console, Analytics and Tag Manager, and every third-party tool the site connects to: CRM, email marketing, payments, bookings.
Ask for accounts in your agency’s name rather than borrowing the client’s personal logins.
3. Content, early
Content is almost always late. Agree early who writes it, in what format and by when. On bigger sites, keep a simple content map listing every page, who owns it and where it stands. If the client is slow, agree on placeholder content so development doesn’t stall.
4. A locked scope
Write down what’s included: the number of templates, the main features and integrations, the number of revision rounds. Agree how change requests will be handled. A clear scope protects your margin and the relationship.
5. Communication rules
Pick where conversations happen and keep them there: one shared channel or email thread, one project board for tasks and approvals, and one main contact on each side.
If a white label partner is building the site, the client only ever talks to your agency, and your project manager passes tasks to the partner in your internal tools. Our article on white label client communication explains the setup.
6. A clean developer handover
Once design and scope are signed off, put the development handover together. It should include the final designs (ideally in Figma, with mobile versions and component states), the content map and whatever content has arrived, the list of plugins, integrations and third-party services, access to staging and the repository, and the deadline, priorities and acceptance criteria.
A good handover lets developers get going without sending back a page of questions. If a partner is doing the build, for example for Figma to WordPress development, this is the brief they work from.
7. A timeline the client can see
Clients relax when they can see progress. Share a simple timeline: design approval, development, content entry, review, launch. Update it when things change, and if a date is going to move, tell the client before it does.
8. Talk about launch on day one
Discuss launch and what comes after during onboarding, not in the last week. Who checks the site before it goes live? How will the client edit content, and do they need training? What do support and maintenance look like afterwards?
That’s also a natural moment to bring up a care plan. Our guide to WordPress care plans covers how to package one.
Make it repeatable
Turn all of this into templates: a kickoff agenda, an access checklist, a content map and a developer handover document. Each new project then starts faster and with fewer gaps.
If your team is stretched, Deviart can take over WordPress development after onboarding, as your invisible white label team. Get in touch to see how we fit into your process.
