Skip to content
Get a free quoteGet a quote
Published
Byline
GoHighLevel Partners Editorial

A decline answers a specific proposition, not everything you sell — the branch should depend on which part the buyer was refusing.

Downsell step logic: what to offer after someone says no

A downsell is the step that runs when a buyer declines an offer, replacing it with something smaller rather than ending the sequence. It exists because “no” is usually an answer to a specific proposition — this much, this commitment, this now — and not a refusal of everything you sell.

The logic behind it is where most implementations go wrong. A downsell that simply repeats the offer at a lower price teaches buyers to decline first, and one that appears regardless of what the buyer did reads as pestering. What makes the step work is that the branch depends on the actual reason for the decline, as far as you can infer it.

The three things a decline can mean

Reason The right downsell The wrong one
Too expensive right now The same thing in instalments, or a smaller scope at a lower price A discount on the identical item, which devalues the original price
Too much commitment A shorter term, a single unit, or a trial The same commitment with a sweetener attached
Not the right thing A different product, or nothing at all Any variation of the thing they did not want

You rarely know which of these applies, which is why the offer selection has to be driven by whatever evidence you do have: what they originally bought, what they looked at, what they answered on the form. A downsell chosen from the buyer’s own behaviour outperforms one chosen from a template, and it does not train anyone to decline.

Where the step sits in the sequence

A typical purchase path has a main offer, an optional add-on at checkout, one or two post-purchase offers, and a downsell branch hanging off each decline. The add-on at checkout is a different mechanism and follows different rules — where an order bump belongs covers why it belongs before payment rather than after.

The important structural rule is that a downsell follows a decline, not a purchase. Presenting a cheaper version to someone who has just accepted the expensive one produces regret and refund requests. Wire the branch to the decline path explicitly rather than to “next step”, which is the default in most builders and the most common cause of the wrong page appearing.

Limit the depth. One downsell after a decline is a reasonable second attempt; a chain of three is a maze, and the completion rate of the whole funnel falls because buyers stop trusting that they have finished. If a buyer declines the downsell, take them to the thank-you page and let the follow-up sequence do the rest.

Pricing the downsell without damaging the main offer

The risk in every downsell is that it makes the original price look negotiable. Three approaches avoid that:

  • Reduce the scope, not the price of the same thing. Fewer sessions, one module, a shorter term. The buyer gets less, so the original price stays coherent.
  • Change the payment shape. The same product in instalments addresses affordability without discounting — with the caveat that instalment plans fail quietly when cards expire, which is what recurring payments and failed cards is about.
  • Offer a lower tier that already exists. If your product has a published entry level, routing a decline there is honest and repeatable — the structural version of free and paid access tiers.

Where a genuine discount is the right answer, make it conditional and enforced by the system rather than by intention: limited in time, limited in use, tied to the decline. The mechanics are in coupon types, limits and traps; the most common trap is a code that escapes into general circulation and quietly becomes your standard price.

The page still has to sell

A downsell page is often built as an afterthought — a headline, a price and a button — which is why so many convert poorly. It is a second offer to someone who has just declined, so it has more to overcome, not less. It needs to say what this is, why it is different from what they turned down, and what they get, with the same clarity as product detail page structure or what an offer page has to answer.

Two practical points. Make the decline option visible and plainly worded; a page where the only obvious action is “yes” produces accidental purchases and the refunds that follow. And check the page on a phone, since offer pages built in a hurry are the ones most likely to reorder badly, as how a phone stacks your columns describes.

Terms, and what the buyer actually agreed to

Anything added after the original agreement needs its own consent and its own terms — a subscription introduced at a downsell step is a different commitment from the one-off purchase the buyer authorised. what a consent record has to contain sets out what the record has to contain, and this is precisely the situation where a thin record causes trouble later. Where the downsell is a trial rather than a purchase, the boundary conditions matter more than the offer, which is the ground in how a product trial is run.

Test the branch, then measure the whole funnel

Downsell logic is conditional, and conditional paths are the ones that break silently. Walk the decline path end to end with a real transaction before publishing, and repeat it after any change to the funnel — configuration of this kind is among the things that does not always survive being copied between accounts, as what moves and what breaks on import notes.

Then judge it on the whole sequence rather than on the step. A downsell that converts well while total revenue per buyer falls is cannibalising the main offer, and that only becomes visible when you measure the path as a series of transitions, which is the approach in measuring conversion by stage. Refund rate belongs in the same view: a downsell accepted under confusion shows up there rather than in the conversion figure. Where two versions of the step are plausible, run them against each other properly, as split testing describes, and give the comparison enough volume to mean something.

See also: Move Step Between Funnels: Order, Paths and Attachments

Frequently Asked Questions

What is a downsell step?

The branch that runs when a buyer declines an offer, presenting something smaller instead of ending the sequence. It exists because a decline is usually an answer to a specific proposition — this price, this commitment, this moment — rather than a refusal of everything you sell.

Should a downsell just be the same product at a lower price?

No. Discounting the identical item makes the original price look negotiable and teaches buyers to decline first. Reduce the scope instead, change the payment shape, or route the decline to a lower tier that already exists in your product range.

Should a downsell follow a purchase?

Never. Presenting a cheaper version to someone who has just accepted the more expensive one produces regret and refund requests. Wire the branch explicitly to the decline path rather than to ‘next step’, which is the builder default and the usual cause of the wrong page appearing.

How many downsells should a funnel have?

One after a decline is a reasonable second attempt. A chain of three becomes a maze and lowers completion for the whole funnel, because buyers stop trusting that they have finished. After a declined downsell, go to the thank-you page and let the follow-up sequence do the rest.

Does a downsell need its own terms?

Yes, where it changes the commitment. A subscription introduced at a downsell step is a different obligation from the one-off purchase the buyer originally authorised, so it needs its own agreement and its own record of what was accepted.

How should downsell performance be judged?

On the whole sequence, not the step. A downsell that converts well while total revenue per buyer falls is cannibalising the main offer. Track refund rate in the same view, since a purchase accepted under confusion appears there rather than in the conversion figure.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

  • Setup (one-time)$850
  • Ongoing (per month)$38.80
Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.

Leave a Reply

Your email address will not be published. Required fields are marked *

$850 setup, $38.80/mo ongoingGet a quote