// Client onboarding
Turn a signed agreement into a clear project start.
An illustrative onboarding workflow that connects the sales handoff, client information, and delivery tasks.
The starting situation
A deal is agreed, but delivery waits while someone finds the brief, requests missing information, creates folders, and assigns tasks. Different teams repeat the same questions. This example gives each project a visible starting checklist and owner.
The proposed workflow
- Confirm the agreed start condition in the CRM and check whether onboarding already exists.
- Create a project checklist from the approved service template.
- Prepare a client questionnaire and request approval before sending it.
- Create the workspace with agreed access permissions and link the source brief.
- Assign owners and due dates; flag missing information before the kickoff.
Where a person decides
A project owner approves client communications, access, and any scope changes. Incomplete briefs remain visible as blockers. Repeated CRM events must not create duplicate projects or invitations.
Tools and data
A CRM such as Attio, a form, shared storage, and the team’s task manager. Templates, ownership rules, and available integrations are confirmed during scoping.
What a pilot should measure
Compare time from the agreed start condition to kickoff readiness, missing checklist items, and manual handling. Separate waiting for the client from internal preparation time.
What to bring to an audit
Bring an anonymized recent onboarding, the current checklist, a sample brief, and the tools used. Start with one service type and an owner who can confirm that the project is ready.
