Client Onboarding: Starting the Project Right

The first 48 hours after a client pays determines whether they refer you to three people or warn everyone they know

The sale is done. The deposit is paid. The project has started.

Now begins the part that determines whether this client refers you to three people or tells everyone they know to avoid you.

Client onboarding is not admin. It is the experience of working with you: the first impression after the sale which sets the expectation for everything that follows. Done well it builds trust before any work is delivered. Done badly it creates the anxiety that leads to micromanagement, scope creep, and difficult conversations.

This lesson gives you the onboarding process and the Claude prompts to make it excellent.

What Happens in the First 48 Hours

Most client anxiety happens in the 48 hours after paying. They have transferred money. Nothing visible has happened yet. They start to wonder whether they made the right decision.

Your job in the first 48 hours is to make them feel that the project is in safe hands before you have built anything.

The welcome email is sent within two hours of the deposit clearing. It confirms what happens next, what you need from them, and when they will hear from you again. Not long. Just thorough and organised.

The project brief is a document you fill in together with the client before work starts. It forces both parties to agree on scope, success criteria, and timeline before a single line of code is written. This prevents most scope disputes before they happen.

The first check-in happens within five business days of starting and is a short update on where you are and what is coming next. Even if you have nothing to show yet, an update is better than silence.

The Welcome Email

Using @MARKETING.MD voice — write a client onboarding welcome email.

Client: [NAME]
Project: [DESCRIPTION]
Deposit received: [DATE]
Planned start date: [DATE]
First thing I need from them: [E.G. CONTENT, BRAND ASSETS, ACCESS, BRIEF]
Expected first deliverable: [WHAT AND WHEN]

Write an email that:

• Opens with a warm but not excessive confirmation that we are going ahead
• States exactly what happens next in clear order
• Tells them what they need to send me and by when
• Gives them the date they can expect the first update or deliverable
• Gives them how to reach me if they have questions in the meantime
• Is under 200 words
• Ends with something human and not "kind regards, looking forward to a

fruitful collaboration"

The Project Brief

The project brief is a shared document. You draft it and they review and confirm. It takes 15 to 30 minutes to complete together and prevents hours of conflict later.

Using @SALES.MD and this project's details — write a project brief for a new client.

Project: [DESCRIPTION]
Client: [NAME AND COMPANY]
Budget and timeline: [AMOUNTS AND DATES]

Key deliverables: [FROM THE PROPOSAL — what I agreed to deliver]

What success looks like for them: [FROM THE DISCOVERY CALL NOTES]

Write a project brief document with these sections:

1. PROJECT OVERVIEW (2 to 3 sentences summarising the project)
2. GOALS (what we are trying to achieve in specific measurable terms where possible)
3. DELIVERABLES (exact list from the proposal, numbered)
4. TIMELINE (milestone by milestone — what is due when)
5. WHAT I NEED FROM THE CLIENT (content, assets, access, approvals, and by what date)
6. SCOPE BOUNDARY (what is explicitly NOT included in this project)
7. REVISION POLICY (how many rounds of revisions are included and how additional

changes are handled)

1. COMMUNICATION (how we will communicate, expected response times on both sides)

Keep it clear and scannable. Use numbered lists. No legal language — this is a

working document and not a contract.

Send this brief with the welcome email or in a follow-up the same day. Ask them to reply confirming the details are correct before you start.

That reply saying "yes, this looks right" is worth more than any signed contract for a small project. It means both parties agreed to the same thing before anyone started working.

Managing the Project After It Starts

Client management is largely communication management. Clients who feel informed and in control rarely become difficult. Clients who feel kept in the dark often become anxious which comes out as micromanagement or late-stage change requests.

Update proactively. If a week passes with no communication the client will fill the silence with worry. A two-line "still on track for [DATE], next update on [DAY]" email takes 90 seconds and prevents an anxious check-in.

Surface problems early. If something is taking longer than expected or you hit a blocker, say so before it affects the delivery date. "I hit a technical issue — this might push the delivery by 2 days. Wanted to let you know now rather than on delivery day." Most clients are more understanding about delays they are told about in advance than delays they discover at the deadline.

Ask for feedback at milestones. Do not deliver the whole project and ask for feedback. Deliver a first draft or phase 1 and ask specific questions: "Does this direction look right to you? Any specific elements you want changed before I finish the rest?" Catching a wrong direction at 20% is much cheaper than at 100%.

The End-of-Project Email

How you close a project is almost as important as how you open it because this is the moment that determines whether you get a referral.

Using @MARKETING.MD voice — write an end-of-project email for a completed project.

Client: [NAME]
Project: [DESCRIPTION AND WHAT WAS DELIVERED]
Any specific results or outcomes already visible: [IF APPLICABLE]

Write an email that:

• Confirms the project is complete with a brief summary of what was delivered
• Links to or attaches the final deliverables
• Notes any maintenance or follow-up instructions they need to know
• Asks for a brief piece of feedback with one or two specific questions and not

a generic "how did we do?"

• Mentions once and briefly that referrals are welcome if they know anyone who

would benefit from similar work

• Is warm but not gushing
• Under 200 words

Adding to SALES.md

## Client Onboarding Process

Day 0 when deposit is received:

1. Send welcome email within 2 hours — confirm next steps and what I need from them
2. Send project brief — ask them to confirm before work starts

Week 1:

1. First update email — where I am and what is coming next even if nothing is built yet

During project:

1. Update proactively — never let more than a week pass with no word
2. Surface problems early before they become delivery delays
3. Get feedback at milestones and not just at delivery

Project close:

1. End-of-project email — deliver everything, ask specific feedback, mention referrals once

Your Action Right Now

Write your welcome email template using the Claude prompt above adapted to your typical project. Save it. The next time a deposit clears you have a professional organised welcome email ready to send within an hour.