What to Include in a New Client Welcome Packet (Simple Outline)

A welcome packet is the answer to every question your new client is too polite to ask: Who do I actually talk to? When do I hear from you? Is it okay to text? What happens if I'm slow with feedback?Left unanswered, those questions don't go away — they turn into assumptions, and the assumptions surface at the worst possible moment, usually attached to an invoice.

The good news: a welcome packet that works fits on two pages. Here's the outline we recommend, why each piece is there, and the mistakes that turn welcome packets into unread PDFs.

The two-page outline

1. A short, human welcome

Two or three sentences. You're glad they're here, you're excited about the specific thing you're building for them, and here's what this document covers. Skip the company history — they already hired you.

2. Who's who

Name, role, and photo for each person they'll interact with, and — critically — who their main contact is. If you're solo, this section is one line, and it's still worth including: “You'll work directly with me on everything.” Clients of small agencies often genuinely don't know whether to email the owner or the person who ran the kickoff.

3. How we work together

The section that prevents the most friction. Cover:

• Channel:where day-to-day communication happens (email, Slack, your portal) and where it doesn't (please not Instagram DMs)
• Response time:what they can expect from you, and what you ask of them — “we reply within one business day; feedback within three days keeps the timeline intact”
• Feedback: how revisions are requested, how many rounds are included, and who has final say
• Urgent: what counts as urgent and how to flag it

Write this in a warm voice, but write it. Every line here is a boundary you won't have to set awkwardly later.

4. The timeline

Key milestones with dates, plus the dependencies that make those dates real: “Design review on the 14th assuming we have your brand assets by the 5th.” This sentence structure does quiet, important work — it makes the client's role in the schedule visible before any delay happens, so a slipped deadline reads as cause and effect rather than blame.

5. What we need from you

The client's to-do list: the questionnaire, the files, the access, the kickoff booking. Don't list them as bullet points to remember — link to the place where they get done. Ideally that's one link with everything in it, so this section is two sentences and a button.

6. Money and policies

Invoice schedule, payment terms, accepted methods, late-payment policy, and your cancellation/pause terms in plain language. None of this is new — it's all in the contract — but the welcome packet is the version they'll actually re-read when a question comes up.

7. The single next step

End with exactly one action: “Complete your onboarding here — takes about 20 minutes.” A packet that ends with five action items gets archived “for later.” One clear step gets done.

The mistakes that kill welcome packets

• Length. Past two pages, read-through falls off a cliff. Detailed scope belongs in the contract; brand questions belong in the intake form; reference material belongs in a linked folder.
• Selling.Awards, testimonials, and service menus are pre-sale material. Their presence in a welcome packet quietly says “this is a brochure,” and brochures don't get read carefully.
• Sending it as one of six attachments. The welcome email should be short and warm with one link, not a delivery van of PDFs and action items.

PDF, page, or portal?

A web page beats a PDF for most teams: you can fix a typo without re-sending, links to your form and scheduler are clickable, and it reads properly on a phone — where many clients will open it. The step beyond that is making the packet the front door of the onboarding itself: in Onvoy, the welcome content, the questionnaire, the uploads, the signature, and the payment live in one branded flow, so “read the packet” and “do the onboarding” stop being separate requests.

Whatever format you choose, write it once, template it, and reuse it. The packet's value compounds with repetition — see the client onboarding checklist for where it slots into the broader sequence.