I built these systems because I was tired of being the system.

I've spent about 15 years running a painting company in Quebec. I've estimated thousands of jobs, managed crews and foremen, dealt with demanding customers, made plenty of mistakes, and spent a ridiculous amount of time fixing problems that should never have happened.

For a long time, the company worked because I knew everything. I knew which painter was best for which job, what had to be done next, which customer needed a call, where the equipment was, and what would go wrong if I didn't intervene.

That's a useful skill. It's also a terrible way to run a growing company.

The better I got at solving every problem myself, the more everyone needed me. So I started working on a different question: how do I make the problem less likely to happen in the first place?

Our standards had to work with real people.

We worked on high-end homes, where customers expect excellent results. And we built a strong reputation while hiring and promoting people who didn't always arrive with years of experience.

That didn't happen because every painter was naturally brilliant or every new manager somehow knew exactly what to do.

It happened because we became better at showing people what good work looks like, preparing jobs properly, defining responsibilities, checking quality, and catching mistakes before they became expensive.

We wrote down procedures. We standardized work orders. We started tracking labor budgets while jobs were still running. We organized the equipment. We prepared upcoming jobs before a crew needed them. We gave foremen real authority, then checked the results of their work.

People still made mistakes. I still made mistakes. When something failed, we asked why, corrected it, and improved the routine.

Over time, the business became easier to operate. We weren't relying on one person remembering every detail, and inexperienced employees had a better chance of doing excellent work because the expectations were clear.

Simple to use. Complicated to design.

I have no interest in procedures for the sake of procedures.

If a whiteboard fixes the schedule, use a whiteboard. If a checklist keeps the crew from forgetting equipment, put that checklist on the work order. If a small spreadsheet shows which jobs make money, use the spreadsheet. If software or AI is genuinely useful, use that too.

The objective isn't to make the company look sophisticated. It's to make the company function.

But simplicity takes work. Somebody has to understand the details, deal with the exceptions, decide what belongs in the procedure and what doesn't, and test whether people can follow it on a busy day.

That's the part I enjoy. I like taking a messy process apart, figuring out how it really works, and putting it back together as an ABC system that people can use without needing me to explain it every morning.

Simpler is smoother. But somebody has to do the complicated thinking first.

What changed in my business

There were years when we went over labor budgets far too often. In one exterior season, our crews averaged about 25% over their estimated labor hours. The following season, with most of the same painters, we averaged about 10% under.

We didn't solve that by telling everybody to work harder. We improved estimating discipline, made budgets visible, clarified the foreman's job, checked production regularly, and rewarded good results without letting quality slide.

We made similar changes to job preparation, materials, customer communication, scope control, estimating, and scheduling. Some worked right away. Others took several rounds of correction. A few ideas failed completely.

I still had responsibilities. This wasn't some magical self-running company. But far fewer things needed my constant attention, and that changed both the operation and my life.

Why I'm doing this now

After years of building these systems for my own company, I want to help other painting contractors solve the problems that keep consuming their time and money.

I've put the case studies and many of the procedures out in the open. Read them, borrow ideas, adapt what works. If you want help figuring out which problem to tackle, designing the right system, or making sure your team actually uses it, that's the work we do.

The goal isn't to make owners dependent on a consultant. It's to make the operation less dependent on any one person.

A note on AI

Yes, AI helped write this website. Obviously. I spend my time figuring out the best way to get things done. Why wouldn't I use a tool that makes writing faster and clearer?

I'm a business operator, not a professional writer.

My role is to provide the substance. The ideas, observations, experiences, problems, solutions, and reasoning come from me and my years of running a business.

I explain what happened, what I tried, what worked, what failed, and why I do things the way I do. I challenge the output, correct inaccuracies, add missing context, and review the final content to make sure it accurately represents my thinking.

AI's role is to organize and communicate it. It helps structure my thoughts, improve clarity, eliminate repetition, and turn my sometimes scattered explanations into coherent, readable articles.

The machine doesn't have my experience. It hasn't managed my employees, dealt with my customers, or solved my operational problems.

I have.

The thinking is mine. The writing is assisted. And I take responsibility for what's published.