Ninety days in, nobody remembers why they bought

Dongyun Lee·Aug 4

It is 10:07 on a Tuesday. Onboarding ended six weeks ago, the implementation project is closed, and you are staring at a blank email with "Just checking in" in the first line. Delete it. Your first post-onboarding follow-up should remind the customer why they bought, compare that reason with what has changed, and propose one useful next move.

If you cannot write those three things, the problem is not the email. The account lost its memory somewhere between the sales call, kickoff, and onboarding close.

That is why so many 90-day messages ask, "How is everything going?" The sender has a date and a contact, but no reason to enter the customer's day. The customer has to reconstruct the entire relationship before they can answer.

What should you say after onboarding ends?

Start with the original purchase, not the passage of time.

A useful first follow-up contains four parts:

The business reason the customer chose to act.
The result both sides agreed would count as progress.
The evidence you can see so far.
One question or next step that closes the gap.

Suppose a 24-person support team bought your product because managers spent 38 hours each month assembling renewal context from tickets and spreadsheets. During sales, they agreed that success meant cutting weekly account preparation from 90 minutes to 20. Onboarding got the integrations live and trained 12 account owners.

The first follow-up should not say:

Hi Maya, just checking in to see how things are going since onboarding. Let me know if you have any questions.

It should say:

Hi Maya, you bought Dealpilot to reduce the 38 hours your managers were spending on renewal preparation each month. We agreed the first useful test was whether account owners could prepare for the Monday review in 20 minutes instead of 90. Twelve owners are now active, but only seven have prepared an account before the review. Could we look at the five who have not and decide whether the blocker is missing context or a workflow change?

The second message gives the customer something concrete to correct. It also proves that the relationship did not reset when onboarding closed.

Why does "How is everything going?" get ignored?

It creates work without creating value.

The customer has to decide what "everything" means, gather an opinion, and guess what kind of answer you want. Are you asking about product usage, the onboarding experience, the commercial relationship, an unresolved issue, or renewal? A broad question feels easy to send because the sender has moved all the thinking to the recipient.

Timing alone is not a reason either. "It has been 90 days" explains why a task appeared in your CRM. It does not explain why the customer should open the message now.

This is the same problem behind most annoying follow-ups. Frequency gets blamed, but the real failure is usually a lack of purpose. A specific fourth email can be welcome. A vague first email can be irritating.

Post-onboarding messages are especially exposed because the customer has just finished a period of structured activity. There were kickoff calls, setup tasks, training sessions, and weekly updates. Then the project closes. If the next message is a generic check-in, it feels like the vendor stopped paying attention at the exact moment the customer was supposed to start getting value.

Ask a narrower question. Better still, state what you see and ask the customer to interpret it with you.

Which account details must survive onboarding?

Three pieces of context matter more than a complete activity log.

The buying reason

This is the change that made staying the same unacceptable. It is not a category label such as "improve efficiency" or "better reporting." It is the specific pressure that moved the deal.

Perhaps the VP of Sales could no longer explain five slipped renewals to the board. Maybe a new operations lead inherited a spreadsheet nobody trusted. Perhaps the company added 40 accounts without adding another customer success manager.

Use the customer's wording where possible. It will sound familiar because it is theirs.

The success criteria

Success criteria turn the buying reason into something both sides can inspect. They do not need to be perfect metrics. They do need to be observable.

"Better visibility" is not observable. "Every account over $20,000 has an owner and a dated next action before Friday's review" is. So is "The weekly preparation process takes less than 30 minutes" or "No renewal reaches 60 days without an executive contact confirmed."

Onboarding completion is not the same thing. Connecting an integration, inviting users, and finishing training prove that setup happened. They do not prove that the customer is getting the result they bought.

The promises made during sales

Promises include formal commitments and small statements the customer may have treated as commitments. A salesperson might say that a workflow will support a particular approval step, that an import will preserve a field, or that the customer success manager will review adoption after launch.

These details often disappear because they are spread across calls and email threads. Yet the customer remembers them. Your follow-up should acknowledge what was promised, confirm what was delivered, and name anything still open.

A strong sales-to-CS handoff should carry all three elements forward. If it only transfers contacts, contract value, and implementation status, the new owner receives the account record but not the account story.

What if the buying context is already missing?

Reconstruct it before contacting the customer. Do not make them repeat discovery from a blank page.

Start with the evidence closest to the decision:

The last two sales call recordings or notes.
The proposal and business case.
Emails sent in the week before signature.
The kickoff recap and onboarding success plan.
Open commitments recorded during implementation.

You are looking for sentences with pressure in them: "We need this before the next planning cycle," "The board asked again," or "I cannot add another person to manage this." Then find the first promised result and check what the account has done since launch.

If the evidence conflicts, write a hypothesis instead of pretending certainty:

My notes show that the immediate priority was getting renewal risks into the Friday forecast before the Q4 planning cycle. Is that still the right outcome, or has the priority changed since onboarding?

That question is easy to answer. It proves you did the work and gives the customer permission to update the story.

If no source contains a usable buying reason, say so internally. The gap is a process defect, not a writing problem. Fix the account record after the conversation so the same loss does not happen at the next handoff.

When should you send the first post-onboarding follow-up?

Send it when the customer has had enough time to produce evidence, not simply when a standard interval expires.

For a product with a weekly workflow, that may be 14 to 21 days after onboarding. The customer needs two or three real cycles before you can ask what changed. For a monthly reporting process, the first useful review may come after one complete month. A 90-day review makes sense when the promised outcome takes a quarter to appear.

Use the customer's operating rhythm as the clock:

After the first weekly team review using the new process.
After the first month-end close.
Before the next executive forecast.
Once a full cohort has completed the workflow.
Before a contract or planning decision tied to the purchase.

Do not wait for an arbitrary date when the evidence arrives earlier. Do not force an outcome review before the customer has had a fair chance to create the outcome.

The best trigger combines elapsed time with a meaningful event. "Thirty days since launch" is weak. "The first month-end report is complete, 30 days after launch" gives you a reason to talk.

What should you ask in the first review?

The first review should determine whether the original success definition still holds and whether the customer is moving toward it.

You can usually do that with four questions:

Is the original business problem still the priority?
What evidence shows the new process is working or not working?
Which promise or dependency remains unresolved?
What is the smallest next move that would create visible progress?

Keep the conversation tied to the account, not a generic satisfaction script. A customer can be happy with your team and still fail to adopt the workflow. They can dislike part of onboarding and still be on track for the business result. "Are you happy?" compresses those different realities into a polite answer.

Use concrete evidence instead. If nine of 12 users completed the key action, ask what is different about the remaining three. If preparation time fell from 90 minutes to 45, recognize the improvement and examine the last 25 minutes. If the promised executive dashboard is still not live, address the promise before suggesting expansion.

Quiet accounts deserve the same precision. Silence after signing can hide unclear ownership, lost momentum, or a priority change. The diagnostic approach in why customers go quiet after signing also applies after onboarding: observe the behavior, narrow the possible cause, and reduce the next step.

How do you make this follow-up repeatable?

Store the reason, criteria, and promises where the person writing the message can actually find them.

A useful account record needs five short fields:

Buying reason, in the customer's language.
First measurable or observable success criterion.
Promises and open commitments.
Date or event for the first value review.
Named owner for the next customer contact.

The owner should set the review trigger before onboarding closes. Waiting until day 90 to decide what day 90 means guarantees a generic task.

Then connect account evidence to the same record. That might be usage, a completed deliverable, a changed process, a stakeholder response, or a manually recorded result. The goal is not to collect every signal. It is to give the owner enough context to answer one question: what should we say now that would help this customer move?

Review the record at onboarding close. If the buying reason or success criterion is blank, the project is not ready to hand over, even if every implementation task is green.

Your first post-onboarding follow-up is not a courtesy note. It is the first proof that onboarding produced continuity instead of closure. Remind the customer why they acted, show what has changed, and make the next move smaller than the problem.