Skip to content

Early access, 25% off, until the course opens November 2.

Get your seat for $299

Field notes

The Three Systems You Need Before $1M (And What Breaks Without Them)

The three systems a home service business needs before $1M: a written job flow, honest hours against job revenue, and an owner who stops being the bottleneck.

Published September 27, 2026

The jobs may be there. The crew may be there. But dispatch changes, job questions, approvals, and tomorrow’s schedule can still land on one phone.

If you are asking how to scale a home service business, start with what still routes through you.

Three breaks show up quickly:

  • The same common job is done differently depending on who runs it.
  • Paid time is recorded, but the time tied to each job is unclear.
  • Routine decisions wait for the owner.

Build the systems in order. First define the work. Then measure the time in that work. Then hand off repeat decisions. Each system creates one artifact you can make this week.

System 1: Write down the job you run most

Start with one written job flow for the service or install your crew runs most often. This is not a binder project. It is a short standard someone can use tomorrow.

Say the job is a water-heater swap. Write five or six steps:

  1. Arrive, confirm the scope, and note what is different.
  2. Check the required conditions before starting.
  3. Photograph the key before-and-after points.
  4. Complete the work and test the result.
  5. Show the customer what was completed.
  6. Record what changed or needs escalation.

Beside every step, write what good looks like. For the test step, name the result that must be confirmed before the tech leaves. Add one exception path: stop, document the condition, and contact the named person.

Use the same page as a training standard. List what a helper must demonstrate before doing each part without supervision. That gives the crew a visible next rung tied to the work itself. The Toolbox for the Trades episode on process optimization covers documentation, training systems, and career paths.

Without a shared flow, each new person learns from whoever is nearby. You have no common definition of the work to measure or hand off.

System 2: Track hours honestly against the job

Your artifact is one week of job-level time. Have the crew clock in when work on a job starts and clock out when that work ends. Put those hours beside the revenue from those jobs.

Sales per hour is revenue for the selected work divided by the hours recorded against that work. It is your observation, not a target to copy from another business.

For example, three techs with 40 paid hours each add up to 120 paid hours. Pull the billed revenue for the jobs those hours supported and divide it by 120. Then mark the hours spent driving, at the shop, or returning for a part. The useful question is where the time went, not whether your number matches anyone else’s.

The Masters of Home Service episode on time tracking describes accurate tracking as a way to clean up payroll, reduce unbillable hours, and make decisions using Sales Per Hour.

Without this system, payroll can be accurate in total while the work behind those hours remains unclear. Start with one honest week before trying to explain a month.

How to tell which system is breaking now

Ask three questions:

  • When a good tech is unavailable, can another person run the same common job from a written flow?
  • Can you match last week’s paid hours to the jobs and revenue those hours supported?
  • Which routine decision waited for you this week even though someone else could have made it within a clear boundary?

If the first answer is no, begin with System 1. If the second is no, begin with System 2. If the third keeps happening, prepare System 3.

The systems are ordered, but the questions expose the immediate leak. Cleaner time tracking does not define an undefined job. Delegation is fragile when the standard and limits are unclear.

System 3: Hand off one repeat decision

Make one decision-handoff card this week. Write the decision, the person who owns it, the boundary, and when it comes back to you for review.

For example: “A lead tech can approve a standard job within the range I set. Bring it back to me when the work falls outside that range.”

Other repeat decisions may include resequencing tomorrow’s schedule when a job runs long or ordering standard stock under an owner-set limit. Start with only one. The point is to make a repeat decision predictable, not to disappear from the business.

This is the shift from operator to manager: you set the standard, limit, and review point; another person acts within them. The Scale Past $1M episode names stepping out of daily decisions, training a team to quote and invoice in the field, and building simple documented processes that get used.

Without this system, growth adds more requests to the same phone. A handoff works only when the decision, owner, boundary, and review point are named.

Do this week

Tonight, write five or six steps for the job your crew runs most.

This week, record actual job hours and put the total beside the revenue from that work.

Before Friday, make one decision-handoff card and name who owns it.

Do the one that matches your diagnostic first. Do not try to build all three at once when the first failure is obvious.

Keep going

Want to talk through what you just read?

Tell us how your business runs today, and we’ll talk through how this applies to it.