Build a New-Client Onboarding Email Sequence and Kickoff Checklist

Get a dated onboarding email sequence, focused intake questions, exact access requests, a timed kickoff agenda and a checklist so day one isn't blocked.

You getSequence overview table, full text of each email and kickoff call agenda

Prompt

Prompt
Act as an operations consultant who sets up client onboarding for freelancers and small agencies.

Your job: build a new-client onboarding email sequence and a kickoff checklist so nothing blocks the first day of work.

Before writing anything, ask me these questions in one message, then wait for my answers:
1. What service do you deliver, and what does a typical first project look like?
2. Which accounts, files or tools do you need from the client?
3. How many days are there between contract signing and the kickoff call?
4. What tone do you want: formal, friendly, or in between?

Rules:
- Each email has one job and one clear ask, with a reply-by day counted from signing (Day 0, Day 2, and so on).
- Use no more than 8 intake questions, each answerable in under 2 minutes.
- Every access request names the exact permission level needed (for example editor, not admin) and a safer alternative if the client hesitates.
- Keep each email under 150 words with a plain, descriptive subject line.
- Time the kickoff agenda to the minute and end it with agreed next steps and owners.

Output format:
1. Sequence overview table: Day | Email | Purpose | Client action
2. Full text of each email (subject line, then body)
3. Kickoff call agenda (timed)
4. Pre-kickoff checklist table: Item | Owner | Due day

End with one line naming any access or information that could still block day one.

Example output

At a glanceOnboarding email sequence before kickoffFour emails lead to a 45-minute kickoff on Day 5
  1. WelcomeDay 0Confirm scope and dates; client books kickoff slot
  2. IntakeDay 1Gather brand and goals; answer 7 questions
  3. AccessDay 2Get logins and files; grant 3 accesses
  4. Kickoff prepDay 4Share agenda; client confirms attendees
  5. Kickoff callDay 545-minute call covering goals, timeline and access

Example for: a freelance web designer rebuilding a bakery's Webflow site, kickoff 5 days after signing, friendly tone.

1. Sequence overview
DayEmailPurposeClient action
0WelcomeConfirm scope and datesBook kickoff slot
1IntakeGather brand and goalsAnswer 7 questions
2AccessGet logins and filesGrant 3 accesses
4Kickoff prepShare agendaConfirm attendees
2. Emails

Subject: Welcome aboard, next steps for your new site
Hi Maria, thanks for signing. Here's what happens next: a short questionnaire tomorrow, an access request on Day 2, and our kickoff call on Day 5. Please pick a 45-minute kickoff slot here by Day 1. Talk soon, Sam

Subject: 7 quick questions before we start (about 10 minutes)

  1. What are the top 2 things visitors should do on the site?
  2. Which 3 sites do you like, and why?
  3. Who signs off on designs?
  4. Do you have a logo file (SVG or PNG)?
  5. Which pages must stay as they are?
  6. Any launch date tied to an event?
  7. What has frustrated you about the current site?
    Please reply by Day 3.

Subject: 3 accesses I need by Day 4

  • Webflow: Editor role on the site (not workspace owner). If you prefer, transfer a copy of the site instead.
  • Google Analytics: Viewer access. Alternative: export last 90 days as a PDF.
  • Shared drive: one folder with photos and brand files, comment access is fine.

Subject: Agenda for Thursday's kickoff
Hi Maria, agenda below. Please confirm who will join and flag anything to add. Sam

3. Kickoff agenda (45 min)
  • 0:00–0:05 Introductions and roles
  • 0:05–0:15 Goals and success measures
  • 0:15–0:25 Review intake answers, fill gaps
  • 0:25–0:35 Timeline, review rounds, feedback channel
  • 0:35–0:40 Confirm access works
  • 0:40–0:45 Next steps, owners, dates
4. Pre-kickoff checklist
ItemOwnerDue day
Signed contract and depositClient0
Kickoff slot bookedClient1
Intake answers receivedClient3
Webflow Editor access testedSam4
Analytics access confirmedSam4
Project folder and task board set upSam4

Could still block day one: Webflow editor access, since only the bakery's previous developer may hold owner rights.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking about tools and timing first means the access emails and due days match your real project.
  • Naming exact permission levels with safer alternatives cuts back-and-forth with cautious clients.
  • The closing blocker line flags the one item most likely to delay the start.

Use right after a client signs. Have your service, the tools you need access to and your kickoff date ready. Works in ChatGPT, Claude or Gemini; paste the emails into your email tool or CRM.

Common edits

  • Add a Day 7 check-in email asking how the first week went.
  • Turn the checklist into a shared doc the client can tick off themselves.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business