中文导读
Client Onboarding 是一套面向一人公司的运营 playbook，帮助你用更少的人力完成更稳的增长、交付与决策。
说明: 原始步骤、命令与 API 名称保留英文，以避免参数和接口名称失真。
概览
Client onboarding is the skill of turning a signed client into a well-aligned working relationship quickly. For a one-person company, onboarding quality shapes everything that follows: delivery speed, client confidence, scope discipline, and the amount of reactive support you need to provide. Good onboarding reduces confusion before it starts.
适用场景
Use this when you sell services, retainers, advisory work, or implementation work. Use it whenever clients need access sharing, kickoff alignment, asset collection, communication rules, or a defined first milestone.
这个技能能做什么
This skill helps you design the first two weeks of the client experience: what gets sent, what gets collected, how expectations are set, and how the first win is created. The goal is to make the client feel guided, not abandoned after payment.
如何使用
Step 1: Send a welcome message immediately after close. Confirm what happens next and by when.
Step 2: Collect essentials in one place: contacts, access, brand assets, goals, deadlines, and known constraints.
Step 3: Run a kickoff process with a defined agenda. Confirm goals, roles, communication cadence, approval path, and success criteria.
Step 4: Set operating rules early. Response times, revision policy, out-of-scope rules, and meeting cadence should be explicit.
Step 5: Deliver a first quick win or a clear first milestone as fast as possible.
Step 6: End onboarding when the working rhythm is established, not merely when paperwork is done.
输出结果
The output should include:
- Welcome email
- Intake checklist
- Kickoff agenda
- Communication and approval rules
- First-30-days milestone plan
常见错误
Do not spread onboarding across five tools with no clear owner. Do not assume the client understands your process. Do not delay the first visible win. Do not leave scope or communication norms undefined. Ambiguity becomes friction later.
Direct Answer
Use this skill when you need one clear operating move, one measurable outcome, and one next step that can ship today.
Evidence To Collect
- Time-to-kickoff baseline and new time-to-kickoff (days from payment to kickoff call)
- Intake completion rate at kickoff (required fields collected vs. total required)
- Access readiness at kickoff (required tools granted vs. requested)
- First-value milestone date before and after onboarding changes
- A before/after onboarding timeline screenshot you can reuse in a case study
Source Links To Cite
- The live onboarding page or SOP this recommendation changes
- Client onboarding intake form or checklist used in production
- Project kickoff meeting standard from Atlassian: https://www.atlassian.com/work-management/project-management/project-kickoff
- Project kickoff checklist examples from Asana: https://asana.com/resources/project-kickoff-meeting
- Access control baseline from NIST SP 800-53 Rev. 5 (AC family): https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
- Least-privilege verification guidance from OWASP ASVS: https://owasp.org/www-project-application-security-verification-standard/
- U.S. tax onboarding document reference (W-9): https://www.irs.gov/forms-pubs/about-form-w-9
优秀标准
- The deliverable is specific and easy to verify
- The page includes proof, not just advice
- The next action is obvious for a solo operator
SKILL.md 原文件
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# client-onboarding
Client Onboarding
Overview
Client onboarding is the skill of turning a signed client into a well-aligned working relationship quickly. For a one-person company, onboarding quality shapes everything that follows: delivery speed, client confidence, scope discipline, and the amount of reactive support you need to provide. Good onboarding reduces confusion before it starts.
When to Use This Skill
Use this when you sell services, retainers, advisory work, or implementation work. Use it whenever clients need access sharing, kickoff alignment, asset collection, communication rules, or a defined first milestone.
What This Skill Does
This skill helps you design the first two weeks of the client experience: what gets sent, what gets collected, how expectations are set, and how the first win is created. The goal is to make the client feel guided, not abandoned after payment.
How to Use
Step 1: Send a welcome message immediately after close. Confirm what happens next and by when.
Step 2: Collect essentials in one place: contacts, access, brand assets, goals, deadlines, and known constraints.
Step 3: Run a kickoff process with a defined agenda. Confirm goals, roles, communication cadence, approval path, and success criteria.
Step 4: Set operating rules early. Response times, revision policy, out-of-scope rules, and meeting cadence should be explicit.
Step 5: Deliver a first quick win or a clear first milestone as fast as possible.
Step 6: End onboarding when the working rhythm is established, not merely when paperwork is done.
Output
The output should include:
Welcome email
Intake checklist
Kickoff agenda
Communication and approval rules
First-30-days milestone plan
Common Mistakes
Do not spread onboarding across five tools with no clear owner.
Do not assume the client understands your process.
Do not delay the first visible win.
Do not leave scope or communication norms undefined. Ambiguity becomes friction later.
## Direct Answer
Use this skill when you need one clear operating move, one measurable outcome, and one next step that can ship today.
## Evidence To Collect
- Time-to-kickoff baseline and new time-to-kickoff (days from payment to kickoff call)
- Intake completion rate at kickoff (required fields collected vs. total required)
- Access readiness at kickoff (required tools granted vs. requested)
- First-value milestone date before and after onboarding changes
- A before/after onboarding timeline screenshot you can reuse in a case study
## Source Links To Cite
- The live onboarding page or SOP this recommendation changes
- Client onboarding intake form or checklist used in production
- Project kickoff meeting standard from Atlassian: https://www.atlassian.com/work-management/project-management/project-kickoff
- Project kickoff checklist examples from Asana: https://asana.com/resources/project-kickoff-meeting
- Access control baseline from NIST SP 800-53 Rev. 5 (AC family): https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
- Least-privilege verification guidance from OWASP ASVS: https://owasp.org/www-project-application-security-verification-standard/
- U.S. tax onboarding document reference (W-9): https://www.irs.gov/forms-pubs/about-form-w-9
## What Good Looks Like
- The deliverable is specific and easy to verify
- The page includes proof, not just advice
- The next action is obvious for a solo operator
预览原始 SKILL.md. 下面可以直接查看完整原文。可滚动阅读、检查结构，再下载精确的 SKILL.md 原文件。
# client-onboarding
Client Onboarding
Overview
Client onboarding is the skill of turning a signed client into a well-aligned working relationship quickly. For a one-person company, onboarding quality shapes everything that follows: delivery speed, client confidence, scope discipline, and the amount of reactive support you need to provide. Good onboarding reduces confusion before it starts.
When to Use This Skill
Use this when you sell services, retainers, advisory work, or implementation work. Use it whenever clients need access sharing, kickoff alignment, asset collection, communication rules, or a defined first milestone.
What This Skill Does
This skill helps you design the first two weeks of the client experience: what gets sent, what gets collected, how expectations are set, and how the first win is created. The goal is to make the client feel guided, not abandoned after payment.
How to Use
Step 1: Send a welcome message immediately after close. Confirm what happens next and by when.
Step 2: Collect essentials in one place: contacts, access, brand assets, goals, deadlines, and known constraints.
Step 3: Run a kickoff process with a defined agenda. Confirm goals, roles, communication cadence, approval path, and success criteria.
Step 4: Set operating rules early. Response times, revision policy, out-of-scope rules, and meeting cadence should be explicit.
Step 5: Deliver a first quick win or a clear first milestone as fast as possible.
Step 6: End onboarding when the working rhythm is established, not merely when paperwork is done.
Output
The output should include:
Welcome email
Intake checklist
Kickoff agenda
Communication and approval rules
First-30-days milestone plan
Common Mistakes
Do not spread onboarding across five tools with no clear owner.
Do not assume the client understands your process.
Do not delay the first visible win.
Do not leave scope or communication norms undefined. Ambiguity becomes friction later.
## Direct Answer
Use this skill when you need one clear operating move, one measurable outcome, and one next step that can ship today.
## Evidence To Collect
- Time-to-kickoff baseline and new time-to-kickoff (days from payment to kickoff call)
- Intake completion rate at kickoff (required fields collected vs. total required)
- Access readiness at kickoff (required tools granted vs. requested)
- First-value milestone date before and after onboarding changes
- A before/after onboarding timeline screenshot you can reuse in a case study
## Source Links To Cite
- The live onboarding page or SOP this recommendation changes
- Client onboarding intake form or checklist used in production
- Project kickoff meeting standard from Atlassian: https://www.atlassian.com/work-management/project-management/project-kickoff
- Project kickoff checklist examples from Asana: https://asana.com/resources/project-kickoff-meeting
- Access control baseline from NIST SP 800-53 Rev. 5 (AC family): https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
- Least-privilege verification guidance from OWASP ASVS: https://owasp.org/www-project-application-security-verification-standard/
- U.S. tax onboarding document reference (W-9): https://www.irs.gov/forms-pubs/about-form-w-9
## What Good Looks Like
- The deliverable is specific and easy to verify
- The page includes proof, not just advice
- The next action is obvious for a solo operator
评论与讨论
添加评论