Jump to section
A new customer welcome packet is the bundle of information you hand a client the moment they become a customer. Done well, it answers the three questions every new customer is quietly asking – who do I talk to, what happens next, and what do I need to do? – before they have to ask. Done badly, it's a PDF nobody opens.
This is a checklist of what to include, a template you can copy, and a better way to deliver it than a static file. It applies to any B2B setting where a signed deal turns into a project: SaaS and software implementations, marketing and creative agencies, and professional services like accountants, tax advisors, and consultancies.
What is a new customer welcome packet?
A welcome packet – sometimes called a welcome kit or onboarding pack – is the onboarding equivalent of a first day at a new job. It orients the customer, sets expectations, and gives them a single place to start. Historically it was a physical folder or a slide deck; today it's usually a long welcome email, a document, or a link.
What to include: the welcome packet checklist
Five sections cover almost every case. Keep each short – a new customer skims first and reads later.
1. Welcome and who's who
Open with a genuine welcome and a quick reminder of why they bought – the outcome they're chasing, in their words. Then introduce the people: their main point of contact, who to reach for support, and any specialists (implementation, technical, billing). A photo and a one-line role for each goes a long way toward making the relationship feel human instead of a ticket queue.
2. Goals and success criteria
Restate what "done" looks like. This is the single most-skipped section and the most valuable one: write down the specific outcomes and the rough dates you both agreed to during the sales process. It keeps onboarding anchored to the result the customer cares about, not just the tasks, and it gives everyone a shared definition of success to point back to.
3. The onboarding plan and timeline
Lay out the path from today to live: the milestones, who owns each step (you and them), and target dates. This is the spine of the packet. A clear, shared plan is what turns "we'll be in touch" into a project both sides can track – if you don't already have one, our customer onboarding plan template gives you a structure to start from.
4. Key resources and access
Everything the customer needs to get going, in one spot: getting-started guides, relevant help docs or videos, login or access instructions, and any security or compliance information their team will ask for. The goal is to pre-empt the "where do I find…?" emails that clog the first two weeks.
5. One clear next step the customer owns
End with a single, specific action the customer owns – not five, one. "Complete this 3-minute intake form," "book your kickoff call," or "invite your two admins." Giving the customer a small task on day one is the highest-leverage part of the whole packet: it captures the momentum from the sales process before it decays, and it saves you time later (here are four ways to create immediate momentum after a deal closes).
An early intake form is usually the best first task. Every detail you collect up front – team size, goals, technical setup, stakeholders – is something you don't spend the kickoff call gathering, so that call turns from an interview into real progress. See how to collect customer information during onboarding for what to ask, and if you use AI you can even generate the intake form from a prompt.
New customer welcome packet template
Copy this, delete what doesn't apply, and fill in the brackets. It works as a doc, an email, or – better – as the outline of a shared onboarding space.
Welcome to [Your Company], [Customer Name]!
We're thrilled to be working with you. Here's everything you need to get started.
Your goal: [The outcome you agreed on, e.g. "go live with [product] across your sales team by [date]"].
Your team:
- [Name], [Role] – your main contact for anything onboarding
- [Name], [Role] – technical/implementation questions
- Support – [how to reach support, hours]
Your onboarding plan: Here's the path to going live. We've marked who owns each step.
- [Milestone 1] – owner: [you/us] – target: [date]
- [Milestone 2] – owner: [you/us] – target: [date]
- [Milestone 3] – owner: [you/us] – target: [date]
Resources to get started:
- [Getting-started guide]
- [Access / login instructions]
- [Help docs, videos, security info]
Your first step: [One specific action + link, e.g. "Fill in this short intake form so we can tailor your setup – 3 minutes."]
Questions before then? Just reply here or message [contact].
Why a living Space beats a static PDF
A PDF or slide packet has one fatal flaw: the day you send it, it starts going out of date. The plan slips, a date moves, a new resource gets added – and the file in the customer's inbox still says the old thing. So you send a "v2," then a "final v3," and the customer never knows which one is current. Meanwhile you can't tell if anyone opened it, tasks live in email threads instead of the document, and the packet becomes a snapshot of week one rather than a tool for the whole onboarding. General-purpose tools don't really fix this either: a shared doc in Notion or a Monday board can hold the content, but they're built for your team – not a client-facing, branded experience a customer opens without an account.
The modern welcome packet isn't a file you send – it's a link that stays live. This is the core of how Valuecase approaches onboarding: instead of a PDF, each new customer gets their own Space – a single branded page, in your colours and on your domain, that the customer opens with no login and no IT ticket. The plan, the people, the resources, and the next-step task all live in that one place, and it updates as onboarding progresses, so it's always current.
Because it's a real workspace rather than a document, it does things a packet can't:
- The customer owns tasks inside it. Forms and next-step actions sit right in the Space, so the "day one task" above happens where everything else lives. Learn more about building a branded customer onboarding portal.
- It chases for you. Automated reminders nudge the customer when a task is due, so nothing gets missed and you're not the one sending "just following up" emails. You can even set up AI to chase stalled customers with full context.
- You can see engagement. Because the Space is tracked, you know who opened what and which accounts are stalling – engagement tracking flags a stuck onboarding before it becomes a stuck renewal.
That turns the welcome packet from a one-time artifact into the home base for the entire onboarding – the same link on day one and on go-live day.
Send it automatically the moment they sign
However you build your packet, one rule holds: it should go out the day the deal closes, not three days later. The energy behind a fresh signature decays fast, and a same-day welcome tells the customer they made a good decision.
The catch is that "remember to send the welcome packet" is exactly the kind of task that slips on a busy week. This is the other reason a living space beats a file. Because Valuecase connects to your CRM through native two-way HubSpot and Salesforce integrations (plus Zapier and Make), marking a deal closed-won can automatically spin up the customer's Space from a template, pre-fill it with what you already know, and send the welcome – no one on your team has to lift a finger. The handoff from "signed" to "onboarding started" happens on its own, the same day.
FAQ
What should a new customer welcome packet include?
Five things: a warm welcome and introductions to the people they'll work with; the goals and success criteria you agreed on; the onboarding plan with milestones, owners, and dates; key resources and access (guides, logins, security info); and one clear next step the customer owns. Keep each section short and skimmable.
Is the welcome packet the same as the welcome email?
Often, yes. The "packet" is really just the content – the goals, plan, people, resources, and next step – and plenty of teams deliver all of it as one long welcome email. That works, but it's static and gets buried in the thread. Whether you send it as an email, a doc, or a live link, the sections to include are the same. (For the message itself, see our customer onboarding email templates.)
Is a PDF or a portal better for a welcome packet?
A portal, in almost every case. A PDF is out of date the moment a date moves, you can't tell if it was opened, and tasks end up scattered across email. A living, branded space stays current, holds the customer's tasks, sends its own reminders, and shows you engagement – so it works for the whole onboarding, not just day one.
Build your welcome packet as a Space. Give every new customer their own branded onboarding space – plan, people, resources, and their first task in one link, sent automatically the day they sign. See how Valuecase does customer onboarding.
