Start the Free Course

Module 07 — Build your operating system

Connect the handoffs

You'll map the five handoffs between the parts you've built and give each one a trigger, an owner and a check — so nothing falls into the gaps.

  • 3 min read + 25 min exercise
  • Lesson 1 of 3
  • Free · No sign-up

The problem

You have the parts now: every door into one log, a first reply, lanes, conversation rules, a pipeline, follow-up sequences and a marketing hour. The leaks that remain live between them — in the moment a customer should move from one part to the next, and nobody moves them.

Why it matters

Systems rarely fail in the middle of a step. They fail at the handoff: the inquiry that was answered but never became a deal, the quote sent without a follow-up date, the finished job without a review request. Connect the handoffs and the parts start working as one system.

1 The five handoffs

  1. Door → logEvery inquiry gets a row.Gap: answered in the app, never logged.
  2. Log → first replyEvery row gets a reply on target.Gap: logged, then forgotten.
  3. Conversation → pipelineEvery qualified lead becomes a deal.Gap: good chats with no next step.
  4. Pipeline → follow-upEvery quiet deal starts a sequence.Gap: quotes sitting in “sent” for weeks.
  5. Won → review and returnEvery finished job gets a request and a return date.Gap: happy customers never heard from again.

2 Step by step

  1. Write the trigger for each handoff

    The exact event that should move the customer on: “row added,” “they answered the qualifying question,” “quote sent,” “job marked done.”

  2. Give each handoff one owner

    In a small team it's often the same person for the whole flow. That's fine — as long as it's written down.

  3. Decide how it happens: by hand, reminder or automation

    Use the spec from lesson 3.2. Many handoffs need only a rule and a column — for example, when the stage becomes Won, the review request date is set to the day the job ends.

  4. Give each handoff a check

    A question you can answer in seconds during your daily or weekly review: “Any rows without a first-reply time?” “Any quote older than three days without a next step?”

  5. Run the gap test

    Take three recent customers and walk each one through all five handoffs. Wherever you can't point to the moment it happened, that's the gap to fix first.

Example · illustrative

The gap test at the cleaning company

  • Customer 1 came in through Instagram and got a quick answer in the app — but never got a row. No row, no deal, no follow-up. Gap at handoff 1.
  • Customer 2 went through every handoff: logged, answered, quoted, followed up on day 3, booked. No gaps.
  • Customer 3 booked and was happy — and never got a review request, because “Won” didn't trigger anything. Gap at handoff 5.

The fixes: Instagram is now part of every sweep, and marking a deal Won sets the review request date automatically.

Your exercise · about 25 minutes

Map and test your handoffs

Template · Handoff map
1 DOOR → LOG
  Trigger:              Owner:              How (hand / reminder / automation):
  Check:
2 LOG → FIRST REPLY
  Trigger:              Owner:              How:
  Check:
3 CONVERSATION → PIPELINE
  Trigger:              Owner:              How:
  Check:
4 PIPELINE → FOLLOW-UP
  Trigger:              Owner:              How:
  Check:
5 WON → REVIEW AND RETURN
  Trigger:              Owner:              How:
  Check:

GAP TEST — 3 recent customers. Where couldn't I point to the moment it happened?
1.
2.
3.

Parts don't make a system. Handoffs do.

Your next action

Before the end of today, run the gap test on the last customer you won.