Lead
The person is still being qualified. Main job is signal, reply, scope clarity, and first commercial interest.
Status control page
Know exactly where each client stands and what happens next.
This page turns the revenue lifecycle into explicit status labels so you can move clients forward without mixing lead handling, delivery, approval, balance collection, and retainer conversion into one blur.
- 7 client statuses
- 1 next action per status
- 0 reason to guess
Status Map
Use the label that matches the real commercial state.
Awaiting Payment
Scope is agreed and the next step is deposit. This is not a lead anymore, but it is not yet an active project either.
Active
Deposit is confirmed, intake is in, and the sprint is now live.
In Delivery
The sprint work is underway and the next focus is shipped assets, not new selling.
Awaiting Approval
Delivery is complete enough to review. The next step is approval, light revision if needed, and remaining balance.
Expanded
The client moved into a second sprint or a new scoped project after the first one closed cleanly.
Retained
The client is now on a monthly rhythm with defined recurring work instead of one-off sprint packaging.
Next Action By Status
Every status should point to one operational page.
Lead
Next move is reply, objection handling, pricing, or close logic.
Open Reply BoardAwaiting Payment
Next move is offer confirmation and payment request.
Open Close BoardActive
Next move is collecting the minimum kickoff inputs so work can begin without delay.
Open Intake BoardIn Delivery
Next move is shipping the narrow sprint assets and protecting the scope boundary.
Open Delivery BoardAwaiting Approval
Next move is summary, approval, and balance collection.
Open Client RecoveryExpanded
Next move is scoping the next bottleneck as its own sprint.
Open Renewal BoardRetained
Next move is running the defined monthly support rhythm, not dropping back into ad hoc request handling.
Open Retainer ConversionStatus Shift Rules
Move the label only when the trigger is real.
Lead To Awaiting Payment
Shift only after scope is agreed and the next expected action is deposit, not more broad conversation.
Awaiting Payment To Active
Shift only after deposit is confirmed and the kickoff inputs are actually in motion.
Awaiting Approval To Expanded Or Retained
Shift only after the current sprint is closed cleanly, not while approval and balance are still unresolved.