Most people picture a mop bucket, a stack of flyers, and maybe a hand-painted van when they think about a cleaning business.
I get it. I thought about the same things when I was figuring out whether this was worth building.
What I did not picture was a real-time scheduling dashboard, a customer portal with job history and service notes, automated review requests timed to the exact moment a client is happiest, and a hiring pipeline with structured interviews and standardized onboarding that does not depend on me being in the room.
That is Wasatch Cleaners. And it is also the blueprint I used to build everything else.
Here is what treating an unglamorous service business like a technology company actually means, why it works, and what any operator can take from it.
The Mindset Shift That Changes Everything
The cleaning industry has a reputation. High turnover, word-of-mouth scheduling, jobs written on sticky notes, owners who are the business. And to be honest, most of the industry has earned that reputation.
The shift is not about the service itself. Cleaning is cleaning. The shift is about how you think about the business you are building.
When I decided to treat Wasatch like a tech company, I stopped asking “how do I get more jobs” and started asking “what does a scalable, data-driven, repeatable operation look like in this industry?”
That is a completely different question. It produces completely different answers.
Tech companies obsess over systems, feedback loops, and infrastructure. They hire for fit and train for skill. They measure what matters and use that measurement to make decisions. They build things that work without the founder standing in the middle of every transaction.
Service businesses can do every single one of those things. Most just do not.
When your mindset is “I am building an operating system for this category of business,” you stop being a cleaner who owns a company and start being an operator who runs a platform. The difference compounds over time in ways that are genuinely hard to explain until you are living it.
Systems Over Hustle: Why Working Harder Is the Wrong Answer
I am going to say something that will frustrate some people: hustle, by itself, is not a strategy.
Hustle is what you do when you do not have systems. And I say that with real respect for the grind, because I have been in it. Early mornings, late nights, doing it all because it had to get done. That phase is real and necessary.
But staying in hustle mode past the point where systems could replace it is a choice. And it is usually a fear-driven one.
The fear is: if I systematize it, will the quality drop?
The opposite is true. When a process is documented, trained, and checked against a standard, you get more consistency, not less. The quality floor goes up. The best team members rise faster because they are not learning by osmosis.
At Wasatch, every job has a documented protocol. Every new hire follows a structured training sequence before they are solo on a job. Every client interaction follows a communication standard. None of that happened overnight. It was built, tested, revised, and built again.
The result is a business that does not collapse when I am traveling. It does not skip a beat when a team member calls out sick. The systems hold.
That is what you are building when you build systems: resilience. And resilience is the thing that makes a business worth anything to anyone else, including a future buyer.
Software and Data: The Actual Infrastructure
Here is where I will lose some people. Because this part sounds expensive or complicated, and it is neither.
Wasatch runs on real software. Scheduling, customer records, job notes, invoicing, team communication, and performance tracking all live in systems built for this purpose. Nothing critical lives in someone’s head or someone’s phone.
Data is the byproduct of a well-run operation. When you have the right software, you start accumulating signal without even trying: which clients retain, which churn and why, which team members have the lowest re-clean rates, which neighborhoods book most frequently, what the average lifetime value of a customer looks like, and where the leaks are.
That data tells you where to spend your next dollar. It tells you which problems are actually problems and which ones are noise. It makes you a better operator.
And here is what took me a while to fully appreciate: the software you build (or configure, or customize) to solve your own operational problems is not just a tool. It is intellectual property. It is a moat.
When we started documenting every workflow at Wasatch and building software infrastructure around it, we were not just making operations smoother. We were building the foundation for Tidumo, an operating system for cleaning businesses. The product came out of the operations. The operations were the research and development.
That only happens when you are treating data as an asset from day one.
Hiring, Training, and Retention Without Drama
High turnover in service businesses is treated like a law of nature. It is not. It is a symptom of something fixable.
Most cleaning companies hire anyone who shows up, train them by following another employee around for a day, and wonder why they are always short-staffed. That is not a workforce problem. That is a systems problem.
At Wasatch, we built a hiring process with real stages:
- A structured application (not just “call this number”)
- A phone screen with consistent questions
- An in-person interview with a scoring rubric
- A paid orientation and training period before solo work
- A 30-day check-in tied to performance data, not just a gut feeling
Does this take longer than “she seemed nice, she can start Monday”? Yes. Does it produce a better team with lower turnover? Every time.
Retention is the other half. People stay where they feel respected, where the work is predictable and fair, where there is a path forward. That means consistent scheduling, transparent performance feedback, and leaders who show up as humans.
I bring my whole self to this work. My faith, my care for people, my belief that every job has dignity. You cannot fake that, and you should not try. But you also cannot substitute it for structure. People need both: a culture they believe in and systems they can trust.
When you get both right, people stay. And when people stay, the quality of your product improves. The math is simple even if the execution is not.
Customer Experience Is a Product Decision
Most service businesses think of customer experience as vibe. Are the cleaners nice? Does the house smell good when they leave? That is table stakes.
Customer experience, done right, is a product decision. It is designed, not improvised.
At Wasatch, the experience starts before anyone walks in the door. The booking process is clean and fast. Confirmation communication is automated and warm. The team shows up in uniform, on time, with the right equipment. After the job, there is a follow-up that gives the client a real channel to share feedback before they leave a review anywhere public.
Every one of those touchpoints was designed. We asked: what does a client need to feel at this moment? Then we built for that.
The result is a client base that refers people. That stays for years. That books add-on services without being sold to.
Premium pricing becomes defensible when the experience matches it. We are not the cheapest option in the market. We are not trying to be. We are the option that works reliably, communicates clearly, and treats your home like it matters. That is a different product at a different price, and the right clients recognize it immediately.
Word-of-mouth is still the best marketing channel we have. But it scales faster when the experience behind it is consistent, not occasional.
From Operations to a Product: The Flywheel
This is the part that most people miss, and it is the most important part of what I have built.
Here is how the flywheel actually works:
- You build a great operating business. Wasatch runs well. Real revenue, real systems, real data.
- The systems generate data. What works, what does not, where the margin lives, where the friction is.
- You productize the software. The tools you built to solve your own problems become a product for the whole industry. That is Tidumo.
- The productized systems make the original business stronger. Better software means better operations, which means better data.
- You build or buy the next one. The playbook is documented. The systems are transferable. The next business takes less time to get to performance.
This is not theoretical. Every piece of infrastructure I built for Wasatch taught me something I could use for the next brand. Every process we documented became a template. Every mistake we made became a lesson we did not have to pay for twice.
The cleaning business is real and profitable and something I am proud of. It is also the foundation of everything else. That is what happens when you decide, early, that you are building an asset and not just buying yourself a job.
Any business can be built this way. It requires patience and a long view, but the compounding effect is real. What looks like a cleaning company from the outside is, from the inside, a data platform with a mop bucket attached.
What Any Operator Can Steal From This
You do not have to run a cleaning company to apply this. You do not even have to be in a service business. But if you are an operator in any unsexy category, here is what I would tell you to take and use:
Treat your operations like infrastructure. Every process you run manually is technical debt. Document it, systematize it, automate what you can.
Measure what actually matters. Pick three to five numbers that tell you the truth about your business. Track them weekly. Let them guide decisions.
Build your hiring process before you are desperate. Hiring under pressure is how you end up with the wrong people in critical roles. Build the process when things are calm.
Design the customer experience on purpose. Map every touchpoint. Ask what the client needs to feel at each one. Build to that.
Think about the exit before you need it. A business that depends on the owner is not an asset. It is a job with overhead. Build it so it could run, be sold, or be replicated without you.
The businesses that win long-term are the ones that build infrastructure early, even when it feels like overkill. Especially when it feels like overkill.
A Closing Word
I want to be clear about something: none of this was obvious when I started. I made the mistakes. I hired fast and regretted it. I let things live in my head too long. I stayed in hustle mode past the point where it was serving me.
What changed was a decision to see the business differently. To ask bigger questions. To treat every friction point as a design problem and every system as an asset in progress.
That decision has compound interest. And I believe, genuinely, that every operator has the capacity to make it.
If this way of thinking connects with you, I would love to stay in the conversation. Subscribe to my Operator’s Notes newsletter for what I am learning in real time, or come find me on The Broker’s Table podcast, where we go deep on the real mechanics of building businesses that last.
The unglamorous industries are where the real opportunity is. Most people are not paying attention. That is the point.
