growthprocessautomation
← Claude Skills · The library
Claude skillOps

Customer onboarding

Turn a messy new-customer kickoff into a sequenced checklist with owners and due dates — keep the human checkpoints.

Download SKILL.md

When to use

Use this when a won deal sits for a week because nobody knows who sends the kickoff, who collects logins, or when the first working session actually is.

Prerequisites

  • A written kickoff checklist (even a bad one in a doc)
  • One place that represents "this is a customer now" (CRM stage or a won deal)
  • Named owners for the human checkpoints (kickoff call, access, first deliverable)

SKILL.md

First half on the page. The rest is one click — no email. Crawlers get the full file either way.

---
name: customer-onboarding
description: Open a sequenced onboarding checklist when a deal is won. Assign owners and due dates. Never send customer-facing email without a human, never invent a kickoff time.
---

# Customer onboarding

## Flow

1. Trigger: deal stage = won (or the equivalent in your CRM).
2. Clone the onboarding template onto the company record.
3. Stamp owners and due dates from the template (business days, not calendar fairy dust).
4. Create internal tasks. Do not email the customer yet.
5. Draft the kickoff note (what happens this week, who they reply to). Queue it.
6. Nudge internal owners if their task is overdue. Stop at one nudge per task per day.

## Default template (edit this)

- Kickoff call booked (owner: AE / operator)
- Access collected: inbox, CRM, books — whatever this job needs (owner: ops)
- First working session on the calendar (owner: whoever ships)
- Shared folder / channel created (owner: ops)
- Week-1 recap drafted (owner: whoever shipped)

Five is enough. Extra rows become a graveyard.

## Safeguards

- Never send customer-facing email without a human confirm.
- Never invent a meeting time or write into their calendar.
- Never mark onboarding complete because tasks exist — complete means the owner checked them.
- If the won deal is missing a primary contact email, stop and flag. Do not guess.

## Example kickoff draft

```
Subject: Kickoff — what happens this week

Hi Jordan — we're on for the build. This week: (1) 30-min kickoff,
(2) you send access to the AP inbox, (3) we dry-run the first 10 bills
before anything writes to QuickBooks. Reply with the access and we're
moving.

— Scott
```

## Add it to your agent

Read this file and follow the instructions. Run the template against the last five won deals as a table before you turn the trigger on.
Still ungated. Page stays short until you ask.

Common questions

Will this spam the new customer?

Customer-facing mail is drafted and queued. Internal nudges (Slack/task) can go out on their own. That's the split.

What if onboarding is different for every job?

Then the template is too long. Cut it to the five things that are always true. The rest stays a human call.

Want this built for your team?