mcpField
C
client-onboarding-workflow

client-onboarding-workflow

github.com/zanecole10Productivity10740 installsUpdated 52w ago
Repository

About client-onboarding-workflow

A skill for service providers that structures client onboarding by project stage. It produces welcome emails, information-gathering forms, kickoff agendas, requirements templates, and a recurring progress update plan.

Key features

  1. 01Welcome email sequence
  2. 02Requirements questionnaire
  3. 03Kickoff meeting agenda
  4. 04Requirements document template
  5. 05Weekly progress update plan

Use cases

  1. 01Set onboarding steps after a client signs
  2. 02Gather client requirements and workflows
  3. 03Plan kickoff meetings and regular updates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zanecole10/software-tailor-skills --skill client-onboarding-workflow

After installing, type/client-onboarding-workflowin Claude Code to confirm it loaded.

Details

From the project README

Client Onboarding Workflow Builder

First impressions matter. Professional onboarding = confident clients.

What This Skill Does

Input your service → Get complete onboarding system: ✅ Welcome Email Sequence - Automated client welcome ✅ Information Gathering Forms - Collect requirements systematically ✅ Kickoff Meeting Agenda - Productive first meeting structure ✅ Requirements Doc Template - Capture everything clearly ✅ Progress Update Schedule - Weekly client communication plan

Onboarding Timeline

Day 1: Contract Signed + Deposit Received

  • Auto-send: Welcome email + next steps
  • Include: Calendar link for kickoff meeting
  • Attach: Onboarding questionnaire

Days 2-3: Client Completes Questionnaire

  • Questions about users, workflows, pain points
  • Screenshots/docs of current process
  • Access credentials (if needed)

Day 4-5: Kickoff Meeting (60 min)

  • Review questionnaire responses
  • Clarify requirements
  • Set expectations
  • Introduce tools/process

Day 6: Send Requirements Doc

  • Formalized version of what you're building
  • Client reviews and approves
  • Prevents "but I thought you were building..." later

Week 2-6: Weekly Updates

  • Every Friday: Progress email with screenshots
  • Keeps client engaged and excited
  • Reduces "how's it going?" interruptions

Welcome Email Template

Subject: Welcome to [Your Company]! Here's What Happens Next

Body: "Hi [Client Name],

Welcome aboard! I'm excited to build [Project Name] for you.

Here's what happens next:

This Week:

  1. Complete the onboarding questionnaire (link below) - takes 15 min
  2. Schedule our kickoff meeting (calendar link below)
  3. I'll review your responses and prepare questions

Next 4-6 Weeks: You'll receive weekly Friday updates with screenshots of progress.

Questions? Reply to this email anytime.

Let's build something great!

[Your Name]


📋 Onboarding Questionnaire: [link] 📅 Schedule Kickoff Meeting: [Calendly link]"

Kickoff Meeting Agenda

1. Introductions (5 min)

  • Build rapport
  • Set casual, collaborative tone

2. Review Project Goals (10 min)

  • "What does success look like for you?"
  • Confirm you understand the problem

3. Walk Through Questionnaire (20 min)

  • Clarify unclear responses
  • Ask follow-up questions
  • Sketch workflows on screen share

4. Set Expectations (10 min)

  • Timeline and milestones
  • Communication cadence
  • How to request changes

5. Technical Setup (10 min)

  • Exchange access credentials
  • Set up tools (GitHub, staging site)
  • Test communication channels

6. Next Steps (5 min)

  • You: Send requirements doc by Tuesday
  • Them: Review and approve by Friday
  • You: Start development next Monday

Why This Works

Without onboarding: Client feels uncertain, interrupts you constantly, changes mind mid-project

With onboarding: Client feels confident, trusts the process, stays out of your way while you build

Professional onboarding = fewer headaches = faster delivery = happier clients.

Comments

Markdown supported