The Effort Ceiling

Bradley Hamner describes a familiar response to problems in his business: work longer. More days, more hours, fewer periods when he was unavailable. It helped him keep things moving, but left him with an uncomfortable question about growth.

I realized that for me to double this business, to go from 750 to 1.5 million, or from 1.5 to three, I can't double my effort. So something has got to change.

The revenue figures in that question describe the growth he was contemplating. His point is about capacity. A plan that requires twice as much of a person who is already fully occupied has an unresolved assumption at its center.

Look for work that repeatedly comes back

A founder's calendar is a useful place to start. Which tasks recur? Which exceptions require the same explanation? Which decisions reach the founder because nobody else knows what a good answer looks like?

Some of that involvement is valuable. A difficult hire, a major customer relationship, or a consequential investment may deserve the founder's attention. The problem is when ordinary work competes for the same time because the company has never agreed how it should be handled.

Pick one recurring process. Follow it from the first request to completion, including the points where someone waits, checks, or repeats a step. The aim is to understand the work before trying to speed it up.

Make the process clear before automating it

Thomas Morales draws a useful distinction between making work reliable and automating it.

Automation isn't the end goal. Systemization is. If you can automate something, that's beautiful, but we often can't or we shouldn't. So then the thing we want to actually try to do is we systemize.

For a recurring job, the team needs to know what starts it, who owns it, what a completed result looks like, and when an exception needs help. A short working document can be enough. It should reflect the way the job actually gets done and be easy for its owner to correct.

Then test the handover. Let someone else use the instructions on a real piece of work. The questions they ask will expose more than a founder reading their own document and deciding it is clear.

For example, an account lead can renew a customer on existing terms. A request for a lower price or different payment terms goes to the designated approver. Agree those boundaries before handing over the work.

Software can help once those choices are understood. Automating an unclear process may simply produce the same confusion more quickly and make it harder to see where it began.

Plan for the capacity people actually have

Yvette Owo's account of managing businesses alongside health constraints makes the capacity question concrete. Availability is not a constant. A company needs a way to keep important work moving when a key person has less time than the plan assumed.

For each essential process, identify who can cover it and what can wait. If there is no cover, make that dependence visible and decide whether to reduce it. A plan that names this limit gives leadership a choice before an absence forces one.

This does not mean documenting every activity or removing the founder from work they do well. Young businesses often need direct involvement while they learn what customers want. Procedures are most useful where the work repeats and the company already understands the result it needs.

Choose one such process and give it an owner, a usable description, and a review date. The evidence of progress is straightforward: it gets done to the agreed standard without returning to the founder each time. That creates capacity the next growth plan can actually use.