The first week of a client engagement determines whether the rest of the project runs smoothly or spirals into scope chaos. Here's the onboarding process that prevents problems.
Step 1: Discovery call
Ask detailed questions about the project. Focus on specifics: exactly which pages, features, or deliverables they need. Ask what success looks like. Ask about stakeholders who will be reviewing work. Document everything.
Step 2: Written scope of work
Translate the discovery call into a specific scope of work. List every deliverable, its description, and its revision limit. Include an exclusions section. Include a change order clause. Be thorough — ambiguity here costs you money later.
Step 3: Client review and signature
Send the scope document to the client for review. Give them time to read it and ask questions. Then get it signed. ScopePilot makes this a single flow: the client reviews the scope, asks questions, and signs — with a timestamped audit trail.
Step 4: Set communication expectations
Establish where project communication happens (email, Slack, project tool), when you're available, and how feedback should be submitted. A structured feedback process reduces scope-expanding side conversations.
Step 5: Kick off with clarity
Start the project by referencing the signed scope. "As per our agreement, I'll be starting with deliverable #1 this week. You'll see the first draft by Friday." This reinforces that the scope is the reference document.
Why this works
By the time you start working, the client has explicitly agreed to what's included, how revisions work, and how changes are handled. There's no room for "I thought that was included" because they signed a document that says otherwise.