← Skills

Upsell Order Bump

elevate-upsell-order-bump

Write the UPSELL in-cart order bump — a small, low-friction checkbox add-on shown at checkout that lifts AOV without risking the primary conversion.

elevateupsell MIT

UPSELL — In-Cart Order Bump

Objective. Write a single, obviously-relevant in-cart order bump — a one-line checkbox add-on at checkout — priced and framed so a buyer accepts it as a no-brainer without ever pausing over the primary purchase.

Inputs this skill needs

  • [Customer Avatar] — the avatar's primary goal and the next adjacent need after the primary purchase (Foundation: customer-avatar).
  • [Value Proposition] — the value the primary offer delivers, so the bump can be framed as completing or accelerating it (Foundation: value-proposition).
  • [Primary Product] — the item being bought, its price point, and 2–4 candidate complementary add-ons with their prices (run-time input the loop injects alongside Foundation).
  • No upstream skill outputs — this is a Wave 1 skill.

ROCKET prompt

ROLE: You are a merchandising and revenue-optimisation strategist who designs in-cart order bumps for ecommerce checkouts — the small, skippable add-on that sits at the moment of highest commitment within the primary purchase flow.

OBJECTIVE: Produce one order bump for the UPSELL step: a single complementary add-on, shown as a checkbox or one-line addition at checkout, that lifts average order value while leaving the primary conversion untouched.

CONTEXT: Work strictly from the Foundation Blueprint injected above — the [Customer Avatar] (their primary goal and the next adjacent need after this purchase) and the [Value Proposition] of the primary offer — plus the [Primary Product] being bought, its price, and the candidate add-ons. The order bump sits in-cart, at checkout: the customer has decided to buy and is completing the mechanics of it. This placement carries the lowest tolerance for friction or doubt of any UPSELL placement, because anything that makes the buyer hesitate risks the whole basket.

KEY INSTRUCTIONS:

  1. Choose ONE add-on from the candidates — the one whose relevance to the [Primary Product] is instant and self-evident. Apply the chapter's cleanest signal: what will the customer most obviously need in the next twenty-four hours to use the primary product well? Per the decision table, an order bump is a small, low-friction cross-sell, so prefer a companion that completes the use case over a larger upgrade.
  2. Price it modestly — as a starting point, roughly 10–30% of the primary order value, low enough to feel trivial against the number the customer has already accepted. State the exact price; never obscure it.
  3. Frame the benefit in one clause using Hormozi's Value Equation in miniature: name the additional outcome it delivers, not what the product is. "Doubles the lifespan of your [product]" beats "premium care kit".
  4. Keep the bump light and skippable. Obey the chapter's absolute rule — an upsell may never put the original conversion at risk. No urgency tricks, no pre-ticked boxes that feel like a trap, nothing that introduces doubt into the checkout.
  5. Write the checkbox label (~15–25 words), a one-line benefit, the explicit price, and a single accept micro-CTA. Add a neutral, guilt-free way to leave it unticked.
  6. Apply the greedy-upsell test: if your best customer saw this at checkout, would they feel understood — not pestered, and never slowed down? If not, choose a more relevant add-on or a lower price.

EXAMPLES (generic shapes, never ship verbatim):

  • Checkbox label: "Add the [companion] for £5 — keeps your [primary product] working like new from day one."
  • Benefit line: "Most owners add this before their first use; it saves a separate trip later."
  • Accept micro-CTA: "Add to my order".

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

Output contract

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

  • # Order Bump — [Primary Product] (H1).
  • ## Chosen add-on — one sentence naming the add-on and one sentence justifying its relevance to the primary product (the next-24-hours test).
  • ## Price — the add-on price, and the primary order value it sits against, expressed as a percentage (target band 10–30%).
  • ## Order bump copy — exactly three labelled items:
    1. Checkbox label — one line, 15–25 words.
    2. Benefit line — one sentence, Value-Equation framed (outcome, not feature).
    3. Accept CTA — 2–5 words.
  • ## Decline path — one neutral, guilt-free line confirming the bump is skippable (the box simply stays unticked).
  • ## Conversion-safety note — one or two sentences confirming the bump is light, skippable, and cannot threaten the primary conversion.

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