thinkhard.SI

Prompt repository Customer support & success

Plan a new customer's onboarding

You need milestones, training and check-ins that get a new customer to first value quickly.

Registry no.
SUP-012
Collection
Customer support & success
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7
Added

Customer support & successAny chat

The prompt

Score 10 of 10, Excellent

Use it when You need milestones, training and check-ins that get a new customer to first value quickly.

  • {{customer_name}}
  • {{purchase_details}}
  • {{customer_goals}}
  • {{customer_team}}
  • {{constraints}}
  • {{our_onboarding}}
  • {{plan_length}}
Full prompt and why it works
Prompt
Plan the onboarding for our new customer {{customer_name}}, as a document I can share with them at the kickoff call. The goal is to get them to first value (the first point where they get a real result from what they bought) as early as possible, because customers who see a result early are far more likely to stay.

What they bought:
"""
{{purchase_details}}
"""

What they want to achieve, from the sales handoff:
"""
{{customer_goals}}
"""

Their team and roles: {{customer_team}}
Deadlines and constraints (launch dates, approvals, holidays): {{constraints}}
What onboarding we provide (sessions, hours, resources): {{our_onboarding}}
Plan length: {{plan_length}}

Include:
1. First value: one sentence defining it for this customer, and a target date.
2. Milestones: a table with Week, Milestone, What "done" means, Owner on their side, and Owner on ours. Put the setup tasks that block everything else first.
3. Training: who needs which session, by role, so no one sits through training they do not need.
4. Check-ins: when, with whom, and the question each one answers.
5. What we need from them: access, data, decisions and people's time, with dates.
6. Risks to watch: up to four, such as no executive sponsor or a data migration that depends on their IT team, each with what we will do about it.

Keep it to about two pages (under 700 words), in plain language their team can follow without knowing our product's vocabulary.

Use only the services and resources listed above. Do not promise extra sessions, custom work, integrations or dates we have not committed to, since the customer will plan around this document. Leave out filler such as "We're excited to partner with you".

If the goals from the handoff are vague, for example "improve efficiency", do not guess a measure. Write "[TO AGREE AT KICKOFF]" where the measure goes, and add three questions for the kickoff call that would pin it down.

Variables

{{customer_name}}
The customer's company name.
{{purchase_details}}
What they bought: product, plan, number of users, add-ons and contract start date.
{{customer_goals}}
What they want to achieve, from the sales handoff or their own words.
{{customer_team}}
The people involved on their side and their roles, for example "Ops lead (sponsor), two admins, 40 end users".
{{constraints}}
Deadlines and limits: a go-live date, approvals needed, holidays, other projects.
{{our_onboarding}}
What your onboarding includes: number of sessions, hours, resources and who runs them.
{{plan_length}}
How long the plan covers, for example "30 days" or "90 days".

Why it works

  • What good looks like. First value is defined up front with a target date, so every milestone serves the result the customer bought rather than a list of setup tasks.
  • What to avoid. It promises only the sessions and services you provide, since the customer will plan their own staff time around this document.
  • If unsure. Vague goals get a marker to agree at kickoff and the questions that would pin them down, instead of an invented measure.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.