There is a question I ask founders when they tell me they are exhausted. It is a simple one. If you disappeared for two weeks, no phone, no laptop, no check-ins, what would still be standing when you got back?
Most people go quiet. They start doing the math on all the things that only they can do. The vendor who only calls their cell. The invoice that only they know how to approve. The tenant complaint that always lands in their inbox. The hire who texts them a question every hour. And in that quiet, they realize the truth: they do not own a business. They own a very demanding job that happens to have their name on the door.
I have run companies for more than fifteen years now, across real estate and property management, a cleaning company (Wasatch Cleaners), and operator software (Akovex). I have managed hundreds of units across Utah and California. And I will tell you plainly: the single biggest shift in my life as an operator was the day I stopped trying to be indispensable and started building things that did not need me. That shift is the difference between owning a job and owning an asset. It is also, quietly, a matter of stewardship. Let me explain both.
Founder-Dependence Is the Ceiling
Here is the hard math. When you are the business, your growth is capped by your calendar. You have a fixed number of hours, a fixed amount of attention, and a body that needs sleep. Every dollar of revenue has to pass through you, which means the whole machine can only move as fast as one tired person can move it.
That is the ceiling on your wealth. It is also the ceiling on your freedom. You cannot take a real vacation, because the business is a plate you are spinning, not a thing that spins on its own. You cannot get sick. You cannot have a slow week. And the cruel part is that the better you are at your job, the more the business bends itself around your competence, until you are the load-bearing wall and no one can remodel the house without knocking it down.
I want to be honest here. The pull toward founder-dependence is not laziness. It is usually the opposite of laziness. It is care. You do it well, you do it fast, you know the customer by name, and handing it off feels like lowering the bar. But care that only lives in one person’s head is fragile care. The most loving thing you can do for a business, and for the people who depend on it, is to make it survivable without you.
The Four-Stage Flywheel
The way out is not a single heroic decision. It is a loop you run over and over, and it compounds. I think of it in four stages: operate, systematize, productize, repeat.
- Operate. Do the work yourself first. This is not the stage to skip. You cannot document or delegate something you do not deeply understand. Run the leasing process by hand. Clean the unit. Close the deal. Feel where it is clumsy.
- Systematize. Turn what you just did into a written, repeatable procedure. Not in your head. On paper, or in a shared doc, in the exact order the steps happen.
- Productize. Hand the system to someone else, or to software, so it runs without your hands on it. The goal is that the output becomes predictable regardless of who is holding the wrench.
- Repeat. Move up to the next messiest thing you are still personally doing, and run the loop again.
Each turn of the flywheel buys back a little of your time, and you reinvest that time into the next turn. It is slow at first and then it is not slow at all.
Write the Procedures Down
I am going to be very practical, because this is where most people stall. A standard operating procedure is not a corporate document. It is a recipe. If a competent stranger could read it and produce roughly the same result you would, it works. If they would need to call you halfway through, it is not done.
Here is how I build them without it becoming a second job:
- Document while you do the work, not after. The next time you handle a task, narrate it. Screen-record it, or write each step as you take it. Memory lies; the live run does not.
- Write for the newest person, not the smartest. Assume no context. Spell out the boring parts, because the boring parts are exactly what gets dropped.
- Include the decision points. Good procedures do not just list steps, they tell the reader what to do when something is off. If the payment fails, do this. If the tenant is upset, escalate here.
- Store them where the work happens. A brilliant SOP no one can find is a diary. Put it in the tool your team actually opens every day.
- Let the doers own the edits. When the person running the procedure hits a gap, they fix the doc. Living procedures beat perfect ones.
At Wasatch, our cleaning quality did not become consistent because we hired better people. It became consistent because the checklist did the remembering, so a good day and a bad day produced the same clean home.
Hire and Actually Delegate
Delegation is where good intentions go to die. People hire help and then supervise it so closely that they have simply added a spectator to their own job. That is not delegation. That is babysitting with extra payroll.
Real delegation means handing over the outcome, not just the task. You do not want someone who does the steps you dictate. You want someone who owns the result and comes to you with it finished. That requires three things: a clear definition of what “good” looks like, the authority to make the small decisions, and the room to do it a little differently than you would.
That last one is the hard one. They will not do it exactly your way, and if the result is right, that has to be fine. I have learned to judge my team on the scoreboard, not on whether they held the bat the way I would have. Give people the procedure, give them the standard, and then get out of the batter’s box.
Build the Management Layer and Watch the Numbers
Once work is delegated, you need a way to know the truth without hovering. That is what the management layer is for. It is the small set of people and instruments that let you steer the business by looking at it rather than by touching every part of it.
Two pieces matter here.
First, a person who runs the day. As you grow, you need someone whose job is to make sure the systems are being followed, not just to do the work inside them. An operator over the operators. This is the hire that finally lets you step back, and it is worth waiting for the right one.
Second, a dashboard that tells you the score. You should be able to glance at a handful of numbers and know whether the business is healthy. For property management that might be occupancy, days-to-lease, delinquency, and work-order turnaround. For cleaning it might be jobs completed, redo rate, and on-time percentage. The specific metrics matter less than the discipline: pick the few numbers that reveal the health of the thing, and look at them on a rhythm. Building software at Akovex taught me this more than anything, because when you build the dashboard for other operators, you are forced to decide what actually matters and let the rest go.
When the numbers, not your gut, tell you something is off, you have arrived. You are now steering the asset instead of being the asset.
The Two-Week Test
Here is the test I promised at the start, and I mean it as a real exercise, not a thought experiment. Can it run without you for two weeks?
Plan it. Put it on the calendar. Tell your team you will be unreachable, and then actually go. Two weeks is the magic number because one week can be survived on momentum and adrenaline. Two weeks forces a real decision to be made without you. It surfaces every place where you are still the single point of failure, and it does it while you are calm enough to fix it rather than panicked in the middle of a crisis.
The first time you try this, things will break. That is the point. Each break is a map to the next procedure you need to write or the next decision you need to delegate. Run the test once a quarter and watch the list of breakages get shorter every time. The day nothing breaks is the day you own an asset.
Why the Asset Is Worth More
There is a financial reason all of this matters, beyond your sanity. A business that depends on you is difficult to sell, and it sells for less. A buyer is not paying for your personal hustle, which walks out the door with you. They are paying for a machine that produces results predictably. The more the business runs on systems and a team rather than on the founder, the more transferable it is, and transferable businesses command higher multiples.
You do not have to be planning to sell for this to matter. A sellable business is simply a healthy business viewed from the outside. But if a sale or valuation is ever on your horizon, please talk to a qualified advisor about your specific situation. Nothing here is financial or legal advice; it is one operator’s experience, not a plan for your books.
Systems as an Act of Love
I said this was also about stewardship, and I want to close there, honestly.
I am a woman of faith and a mother, and those two facts shape how I think about a business more than any spreadsheet does. We are given a limited number of days and a handful of people to love well inside them. A business that consumes every hour of its founder is not just a wealth problem. It is a stewardship problem. It quietly spends the very thing you were building the business to protect, which is your time with the people who matter.
So I have come to see systems as an act of love. Writing the procedure is love. Building the team is love. Trusting the dashboard instead of grabbing the wheel is love, because every one of those things buys back an hour and hands it to your family, your faith, your rest. Being needed everywhere is not the same as being faithful. Sometimes the most faithful thing an operator can build is a business that can, for a while, get along just fine without them.
Being recognized as one of Utah Business magazine’s Women to Watch was kind, but the recognition I care about is quieter. It is a Tuesday afternoon where the business is humming, the team is handling it, and I am somewhere else entirely, present with the people I built it all for in the first place.
If this way of thinking is useful to you, I share more of it in my newsletter, Operator’s Notes, where I write about the unglamorous mechanics of building something that lasts. And I dig into these conversations with founders and operators every week on my podcast, The Broker’s Table. Come sit down with us. There is always a seat.
