Start from the customer's questions
After signing, a buyer asks three things: What happens now? Who do I talk to? Did I make the right choice? Your follow-up has one job, which is to answer those three questions before they have to ask. The internal side is covered in Build the sales-to-delivery handoff. This chapter covers what the customer sees.
Map six touchpoints
Write the sequence on one page, with a day, a channel, an owner and a purpose:
- Within one hour: a confirmation from the person who sold, thanking them and stating the next step.
- Day 1: a welcome from the delivery lead, introducing the team and the kick-off date.
- Day 3: a short preparation list: what you need from them, by when.
- Day 7: a reminder and a confirmation that the kick-off is on, with the agenda.
- Around day 14, or after the first delivery milestone: a check-in on the first result.
- Day 30: a 15-minute call asking what is working and what is not.
Adjust the days to your delivery rhythm, but keep the count small.
Remind them why they bought
In the first message, restate the problem they hired you to solve, in their words, taken from your call notes. "You told us the main issue was slow proposals and no visibility of the pipeline" does more to calm remorse than any generic welcome. It also proves someone listened.
Set expectations in three lines
Every message from the first week should answer: what happens next, when, and what we need from you. Keep it to three lines. If a customer must read a page to understand the next step, they will leave the email unread.
Give them a small early win
Early value cuts remorse faster than reassurance. Share a quick deliverable in the first two weeks: the project plan, a first audit finding or a configured account. A short Loom video walking through the plan is often enough. Let them book the kick-off straight away with Calendly rather than through back-and-forth emails.
Automate the triggers, write the words yourself
Build the sequence as tasks and reminders in your CRM, for example HubSpot or Pipedrive, triggered when the deal is marked won. The system should create the task, assign the owner and flag it if it is overdue. The messages should still come from a named person's own address, in plain text, written like a person. Customers can tell a template from a human.
Expand the relationship
Use the first month to meet more people at the customer. Ask your buyer who else should be at the kick-off. A relationship with one contact is fragile, as the playbook chapter on multi-threading explains. Do not ask for a referral or a review yet. Wait until they have seen a result.
Common mistakes
- Going silent for a week after the deal closes.
- Sending a long welcome pack nobody reads.
- Putting the sales rep and the delivery lead in conflicting messages.
- Automating the wording as well as the timing.
- Asking for a testimonial before the customer has had a win.
How you know it works
Every closed deal triggers the sequence without anyone remembering to do it. Customers reply to the first message, attend the kick-off on time and send what you asked for within the week. Early cancellations and "can we pause?" requests fall. In the day-30 call, customers describe their result in their own words, and you write it down for the next sales conversation.