SIG9
TOOL

Which stage of your client lifecycle stalls?

This map scores ten handoffs across Acquire, Convert, Onboard, Deliver, and Retain and expand. It marks the stage where work needs the most chasing and names the system that covers it. Customer data, visibility, and failure handling sit underneath every stage as controls to check while scoping the bottleneck.

Your answers

Rate each handoff by how it runs in a normal week. The answers already picked are an example, so change them to match your business and press Map it.

Acquire

01 / 10Turning interest from your marketing into a lead someone owns
02 / 10Recording where each lead came from

Convert

03 / 10Getting a first reply to a new lead
04 / 10Getting a proposal or quote out after a call

Onboard

05 / 10Kicking off a project once the client signs
06 / 10Collecting the details and access the work needs

Deliver

07 / 10Handing work from one person to the next during delivery
08 / 10Getting client feedback or approval before work waits

Retain and expand

09 / 10Sending clients a report on what changed and why
10 / 10Raising the renewal or the next project before the work ends

About your business

Every field here is optional, and you can skip any of them.

People on the team, including you.

Where it stalls

[ WORST ] Convert is where work waits on someone the most, and the system that covers it is inquiry handling, follow-up and proposals. Onboard stalls as well, and the system there is client kickoff, access collection and setup.

EACH STAGE SCORED OUT OF FOUR, HIGHER MEANS MORE CHASING
StageScoreSystem that covers it
Acquire1lead capture and routing
Convert[ WORST ]4inquiry handling, follow-up and proposals
Onboard[ STALLS ]3client kickoff, access collection and setup
Deliver1delivery handoffs, approvals and updates
Retain and expand3client reporting, renewal and expansion prompts
[ ACROSS EVERY STAGE ]

Customer records, visibility and failure handling are the control layer underneath the lifecycle. Check them while scoping the worst handoff; they are not a separate stage.

Bring this map to me and I'll tell you which handoff I'd fix first.

How this is calculated

Each handoff gets one of three answers. Runs without anyone pushing it scores zero, works when someone chases it scores one, and stalls or gets dropped scores two.

Each stage has two handoffs, so a stage scores from zero to four. The stage with the highest score is the bottleneck, as long as it scores two or more. When two stages tie, the earlier one wins, because a stage can only work on what the stage before it hands over.

A stage that scores three or more is marked as stalled, and the map shows up to two of them. The five stages stay in lifecycle order: Acquire, Convert, Onboard, Deliver, and Retain and expand.

Controls across every stage

Customer data, visibility and failure handling form a control layer across the lifecycle. They are checked while scoping the handoff that stalls; they are not treated as a sixth stage.

The system for each stage

StageThe system that fixes it
AcquireLead capture and routing
ConvertInquiry handling, follow-up and proposals
OnboardClient kickoff, access collection and setup
DeliverDelivery handoffs, approvals and updates
Retain and expandClient reporting, renewal and expansion prompts

Assumptions and limits

  • The answers are yours, and the starting answers are an example.
  • There is no benchmark. The score compares your stages with each other and with nothing else.
  • It shows where work waits on people. The coordination cost tool puts an hourly cost on the chasing.

Questions

What is a stalled handoff?

A point where work passes from one person or tool to the next and then waits until someone notices. A proposal that sits in drafts after a good call is one. A new client who waits a week for a kickoff is another.

Why does the earlier stage win a tie?

Because every stage works on what the one before it hands over. If leads stall at convert, a faster delivery stage still only serves the clients who made it through.

What if no stage scores two or more?

Then nothing stalls badly, and the tool says so. Start wherever the chasing takes the most of your time.

Why are data and failure handling not another stage?

Because records, visibility and recovery support every stage. A broken customer record can block onboarding or delivery, and a silent failure can hide anywhere, so I check those controls while scoping the stage that stalls.

Mashrur Rahman · Founder, SignalNinePUBLISHED