Skip to content

Coaches & Experts

Drop-off usually shows up in the calendar before it reaches your inbox.

A client who is on their way out stops filling in the check-in, misses a call, and lets a module sit half-finished. Each signal sits in a different tool and none of them looks serious alone. The systems on this page are designed to put those signals together in week seven, while there is still program left to run. They would not do the coaching, and they would not talk to your clients for you.

WEEK 7 OF 12 · CLIENT REVIEW
Client
Alex
Program week
7 of 12

12-week group program, third cohort, paid in three instalments

Last check-in
At risk: 9 days ago

Weekly form, previously submitted every Sunday night

Milestone
At risk: Missed

Week 6 milestone still open

Session attendance
At risk: Down

2 of the last 3 group calls missed

Term ends
Deadline: In 5 weeks
Next action
Next action: Coach review

Before Thursday’s group call

Alex, the nine-day gap in the check-ins and the $6,000 program fee on this page are one illustrative cohort, written to make the workflow legible — not a client we have worked with.

The client decided three weeks before they told you.

The email arrives on a Thursday: they have been thinking about it, and they will not be continuing past this term. You open their file and every warning is already sitting there. The Sunday check-in form stopped nine days ago. They missed two of the last three group calls. Their module progress has not moved since week four, and the commitment they made on the week-five call was never followed up because that call is a recording nobody has rewatched. None of it was hidden. It was spread across a booking calendar, a spreadsheet, a course platform and a community channel, and no single one of those looked alarming on its own while you were running a cohort of thirty other people. The week there was still something to do about it was week seven. By the time the four signals lined up in your head, the client had already made the decision and was only telling you about it.

Where value leaks

The places a client leaves before the conversation happens.

From research into how a program actually behaves week to week. A ten-client practice meets these differently than a hundred-client one.

01

Tomorrow’s session opens without knowing what was promised on the last one

Where a client actually stands lives in four places at once: the call recording, the weekly check-in form, the course platform’s progress bar, and whatever the coach remembers. With eight clients the coach holds all of it. With forty across two cohorts and an associate coach running half the sessions, nobody holds it — so the commitment made three weeks ago is either raised from memory or not raised at all, and the client notices which.

TOMORROW 9:00 · SESSION PREP
Last session
Recording, 58 minutes
Commitment made
At risk: In a direct message
Check-in form
At risk: Row 214 of the tracker
Course progress
At risk: Module 6 of 10, unchanged
Time to assemble
At risk: Nobody has it
02

“I want to start with the next cohort” — and then nothing

The application comes in, the call runs long because it went well, and the prospect says they want to start with the next intake. The enrolment link goes out that afternoon. What happens next depends entirely on whether the coach remembers to come back to it during a week full of client sessions — and the conviction that was in the room on the call does not keep for long. The exact words that made them ready to start are sitting in a recording nobody will open again.

DAY 6 · AFTER THE DISCOVERY CALL
Call outcome
At risk: Said yes on the call, no payment
Stated goal
First hire before Q4

Said twice on the call, not written anywhere

Enrolment link
At risk: Opened twice, not started
Program value
Value: $6,000
Next contact
At risk: None scheduled
Owner
At risk: The coach, between sessions
03

A quiet client looks exactly like a happy client

They are not complaining, their payment plan is current, and their name still appears on the roster, so nothing about them surfaces in a normal week. Meanwhile they have stopped posting in the community, watched the last two calls as replays instead of attending, and left the last check-in blank. The first hard evidence anyone sees is the client saying they will not be continuing — which is a different emergency from the one where a card fails, and the two are easy to confuse from the outside.

04

Instalment payments fail without anyone leaving

A card expires in month two of a three-payment plan. The processor retries, emails the client, and the email lands in a folder nobody opens. The client is still attending, still posting, still on the roster — and no longer paying. Nobody in the business is looking at the payment processor daily, so the gap tends to surface when someone reconciles the month, and the awkward conversation is then about several months of arrears rather than one expired card. Any watch on client health has to read the payment record alongside the attendance record, or it will call a paying client and a non-paying one the same thing.

05

Renewal conversations start too late

The right moment to talk about continuing is the week a client has just hit something they are proud of, usually somewhere around week eight or nine. Instead the conversation lands on the final call, when the client is already mentally packing up, or it never happens at all and a monthly subscription simply lapses. Nothing in the calendar says which clients are inside their last four weeks, so the reminder is the end of the term itself.

06

Client wins happen but are not captured as proof

A client posts at eleven at night that they closed their first retainer. It gets a row of reactions, then scrolls away behind the week’s questions. Three months later the coach is rewriting the sales page or answering a prospect who wants evidence the program works, and the strongest results they have are half-remembered — no numbers, no timeframe, no permission to quote anyone.

11:48 PM · COMMUNITY POST
Client message
Result reported

“Signed my first retainer client today.”

What was reported
First retainer, three-month term
Reactions
14
Recorded as proof
At risk: No
Permission to quote
At risk: Never asked
Renewal conversation
Deadline: In 5 weeks
Next action
Next action: Coach approval

The workflow

Week five, watched and unwatched.

The same drifting client: first as the calendar shows her, then with attendance, check-ins and payments read together.

Today

A client drifting in week five — today

  1. Trigger

    Client skips the Sunday check-in

    Week 5 form not submitted

  2. Data

    The signal stays inside one tool

    A blank row in the tracker

  3. State

    The client still reads as active

    Payment plan current, seat filled

  4. Human

    Coach is mid-cohort and carrying it from memory

    Thirty other clients that week

  5. Action

    Catch-up message sent after the second missed call

    Two weeks later

  6. Outcome

    Seat empty for the next cohort

    The email said they’d been thinking about it

With a system

The same client, if a system were watching the pattern

  1. Trigger

    Client skips the Sunday check-in

    Week 5 form not submitted

  2. Data

    Attendance, check-ins and module progress read together

    Calendar, form, course platform

  3. Rule

    Drift threshold set for this program

    Two missed signals inside ten days

  4. State

    Client file assembled for review

    Week 7 · five weeks of term left

  5. Human

    Coach decides what this actually is

    Hard week, or a client leaving

  6. Action

    Outreach sent in the coach’s own words

    Draft edited before it goes

  7. Outcome

    Intended: the conversation happens with weeks of term still to run

    Milestone reset in week 8

Systems

What we would build around the client relationship.

Deliberately small. The coach keeps the judgement the client is paying for.

These are systems we would build. Nothing on this page describes a delivered result.

Midpoint Review & Renewal Window

Designed so that when a client passes the midpoint of their program, their progress, attendance and open milestones are assembled into one review the coach reads before the renewal conversation.

Detects
Program week, milestone status and the approaching end of a term or billing cycle.
Assembles
Sessions attended, check-ins submitted, modules completed and commitments made on past calls, in one file.
Human decides
The coach decides whether to open a renewal conversation, offer a different program, or let the term end.
Intended outcome
Built so the coach can open the renewal conversation while there is still a recent result to point at.

Discovery Call Commitment

Designed to hold what the prospect actually said when a call ends without a payment, and return it to the coach as a follow-up worth sending.

Detects
Calls that ended in clear intent but no payment, and enrolment links opened but never completed.
Assembles
The stated goal, the objection raised, the timeline they named, and whether the enrolment link was opened.
Human decides
The coach reads and edits each follow-up before it leaves, and decides who is a fit for the program.
Intended outcome
Built to bring the follow-up back while the intent is still warm.

Quiet Client Watch

Designed to raise a client for review before the next session when their attendance, check-ins, course progress or payments fall out of their own pattern.

Detects
Missed sessions, blank check-ins, stalled modules, silence in the community, and instalments that failed without anyone saying they were leaving.
Assembles
The last four weeks of that client’s engagement and payment record, next to the program they paid for.
Human decides
The coach decides whether this is a rough week, an expired card or a client on their way out, and what gets said.
Intended outcome
Built to surface the drifting client in week seven, rather than after the client says they are done.

Client Win Capture

Designed so that when a client reports a result, it is recorded with its numbers and timeframe and offered back to the coach as renewal evidence, a testimonial request or sales-page proof.

Detects
Results reported on calls, in community posts and inside check-in forms.
Assembles
What changed, over what period, in the client’s own words, attached to their program week.
Human decides
The client gives permission and the coach approves any public use of a result.
Intended outcome
Intended to put a win on record, with its numbers, the day a renewal, a referral or a sales page needs it.

Human control

Automate delay. Not judgement.

A system can

  • Reading attendance, check-ins and module progress as one picture
  • Flagging clients who have fallen out of their own pattern
  • Assembling the client file before a session — including what was committed to on the last call
  • Watching where each active client sits against the end of their term
  • Logging client results with their numbers and dates
  • Turning last week’s commitment into a check-in the coach can edit in a minute

People still decide

  • Judging whether a client is struggling or simply having a hard week
  • Deciding whether a missed payment is an expired card or a client leaving
  • Deciding what is actually said to a client who is drifting
  • Offering a renewal, a pause, a refund or an exit
  • Accepting or declining someone into the program
  • Setting pricing, program structure and payment terms
  • Granting permission to use a client’s result publicly
  • The coaching itself — the advice, the challenge, the relationship

We are not building a coach. The relationship is the product, and clients pay for a specific person’s judgement — a system that answers them on your behalf devalues the thing they bought. What we would build reads the signals already scattered across your calendar, your course platform and your check-in forms, and aims to put the client who needs attention in front of you while there is still time to do something about it.

Tell us about the client who left quietly.

When they went quiet, what the calendar showed at the time, and when you found out. We start with the program, not with software.