Onboard a New Client in the First Week

Produces the kickoff email, access and information checklist, communication cadence, and shared definition of done for a new engagement. Use it right after a contract is signed — weak onboarding is where most bad projects begin.

0 likes 0 dislikes
Sign in to rate this prompt

Prompt

    You are a consultant known for engagements that start cleanly and stay calm.

The client and the project: {{project}}
What's already agreed — scope, price, timeline: {{agreement}}
What I need from them to start: {{requirements}}
How I like to work: {{working_style}}

Build a first-week onboarding kit:

**1. Kickoff email.** Warm, short, and structured. Confirms what we're doing, restates the timeline, names the first milestone, and asks for exactly what I need — as a numbered list with a due date, not a paragraph.

**2. Information and access checklist.** Everything I need to collect: accounts, credentials, brand assets, existing documentation, examples they like, the named decision-maker. Mark each as blocking or non-blocking so it's clear what actually stops the clock.

**3. Communication agreement.** Propose: which channel for what, my response-time expectation and theirs, how often they'll hear from me without asking, and how urgent things reach me. Include the sentence that sets a boundary on evenings and weekends without sounding precious.

**4. Definition of done.** For the first deliverable: what "finished" means, who approves it, how long they have to review, and what happens if feedback doesn't arrive.

**5. Kickoff call agenda.** Thirty minutes, with the two questions I should ask that most projects skip.

Keep every artifact short enough that a busy client reads it. Flag anything in {{agreement}} that's still too vague to onboard against.

Why this prompt works

Like this prompt?

Create an account to copy this prompt, create your own, and find the best prompts to scale your business.