Who Owns the Gap Between "Closed" and "Invoiced"?
Ask most teams where a signed deal goes next and you'll get a confident answer. Ask who moves it there and the room gets quiet. The deal is closed, the invoice is sent, and somewhere in between a task fell through a crack. Nobody meant to drop it. Nobody was ever told to pick it up.
That's the failure this piece is about, and it's more common than most operations leaders admit. A stalled handoff rarely looks like a problem on any single day. It looks like a bit of silence. The contract was signed on Thursday, the account manager assumed finance had the details, finance assumed sales would send the order form, and by the second week a customer is asking why nothing has arrived.
Why the stalled thing stays hidden
Most task systems are organized around people and projects. A task belongs to someone or it doesn't appear on anyone's list. The trouble is that handoffs live between owners. The step from "deal closed" to "invoice sent" usually crosses at least two departments, and the task that connects them often has no name at all. It exists in the gap, so no one's board shows it.
This is why searching your tracker for "stalled" tends to return nothing useful. The stalled item was never created as an item. You can't filter for something nobody was ever assigned.
A weekly exercise that surfaces the gaps
The fix doesn't require new software or a reorganization. It requires writing down the handoffs you already depend on, once a week, and checking each one for an owner.
Start by listing your handoffs as pairs of stages. Keep them concrete:
- Deal closed to contract countersigned
- Contract countersigned to account set up
- Account set up to invoice sent
- Invoice sent to first payment received
- Support ticket resolved to customer notified
Then, for each gap between two stages, name one person. Not a team, not "sales ops," but a single human who answers for that step when it stalls. If you can't name one person, you have found your stalled thing. It has no owner, which is why it's stuck.
Naming one person matters more than it sounds. A shared responsibility is usually no one's responsibility. The discipline is in forcing a single name, even when the honest answer is "whoever is around that day."
Where AI fits, and where it doesn't
An AI assistant can help with the tedious part of this exercise: pulling the list of closed deals, comparing them against invoices issued, and flagging the pairs where the second step never happened. That kind of cross-check is exactly the sort of work people skip because it's dull, and it's where a stalled handoff hides.
What the assistant should not do is decide who owns the gap. Assigning a name is a judgment about your team, your capacity, and your priorities. It belongs to the person accountable for the workflow. A good setup lets the assistant surface the candidates and draft the question ("Deal Acme closed on the 3rd, no invoice yet, who is taking this?") while a human makes the assignment.
Keep the scope narrow when you start. Pick one handoff that has caused trouble before, measure whether the weekly check catches it, and expand only once the first gap is reliably owned.
What changes after a few weeks
Teams that run this habit for a month usually notice two things. First, the number of stalled items they discover is higher than they expected, which is uncomfortable but useful. Second, the conversations change. People stop asking "whose is this?" in the hallway and start looking at a short list with names next to each step.
The goal isn't a perfect process. Handoffs will always be messy. The goal is that every gap between two stages has an answer to the question "who picks this up?" When that answer exists, the stalled thing has somewhere to go.
Start this week. Write down three handoffs your revenue depends on, name one person for each gap, and check back next Monday. If a name is missing, you've already found the work nobody was doing.
