A customer says yes. The project is booked, the agreement is signed, or the first purchase is complete.

What happens to the relationship after that?

Some businesses have a natural repeat-service cycle. Others complete projects a customer may need only once. Both can create a better post-sale experience: deliver what was promised, resolve problems, stay useful when appropriate, and make it easy for a satisfied customer to return or recommend the business.

If your results from the CAI Assessment identify Retention & Expansion as a primary constraint, this guide will help you inspect what happens after the sale. The goal is not to send more messages to every customer. It is to find where relationships lose context and choose one useful improvement.

Choose your starting point: Select five recent customers. Include a completed job or project, an active customer, and someone whose experience did not go as planned. Use your CRM, project records, or team notes to follow each relationship.

An appropriate post-sale relationship

Resolve service issues first. Some customers will not need to buy again; future contact should match their actual needs and preferences.

  1. Handoff

  2. Delivery

  3. Issue resolution

  4. Appropriate future need

  5. Review / referral or expansion

Check 1 of 5

Did the delivery team receive the promise made during the sale?

A customer should not have to explain their needs again because the person delivering the work cannot see what was discussed.

Imagine a homeowner hiring a contractor for a kitchen renovation. During the sales conversation, the homeowner explains that access to the kitchen must be restored before a family event. The project is approved, but that timing never reaches the person scheduling the work.

Test it
Open each customer’s sales record and delivery record. Can the person responsible for the work see the agreed scope, expectations, timing, important preferences, and anything the customer was told would happen next?
Write down what happened
Record one promise that transferred clearly and any detail that was missing or contradicted after the sale.
If this check fails
Define the minimum handoff information the delivery team needs. Make the handoff an explicit step with an owner, rather than assuming that a won sale automatically communicates the full context.

If the context was already lost before the sale, the CRM & Customer Lifecycle check helps trace how conversations and next actions are recorded.

Check 2 of 5

Do you know whether the customer received the outcome they expected?

A completed invoice or closed project does not, by itself, tell you whether the customer’s problem was resolved.

The renovation may be finished, but the homeowner might still be waiting for a final detail. A recurring-service customer might be paying on schedule while repeatedly experiencing the same issue. Asking for another purchase or a referral at that moment would miss the more important need.

If the answer is unknown, choose an appropriate way to ask a recent customer whether the result met their expectations. Keep the question short enough that someone can answer honestly.

Test it
For each of your five customers, find the point at which the team confirmed that the promised work was delivered. Is there a record of unresolved issues, follow-up work, or customer feedback?
Write down what happened
Mark each experience as confirmed , issue open , or unknown . Record the specific issue rather than reducing the customer’s response to a vague “happy” or “unhappy” label.
If this check fails
Create a simple completion and issue-resolution step. Make someone responsible for closing open concerns. Resolve service problems before sending promotional follow-up.

Check 3 of 5

Is there a legitimate future need—and do you know when it might arise?

Retention looks different across businesses.

A pest-control company may offer ongoing service that the customer expects. A contractor who completes a kitchen renovation should not invent a monthly reason to contact the homeowner. That customer may have a future project, need help with a warranty question, or know someone who needs similar work—but none of those should be assumed.

  • Is there a recurring service or renewal the customer already expects?
  • Is there a related need the customer actually mentioned?
  • Is a practical check-in useful after delivery?
  • Would no further outreach be the most respectful next step?
Test it
Look at the five customer relationships. For each one, ask:
Write down what happened
Record the real reason for a future contact, its appropriate timing, and whether the customer expressed a communication preference. If there is no relevant reason, write none .
If this check fails
Segment customers by their actual relationship and need. Build reminders around useful moments, such as a scheduled service, agreed check-in, or customer-stated future project. Avoid placing every past customer into the same generic sequence.

Check 4 of 5

Have you made it easy for a satisfied customer to advocate?

A positive experience can lead to a review, referral, testimonial, or repeat conversation. But first, the business needs to know that the experience was positive and that any open issues have been addressed.

A customer with an unresolved issue needs service, not an advocacy request.

Test it
Review how and when you ask customers for feedback, reviews, or referrals. Does the request come after the work is genuinely complete? Is it easy to act on? Can customers share an honest experience without pressure?
Write down what happened
Note whether a request was made, what it asked for, and whether it fit the customer’s experience. Record any customer who volunteered praise or referred someone so the team can thank them appropriately.

If this check fails: Create a simple, respectful request at the right moment. Ask for an honest review rather than a positive rating, and do not offer an incentive for a Google review. Google’s policies prohibit incentivized reviews and selectively soliciting positive reviews: Google Business Profile review policy.

Check 5 of 5

Can you tell what happened after the initial sale?

If every customer record stops at “Closed Won,” the business cannot easily see who returned, renewed, referred someone, raised an issue, or ended the relationship.

That makes it difficult to improve the post-sale experience. It also makes expansion look like a collection of anecdotes rather than something the team can learn from.

  • The service or project they originally purchased
  • Whether the promised work was completed
  • Any unresolved issue
  • A later purchase or renewal, when relevant
  • A referral or review, if one occurred
  • The next appropriate action—or a deliberate decision that none is needed
Test it
For your five customers, see whether you can identify:
Write down what happened
Mark what you can verify, what someone remembers but never recorded, and what remains unknown.

If this check fails: Start with a few outcome fields or notes the team will actually maintain. Do not build a complicated dashboard before the underlying customer history is reliable. The Measurement & Attribution check explains how to distinguish verified outcomes from assumptions in your reporting.

What should you improve first?

Choose the first repair

Address unresolved service problems before asking for reviews, referrals or another purchase.

  1. If

    Promises do not reach delivery

    Then

    Repair the sales-to-service handoff.

  2. If

    Open issues are invisible or unresolved

    Then

    Establish ownership and close the service loop.

  3. If

    Customers receive irrelevant follow-up

    Then

    Base future contact on their actual needs and preferences.

  4. If

    Satisfied customers have no easy way to share their experience

    Then

    Add a timely, honest review or referral request.

  5. If

    You cannot see post-sale outcomes

    Then

    Record a small set of useful customer events before trying to optimize them.

Review the five customer journeys. Start with the earliest recurring break:

For the renovation contractor, a missing project deadline in the delivery handoff comes before a referral program. For a recurring-service company with reliable delivery but repeated cancellations, understanding why customers leave may be the first useful action.

Your five records are a diagnostic sample. They can expose a broken process; they cannot establish a precise retention rate or prove how much additional revenue a new sequence will create.

Growth can come from relationships you have already earned

The Customer Acquisition Infrastructure (CAI) does not end when someone becomes a customer. The experience after the sale can affect whether they remain, return, expand the relationship, or recommend the business.

Retention & Expansion begins with delivering the original promise. From there, the next action depends on the customer: resolve a problem, provide a useful check-in, support an expected renewal, respond to a new need, invite honest feedback, or simply leave the relationship in a good place.

A strong post-sale system helps the business recognize which of those actions is appropriate and follow through.