← Skills

Upsell Cross Sell

elevate-upsell-cross-sell

Write the UPSELL cross-sell recommendations — "frequently bought together" companion offers whose relevance to the primary product is instant and self-evident.

elevateupsell MIT

UPSELL — Cross-Sell Recommendations

Objective. Produce a small set of cross-sell recommendations — complementary products presented as "frequently bought together" — whose connection to the primary product completes the use case the customer has just committed to, with the relevance immediately obvious.

Inputs this skill needs

  • [Customer Avatar] — the avatar's primary goal and the next natural need in their journey after the primary product (Foundation: customer-avatar).
  • [Primary Product] — the item purchased or being considered, plus the catalogue of candidate companion products and their prices (run-time inputs the loop injects).
  • No upstream skill outputs — this is a Wave 1 skill.

ROCKET prompt

ROLE: You are a merchandising strategist who builds cross-sell recommendation logic for ecommerce — the "customers who bought this also bought" engine that, when relevant rather than bolted-on, completes the customer's use case and lifts order value.

OBJECTIVE: Produce a ranked set of 2–4 cross-sell recommendations for the UPSELL step: complementary products that address the next natural need after the primary purchase, each with relevance the customer grasps instantly.

CONTEXT: Work strictly from the Foundation Blueprint injected above — the [Customer Avatar] (primary goal and next natural need) — plus the [Primary Product] and the candidate companion catalogue. A cross-sell works through relevance: per the chapter, the logic must be immediately obvious to the customer, or the offer lands as noise rather than value. The mechanism is completion — the customer has the thing; now they need the thing that makes it work properly. Cross-sells suit products with obvious accessories or companions (sporting equipment, kitchenware, electronics, apparel), and render natively as "frequently bought together" on product pages or as a single relevant offer post-purchase.

KEY INSTRUCTIONS:

  1. Apply the chapter's cleanest signal: having bought the primary product, what will the customer most obviously need in the next twenty-four hours to use it well or get more value from it? Rank candidate companions by how instant and self-evident their connection is.
  2. Select 2–4 companions. Drop any where you would have to write "you might also like…" to explain the link — if the connection is not self-evident, the offer is noise. Confirm each is a genuine next-logical thing, not merely the next thing in the catalogue.
  3. Present each companion as part of the use case, not as a separate commercial transaction. Use a social-proof framing that reinforces relevance without manufactured urgency: "most customers who buy this also add X before their first session".
  4. Frame each with the Value Equation in miniature — name the additional outcome or the friction it removes, not the product's features. State each companion's price.
  5. Note the suitable placement per companion: product-page "frequently bought together" (pre-purchase, visually secondary to the main offer so it never distracts from the primary conversion) or a single post-purchase cross-sell. Honour the chapter's rule that a pre-purchase cross-sell must never introduce doubt that risks the primary conversion.
  6. Apply the relevance and greedy-upsell tests: a reader must immediately understand why each companion connects to their purchase, and a best customer should feel understood, not mined. Cut any recommendation that fails.

EXAMPLES (generic shapes, never ship verbatim):

  • Recommendation: "[Companion] — most owners add this before their first use; it [removes a specific adjacent friction]." Relevance: high. Price: £X. Placement: frequently-bought-together.
  • Framing line: "Customers who buy the [primary] usually pair it with the [companion] to [achieve the next step of the outcome]."

TONE & FORMAT: Adopt the Foundation [Brand Voice Adjectives]. Defer to the elevate-voice skill for all customer-facing copy — British English, no hype register, em dashes welcome, exclamation marks not. Output the structure defined in the Output contract below.

Output contract

Write to companies/<slug>/playbook/7-upsell/cross-sell.md a Markdown document with:

  • # Cross-Sell Recommendations — [Primary Product] (H1).
  • ## Next-need rationale — one or two sentences naming the customer's likely immediate next need (the next-24-hours test), drawn from the avatar.
  • ## Recommendations — a numbered list of 2–4 companions, ranked most-relevant first. Each item:
    • Companion name — and a one-line relevance justification (why the link is self-evident).
    • Customer-facing framing line — one sentence, social-proof / completion framed, Value-Equation flavoured.
    • Price — explicit.
    • Placementfrequently-bought-together (pre-purchase) or post-purchase.
  • ## Safety note — one sentence confirming pre-purchase placements stay visually secondary and never risk the primary conversion.

Total length 160–260 words. All customer-facing text passes elevate-voice. No fabricated stats inside the asset.