Most revenue intelligence starts listening when a salesperson joins the call. Verspa’s starts when the buyer arrives. Every demo and every reply lands on the deal, every deal has an AI agent reading the people on it, and every next step becomes a task on the right desk. So when a buyer comes back, the demo already knows the deal, and you know which deals are real.

Welcome back, Sofia. Last time you asked how eliminations work across your three entities, so let’s start there, then go through the approvals your proposal covers.
Its running orderShown with Marlow, an example finance platform. Choose a buyer, then before or after the demo.
There is nothing to migrate. Your team keeps working in the CRM it already uses. Verspa reads every deal, owner and task from it, and its own work goes back the other way: tasks and the moment they are done, each demo’s result, and every email, message and booking.

Most pipelines track what someone logged. Verspa’s tracks what the buyers did: every email, call, meeting, social media message, web chat and AI buyer aware demo from everyone on the deal. Each risk arrives with the click that fixes it, and you can move a stage, add a note or set the next step right from the board, or ask Verspa to.
Choose a deal to see its people and risks, then fix one
Every contact and company in Verspa has an AI agent. So does every deal. Whenever the stage moves, someone joins or a note lands, it reads the deal and what each person’s AI agent thinks of them, then writes down where the deal really is, the biggest risk and the next move. Quiet deals are reread on a schedule, so a stall is noticed while there is still time, and what it finds goes into the Roundup.
See the AI agents behind every person
Further on than its stage says. Sofia has taken two demos and brought in Daniel, who holds the budget, and today Daniel booked a call with Sam.
Choose a deal to read what its AI agent wrote
No separate revenue intelligence tool, and no forecast rebuilt in a spreadsheet the night before the call. Won plus commit is the number you defend, every period is measured against your targets, and Verspa writes the read for you, checked claim by claim against the numbers. Board mode puts the same page in front of the board.
Q3 lands at £612,000 if Commit holds: 82% of target, £138,000 short.
Pull Thornbury into Commit · ask Sofia for the signing date
Checked against these numbers, claim by claimChoose a period or a desk, or open Board mode
Set a target for each desk, quarter by quarter, so a new starter can ramp. Quarters follow your own financial year, so if yours starts in April, so does Q1. The floor adds every desk up, people and AI desks alike, and the forecast shows each one’s pace against its own number.

A revenue target per desk, set period by period so a desk can ramp. The floor is the sum.
| Desk | Q1 | Q2 | Q3 | Q4 |
|---|---|---|---|---|
| Sam CarterPerson | ||||
| Rhea KapoorPerson · joined in April | ||||
| EllisAI desk | ||||
| The floorEvery desk | £480,000 | £615,000 | £750,000 | £840,000 |
Change a target, or the month your year starts

A task list is only as good as what goes into it, so Verspa fills yours. It raises what it thinks you should act on, with the action attached. The demo leaves what a buyer asked for, plays and AI desks add their own, and your team adds anything, for any person, company or deal. The urgent ones wait for you in the Tray.
Group by source or action, open a task, then close it
Tasks from your CRM come in. Tasks made in Verspa go out. And a task can close itself: give it the events that finish it, a reply, a booking, a demo started, and the moment the buyer does one, it is done, in Verspa and in your CRM.
In the demo, Daniel asks for a customer with three or more entities.
The task lands with the desk that owns Daniel, due Friday, set to close when Daniel replies.
It is on Daniel’s record in your CRM, where Sam can see it and work it.
Sam emails Daniel two references from the same industry.
Daniel replies, and the task closes itself, in Verspa and in your CRM.
No. A demo never creates a deal, moves a stage or sets an amount. It counts as a touch on every deal the buyer is on, so the deal shows when they last spoke to you, and Verspa adds what they asked for as notes and tasks. A deal is made by your team, by Verspa when you approve it, by an import from your CRM or when a buyer accepts a quote.
Keep the tool you have if it works for you. Verspa still brings your deals in, so every AI buyer aware demo and every follow up knows where the buyer stands. If you do not have one, Verspa’s forecast, targets and deal reads give you a number to run the quarter on, without another tool.
You decide. Set a deal’s forecast category and it stays where you put it. Where you have not, the stage decides: 80 percent or more is Commit, and 50 percent or more is Best case. The forecast leads with won plus commit, and a deal past its close date sits in its own group, so nothing is counted quietly.
Yes. Choose MEDDIC, MEDDPICC, BANT, SPIN, GAP or CHAMP, or build your own fields, and every deal gets a qualification tab. Any gaps show on the deal as a named risk, with the fields still to fill.
Anyone working the deal, and Verspa itself. Your team adds tasks for any person, company or deal. Verspa raises the ones it thinks you should act on, with the action attached, and the AI buyer aware demo, the web chat, plays, Wire rules and AI desks add their own. Tasks in your CRM come in too, and tasks made in Verspa go back.
Each desk sees its own. The floor shows the whole workspace, desk by desk, for the people who run it, and a member can only see or delete the deals on their own desk.
