A 5-day client onboarding workflow for solo consultants
A project often starts before anyone agrees on the basics: who approves the work, what access is needed, how feedback will work, and what is explicitly out of scope.
The first week sets the tone. If it is scattered across email, calls, and half-filled documents, the project starts with missing assets, unclear decisions, and quiet scope creep.
Here is a 5-day onboarding workflow that keeps the first week visible.
Day 1 — Welcome and access
Send one email with three things:
- what happens next;
- the access and assets you need;
- the date you need them.
Ask for platform invitations or a shared password manager. Do not ask the client to email passwords.
If an asset is not ready, ask for the date it will be available. “Later” is not a date.
Day 2 — Kickoff
Run a 45-minute call with a written agenda:
- goals and success criteria;
- deliverables and exclusions;
- who approves the work;
- feedback window and meeting cadence;
- risks and dependencies;
- the first milestone.
The most important question is: who is the final decision-maker? If the answer is “the team”, ask who breaks a tie.
Day 3 — Project brief
Turn the call into a one-page brief:
- objective;
- audience;
- deliverables and acceptance criteria;
- what is not included;
- constraints and dependencies;
- decision-maker;
- first milestone.
Send it for approval. Do not start dependent work until it is approved.
Day 4 — Scope confirmation
Send a short confirmation that repeats the scope in plain language:
- deliverables;
- exclusions;
- revision limit;
- feedback window;
- timeline;
- dependencies;
- change control.
Ask the client to reply “approved”. A written approval is enough; it does not need to be a legal document.
Day 5 — Start
Confirm access, communication cadence, and the first milestone. Update the tracker. If a dependency is late, move the timeline by the same number of days and document it in writing.
A worked example
A three-week rebrand project is fixed at $3,500.
On day 1 the client has not sent the logo files or hosting access. The access checklist catches it. On day 2 the kickoff agenda identifies the founder as the only decision-maker. On day 3 the brief records the dependency: “Logo files and hosting access needed by Wednesday.”
The files arrive two days late. The timeline moves by two days. There is no argument because the dependency was written down before work started.
Five onboarding red flags
- No named decision-maker.
- No signed proposal or written approval.
- No deposit or payment date.
- Access is “coming later” with no date.
- The scope is already growing before kickoff.
If two or more are true, slow down and fix the basics before starting production work.
What not to do
- Do not start dependent work before access and scope are confirmed.
- Do not accept “we’ll send it later” without a date.
- Do not let feedback live only on calls.
- Do not treat a template as legal advice.
Honest limitations
This is a practical workflow, not legal, tax, or financial advice. Adapt the documents to your contract and jurisdiction. A template cannot guarantee that a client will behave well; it can only make the first week easier to see.
If you want the editable version
I packaged the welcome emails, kickoff agenda, project brief, access checklist, scope confirmation, tracker, and worked example into a 19-file kit:
Client Onboarding Pack for Solo Consultants
It is $12, one ZIP, no subscription. The workflow above is free to use whether you buy it or not.
Disclosure: I used AI assistance to draft and format this article and the templates; I reviewed and edited them before publication. Not legal advice.
Top comments (0)