18 Feb 2026 · Journal
Mapping handoffs in B2B SaaS
Most B2B “product journeys” are sales processes with a login screen attached. If your atlas stops at in-app events, you are mapping the brochure.
Handoff Friction Clinic was built after we watched a well-instrumented trial die in a salesperson’s inbox. The product team had a beautiful onboarding funnel. The security questionnaire lived in email. Nobody had given that wait a stage name, so every dashboard looked like a product problem.
A usable B2B atlas has columns for work that happens to the buyer, not only clicks the buyer makes. Security review queued. Legal redlines. Procurement portal. Admin who must accept an invite but was on leave. These are not “qualitative colour.” They are stages with start times, owners, and (when you can get them) timestamps.
Where the data actually lives
CRM export, ticket tags, and calendar holds are often enough for v1. You do not need a perfect warehouse join on day one. In Lab we accept estimated columns if they are labelled as estimates. What we do not accept is pretending the off-product wait does not exist.
Ownership is the other half. If “security review” has no named owner, the stage will rot. Mapping it forces a conversation product would rather avoid: who is accountable for time-to-first-reply? That conversation is the outcome. The spreadsheet is just the artefact.
Thailand-based B2B teams face an extra texture: Line and WhatsApp threads that never hit CRM. We still put them on the atlas as a channel, even when the only evidence is five interviews. Better a labelled gap than a silent one. Signal Desk later helps teams decide which of those threads deserve a real event.
If your trial-to-paid number has been flat for a year, try drawing the handoffs before you A/B test empty states. Empty states are rarely where the baton falls.