Listen on Spotify // Listen on Apple podcasts
I build systems for a living, and I once wrote this in my own meeting notes:
“I’m unclear about how the inquiries happen, where they happen, and what happens after they inquire.”
Humbling.
I had tools. I had processes. Parts of my client experience were well supported. But when I looked more closely, I realized my one-to-one offers had follow-up and onboarding that my memberships and group programs didn’t.
I could still make things happen because I remembered what came next.
That felt functional because I was good at carrying it. It wasn’t proof that the system worked equally well across my business. It was proof that I could compensate for the gaps.
And that’s worth looking at before you buy another tool.
When every tool works, but the process still needs rescuing
Consider a pretty normal lead-to-client process.
Someone fills out a form, books a call, receives a proposal, signs, pays, and gets onboarded.
If you inspect each tool separately, everything might look fine. The form collects information. The calendar books appointments. The proposal software sends documents. The payment processor takes money.
Yet you still have to remember to review the inquiry, update the lead, send the proposal, check the payment, create the project, and deliver the welcome email.
Some of those steps may reasonably belong to you. The question is whether the process supports you in doing them—or whether remembering is the only thing keeping them connected.
Imagine drawing each tool as a box. Now draw the arrows showing how work moves between them.
Those arrows are the handoffs.
You can rebuild every box and still leave every arrow pointing back to your brain.
That’s the gap I want you to investigate.
Being good at remembering can hide an unreliable process
There’s a difference between knowing where someone’s information lives and having a dependable follow-up process.
If the follow-up only happens when that person pops into your head, the CRM is storing information. It isn’t yet supporting the whole job you need it to do.
The same applies to onboarding. Getting every client across the finish line doesn’t tell you how much checking, chasing, copying, or reconstructing it required.
When you’re used to doing that work, it can become difficult to see. It’s just how Tuesday goes.
But it matters when you want someone else to help. It matters when your workload changes. And it matters when you have a week where you can’t keep every unfinished detail in view.
A useful system makes the next step recoverable without requiring you to reconstruct the entire situation first.
Audit one handoff—not your entire business
Start smaller than “fix my backend.”
Choose one transition: sales call to proposal, payment to onboarding, or client meeting to follow-up.
Write down the tools involved. Then look at what has to happen between them.
For each handoff, make four decisions.
1. Trigger: What tells the process to move?
“After the sales call” can leave quite a bit open to interpretation.
Does every call require a proposal? Does the lead need to be qualified first? Are you waiting for more information?
A useful trigger is something recognizable: the lead is marked qualified, the agreement is signed, or payment is received.
You’re defining the condition that makes the next step appropriate.
2. Owner: Who is responsible for the next move?
“The team” is not specific enough.
Name the person responsible. If software performs the action, be clear about what it executes and who checks exceptions or failures.
You don’t have to delegate every repetitive step to another human. Technology can help. You do need to know where responsibility sits.
Even when you’re the owner, defining the handoff helps. You shouldn’t have to make the same decision from scratch every time it happens.
3. Status: Where does the handoff leave a visible receipt?
If you send a proposal, what changes?
Perhaps the CRM says “Proposal Sent.” Perhaps a follow-up task appears with a date. Perhaps the project records what you’re waiting for.
The information needs to become visible somewhere you’ll actually encounter it.
That doesn’t require forcing everything into one app. I’ve built workflows where communication stays in HoneyBook while follow-up tasks and dates live in Notion.
Two tools can work together perfectly well. The trouble starts when nothing records the transition and you’re the only person who knows what happened.
4. Exception: What happens when the process gets weird?
The proposal is signed, but payment fails. The client pays, but the questionnaire is incomplete. A discovery call leads to another discovery call rather than an immediate yes.
These aren’t especially surprising situations in a service business.
If the process only works when everyone follows your ideal sequence, you’ll keep having to invent the recovery plan.
Decide what should happen when something is late, missing, or unusual. Where will it show up? Who needs to act? What are they waiting for?
This is part of how a system earns trust: it helps you find the next step even when the original plan changes.
Test the process before automating it
Once those decisions are clear, run three cases through the workflow:
A normal case that follows the expected path.
A delayed case that spends longer waiting or following up.
An unusual case involving an exception.
Check whether the next action is clear, whether missed steps become visible, and whether someone else could understand the process without asking you to explain every arrow.
Then consider automation.
A form submission can trigger five actions and still leave everyone confused. More notifications won’t establish which record is authoritative or who needs to do something next.
Automate the stable, repeatable move. Keep human judgment where the relationship, context, or stakes require it.
Payment received might trigger an onboarding task. Deciding whether a new client request changes the agreed scope still needs judgment.
Start with the step you keep having to remember
You don’t need to replace your whole setup to improve one unreliable handoff.
Choose the transition you keep checking behind. Define its trigger, owner, status, and exception. Put that next step somewhere visible, and give yourself a realistic moment to review it.
That’s how the tool, process, ritual, and intended outcome start working together.
If you want to learn how to think through and build that support yourself, that’s the work we do in Systems School. If you want ongoing help implementing it, Burnout-Proof Business offers a different level of support.
Whichever route you take, the point is the same: important work should have something more dependable behind it than the hope that you’ll remember.
You still get to make decisions, care about the client, and adapt when something changes. You just don’t have to reconstruct every next step before you can do any of that.
