Build a System Others Can Replicate: The Difference Between a Practice and a Business
There is a question I ask every agency leader I coach, and the answer almost always reveals the single most important thing they need to work on. The question is: if you disappeared for a month, what would break?
Not what would be inconvenient. Not what would slow down. What would actually break, meaning stop functioning entirely or produce outcomes so poor that clients and associates would notice something was seriously wrong?
The honest answer to that question is a map of your agency’s single points of failure. And in most agencies I have seen, there are more of them than the leader realises, because most of the systems exist only in their own head.
“A practice depends on the practitioner. A business runs, at least partially, without them. That is the only meaningful difference between the two.”
The Defining Characteristic
A practice depends on the practitioner. A business runs, at least partially, without them. That is the only meaningful difference between the two, and it is the difference that determines whether you are building something that grows beyond your own capacity or simply creating a more sophisticated version of a job.
Most financial advisory agencies in Singapore are practices. Some of them are very profitable practices. But they are practices nonetheless, because when the leader is away, the machine slows down or stops. The activities that produce cases depend on the leader’s personal relationships. The coaching that develops new advisers depends on the leader’s presence. The client service that retains existing clients depends on the leader’s personal attention.
None of this is wrong in the early stages. You have to build it yourself before you can build the system around it. But at some point, the system needs to be built, or the practice will always be constrained by what one person can personally deliver.
Where to Start: Document What You Already Do
Building systems that others can replicate starts with documenting what you already do. Not redesigning from scratch. Not implementing software. Just writing down, in enough detail that someone else could follow it, the processes that currently live only in your head.
How do you onboard a new associate? What happens in their first week, their first month, their first ninety days? What materials do they receive? Who speaks to them and when? What are the specific activities they are expected to complete, and how are those activities tracked and reviewed?
How do you manage your client review cycle? What triggers a review conversation? What does that conversation typically cover? How is the output recorded, and who is responsible for any follow-up actions?
How do you handle referrals? What is the process when a client introduces someone new to you? Who follows up, how quickly, with what message, and how is that lead then managed through to either conversion or a deliberate decision to stop pursuing it?
The Act of Writing It Down Is Itself Valuable
Most leaders who go through this process discover something unexpected. The act of writing their processes down reveals, often for the first time, the gaps, the inconsistencies, and the steps that make no logical sense but exist because that is how they have always been done.
It also reveals the steps that depend entirely on the leader’s personal judgment and cannot easily be systematised. These are valuable too. They tell you where you need to develop the people around you so that judgment can eventually be distributed, rather than remaining concentrated in a single person.
Write it down. Not because you are planning to leave. Because the act of writing it down is the beginning of building something that does not require you to be everywhere at once.
Ready to build a business that runs without you having to be everywhere?Systems building is one of the areas I work on directly with the leaders I coach. If you want to identify your agency’s single points of failure and start closing them, let’s talk.
