thinkhard.SI

Prompt repository Small business

Write a welcome packet for new clients

You need new clients to know what happens next, what you need from them and how to reach you.

Registry no.
SMB-017
Collection
Small business
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
10
Added

Small businessAny chat

The prompt

Score 10 of 10, Excellent

Use it when You need new clients to know what happens next, what you need from them and how to reach you.

  • {{business_name}}
  • {{service}}
  • {{process}}
  • {{client_inputs}}
  • {{communication}}
  • {{payment_terms}}
  • {{change_policy}}
  • {{common_questions}}
  • {{voice}}
  • {{signer}}
Full prompt and why it works
Prompt
Write a welcome packet for new clients of {{business_name}}, which provides {{service}}. New clients are most uncertain between saying yes and the first piece of real work, and most client problems start with an expectation nobody wrote down. The packet should leave them knowing exactly what happens next, what I need from them, and how we will work together.

How a typical engagement runs, step by step:
"""
{{process}}
"""

What I need from clients, and when:
"""
{{client_inputs}}
"""

Communication: {{communication}}
Payment terms: {{payment_terms}}
How changes and extra requests are handled: {{change_policy}}
Questions new clients often ask: {{common_questions}}
How I sound: {{voice}}

Use these headings:
1. Welcome: three or four sentences, warm and specific to the service, signed by {{signer}}.
2. What happens next: a numbered timeline from today to the finished work, with typical timing for each step.
3. What I need from you: a checklist with a due point for each item, for example "Logo files, before our kickoff call".
4. How we'll communicate: channels, response times, working hours, and what counts as urgent.
5. Payments: when invoices arrive and how to pay.
6. Changes and extra work: how a new request is handled and priced.
7. Questions: the common questions with short answers.

Keep it between 500 and 900 words, in short paragraphs and bullets, so it reads in about five minutes and works as a PDF or a web page.

Use only the terms and timings above. Do not add policies, fees, deadlines or guarantees I have not given. Where the packet covers something my contract also covers, such as payment or cancellation, keep my wording and add one line saying the signed agreement applies if anything differs.

If anything is missing for a heading, keep the heading and write "[to add: ...]" with what belongs there, so I can see the gap.

Variables

{{business_name}}
Your business name.
{{service}}
What you provide, for example "brand identity design" or "monthly bookkeeping".
{{process}}
The steps from signed agreement to finished work, with typical timing.
{{client_inputs}}
Everything you need from a new client (files, access, decisions, approvals) and when you need it.
{{communication}}
Channels, your hours, how quickly you reply, and what to do if something is urgent.
{{payment_terms}}
Deposit, invoice timing, due dates and how clients pay.
{{change_policy}}
For example "anything outside the proposal is quoted separately before I start it".
{{common_questions}}
Questions new clients usually ask, with your answers if you have them.
{{voice}}
A few words on how you sound, for example "friendly and organized".
{{signer}}
Who signs the welcome, for example your first name and role.

Why it works

  • Who it's for. It is written for the uncertain stretch between yes and the first real work, which is where unwritten expectations turn into problems.
  • Format. A checklist with a due point for every item you need tells clients exactly what to send and when, which is the part they most often miss.
  • If unsure. Empty sections stay in place with a marked gap, so you see what is missing instead of receiving invented policies.

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.