GPT Tasks/Design a Client Onboarding Experience
Task library

Work · GPT Task

Design a Client Onboarding Experience

Turn a service, client context, agreed expectations, access needs, responsibilities, timeline, and communication preferences into a client onboarding workflow with welcome, intake, kickoff, milestones, and friction checks.

Context → structured prompt → explicit AI handoff

Runs in this browser. No upload by this page. External AI handoff is explicit. Review before sharing.

Prompt workbenchConfigure → review → use
01

Configure task

Setup
Describe the service or engagement, who is involved, the starting point, and what the onboarding experience needs to accomplish.
List supplied scope, deliverables, responsibilities, communication expectations, approvals, or boundaries that are already known.
Prompt style
Additional options
Add files, account access, intake information, kickoff timing, dependencies, stakeholders, or other onboarding constraints.

What you’ll need

  • Service or engagement context plus the expectations and responsibilities already agreed
  • Service and client context
  • Agreed expectations and responsibilities

What you’ll get

  • Onboarding journey and stages
  • Welcome and orientation content
  • Client intake requirements
  • Access and asset checklist
  • Kickoff agenda or async start sequence
02

Prompt preview

Editable

Review or edit the generated prompt before you copy it or explicitly open an AI chat.

Export

ChatGPT opens with the current prompt prepared. Gemini copies the current prompt, then opens Gemini so you can paste it. Keep secrets and sensitive information out of URL-carried prompts.

Task referenceExamples, expected output, boundaries, and routing.

Examples

1. Freelance website project

Context: A freelancer provides the signed scope, client contacts, required assets, kickoff window, revision process, and communication channel.

Goal: Create a smooth project onboarding flow without changing agreed terms.

Useful output: Welcome sequence, intake checklist, asset requests, kickoff agenda, roles, milestones, and friction checks.

2. Agency retainer

Context: An agency provides retainer scope, recurring deliverables, stakeholder list, reporting cadence, and account-access requirements.

Goal: Build a reusable hybrid onboarding experience.

Useful output: Stages, access checklist, kickoff, communication norms, recurring setup, template needs, and open questions.

3. Consulting engagement

Context: A consultant supplies a multi-stakeholder project scope, sponsor responsibilities, workshop dates, and document-access needs.

Goal: Plan a structured start with clear responsibilities.

Useful output: Onboarding journey, stakeholder intake, access plan, kickoff agenda, approval points, and first milestones.

Expected output

  • Onboarding journey and stages
  • Welcome and orientation content
  • Client intake requirements
  • Access and asset checklist
  • Kickoff agenda or async start sequence
  • Roles, responsibilities, and communication norms
  • Milestones and early success checkpoints
  • Templates/messages to prepare
  • Friction risks, assumptions, and next actions

Truth boundary

Use only supplied services, terms, timelines, access needs and responsibilities. Do not invent contractual obligations, approvals, credentials, policies, client facts or promised outcomes.

Overlap guard: Owns the post-agreement beginning of a client relationship: welcome, intake, access, kickoff, responsibilities, and early milestones. Use Proposal/SOW before agreement, Service Recovery after a service problem, and Final Handoff at project close.

Privacy and handoff

Runs in this browser. No upload by this page. Copy/download locally or explicitly open ChatGPT or Gemini. Source files are attached in the chosen AI service, not uploaded by Mycelgrid. Review the generated prompt and AI output before using or sharing it.