Skip to main content

From customers who came from someone else

How to Collect Switching Story Testimonials

A customer who left a rival for you has the story your prospects most want to hear: what pushed them to look, what nearly stopped them, and whether moving was as painful as they feared. Most never tell it because nobody asks the right questions. Build the request below, tuned to how long ago they switched.

  • Four questions that follow the switch from trigger to result
  • Versions for recent and settled switchers
  • No need for the customer to name the old vendor
Use the free toolGet started free (opens in a new tab)
New message

SubjectHow did the move to Ledgerly go?

Hi Marta,

You moved to Ledgerly recently, and people thinking about the same change always ask us what it is actually like. Would you tell it in your own words?

1. What made you start looking beyond your previous system?

2. What nearly stopped you from switching?

3. How did the move itself go, honestly?

4 ready-to-send versions

Free tool, no sign-upTry it below

The problem, solved

Why switch stories rarely get told

The story exists. The usual request just does not ask for it.

Situation 1 of 5

I do not know who switched

Unless sales logged it, the fact that a customer came from a rival lives only in someone’s memory.

How StoryProof solves it

Add switchers as contacts and keep them in a smart list, so the request goes to everyone who moved, not only the ones you remember.

Switch story request

Ask for the story of the switch

Fill in what you know. Recent switchers remember the move itself; settled ones can speak to whether it was worth it.

When they switched
  1. Request while the move is fresh

    Subject: How did the move to [Ledgerly] go?

    Hi [Marta],

You moved to [Ledgerly] recently, and people thinking about the same change always ask us what it is actually like. Would you tell it in your own words?

1. What made you start looking beyond [your previous system]?
2. What nearly stopped you from switching?
3. How did the move itself go, honestly?
4. What is different now, even this early?

No need to name anyone or criticise anyone. Type it, leave an audio note or record a short video: [your StoryProof link]

Thanks,
[Chris]
  2. Two line nudge after onboarding

    Send after they finish setup, not during it.

    Hi [Marta], now that you are set up on [Ledgerly], would you share what tipped you into switching from [your previous system]? Two lines is plenty: [your StoryProof link]

Your entries fill the templates here in the browser. Nothing is sent or stored.

Prompts

The four beats of a switch story

Each beat answers a different worry a prospect has. Ask for all four, even briefly.

Trigger

  • What was happening that made you start looking?
  • Was there a particular week or event that settled it?

Leave out

  • What was wrong with them?

Doubt

  • What almost kept you where you were?
  • Who in your team needed convincing, and why?

Move

  • How long did the change take in practice?
  • What was harder or easier than you expected?

Leave out

  • Was it easy to switch?

Result

  • What can you do now that you could not before?
  • Would you make the same decision again?

In StoryProof

Run switch story collection in StoryProof

  1. 1

    List your switchers

    Add them as contacts and group them in a smart list by how long ago they moved.

  2. 2

    Build the four beat form

    From Pro, set trigger, doubt, move and result as separate steps. Customers can answer in text, audio or video.

  3. 3

    Send the right version

    Email the recent or settled version of the request with your collection link.

  4. 4

    Review, label and place

    Check each reply for unfair remarks about the old vendor, tag it with where they came from, approve it and choose it for the right widgets.

What happens next: Place the finished stories where prospects compare options. The comparison page guide covers that part.

Before you start

Careful with switch stories

  • Naming the rival needs care

    A quote that names a competitor can raise extra questions. Read the competitor mention page before publishing one that does.

  • Do not coach complaints

    Never suggest criticisms of the old vendor for the customer to repeat. Their reasons, in their words, or nothing.

  • Some switches were rough

    If the move was painful, the honest story says so. That can still be persuasive if the result was worth it.

  • StoryProof does not detect switchers

    Nothing in StoryProof knows which tool a customer used before. You supply that from sales notes or by asking.

  • Recent is not settled

    A month in, the customer can describe the move but not the long term result. Ask again later for that.

FAQ

Questions people ask

Short answers to what usually comes up next.

Do customers have to name the competitor they left?

No. "Our previous tool" tells the story just as well, and it avoids putting the customer in an awkward position with a vendor they may still deal with.

When is the best moment to ask a switcher?

Once setup is finished and they have used you long enough to compare. Ask again after six months or so for the "was it worth it" view.

What if the switch story is mostly about price?

Ask what the lower price let them do, or what they would have kept paying for if they stayed. Price alone is a thin story; what it unlocked is a better one.

Can I combine several switch stories into one?

No. Each testimonial is one customer’s words. Show several separately so prospects see the pattern for themselves.

Still have a question? Ask the StoryProof team or book a demo.

Ask your switchers for the whole story

Set up the four beat form and send it to the customers who came from a competitor.

Get started free (opens in a new tab)

Last updated 2026-11-07.