Client portals & onboarding workflows
Before the portals, onboarding ran through email: credentials in one thread, kickoff notes in another, first deliverables in a third.
- Role
- Design, build, documentation
- Stack
- Portal build, onboarding automation, SOPs
- Covers
- Kickoff through handover
- Result
- Portal access from day one
Where the doubt starts
A client signs, and for the next two weeks their experience of the engagement is an email thread. Assets requested in one message, access credentials in another, scheduling in a third, a kickoff deck attached to a fourth that they will never find again.
Nothing is going wrong, but this is when a client decides whether they made a good decision, and an inbox does a poor job of reassuring them:
- Neither side can tell what is outstanding.
- The same four questions get asked on every engagement, and get answered from scratch every time.
- Progress is invisible between milestones, so silence reads as nothing happening.
- Everything that matters ends up in one person’s sent folder, which is a retention risk disguised as a filing habit.
What I built
A portal per client, created at signature, holding the whole engagement (intake, status, deliverables, documentation and handover), plus an onboarding workflow that fills it in on a schedule.
Intake that chases itself
Every engagement needs the same opening set: brand assets, platform access, the name of whoever approves things, and the one business fact that is never written down anywhere. The portal asks for them as a checklist with owners and dates, and follows up on what is missing. It moves the chasing off a person and onto a schedule, which is the same trick as the invoice work and it works for the same reason.
Status as a standing answer
A live view of what is done, what is in progress and what is blocked, including what is blocked on the client. That last column prevents the most expensive conversation in service work, which is the one in week four where delivery is late because of an approval no one realised was outstanding.
Handover as a deliverable
Documentation, run logs, credentials and a recorded walkthrough live in the portal from the beginning, so the handover is ready at any point in the engagement. A client who can pick the work up themselves is a client who chose to stay, and that is a materially different relationship from one who cannot leave.
The part you’d be right to argue with
A portal is another place to log in, and clients already have too many. If it is not more useful than the email thread it replaces, it becomes a dead tab within a month and the thread comes back.
- It has to hold what clients want. Deliverables, credentials, the invoice, the walkthrough. If the useful artefacts live somewhere else, the portal is theatre.
- Notifications still go where they already are. Nothing depends on the client logging in on their own. Email tells them what happened and links to the place it happened, which is the only version of this that survives contact with a busy person.
What I haven’t solved
Some clients want the email thread and will not be moved. For them the portal becomes an internal tool and a link farm, which is still better than nothing but is not what it was built for. I have stopped treating that as a failure to fix and started treating it as a segment.