Help me design a client onboarding process for a service business. Build it from the actual scope and operating constraints I provide; do not invent compliance duties, implementation promises, service levels, data permissions, or client commitments. Service and client type: [SERVICE AND CLIENT] What the client has purchased and what is out of scope: [SCOPE] Current onboarding steps, roles, and systems: [CURRENT PROCESS] Timeline, dependencies, and client responsibilities: [IMPLEMENTATION CONSTRAINTS] Risks, policies, and success measures: [RISKS AND SUCCESS] Create a practical onboarding workflow from signed agreement through the first value milestone. Present it as a table with these columns: phase, purpose, owner, client owner, required inputs, activity, deliverable or decision, exit criteria, target timing, and risk if delayed. Use five to seven phases, including internal handoff, kickoff, discovery or configuration, approvals, launch or handover, and a 30-day check-in where relevant. Then provide three supporting assets: a kickoff-meeting agenda with time boxes, a client-facing checklist of what they must provide and by when, and an internal escalation rule for missing inputs, scope changes, or approval delays. Clearly distinguish contractual commitments from recommended practices. Add a short “do not start until” gate for access, security, legal, or billing prerequisites that I supply. Make responsibilities unambiguous: each task needs one accountable owner, a named client decision-maker, and a concrete exit criterion. Avoid treating a kickoff call as proof that requirements are understood. Before answering, check for handoff gaps, ambiguous ownership, and any milestone that depends on an unapproved assumption. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [SERVICE AND CLIENT] | Describe your service, the typical client, and the type of engagement. | Managed email marketing for independent ecommerce brands, beginning with strategy, campaign setup, and monthly sends. |
| [SCOPE] | List what the client purchased, deliverables, exclusions, and approved assumptions. | Client purchased a 90-day engagement: account audit, welcome-flow improvements, two campaigns per month, and reporting. Paid ads and website development are excluded. |
| [CURRENT PROCESS] | Describe current onboarding steps, internal roles, communication channels, and systems. | Sales hands off through HubSpot; account manager runs kickoff; strategist works in Notion; client communication is by email and a weekly 30-minute call. |
| [IMPLEMENTATION CONSTRAINTS] | State target timeline, dependencies, client obligations, and known scheduling constraints. | Target launch is within 21 days of signature. Client must provide platform access, brand guide, product calendar, and a marketing approver. |
| [RISKS AND SUCCESS] | List relevant policies, risks, required approvals, and the first measurable or observable success outcome. | Do not access customer data until the data-processing addendum is complete. Success is an approved 30-day campaign calendar and a working welcome flow. |
How to use
- Paste your signed scope and actual internal handoff details before asking for a workflow.
- Name a client decision-maker, since group feedback without an owner is a common source of missed launch dates.
- Check that every phase has a concrete exit criterion, not just a meeting or an email sent.
- Then send: “Turn this into a one-page client welcome email that states only client responsibilities and deadlines.”
Variations
Software implementation
Use this for onboarding a new SaaS customer.
Design a SaaS implementation onboarding plan. Customer segment and use case: [CUSTOMER]. Purchased package and exclusions: [SCOPE]. Required integrations and data sources: [TECHNICAL DEPENDENCIES]. Customer stakeholders and decision-maker: [STAKEHOLDERS]. Security, access, and launch criteria: [REQUIREMENTS]. Produce a six-phase table from contract handoff through go-live and adoption review, with owner, client owner, inputs, exit criteria, and risks. Include a technical-readiness gate and an escalation path for delayed data or approvals. Do not promise integrations or timelines not supplied.
Agency kickoff
Use this for a creative or marketing-services engagement.
Create an agency client-onboarding process for [SERVICE]. Signed deliverables and out-of-scope work: [SCOPE]. Client brand, approval, and asset situation: [CLIENT CONTEXT]. Internal team and handoffs: [TEAM]. Timeline and first milestone: [TIMELINE]. Give a workflow with discovery, briefing, asset collection, strategy approval, production readiness, and first delivery. Include a kickoff agenda, a client asset checklist, and a scope-change rule. Make a single client approver mandatory and separate feedback from formal approval.
High-touch renewal
Use this when onboarding starts after a renewal or expansion.
Build an onboarding reset plan after a client renewal or expansion. Existing relationship and current pain points: [ACCOUNT CONTEXT]. New scope: [EXPANDED SCOPE]. Previous commitments and unresolved items: [OPEN ITEMS]. Stakeholders: [STAKEHOLDERS]. Desired first 60-day outcome: [SUCCESS]. Produce a phased plan that preserves prior context while reconfirming scope, owners, data access, governance, and success measures. Include a risks log format and a meeting cadence. Flag commitments that need written confirmation before work starts.
Tips
- Start the clock from receipt of complete prerequisites, not signature alone, unless your contract explicitly says otherwise.
- Use an internal handoff checklist that captures commercial promises, stakeholders, exclusions, and unusual terms before the kickoff is booked.
- Make approval criteria visible: “approve strategy” should specify who approves, what artifact they approve, and by what date.
- Track the time between client requests and client responses separately from your team’s delivery time so delays are diagnosable.
FAQ
How long should client onboarding take?
It depends on scope and dependencies. A useful process names target timing for each phase and clearly states what pauses the clock.
What is the most important onboarding metric?
Measure time to the first value milestone, alongside prerequisite completion and stakeholder adoption. Kickoff attendance alone is not a success measure.
Should clients see the internal workflow?
Share a simplified client-facing plan with their responsibilities, milestones, and decision points. Keep internal escalation notes and staffing details internal.