Previous TutorialThe lead filled in your form on Saturday and nobody knew until MondayCRM with workflow builder (e.g. GoHighLevel)Next TutorialYour calls end and nothing happens until you remember themFathom
All tutorials

Revenue is up and the week feels heavier than it did three years ago

6 minutes

Revenue is up and the week feels heavier than it did three years ago

Time
6 min
Level
Beginner
Steps
Read through
You need
None. Pen, paper, your card statement

The drag you feel isn't discipline slipping. It's tools, approvals and decisions that were each added for a reason and never removed. Here's how to find them.

# Revenue is up and the week feels heavier than it did three years ago

You are billing more than you were three years ago. You are also finishing later, saying "let me check" more often, and paying for software you cannot fully name off the top of your head.

That is not a character problem. It is an accumulation problem, and it has a shape you can go and look at.

## Nothing broke. Things were added.

In year one you had a phone, a spreadsheet and one place client work lived. Every decision fit in one head, and that head was yours.

Then a lead got dropped, so you bought a CRM. A file got lost, so you added a second place to store files. A handoff went wrong, so you added an approval step. A staff member left, so you added a checklist for the next one.

Every one of those was the right call on the day it was made. None of them were ever reviewed after. The cost of a good decision made in 2023 is still being paid in 2026, by everyone, on every job.

This is the part people get wrong: the drag is not the result of bad decisions. It is the result of good decisions that nobody was assigned to undo.

## The three places it hides

**Tools.** Not how many you pay for, but how many places the same fact lives. When a client's phone number exists in the CRM, the invoicing tool, a spreadsheet and someone's phone, every update is four updates, and three of them will not happen. The question is not "which tool is best". It is "where does this fact live, and which copy is the one we trust".

**Steps.** A step that was added to prevent a specific failure, still running long after the person who caused the failure left. Approvals are the usual suspect. So is anything described as "just to be safe".

**Decisions.** The ones that come back every week and get made fresh every time. Which job gets the last slot this week. Whether this discount is allowed. Whether we take this client. Each one is small. Made weekly, unaided, by the owner, they are the reason you are tired at 4pm and not at 7pm.

## How to actually find yours

You cannot fix this by thinking about it in the car. Two things that produce evidence instead of a feeling:

Open your card statement and list every software charge from the last three months. Next to each, write the name of the person who opens it weekly. The ones with no name are your answer, and there are usually more of them than you expect.

Then take one job you delivered last month and write down every step it passed through, including every "send it to me first". Not the process as designed. The process as it actually ran. The gap between the two is where the week goes.

Neither of these takes a consultant. They take an afternoon and a willingness to see the list.

## Where this advice stops being true

Cutting is not automatically good, and "simplify" is easy to say from outside your business.

Some of that friction is the only thing holding quality together. An approval step that looks like bureaucracy may be the reason a bad invoice has not gone out in two years. A second system may exist because the first one genuinely cannot do the thing. If you remove a step and cannot say what failure it was originally preventing, you are not simplifying, you are gambling.

The honest version of the rule is narrower than "remove what you can": remove the thing whose original reason no longer exists, and keep the thing whose reason you can still name. That is slower work than a purge, and it is the only version that survives the following quarter.

And there is a case where none of this applies. If the week feels heavy because you have more work than people, this is not your problem. Complexity drag and being short-staffed feel identical from the inside and have opposite fixes. Count the steps before you conclude you need a hire, and count the hours before you conclude you need a cleanup.

## What changes when you do it

The realistic outcome is not a transformed business. It is that the next new client does not add a full day of overhead, because there are fewer places for their information to go and fewer people who have to be told.

That is what "lighter as it scales" actually means in practice. Not fewer hours this week. Less weight added by next year's growth.

---

If you want a second pair of eyes on the list you come up with, that is a conversation we have with owners regularly. [Book a call](/book-a-call).

Would rather we just did it?

Send it over as a fuel request and our team will take it from here, or book a call and we will walk it with you.