Most business systems get built the week after something breaks. Here's how to use a calmer stretch to build the one that matters, before the next busy season.
The short answer: Build systems when you have the time, not when you need them. Find the one limit that caps what your business can deliver, protect a fixed block each week to build a system that relieves it, and finish it before the next busy stretch arrives.
One of my group sessions once didn't record. The cloud storage on our recording account was full, and I didn't find out until afterwards, when everyone was asking for the replay.
Here's the fix: an AI check now runs on a schedule every week. It looks in the two places our recordings live, confirms each session is saved, and tells me what's safe to delete before the storage fills up again. I could have put that check on someone's weekly list. I'd rather my team spend that time on calls with clients.
What I notice in that story is the timing. I built the system after it failed, in front of the people I was trying to serve. That's how most systems get built.
Why systems get built after they break
When the business is busy, you're servicing it. There's always a client to call, a deal to close, a fire to put out. The work of building how the business runs, the systems and routines underneath it, keeps sliding to next week, because nothing about it is urgent until something breaks.
I described it to a group of owners in September with an image from home. Here in Utah, as we head toward winter and the mountains are about to fill with snow, I find myself grateful for something I almost never think about: roads. Somebody put that infrastructure in over decades so I can get from one place to another whenever I want.
A business without systems has roads too. They're just dirt. As I put it to that group: "oftentimes without a system it can feel very much like a dirt road that we're driving on." You still get where you're going. It's bumpier and heavier than it needs to be, and you can't build a paved road overnight.
Use the calmer stretch
If your business has a calmer stretch, that's when the roads get built. Not because building is pleasant. My view is simple: a calmer stretch is often the only time there's attention to spare.
At my brokerage we run a business planning clinic for our agents each year, around October and November, to help them plan the next year. Planning is the right instinct. But a plan for a busier year, run on the same dirt roads, mostly plans for more strain. Whenever your calmer weeks fall, they're also when you can build the systems that make the plan possible.
That's the idea I want owners to take into the end of the year.
Paving Season is a set stretch of weeks, ideally while business is calmer, with a protected block each week for building one system aimed at the single biggest limit in your business, finished before the next busy stretch arrives.
Three parts carry the weight: one system at a time, aimed at the biggest limit, and finished before you need it.
Pave the road that limits you
AI makes building systems easier than it's ever been, and that creates its own problem. Building a system used to take real effort, so owners built few of them. Now AI can produce plans, templates and automations faster than any team can put them to use. A quiet month with AI can fill up with impressive roads nobody drives on.
The filter I use is the constraint: the one step in a business that caps how much the whole business can produce. The idea comes from The Goal by Eliyahu Goldratt, the book that introduced what he called the Theory of Constraints.
The illustration I use with groups is a car factory. On day one, the factory can make three steering wheels, one body frame and seven engines a day. How many cars does it build? One. The usual instinct is to push engines to 99 a day. Nothing changes, because frames were the limit. Until frames improve, nothing else matters.
In most businesses the constraint sits in one of two places:
- Getting business. You'd take more clients tomorrow if they showed up. The roads worth paving are the ones that bring in and follow up with customers.
- Serving business. More clients would make quality slip. Someone would drop the ball. The roads worth paving are the ones that carry the work.
For me, one constraint that has always been there is capacity: client events, client transactions and generating new business, all at the same time.
Inside whichever one it is, look for the smaller limit. If every part of your client experience depends on a person, your business is limited by people's hours. That's fine in the moments that should be human. But look at your team's last week and you'll find tasks that never touched another person and still had to get done. The recording check is one of those. Those tasks are the easiest roads to pave, and paving them gives your people their time back for the phone calls, the check-ins and the personal invitations.
How I protect the time
Paving Season only works if the time actually happens. If you have a work on the business block on your calendar that keeps getting pushed, treat it like a dentist appointment: you don't skip it because something else came up.
Mine is Saturday. My office is six minutes away. I stop for my favorite coffee on the way, a small reward I only get if I go straight to the office afterwards, and I spend two hours putting systems in place or improving them. That's what works for my personality. Yours might be an early hour before you start selling, or an alarm that tells you it's time to start. Evening blocks tend to lose to family time, so plan around that.
Two habits make the block count:
- Decide the road in advance. When you plan your week, pick the one system that would have the biggest impact right now and put that name on the block. A block that just says systems is easy to waste.
- Keep it small and weekly. One hour a week is 52 hours a year. The way I put it to one group: "you're going to pay the price either way." Either you pay in extra hours working around a broken process all year, or you pay in an hour of discipline now.
When paving doesn't pay
This approach has limits, and they're worth naming.
- A road to the wrong place is still a waste. A beautiful system that relieves a step that isn't your constraint feels productive and changes nothing. If it worked perfectly, would you get or serve more business this month? If not, it can wait.
- Some businesses never get a quiet stretch. If that's you, the season becomes a standing weekly block. The principle is the same: build before you need it, a little at a time.
- Roads need upkeep. The recording check exists because storage keeps filling. Every system you build is something to maintain. Build fewer, and keep them working.
- Don't pave over the human moments. The point of the roads is to give your people more time with clients, not less.
Where to start this month
- Name your constraint. Is it getting business or serving it? Write one sentence on why.
- Find one dirt road. Look at last week. Pick one recurring task on that side of the business that never touched a client, or one step that keeps breaking.
- Block the time. Put a recurring hour on your calendar, with the name of that one system on it.
- Finish it before the busy season. One road done beats five started.
Then pick the next road.
If the road you pick is work that only lives in your head, write it down first. I walk through how in You Don't Have a Hiring Problem. You Have a Handoff Problem.
FAQ: building systems before you need them
When is the best time to build systems in a small business? When you have the attention for it, which usually means a calmer stretch, not the week something breaks. If your business never slows down, use a protected weekly block instead.
How do I decide which system to build first? Find your constraint, the one step that caps what the whole business can produce. Is it getting business or serving it? Build the system that relieves that step, and leave everything else for later.
What is the Theory of Constraints? It's an idea from The Goal by Eliyahu Goldratt: a business can only produce as much as its tightest step allows, so improving any other step doesn't change the result.
How much time should I spend working on my business instead of in it? I'd start with one protected hour a week, which adds up to 52 hours a year. Decide in advance which system the hour is for.
Want help finding your constraint and paving the first road? That's the work inside The Leverage Collective, where we install these systems in 90 days for established agents, team leaders and business owners. See if it's a fit
Get the next one. In the newsletter I share the systems I've built, and which ones turned out to be worth it. Join the newsletter
About me: I'm Shoney Ivens, CEO of a brokerage that's produced over $5.4B in sold real estate volume in the last 5 years.
