The deal loop

The deal loop is the part of Revyn that touches real work. It exists so that practice is never abstract: you prepare for a specific meeting, practise against that prospect, run the call, and feed what happened back in.

#Prep queue

Prep lists the meetings you should prepare for. With a calendar connected (Google or Outlook, under Settings → Connections), upcoming meetings with external attendees appear automatically; you can also add a prep manually.

Open a prep and Revyn assembles a prep sheet: the company (from research), the people (from the invite and your CRM), the deal's MEDDPICC state, open trackers, what was said on the last call, and three suggested opening lines. From the prep sheet you can start a practice call against that prospect with one click.

The prep calendar shows the month with prep status per meeting: not started, drafted, practised.

#Deals

Deals is a board of your open opportunities, by stage, with drag-and-drop between columns. Each deal carries its stage, value, next step, the prospect profile, and a timeline of every event: calls (practice and real), prep, Ask Revyn sessions that referenced it, CRM updates.

With a CRM connected, deals sync in both directions; see Integrations. Without one, create deals by hand or let Revyn draft one from a prep.

#Qualification

Qualification is the MEDDPICC view across deals. For every deal it shows which of the eight fields are uncovered, partial or missed, with the transcript line that established each. It is the same engine that scores calls, applied to the deal as a whole: the union of everything learned across every call on it.

Managers use it to see which deals are moving on hope. Reps use it as the list of questions to ask next.

#Trackers

A tracker is a phrase or topic counted across your calls: a competitor's name, "budget", "security review", "not this quarter". Trackers run on practice calls and imported real calls. Each tracker shows a count, a trend, and the calls it fired on, so "we lose when procurement is mentioned late" becomes a chart instead of a hunch. Archived trackers can be restored.

#Objection intelligence (org)

Objections raised on calls are mined into a library with counts, the deals they appeared on, and the win rate when they appeared. A manager can promote an objection into the knowledge base with the approved response, and into drafted scenarios so the team practises it.

#Outcomes and the loop

When a deal closes, mark it won or lost, or let the CRM do it. Outcomes feed the org analytics that connect practice to revenue: readiness to outcome, objection to loss, skill to revenue. See Analytics. Self-reported outcomes are never overwritten by a CRM sync; if the two disagree, both are kept and the CRM's is marked as such.

#The loop, end to end

1. A meeting lands on your calendar; a prep appears.
2. You read the prep sheet and practise against the prospect.
3. You run the real call; if it is recorded, you import it.
4. The debrief updates the deal's MEDDPICC state and trackers.
5. Ask Revyn drafts the follow-up from the debrief.
6. The deal moves; the outcome, eventually, feeds the analytics.