← BUILD LOGDEAL VELOCITY
BUILD LOG · DEAL VELOCITY

Late-stage deals lived in twelve tabs and one rep's memory. I gave them one home.

The quote in one place, the security review in another, the mutual plan in a thread, the approval in someone's inbox. Every handoff is a chance to stall.

Steal this build ↓See the stackThe people part →
>25%
shorter sales cycle, the late stage streamlined
Sub-45 days
SMB and Mid-Market, end to end
Sub-90 days
Enterprise, end to end
12 tabs → 1
the late-stage deal moved out of browser tabs into one hub, and discounts fell with the friction
THE STORY, FROM THE SEAT

Here is one I actually shipped. What happened, what I did, and the stack if you want to run it yourself.

Late-stage deals at most companies live in twelve browser tabs and one rep's memory. The slow part of the deal is the waiting, and the waiting hides in the handoffs.

Every place the deal has to move from one tool or person to the next is a place it goes to sit.

The Sales Operator
Keep Building,
Heath
FOUNDER, THE SALES OPERATOR
THE BUILD IN FIVE MOVES · THE GIANT METHOD
  1. GLate-stage deals lived in twelve tabs and one rep's memory, and the waiting hid in the handoffs.
  2. IA Lovable app became the one home, Salesforce held the record, Aligned opened a room the customer sees, Mixmax drafted the mutual plan.
  3. AThe operator builds the hub, AI drafts the plan and flags the next step, and the rep and customer drive it live.
  4. NThe weekly deal review ran off the hub on the five PLAN questions, so the team pressed on the deal, not the status.
  5. TThe cycle came in more than 25% shorter: sub-45 days SMB and Mid-Market, sub-90 Enterprise, with lower discounts.
RUN THE PLAY YOURSELFThis exact build is a playbook. Run it on your own data.
→
01 / HOW WE APPROACHED THE PROBLEM

Ran the loop.

The build started with the tabs: the quote in one place, the security review in another, the mutual plan in a thread, the approval in someone's inbox. Consolidating the deal into one home killed the tab-hunting, but a shorter cycle does not come from a cleaner record, it comes from a better conversation. So the late stage got walked handoff by handoff, and every place a deal sat waiting got a next step and an owner.

  1. 1
    One home for the deal

    A hub where the proposal, the plan, and the next step lived together, so nothing had to be assembled from twelve tabs before a conversation.

  2. 2
    The customer sees what is next

    Instead of waiting on a forwarded email, the customer could see what happened next, which removed a whole class of stall.

  3. 3
    Map the handoffs, then close each gap

    I walked the late stage handoff by handoff, quote to security review to mutual plan to approval, found where each one sat waiting, and put the next step and its owner in the hub so no stage stalled on someone's inbox.

02 / WHAT IT TOOK CROSS-FUNCTIONALLY

Nobody ships this alone. Here is who had to move.

A deal hub is only neutral ground if every function trusts what is in it. The room argued from one screen because the data discipline and the coaching rhythm behind the screen held.

REVOPS
The CRM fields and stage gates the hub read from.

The hub renders whatever the pipeline data says. Field discipline and stage definitions had to hold upstream, or the one screen would have argued with itself.

SALES LEADERSHIP AND ENABLEMENT
The review rhythm the hub anchored.

The hub surfaces the PLAN gaps; the weekly deal review is where managers coached to them, until the framework was how deals got talked about.

03 / HOW WE TURNED IT INTO A SALES MOTION · THE PEOPLE PART

The hub cut the busywork. The deal review is what actually moved the deal.

One home for every deal killed the tab-hunting. But a shorter cycle does not come from a cleaner record, it comes from a better conversation. The leadership half was turning the weekly pipeline meeting from an activity report into a customer-commitment read, so the team pressed on the deal instead of the status.

THE FRAMEWORK BEHIND IT
PLAN Selling, run as a deal review

Every late-stage deal ran the five questions that predict a close: is the problem in the customer's words, are the priorities lined up to a business driver, is the decision process mapped, is there a real compelling event, is the next step mutual and dated. Score each one. A deal that cannot answer them is not a commit, it is a hope.

  1. 01
    Ran the review off the hub, not the rep's memory

    The hub fed the evidence so the weekly review was about the customer and the commitment, not who remembered what. The conversation got sharper because the facts were already on the table.

  2. 02
    Coached the gap, not the number

    A slipping cycle almost always traces to one weak answer, usually unmapped decision dynamics. I named that one gap per rep and fixed it, instead of asking the whole team to try harder.

  3. 03
    Made 'next step' mean mutual and dated

    Vague next steps became a mutual action plan both sides could see. The deal moved because the customer committed to something too, not just the rep.

Run the deal review →
04 / WHAT I LEARNED

Not proof. Just what the build taught me.

  1. 01
    The waiting hides in the handoffs

    Every place a deal moves from one tool or person to the next is a place it goes to sit. The late stage got walked handoff by handoff to find each one.

  2. 02
    A cleaner record is not a shorter cycle

    The hub cut the busywork, but the speed came from a better conversation: a weekly review about the customer and the commitment, not the status.

  3. 03
    Speed is removing waits, not pressure

    The customer could see what happened next instead of waiting on a forwarded email. Remove the wait, not the patience.

  4. 04
    Next step means mutual and dated

    Vague next steps became a mutual action plan both sides could see. The deal moved because the customer committed to something too.

05 / THE WORKFLOW

The runnable version. Copy it into your stack.

LovableSalesforceAlignedMixmax
[ SALES OPERATOR ]

The Deal Hub

Heath Barnett · Sales Operator
G / Groundthe problem that started all of it, with the receipt and the cost
Deal velocity

The deal lived in twelve tabs and one memory.

Every conversation started with reassembly: the quote here, the security review there, the plan in a thread.

Drag

The waiting hid in the handoffs.

Every place the deal moved from one tool or person to the next was a place it went to sit.

A / Assignthe build, block by block, and who owns each one. Open a step to see it run.
HUMAN + AI, IN THE LOOP
The operator builds the hub; AI drafts the plan and flags the next step; the rep and customer drive it live.
Consolidate
Lovable01
Build one home for the deal
Details
One app where the proposal, the plan, and the next step live together, not a stitch of twelve tabs.
Human
Salesforce02
Centralize the record
Details
The deal record, quote, and approval sit in one place instead of twelve tabs.
AI + human
Expose the next step
Aligned03
Open a sales room the customer sees
Details
A digital sales room the customer sees, with every next step in one place, so no one waits on a forwarded email.
Human
Aligned04
Surface what is outstanding and who owns it
Details
The room flags the next step and its owner so no stage stalls in an inbox.
AI
Move it
Mixmax05
Draft the mutual action plan
Details
The plan and scheduling generated into the flow, not typed by hand.
AI
Mixmax06
Drive the next step live
Details
Rep and customer drive the plan together inside the hub, quote to approval.
Human
N / Normalizethe motion that made it stick
A workflow without a motion is dead. This is how it became the way the team works.
1

The review ran off the hub

The hub fed the evidence, so the weekly review was about the customer and the commitment, not who remembered what.

2

One gap per rep, named and fixed

A slipping cycle almost always traced to one weak answer, usually unmapped decision dynamics. That one gap got named and fixed instead of asking the whole team to try harder.

3

Every late-stage deal ran the PLAN questions

Five questions that predict a close, scored. A deal that cannot answer them is not a commit, it is a hope.

T / Tie backthe result it drove, and how they know
RESULT · 01

Sub-45 days

SMB and Mid-Market, end to end.

RESULT · 02

Sub-90 days

Enterprise, end to end.

RESULT · 03

25%+ shorter cycle

the late stage streamlined.

OUTPUT · 01

The deal hub

Proposal, plan, and next step in one app.

OUTPUT · 02

Customer sales room

A shared view of what happens next.

OUTPUT · 03

Mutual action plan

Each handoff mapped with its owner.

The Sales Operator
06 / HOW YOU DO IT TOO

Here is what I built. Here is how you build it.

The whole thing installs as one plugin. Or grab the skills a la carte. Everything on this page, runnable, on what you paste today.

✓ EVAL PASS · 4/4
THE PLAYBOOK · ONE INSTALL
Run a deal from discovery to signature

5 skills chained into one runnable play. Installs as a single plugin, no copy-pasting each skill. It runs on what you paste; connect your stack to go live.

SEE THE FULL PLAYBOOK →
SEE IT RUN IN CLAUDE
EXAMPLE CHATSam, an AE, running the loop in one sitting
S
I just wrapped my first discovery call with a 400-person logistics company. Can you score where the deal actually stands?
S
Step 1· Discovery Framework
Ran the call against your qualification framework, filled in what we confirmed, and flagged the gaps. We have the pain and the metric but no confirmed economic buyer yet, and the champion is unproven.
strongpain, metric
gapEB, paper
Receipt
Scorecard filled: 5 of 8 fields solid, economic buyer and paper process still open.
S
They want a demo next week. Help me build one that hits what they told me, not the usual tour.
S
Step 2· Demo Script
Mapped every screen to a problem they actually said out loud on the call, and cut the three features that don't connect to anything they raised. Each beat has a clear 'so what' tied to their metric.
Receipt
6-beat demo mapped to 4 stated problems, 3 unrelated features cut.
S
They liked the demo. Now their VP wants numbers. Can you put together a business case?
S
Step 3· Business Case
Framed the cost of the problem in their own numbers, the value of fixing it, and the risk of doing nothing. Kept every assumption visible so their finance person can check the math.
Receipt
One-page case: problem costing ~$480K/yr, payback under 5 months, assumptions flagged.
S
This is getting real. I want a clear path to signature with the champion. Build the plan.
S
Step 4· Mutual Action Plan
Worked backward from a target signature date and laid out every milestone, owner, and exit criterion. Wrote it so I can send it straight to the champion and we agree on the path together.
Receipt
MAP with 7 milestones and dates, backward from a signature target 6 weeks out.
S
Procurement is about to push on price. How do I prep for that conversation?
S
Step 5· Negotiation Prep
Set your target and walk-away, built a concession ladder so you never give margin for free, and mapped their likely asks with a hold for each. Kept the discount tied to term and volume, not just handed over.
floor12% max
tradeterm + logos
Receipt
Negotiation plan with a 12% floor and 3 trade-for-concession moves, deal on track to close this quarter.
THE SKILLS IT USES
Get a straight verdict on every open deal.
deal-health-analyst
Read the whole relationship at a glance.
conversation-analyst
Turn raw account notes into a one-page brief, every time.
account-brief-prompt
THE OTHER HALF · LEAD THE TEAM
Run the deal review→
I write up one of these a week. Free, receipts only.
RELATED BUILDS
The Love Test
My reps averaged about 2 touches, all reactive to inbound
Reporting That Drove Action
One weekly read that drove sales and CS, not a rear-view deck
THE MARKET ON THIS
The craft behind it: PLAN Selling and the Deal Review (PLAN Selling)Top reasons deals get stuck, and how to treat it (Gong)Deal velocity 101 (Consensus)The sales team guide to using mutual action plans (Salesforce)