Deal Ownership State Machine: One State Per Open Deal
Stages tell you where a deal has been. Ownership state tells you whether it is moving and who has to move it next.
Published 2026-11-09 · Market & data intelligence · Educational, not advice.
Stages show how far a deal has traveled, not who owes the next move. An ownership state machine puts every open deal in exactly one of four states: seller owes, buyer owes, mutual commitment scheduled, or unowned. The real signal is a deal moving from one state to another, especially into unowned. Count state changes, not activity, and run reviews by whose turn it is.
Why stages are not enough
Most CRMs describe a deal by its stage: discovery, demo, proposal, negotiation. Stages tell you how far a deal has traveled. They do not tell you whether it is moving today, or who is supposed to move it.
A deal can sit in Proposal for six weeks and look exactly like one that entered Proposal yesterday. The stage field is a record of where the deal has been. A pipeline review needs to know where the next move comes from.
An ownership state machine gives you that. It sits alongside your stages, not in place of them, and it answers one question for every open deal: whose turn is it?
The four states
At any moment, every open deal is in exactly one of these states. Not two, and not somewhere in between.
1. Seller owes the move
The ball is with your team. A proposal needs drafting, a question needs answering, or a pricing approval needs chasing internally. The deal is waiting on you, and you pay for every hour it waits.
2. Buyer owes the move
You have delivered what you promised, and the next step belongs to the buyer: a signature, an internal review, a reply with stakeholder names. This state only counts if a specific action and a date are attached. “They are thinking about it” is not a buyer-owned state. It is an early sign of the fourth one.
3. Mutual commitment on the calendar
Both sides have agreed to a next event at a set time: a call, a review session, a site visit. Neither side owes a move before then, but the deal has a next checkpoint on the calendar.
4. Unowned
Nobody owes anything, and nothing is scheduled. The last touch was a while ago, the next-step field is blank or out of date, and nobody can say for sure whose turn it is. Deals die quietly here, often while still showing a healthy stage and close date.
Won and lost are ways out of the machine, not states inside it.
Why exactly one
The rule that a deal has only one state is what makes the model work. If a deal can be in two states at once, the model goes back to guesswork. “We are waiting on them, but we also need to send the revised terms” means the deal is seller-owned. Your open action is the one that matters, because it is the one you control.
A simple tiebreak rule keeps classification honest. If the seller owes anything, the deal is seller-owned. Only when your side has nothing outstanding can it be buyer-owned or mutual. If neither side can name the next move and a date, the deal is unowned, whatever the stage says.
Transitions are the signal
What makes a state machine useful is its transitions, the moments a deal moves from one state to another. This is where the Delta Arc view applies: measure the change, then turn it into direction.
- Seller-owned to buyer-owned is progress. Your team delivered, and the next move passed to the buyer.
- Buyer-owned to mutual is progress. The buyer responded and committed time.
- Any state to unowned is the transition to watch. It is the moment a deal stops moving, and it is easy to miss.
- Seller-owned for too long is not a transition at all, which is the problem. Time spent sitting in a seller-owned state is delay your own team caused.
The useful metrics follow directly: how long deals stay in each state, how often they slip into unowned, and how quickly a rep pulls them back out.
Activity is not ownership
This model deliberately ignores raw activity counts. A rep logging a hundred calls a week tells you about effort, not whether any particular deal has a next move. A buyer sending ten emails might be engaged, or might be a stakeholder going in circles without the authority to decide.
What matters is whether each touch changed the state. An email that turns an unowned deal into a scheduled review is worth more than a dozen check-ins that leave it unowned. Count changes in state, not touches.
Running it in a pipeline review
The practical version is simple enough to run on a whiteboard.
- Sort by state, not by stage. Start with unowned deals. Each one needs a decision: re-engage with a specific ask, or close it out.
- Then seller-owned. Each one should have a named person and a date. If it has neither, assign them before the meeting ends.
- Then buyer-owned. Confirm the ask is specific and has a date. Vague waiting gets moved to unowned.
- Mutual last. These are the healthiest. Confirm the event is real and on both calendars.
The meeting should not end with a forecast adjustment. It should end with a list of named owners and next moves. That list is what changes the forecast later.
The hard part is keeping states current between reviews, because most CRMs do not record whose turn it is. Delta Arc CRM Intelligence is built to infer each deal's ownership state from the activity already in a team's existing CRM, and to flag slides into unowned between reviews.
What comes next
Once every deal has exactly one state, the next question is how long is too long in each. The right time limits differ by state and by deal size, and setting them well takes its own care. The next Pulse picks up there.
Sources
This explainer cites no outside data. It applies the method and definitions below.
References for this topic
- Delta Arc methodologythedeltaarc.com
- Delta Arc definitions and evidence classesthedeltaarc.com
This is the free read. Delta Arc CRM Intelligence turns your CRM into a live accountability engine — who owns the next move, and where revenue is stalling. Book a walkthrough.