A buyer experiences one process. Most companies run four: marketing generates, sales development qualifies, sales closes, customer success retains. Each is measured on its own number, and the buyer is passed between them.
The failure is not the structure. It is that nobody owns the joins.
The seams, and what is lost at each
| Seam | What gets dropped |
|---|---|
| Marketing to sales development | Why the lead engaged, and which content told you |
| Sales development to sales | The problem in the buyer's words. See the handoff |
| Sales to customer success | What was promised during the sale |
| Customer success back to sales | Expansion signals the CSM sees and the AE never hears |
Every one of these is a place where the buyer repeats themselves. Buyers read that as disorganisation, correctly.
Organising around the journey does not mean removing roles
The common overcorrection is a pod or a full-cycle rep, on the theory that one person removes the handoffs. Sometimes right, often not: specialisation exists because prospecting and closing are genuinely different skills, and collapsing them usually reduces both.
The cheaper change is to keep the roles and name an owner for each seam. Not a committee. One person accountable for what travels across it and for the number that grades it.
Measure the seam, not the sides
This is the structural fix, and it is a measurement decision rather than an org-chart one.
Each side of a seam optimising its own metric produces exactly the behaviour you do not want:
- Marketing measured on MQLs sends more leads, not better ones.
- Sales development measured on meetings booked books marginal meetings.
- Sales measured on closed revenue ignores what was promised to get it.
Give the seam its own number that both sides carry:
- Marketing to SDR: meetings held from marketing-sourced leads, not MQL
volume.
- SDR to AE: meeting-held rate and next-step rate, both roles.
- Sales to CS: first-year retention on that AE's accounts.
Shared numbers do more than any alignment meeting.
Map the journey once, honestly
An afternoon, with all four functions in the room, on one question per stage: what does the buyer actually do here, and what do we do?
Two things reliably surface:
- Stages where nothing happens for weeks while the buyer is deciding, and
nobody is doing anything because it is between two owners.
- Stages where three functions touch the buyer without knowing about each
other.
Both are invisible on an org chart and obvious on a journey map.
Where this sits
This spans Motion and Measurement in the Tenbound Pipeline Architecture Standard, and it is the clearest case of measurement design creating behaviour. Four functions optimising four numbers around one buyer produces four locally rational decisions that add up to a bad experience.
Related: revenue alignment and the sales development process.