Explain pipeline changes
Compare the pipeline between any 2 dates and see which deals were added, pushed, won or lost.
Ways to get this done with Avoma
Pick the approach that fits how your team works. You can start with one and add another later.
How this works
Shown for:
- 1Trigger
On demand, for a selected reporting period
- 2Context
Avoma Revenue Intelligence reads pipeline snapshots, deal amounts, close dates, and deal status
- 3Reason
Sort every change between the 2 dates into added, pulled in, pushed, won, lost or changed value
- 4Act
Show the pipeline walk with the deals behind each movement
- 5Human judgment
Manager or RevOps explains the movement in the forecast call
Native feature
Understand how pipeline value changed between two snapshots by seeing opportunities added, pulled forward, pushed out, won, lost, or changed in value.
What good looks like
A pipeline walk answers "what changed?" before the forecast call asks it.
Use the same dates every week
Consistent windows make week-over-week trends readable.
Explain the biggest movements first
A few large deals tend to drive most of the change.
Separate new pipeline from moved pipeline
Growth from new deals and growth from pulled-in deals tell different stories.
Customer stories
What teams say
I was able to start using Avoma for pipeline reviews with my team right away. It was more convenient than our previous process.
It helps managers identify opportunities and churn risks by looking at a single report instead of having to sit in on additional meetings.
What’s stopping you from turning every conversation into actionable work?
