Use case · Incumbent displacement brief
Show where the incumbent falls short,
in their customers' own words
Displacement is an evidence problem. AnyCRM reads the public record for what the current provider is failing at, checks when each complaint was written, and hands you the failures that have survived every fix.
- Read for what the vendor fails at
- Split by date, not by sentiment
- Quotes you can read out loud
Prospecting
Sample dataOpen
AnyCRM. Prospecting.
The reading
Public reviews, read against the incumbent, the same corpus, a different question. Wait times on disruption days, largest theme. Refund handling, second theme. Agents cannot see the booking, third theme Every theme here is something a support operation owns, which is what makes it a displacement story rather than a product complaint.
Their words
The line you can read out loud, quoted, never paraphrased. "Forty minutes on hold to be told the person who can refund me works days." Public review, March Coverage hours. Agent authority. Matches your service lines
Risk
The worst of this predates their vendor change. Two thirds of the wait-time reviews were written before a supplier announcement last autumn. Walking in with them is walking in with a problem somebody else already solved. Timing.
Your call
Three moves offered: Rebuild the brief on reviews since the change; Show both windows and let them explain the gap; Lead on refund handling, which has not improved. The brief is rewritten to whichever you choose.
Resolved
Brief rebuilt on the recent window, Themes recounted, quotes replaced. Refund handling still the standing failure, Unchanged across both windows. Nothing in the brief is older than the thing it criticises. Recent window only. Every claim quotable.
Deliverables
Displacement brief, Themes, dates, quotes and the service line for each. Meeting deck, Built on the refund and coverage story. First email, Opens on their customers, not on your logo. Filed on Halden Rail, activity logged, the brief dated to the recent window.
Close
Displacement is an evidence problem.
Halden Rail, whose passengers have a great deal to say in public about a support operation somebody else runs.
How it works
Four steps, and none of them is typing.
- 1
Same reviews, a different question.
Halden Rail
SampleWait times on disruption days
largest theme
Refund handling
second theme
Agents cannot see the booking
third theme
Every theme here is something a support operation owns, which is what makes it a displacement story rather than a product complaint.
Public reviews are read for what a support operation owns: waiting, authority, coverage, handoffs. A complaint about the product is not a displacement story, so it does not go in the brief.
- 2
Themes with quotes, not adjectives.
Halden Rail
Sample“Forty minutes on hold to be told the person who can refund me works days.”
Public review, March
Coverage hoursAgent authorityMatches your service linesEach theme carries the lines customers actually wrote, so the brief contains sentences you can read out loud in a meeting rather than a summary of a mood.
- 3
Dates checked, before the meeting.
Halden Rail
SampleThe worst of this predates their vendor change.
TimingWhen most of a theme predates a supplier change, walking in with it is walking in with a solved problem. The split is shown and the moves are offered: rebuild on the recent window, show both windows, or lead on the failure that never improved.
- 4
It leaves as a meeting pack.
Documents
SampleDisplacement brief
Themes, dates, quotes and the service line for each
Meeting deck
Built on the refund and coverage story
Filed on the account
The brief, a deck built on the surviving failure, and a first email written to a named person, filed on the account with the activity logged.
The risk beat
When something turns, it tells you and shows you the moves.
Here the turn is: The worst of this predates their vendor change. Three moves were offered and a person took one: rebuild the brief on reviews since the change.
Risk beat · AnyCRM AI
Sample data- 1
Detection
The worst of this predates their vendor change.
- 2
Explanation
Two thirds of the wait-time reviews were written before a supplier announcement last autumn. Walking in with them is walking in with a problem somebody else already solved.
TimingSplit by date, not by sentiment - 3
Options
- Rebuild the brief on reviews since the change
- Show both windows and let them explain the gap
- Lead on refund handling, which has not improved
- 4
Human choice
Rebuild the brief on reviews since the changeA person presses one. Nothing is sent or written until then.
- 5
Resolution
Nothing in the brief is older than the thing it criticises.
The meeting cannot be lost to a date, because every line in the pack came from after the change the incumbent will point at.
Recent window onlyEvery claim quotable
Where the answers come from
The record you already have.
The people who deal with the incumbent every day have already written it down in public. The work is reading it against the right question and checking when they wrote it.
Public review sites
Where customers describe the service they receive
Forums and app stores
The unfiltered version of the same complaints
Complaint dates
So a supplier change cannot undercut the pitch
The output
The displacement brief
Every line points back at one of these.
Your service lines
Each theme mapped to something you can actually run
Public signals on the account
Hiring and announcements, for timing
The account record
What you already hold on them: contacts, past calls, an earlier bid
What you receive
Documents, not a dashboard.
A brief where every claim has a quote and a date behind it, a deck built on the failure that has not been fixed, and a first email that opens on their customers.
See the full Sales Leaders pageThe displacement brief
The displacement brief
Themes, dates, quotes and the service line for each
- XLSX
Theme workbook
Every review counted by theme and by window
- PPTX
A meeting deck
A meeting deck
Built on the failure that has not been fixed
The first email
ToThe first email
Opens on their customers, not on your capabilities
Why BPOs need this
What we heard, in their words.
The problem
We tell them the incumbent is weak. They ask us where.
A sales director
The problem
Our evidence turned out to be about a provider they replaced.
A bid manager
The problem
The first meeting is spent proving we did any homework at all.
A head of growth
Questions
The honest answers.
Does it name the incumbent?
The brief describes what is failing and quotes the customers saying so. It is built for your team, and it is not published anywhere.
Why does the date matter so much?
Because the first thing a buyer says is that the problem was fixed when they changed supplier. Splitting the reading by date means the brief cannot be dismissed on timing.
Where do the reviews come from?
Public review sites, forums and the app stores. Nothing is bought and nothing is taken from behind a login.
What if nothing has survived the change?
Then the brief says so. A displacement story with no current evidence is worth knowing before the meeting, not during it.
Give your team the unfair advantage.
Full deal intelligence from day one. No credit card required.