Jump to section
You have configured the product. The integration is tested. The plan on your side looks solid. And yet the customer has gone quiet. Tasks sit overdue. The go-live date creeps. When you ask, your champion says they are "working on it internally."
What they mean is that they are stuck.
They agreed to every recommendation you made. They believe in the software. What they don't have is the time, the design skills or the internal authority to turn their team's way of working inside out – and that is what a rollout actually asks them to do. More reminders from you won't help. What will help is material they can forward.
The part of onboarding nobody designed for
There is a quiet assumption baked into most onboarding processes: that once the software is set up correctly, the customer's team will use it. Configure the product, train the champion, hand over the plan – and the rest takes care of itself.
It doesn't. And the reason is structural, not motivational.
Roughly 20% of what makes a rollout succeed is technical setup. The other 80% is internal behaviour change: getting colleagues to log into a new tool, convincing a department head that the old way is actually going away, and making sure the IT team prioritises a DNS change among the forty other requests in their queue. That 80% sits entirely with your champion. You can configure the product perfectly and the project can still stall because nobody on the customer's side is moving.
This isn't a lazy-champion problem. Your champion has a day job. Running an internal launch campaign – building slides, drafting announcements, writing emails to IT, recording walkthroughs, making the case to every department head individually – is a second job. One they never signed up for, that they have no training for, and that they now have to do on top of everything else.
The diagnostic that changes how you chase
The next time a customer task is overdue, ask yourself one question before you send another reminder:
Is this late because the technical work is hard, or because the champion doesn't know how to ask their colleagues to act?
If it's the first – the integration is genuinely complex, the data migration hit a snag – then a reminder, an offer of help or a short troubleshooting call is the right move.
If it's the second, another nudge makes things worse. You are asking someone to do something they don't know how to do, and each reminder adds pressure without adding capability. What they need is not more urgency. It's a thing they can forward.
Which brings us to the rule this entire approach is built on.
Never ask a customer to explain, launch or sell your software inside their own organisation starting from a blank page.
Your champion is not a copywriter, a slide designer, a change management consultant or an internal comms lead. But a rollout asks them to be all four. The fix isn't training them. It's doing the work once on your side and handing them the finished assets.
What goes in an internal launch kit
An internal launch kit is a set of ready-to-use assets your champion forwards, presents or posts – with zero editing required. It is assembled once from what your best implementations already produced, then reused with every customer. Here is what belongs in it.
Slides for the company town hall (and a separate deck for manager syncs)
Your champion will almost certainly have to present the new tool to a wider audience at some point. The company all-hands is the obvious one, but the higher-stakes version is the manager sync: a smaller room with the people whose teams will actually have to change their workflows, and who can kill adoption by shrugging.
Don't make your champion build either deck. Give them a pre-designed slide set that covers why the company bought the tool, what changes for which teams, the timeline, and where to go for help. Keep it visually finished – your champion should be able to present it without spending a Sunday in PowerPoint. The manager deck should go further: it needs to answer "what's in it for my team specifically" for each department head in the room.
Pre-written internal announcement copy
Every company has somewhere people go for official news – an intranet, a Slack announcement channel, an internal newsletter. Writing that post is the kind of task that sits on a to-do list for two weeks because it feels important but not urgent, and because nobody knows what to say.
Write it for them. A short, warm, clear post that announces the new tool, explains why it was chosen, names the go-live date and tells people what to expect. Your champion copies it, pastes it and hits send. Three weeks of internal drafting becomes thirty seconds.
Ready-to-send emails to the people who don't report to your champion
This is where most internal launches get stuck. Your champion needs something from someone who has no reason to prioritise them: an IT lead who needs to approve a DNS change, a security team that needs to whitelist a domain, the outgoing legacy vendor who needs to be asked for a data export.
Each of those is a small request that can sit in an inbox for weeks – not because anyone is being difficult, but because the request arrives as a vague "hey, can you take a look at this?" instead of a specific, actionable ask with context.
Write the emails. One for IT with the exact technical change needed and why. One for the legacy vendor requesting the data export, with the format and deadline specified. One for the security team with the domain, the certification details and the timeline. Your champion forwards them. The recipient gets a clear ask they can act on immediately. The champion doesn't have to translate between your world and theirs.
Short video guides for end users (60 seconds each)
Nobody watches a 20-minute training video. A handful of 60-second clips – one per core workflow – gets watched. Record them once: how to log in, how to complete your first task, how to find help. Keep each clip to a single action, under a minute, with no intro music and no agenda slide. Your champion shares them in Slack or embeds them in the announcement post, and end users get the answer to "how do I actually do this?" without booking a training session.
A "what's in it for me" one-pager per persona
Your champion's colleagues are not excited about learning a new tool. They are excited about doing less manual work, getting answers faster, or not having their inbox used as a to-do list. But they won't connect those dots on their own.
One page per internal persona – the end user, the team lead, the approver – that says, in plain language, what changes for them and why the new way is better. Not feature lists. The end-user version might say: "Instead of emailing five people to get a decision, you'll see exactly what's waiting for you in one place." The team lead version: "You'll know which accounts are stuck without asking anyone for a status update."
These one-pagers do the internal selling your champion shouldn't have to do from scratch. They also pre-empt the "why are we doing this?" meeting that otherwise lands in week three.
For high-volume segments: the standing open clinic
If you onboard enough customers that bespoke training doesn't scale, the equivalent move is a standing open clinic instead of one-off training requests.
Pick a recurring slot – "Tuesdays at 2pm: live setup and Q&A" – and give your champion a single link they can drop into any internal conversation. End users join when they need to, get unstuck, and leave. No scheduling, no back-and-forth, no training session that half the team misses and then asks to have again.
The clinic does for training what the launch kit does for internal comms: it removes the coordination work from your champion's plate and replaces it with something they can simply point people at.
Ship the kit where your champion already is
The content of the kit matters. Where it lives matters almost as much.
If you email a zip file of assets to your champion, two things happen. They download it, forward one slide deck, and the rest disappears into their downloads folder. A month later, when they need the IT email template, they can't find it and they email you. The kit only works if it stays findable.
The better pattern is to put the entire launch kit inside the same shared workspace the champion already opens to track onboarding progress. In Valuecase, each customer gets their own branded Space – the single place that customer opens to get onboarded, holding their plan, tasks, forms and resources behind one link. The internal launch kit lives in that same Space: the slide decks, the email templates, the video clips, the one-pagers. Your champion opens one link and everything they need to run the internal rollout is right there, organised and ready to forward.
That changes the champion's job from create the rollout to distribute the rollout. The distinction is everything. Creating takes design skill, copywriting time and internal authority. Distributing takes a forward button.
Because Spaces are built from templates, you don't rebuild this kit per customer. You assemble it once as part of your onboarding template, and every new customer's Space comes pre-loaded with it. The same automation that spins up the Space when a deal closes – through Valuecase's native HubSpot and Salesforce integrations – can have the launch kit waiting for your champion on day one. No manual assembly, no "I'll send you the slides later," no forgotten attachment.
A proper customer onboarding kickoff call is the natural moment to walk your champion through the kit. Show them what's in it, explain that each asset is pre-built and ready to forward, and point out the specific email templates that will save them the most time. You're not adding work to their plate. You're taking it off.
Why this works (and reminders don't)
Reminders create pressure. Assets create momentum.
When you send a follow-up email, the champion feels the weight of something they haven't done. When you hand them a finished slide deck and a pre-written announcement, they feel equipped. One triggers guilt. The other triggers action.
This is also why the kit prevents the most expensive kind of onboarding stall: the one where the product works fine and the project still dies. In our experience, those stalls almost always trace back to a champion who agreed with everything and then couldn't move their organisation. They didn't need a better argument from you. They needed better ammunition for the conversations you weren't in the room for. That's what the kit is.
There is a broader lesson here about where onboarding time actually goes. The technical steps you control are rarely the bottleneck. The waiting – for decisions, for sign-offs, for someone on the customer's side to forward an email – is what eats weeks. Our guide on reducing time to value in SaaS onboarding walks through more ways to cut that dead time out of the schedule, and catching stalled onboardings before they churn covers the early-warning signals to watch for.
FAQ
What is an internal launch kit for customer onboarding?
An internal launch kit is a set of ready-to-use assets you give your champion so they can roll out new software inside their company without building anything from scratch. It typically includes pre-designed presentation slides (for all-hands and manager syncs), pre-written internal announcement copy for the company intranet or Slack, ready-to-forward email templates for IT, security and legacy vendors, short video guides for end users, and a "what's in it for me" one-pager per internal persona. The champion's job shifts from creating the rollout to distributing it.
Why do onboarding projects stall even when the software is configured correctly?
Because configuring the product is the smaller half of a rollout. The bigger half is getting the customer's colleagues to change how they work, and that half sits with the champion. A champion can agree with every recommendation and still fail to move their team because they lack the time, the design skills or the internal authority to run an internal launch campaign. More task reminders address none of those three.
How do I know if my champion needs a launch kit or just another reminder?
Ask whether the overdue task is late because the technical work is hard or because the champion doesn't know how to ask their colleagues to act. If it's a technical blocker, a reminder or a troubleshooting call is the right move. If it's an internal-influence problem – they need IT to approve something, or a department head to sign off, or end users to actually show up – another nudge makes things worse. They need material they can forward, not more urgency.
What should the email templates in a launch kit cover?
At minimum: an email to the customer's IT team with the specific technical change needed (DNS, domain whitelisting, SSO configuration) and the timeline; an email to the outgoing legacy vendor requesting a data export with the required format and deadline; and an email to the security or compliance team with your certifications, hosting details and what they need to approve. Each email should be specific enough that the recipient can act on it without a follow-up call. Three weeks of internal drafting and back-and-forth turns into your champion spending thirty seconds pressing forward.
How do you deliver a launch kit without it getting lost in email?
Put the kit inside the same shared onboarding workspace your champion already opens – not as a zip file attachment that disappears into a downloads folder. In a platform like Valuecase, the launch kit lives in the customer's branded Space alongside their plan, tasks and forms, so the champion always knows where to find it. Because Spaces are built from templates, the kit is pre-loaded for every new customer with no per-account assembly.
Can a launch kit replace one-on-one training?
For most end users, yes – a sixty-second video per core workflow and a "what's in it for me" one-pager covers what a training session would cover, and people actually consume it. For teams that still need live help, a standing open clinic (a recurring slot like "Tuesdays at 2pm: live setup and Q&A") replaces one-off training requests with something the champion can simply point people at, with no scheduling back-and-forth.
See what to ship your champion on day one. Book a demo of Valuecase or start a free trial – build your onboarding template once, launch kits included.
