Flow

Where a lead goes to die, and why it's usually a speed problem wearing a quality costume

Once your data is trustworthy and your teams agree on what the words mean, you get to look at the layer where the engine either runs or grinds: how work actually moves through the system. Not whether you have leads, but what happens to them. Not whether you have a process on paper, but whether an account can travel from first signal to closed deal without stalling, leaking, or dying in a gap between two systems that were never properly connected.

This is Layer 3, Flow, and it is where most people think their problem lives even when it doesn’t. It is also where, once the foundation beneath it is solid, real and satisfying fixes actually happen.

The half-life of a signal

Here is a truth about revenue that almost nobody operationalizes: intent has a half-life. When a prospect does something that signals interest — visits your pricing page three times, downloads the comparison guide, has six people from the same company on your site in a week — that signal is hot right now. In an hour it is cooler. In a day it is lukewarm. In a week it is a historical curiosity.

Now walk through what happens to that signal in most companies. It fires. It sits in a queue. Eventually it gets scored. Then it waits for a routing rule to run. Then it lands on a rep, maybe the right one, maybe not. The rep is busy, so it sits in their list. Two days later they get to it, with no context about why this account was interesting in the first place, and they open with a generic “just checking in.”

By the time anyone acts, the signal is dead. The prospect who was researching hard on Tuesday has moved on by Thursday, and your beautifully expensive intent data produced exactly nothing, not because the data was wrong, but because your flow was too slow to use it.

Speed is not a nice-to-have in flow. Speed is the whole game. A perfect signal acted on in an hour beats a perfect signal acted on in a week, every single time.

The handoff, where context goes to die

The other place flow breaks is the handoff, and handoffs are treacherous because they look fine on an org chart. Marketing hands to sales. SDR hands to AE. Sales hands to customer success. Clean boxes, clean arrows. In reality, every one of those arrows is a place where context leaks out.

Here is what a bad handoff looks like. Marketing has been nurturing an account for months. They know this prospect cares about compliance, mentioned a competitor, and has a renewal window in Q3. Then the account crosses the line to sales, and all of that context evaporates. The rep gets a name and a company and starts cold, asking questions the prospect already answered, treating a warm, educated buyer like a stranger. The prospect notices. Of course they notice. It feels like talking to a company that doesn’t have its act together, because it is.

A good handoff carries context, not just ownership. The rep who picks up the account knows why it’s interesting, what’s already been said, and where the buyer is in their thinking. That continuity is the difference between a warm start and a cold one, and it is entirely a flow-design decision, not a talent decision.

A signal that fired and died at Gotransverse

When I looked at the revenue flow at Gotransverse, the complaint on the surface was a familiar one: lead quality. Sales felt the leads weren’t good. Marketing felt the leads were fine and sales wasn’t working them. You have heard this fight before; it is the Layer 2 fight. But the data was clean and the definitions, once we checked, were actually reasonably aligned. So the problem wasn’t quality. It was flow.

Signals were firing correctly. The system knew when an account was hot. But between that signal firing and a human doing something useful about it, there was a maze of delay and dropped context. Routing that took too long. Handoffs that lost the story. Follow-up that happened days late, if at all, and started from zero because none of the earlier context traveled with the account.

It looked like a lead-quality problem because the outcome was the same — leads not converting — but the cause was entirely different. We weren’t generating bad leads. We were killing good ones in transit. So we rebuilt the flow: faster routing, handoffs that carried context forward, follow-up that fired while the signal was still warm. The leads didn’t change. What happened to them did. And the conversion followed.

The lesson I keep relearning: “lead quality” is the most over-diagnosed problem in revenue, and flow is the most under-diagnosed. When sales says the leads are bad, the leads are sometimes bad. But just as often, the leads are fine and the system is strangling them on the way through.

How to see your own flow problems

Flow problems hide because no single person sees the whole path. The rep sees their piece. Marketing sees theirs. Nobody watches an account travel the entire route. So you have to deliberately trace it.

Take a real, recent account that should have converted and didn’t. Walk its entire journey, timestamp by timestamp. When did the first signal fire? When was it scored? When was it routed? When did a human first touch it? How long did each gap take? You will almost always find a stall — hours or days where the account sat somewhere, cooling, while the process ground forward.

Then check continuity. At each handoff, did the context travel? Or did the receiving person start cold? Every place the story restarted is a place you are paying to acquire warmth and then throwing it away.

Flow is a design problem, not a people problem

The thing I most want you to take from this layer is that flow failures are almost never the fault of the people in the flow. Your reps are not lazy because they took two days to work a lead; they were handed it two days late by a system that deprioritized it. Marketing didn’t sabotage the handoff; the handoff was never designed to carry context in the first place.

Flow is an engineering problem. It is about the connections between the parts, the speed of the path, and the continuity of information as work moves. Fix the design and the same people, with the same effort, produce dramatically better outcomes, because they are finally working with the system instead of against it.

Clean data, shared definitions, and a flow that moves fast and keeps context — now you have an engine that actually runs. The next question is whether you can see what it’s doing, which is where measurement comes in.