How to structure cross-sell offers

List what each customer problem looks like after they buy your main offer. A software customer needs set-up and training. A service customer needs reporting. A retainer customer needs an audit to find the next target. Each of these is a related problem, and each can be a cross-sell.

If you cannot name the problem the customer has, you do not have a cross-sell. You have a product you want to sell.

Look at the customers who stayed longest or grew most. Which second thing did they buy, and when? Run a simple table in a spreadsheet such as Google Sheets or pull it from your CRM: for each product, count how many customers also bought each other product within 90 days.

You are looking for pairs that appear often and early. Those are the cross-sells customers already want. If you have fewer than 30 customers, ask five of them what they wish they had bought together.

Write each cross-sell on one page with these parts:

• Trigger: the event that makes it relevant, such as finishing onboarding or hitting a limit.
• Problem: the customer's own words, from a call or ticket.
• Offer: what they get, in one sentence.
• Proof: a result from one of your own customers in a similar situation, or none at all.
• First step: the smallest version they can say yes to.
• Next action: one clear thing to reply with.

If you have no proof, leave the line out. Do not invent one.

A cross-sell is easier when it starts small. Offer a one-hour working session before a full training programme. Offer a pilot on one team before a company-wide add-on. Offer a short audit before a long retainer.

A small first step lowers the risk for the customer and gives you a better sense of fit. It also fits the customer's budget, which matters more than you think when the main purchase was recent.

Choose the single best match for each account and offer only that. Three suggestions create a menu, and a menu makes people postpone. When the first offer is accepted or declined, move on to the next. Check your expansion opportunities to decide which account to pick first.

Sell each cross-sell as a standalone product first. Once you see which pairs repeat, package them into a bundle. Our chapter on testing new bundle configurations shows how to test that. Bundling too early hides which part customers actually value.

Bring the offer up when the trigger fires, not on a calendar. How to time expansion offers explains the triggers, and how to price expansion and growth covers the number. For the conversation itself, use the framing in how to handle expansion conversations.

A good opening line is: "You mentioned that your team struggles with X. We have a short way to fix that. Would it help if I showed you?" It asks permission and ties to something they said.

• Offering a cross-sell during onboarding, when the customer has not yet seen value from the first purchase.
• Selling the product feature and not the problem.
• Presenting three or four options at once.
• Pairing products because they are easy for you to sell, not because they fit the customer.
• Starting too big, so the first step needs a budget meeting.

You can write the problem, trigger and first step for each cross-sell in one sentence. The share of customers who take a second product rises, measured as an attach rate: customers with a second product divided by customers with a first. Renewals for customers who took a cross-sell are at least as strong as for those who did not. If cross-sell customers churn faster, the offers are wrong for them, so stop and review.