Start with the outcome sentence
A feature earns its place by doing one of four things: increasing sales, reducing work, preventing mistakes or handing the team a capability it did not have. Your offer has to make that connection clearly enough that the merchant can repeat it to a colleague without you in the room, because that is usually where the decision gets made.
Use one sentence: "For [merchant type], we help [business outcome] by [specific capability], with [proof or credible demonstration]." If the only way to complete it is with words like "powerful" and "all-in-one," it is not finished. Say what changes for the merchant.
For each feature, finish the sentence "This matters because the merchant can now ___." The blank must hold an operating or financial consequence they would recognize. Then name the evidence: a demonstration, a customer result, observable product behavior or an estimate built for that merchant. Match the strength of the claim to the strength of what you have. A capability that works is not evidence for a promised percentage increase in revenue.
The switching equation
The expected benefit has to clear three things at once: the effort of migrating, the financial cost and the operational risk of the change going wrong.
Ask what would actually have to move: data, automated flows, points balances, staff habits, promises already made to customers and every connected system nobody has thought about yet. A simple utility can be swapped in an afternoon. Email marketing and loyalty drag a long tail of dependencies behind them. Even inside one category switching costs vary enormously, and assuming otherwise is how a two-week migration becomes a two-month one.
Build the offer around the actual obstacle
| Obstacle | Possible response |
|---|---|
| Merchant lacks setup time | Assisted setup with clear responsibilities |
| Remaining contract makes switching expensive | A bounded financial incentive |
| Team fears migration failure | Defined migration plan, testing and ownership |
| Value difference is unclear | Demonstration and merchant-specific economics |
| Needed capability is missing | Honest qualification and a product decision |
Write the offer in four fields: the outcome the merchant buys, the product scope, the delivery (setup, support and timing included) and the commercial terms (what is paid, when and under what conditions). Write the summary so it survives being forwarded. Phrases like "setup included" and "no subscription fee" get read generously by someone who was not on the call, so define them before a buyer concludes you promised unlimited service.
Give every incentive an economic ceiling
An incentive can offset a switching cost, accelerate a decision that is already qualified or fund a bounded pilot. Pick the smallest credible version that addresses the obstacle in the way. Whether you record a credit as acquisition cost or a revenue reduction depends on how your business accounts for it. Either way it reduces what the deal is worth. A $200 onboarding credit on a merchant paying $100 a month is two months of that merchant's fee.
| Item | Amount |
|---|---|
| Account MRR | $200 |
| Monthly contribution | $150 |
| Acquisition and onboarding ceiling | $600 |
| Research and sales effort already spent | $250 |
| Estimated setup | $200 |
| Room left for an incentive | $150 |
If the buyer asks for $500, there are two honest answers: change the model or decline.
The arithmetic will not tell you how to negotiate. It stops the final concession from vanishing out of the business case. Set the same boundary on custom work: weigh expected revenue, delivery effort, the support it creates and whether any other merchant will use it. When enough of those answer badly, decline.
Make the switching plan part of the conversation
Separate requirements from preferences as they come up. A missing data capability can stop the deal outright. A cosmetic adjustment can be scheduled later. Both deserve a straight answer, but not the same place in the queue.
Then show a short transition plan: where they are now, where they are going, who owns which piece of work and the point at which they can judge whether it worked. This is often more persuasive than another feature. The feature addresses what they would gain. The plan addresses the cost keeping them where they are.
Answer common objections with useful questions
- "We already use something." Acknowledge the choice rather than arguing with it, state the specific difference that made you reach out, and ask whether a demo is worth their time. The prospect does not have to dislike the incumbent first, and most do not.
- "Switching is too much work." Ask which part is the burden, then match the support to that answer. A discount offered before you know what the work involves leaves the real objection in place, with less margin attached.
- "We need a custom feature." Find the business requirement underneath and what happens without it. Be precise about what works today, what would need building and what you will not promise. A roadmap item is not an available capability.
- "The price is too high." Four problems hide behind it: value, cash timing, comparison with something else and genuine inability to pay. A lower price solves one or two. Find out which one you face before you move.
Define a credible pilot
A pilot needs four things: an outcome, a period, an owner and a decision rule. Remove any one and what remains is a free period, which tends to become an indefinite evaluation nobody formally ends.
Something like: "During the agreed evaluation period we will complete setup, observe the specified workflow, and review the result together on this date." Define what the merchant supplies and how continuation or payment gets decided. Do not call a pilot successful because the app is still installed at the end. Installation is a stage, not a verdict. What counts is the agreed outcome and the commercial decision that follows.
Do this week
- Write a forwardable offer: outcome, scope, delivery, price and three reasons to choose you.
- Set a maximum incentive and a maximum setup commitment, and check them against your acquisition ceiling.
- List what would have to move for your last three switching prospects, and draft a short transition plan.
- Track offer acceptance, incentive cost, onboarding effort, paid conversion and retention by offer.
Questions
How do you convince a Shopify merchant to switch apps?
Show that the expected benefit clears three things at once: the effort of migrating, the financial cost and the operational risk of the change going wrong. Price is the smallest part of the decision. Build the offer around the specific obstacle, and show a short transition plan with clear owners.
How much incentive should I offer a merchant to switch?
Set a ceiling from your own economics: your acquisition and onboarding ceiling, minus effort already spent and estimated setup cost. Offer the smallest credible incentive that addresses the actual obstacle. If the buyer asks for more than the room you have, change the model or decline.
What should a software pilot include?
Four things: an outcome, a period, an owner and a decision rule. Without them it is a free period that can drift into an indefinite evaluation. Judge success on the agreed outcome and the commercial decision, not on whether the app is still installed.
Related guides
Chapter 12: How to run a Shopify app demo that earns a decisionChapter 13: How to keep Shopify app deals moving or close them outNumbers marked as planning examples are arithmetic illustrations, not Shopify benchmarks or promised results. Founder-reported figures are not independently audited. Platform rules change: confirm current requirements with Shopify before you act.