Switching Cost Message Brief
Explain the real work of adopting your software, supported transition options and unresolved limits without promising an effortless migration.
Read this resource as Markdown
When to use this template
Use this after interviews or task observations reveal what a buyer would need to change. Connect each transition concern to a demonstrated option, a documented limitation or an unresolved question.
Choose another approach when: You have not tested the proposed transition, want to claim migration takes minutes from one friendly attempt, or intend to describe an unsupported import as an available feature.
Gather these inputs
- Recent accounts or observations of the task, setup effort and people affected.
- Verified import, export, preview or manual setup options for the exact product version.
- Known limits and the person responsible for keeping the public explanation accurate.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
Fictional example: designers considering Handoff Notes worry about moving every old project. A tested pilot can create a new text checklist, but cannot import an archive from other tools. The founder’s explanation says: “Try one new handoff using sample notes. Existing projects stay in your current tool. This pilot does not import previous checklists.” The founder describes only the demonstrated pilot flow and its access restrictions. An interviewee’s estimate of their own archive work stays a single account. It does not become “migrate everything in five minutes”. A designer whose existing shared document is sufficient can keep using it; the message explains an option without inventing a switching problem.
How to use it
- Separate the buyer’s observed concerns from your assumptions about why they hesitate.
- Check each proposed transition step against the actual product and its limitations.
- Write a bounded explanation, then ask relevant readers what work they expect to do.
Check before using it
- The message does not equate a sample evaluation with a full migration.
- Time and compatibility claims are supported within their stated conditions.
- An available manual step is not advertised as automatic import or guaranteed onboarding.
What to measure
Compare the effort buyers expected with the effort observed in actual transitions. Record confusion, unsupported expectations and tasks that still require help. These observations can improve an explanation; they do not establish a universal migration time or conversion effect.
Research and sources
Intercom discusses adoption effort, habits and uncertainty in onboarding. The message brief is an original editorial application. Its example does not adopt the article’s performance assertions, endorse a migration service or guarantee that clearer copy causes adoption.
- Intercom: Improve your user onboarding with Jobs-to-be-Done insights — checked 2026-10-24. 2020 practitioner discussion of adoption effort, habits and uncertainty. Product examples and performance assertions are not adopted.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.