What Are the Three Parts of a Business That Runs Without You?

Every business that runs without its owner is built on three parts: the right product, a documented process, and the right people — and it is always the people that decide whether the other two survive. I'm Christian Saab, founder of CPG Recruitment, and since March 2020 my team has built teams across 25+ industries in Canada and the US. I left a six-figure engineering job at 24 to build companies, and engineering is where I learned to look at a business the way you look at a machine: inputs, steps, output. They don't teach this in business school. A factory floor teaches it in a week.

What are the three parts of the formula?

The three parts are product, process and people — listed in ascending order of how hard they are to get right. Product is the technology or service you actually deliver. Process is the documented, repeatable set of steps that turns that product into a result for a customer. People are the ones running the steps. Two of those you can buy with money. The third you have to find, and finding is a completely different skill than buying.

Most owners spend 90% of their attention on the first two, because the first two respond to effort in a predictable way. You research a tool, you buy the tool, the tool works. You write the process, you post the process, the process exists. People don't behave like that, which is exactly why people are where businesses quietly fall apart. If you want the wider version of this argument, I've written about the two engines every business needs to grow — sales and talent — and this formula is what sits underneath the talent side.

Why is the product the easiest part to fix?

Product is the easiest part to fix because it is a purchasing decision. If your software is slow, there is a faster one. If your equipment is outdated, there is a supplier who will sell you a better one on Tuesday. If your service offering is too narrow, you can widen it. These are problems you can solve with research, a budget and a weekend.

That is also why product is the part owners keep going back to. It is the part where effort reliably produces a result, so when something feels broken, the instinct is to go shopping. I have watched businesses buy their third CRM in four years while the actual problem sat in a chair on the second floor.

What does a documented process actually look like?

A documented process is one where a person who has never done the job can open the file and do the job. That is the whole test. It is not a bullet list on a whiteboard, and it is not "Dave knows how to do it." It is step one, step two, step three, with the decision points named and the outputs defined.

In recruitment, that is the difference between a search that drifts and a search that closes. Our process starts with a recruitment launch meeting before a job is ever posted, and everything downstream is written: who screens, what gets asked, what happens after each stage. Documenting it is a large part of why we cut average time-to-fill from 68 days to 37. The process didn't get smarter. It stopped living in somebody's head.

Here is the honest version, though: a written process only removes ambiguity. It doesn't create judgment, effort or honesty. It assumes those.

Why are people the Achilles heel of every system?

People are the Achilles heel because they are the only part of the system with their own judgment. Software does what you configured it to do. A process does what the document says. A person decides, every single morning, whether to follow it — and nothing in your tech stack overrides that decision.

Best software. Best process. Wrong people. Everything crumbles. I have seen it with clients who had genuinely excellent systems, the kind you'd put in a case study, running at a fraction of their capacity because two roles were filled by people who were never going to run them properly. The system wasn't wrong. The system was unattended.

What happens when you run a great process with the wrong people?

You get the appearance of a system and none of the output. The steps get skipped quietly. The CRM gets updated at 4:55 on a Friday with whatever will pass. Handoffs get made verbally so there is no record of them. From the outside, the dashboard still looks like a business. From the inside, nothing compounds.

The bill for this arrives later, and it is bigger than most owners expect — I've broken down what a bad hire actually costs a business, and the salary is the small part. The expensive part is the six months of a broken system that you spent diagnosing as a software problem.

How do you hire for a system instead of for a seat?

You hire for the system by defining who the system needs before you define the job title. A documented process tells you something a job description never will: exactly which decisions this person will own, what they receive, what they must produce, and where their judgment replaces a written rule. That is your real hiring brief.

Then you raise the bar to match. The fastest way to check whether your bar is high enough is to ask yourself whether you'd re-hire the people already doing this work — I've written about what to do when the answer is no in are your hiring standards too low. Across 25+ industries, the businesses that scale are not the ones with the best tools. They are the ones that refused to fill a seat quickly and cheaply because the seat was load-bearing.

How do you know which of the three is actually broken?

Ask which one you changed last. If output dropped and nothing about the product or the process changed, it is people — either the wrong person in the seat, or the right person with no accountability. If output has never been good, it is probably process, because there is nothing for anyone to execute consistently. If customers complain about the thing itself rather than the experience of getting it, it is product.

Run that diagnostic honestly and you will usually land on people, which is uncomfortable, because it is the answer that cannot be fixed with a purchase order. It is also the one that pays back the most. Fix the product and you get a better tool. Fix the process and you get consistency. Fix the people and the other two start running themselves.

Frequently Asked Questions

Can good people fix a bad process?

Good people will carry a bad process for a while, and that is the trap. They compensate, they patch, they remember the steps nobody wrote down — and the business looks fine until they leave, at which point everything they were holding up falls at once. Strong people buy you the time to document the process. They are not a substitute for having one.

Should I document my process before I hire, or hire first?

Document first, even roughly. You do not need a polished manual, but you do need to know what the role actually owns, because that is what you interview against. Hiring before you can describe the work in steps is how you end up evaluating candidates against a standard that only exists in your head and changes with every interview.

Does this formula apply to a two-person business?

It applies harder. In a two-person business, one wrong hire is 50% of your people layer, and there is no depth to absorb it. Smaller teams get less margin for a hiring mistake, not more, which is why the owners who can least afford a long search are usually the ones who most need a structured one.

What should I audit first if all three feel broken?

Audit the people layer first, because it is the one that will distort your reading of the other two. If the wrong person is running a process, you cannot tell whether the process works. Get the seat right, then measure the process, then decide whether the product needs anything at all. Most of the time, by step three, it doesn't.

Where to start

If you have the tools and the documentation and the results still are not there, the gap is almost certainly in the third layer — and that is a fixable problem, not a permanent one. Book a recruitment consultation with CPG Recruitment and we'll look at which seats in your business are load-bearing and whether the people in them can carry the system you've built. You can also see how we run employer searches at CPG Recruitment for employers. For the company-side version of this article, written for operations leaders scaling a documented process, read why documented processes fail when the people are wrong.