Vol 1 · Issue 87 · Friday, August 7, 2026

A consultant I know hit about $22K a month and decided it was time to hire.

Smart call. He was maxed out. Every hour he had was booked, which meant the only way up was more hours, and he had run out of those a while ago.

So he hired what he described to me as "a junior version of me." Sharp kid, good instincts, could hold a client conversation. He was going to train him up on delivery, hand off half the client load, and free himself up to go sell.

Six months later he called me. Revenue was up about fifteen percent. His hours were exactly the same. And he was, in his words, more stressed than before he hired anybody.

This happens constantly, and it happens to the people who are doing everything else right.

Try this. Write out everything you did last week. Not categories. Actual tasks. Should take fifteen minutes and it should run forty or fifty lines.

Now go through and mark each one E or D. E for the things that gave you energy. D for the things that drained it.

Then look at which ones you have been fantasizing about handing off.

For most owners, the answer is some mix of both, and a suspicious amount of it is E. The client strategy calls. The interesting delivery work. The creative parts. The stuff you are good at and secretly enjoy.

Meanwhile the invoicing, the scheduling, the follow up, the proposal formatting, the chasing people for documents, the four hours a week of pure administrative sludge, all of that stays exactly where it is. Because it feels too small to hire for. Because explaining it would take longer than doing it. Because it is "only" four hours.

So you hire somebody to do the interesting work, you spend three months training them on the interesting work, and at the end of it you are still doing four hours of sludge a week plus you now have a person to manage.

You did not buy back time. You traded delivery hours for management hours and paid a salary for the privilege.

That is what happened to my consultant friend. He handed over half his client load and picked up hiring, training, reviewing, correcting, answering questions, and worrying about somebody else's output. Net zero on hours, net negative on stress, and now with payroll.

There is a sequence to this and it is not intuitive, because it starts with the least glamorous work in your business.

First: administrative and operational. Scheduling, invoicing, inbox triage, follow up sequences, document chasing, data entry, proposal assembly, calendar management. The sludge.

Second: delivery. The actual work clients pay for.

Third: sales. Last. Genuinely last, and I will defend that in a minute.

Everybody wants to skip to two or three. Here is why one comes first.

Admin work is the easiest thing on earth to document, which means it is the fastest to hand off cleanly. It has clear right answers. The invoice is correct or it is not. The meeting got booked or it did not. You are not training judgment, you are training a sequence, and a sequence transfers in days rather than months.

It is also the cheapest hire you will make, which means you can start at ten or fifteen hours a week instead of betting a full salary on your first attempt at managing someone.

And it hits harder than you think. Four hours of sludge a week is two hundred hours a year. But that is not even the real number, because sludge does not sit in a block. It is scattered in twenty minute pieces across every day, and every one of those pieces costs you the fifteen minutes on either side of it. Killing four hours of admin usually gives back something closer to seven hours of usable, focused time.

Seven hours a week of thinking time is what a strategy hire is supposed to buy you, and it costs about a fifth as much.

This is the one people fight me on, usually the people who hate selling, which is most people.

You cannot hand off sales until you have a sales process that exists outside your head. Not a personality. A process. What you say in the first four minutes, what questions you ask and in what order, how you handle the price objection, how you handle the "let me think about it," what the follow up cadence looks like when they go quiet.

If that lives only in your instincts, then hiring a salesperson means hiring somebody to guess at your revenue. They will develop their own process, it will be worse than yours for at least six months, and every one of those months is leads burned that you cannot get back.

Admin mistakes cost you an apology. Delivery mistakes cost you a client. Sales mistakes cost you clients you never found out you almost had. That is why it goes last, and it is also why Wednesday's piece on documentation matters more than it sounds like it does.

The order is not about importance. It is about how expensive it is to be wrong while somebody learns.

Your first hire should be a contractor at ten to fifteen hours a week. Not a full time employee.

Not because contractors are better. Because you have never managed anybody before, or at least never managed anybody in this business at this stage, and your first attempt is going to be rough. That is not pessimism, it is just the first rep. Everyone's first rep is rough.

Ten hours a week means you find out whether this person and this arrangement work inside about three weeks, at a cost you can absorb without a knot in your stomach. It means you learn to delegate on a small surface area before you do it on a big one. And it means if it does not work, you have a conversation instead of a legal situation.

Then you scale the hours as the trust and the documentation build. Ten becomes twenty. Twenty becomes full time. By the time you are hiring an actual employee you have already learned how to hand off work, which is a skill, and one nobody tells you that you have to learn.

One thing to get right before you post anything. Write the job as a list of outcomes, not a list of tasks. Not "manage the calendar." Instead: "no client waits more than four hours for a scheduling response, and my calendar is never double booked." Outcomes tell somebody what winning is. Task lists just tell them what to be busy doing.

Once you have somebody, here is the handoff that actually sticks. Three weeks, one shape per week.

Week one, they watch. You do the work, they observe, and they write the process doc. Not you. Them. This is the single highest leverage move in the whole sequence, because a person who has never done the task will document the parts you have gone blind to. Your version says "update the client file." Their version says "update the client file, which is the third tab, and if the status is greyed out it means the deposit has not cleared."

You will read their doc and be mildly annoyed at how much detail is in it. That detail is the reason it will work for the next person.

Week two, they do it, you watch. They run the task, you are available but you do not touch. Let them get stuck. Getting stuck is where the doc gets fixed, and a person who worked through being stuck once will not ask you about it again.

Week three, they do it, you check output only. You do not watch the process. You look at the finished thing and you tell them whether it hit the outcome. That is the whole review.

Week four, you check a sample. Then you stop checking.

Hand over one number with the job. Just one. If they own scheduling, the number is something like percentage of inquiries booked within four hours. If they own invoicing, it is days from work completed to invoice sent. One number they can see, that they own, that tells them whether they are winning without asking you.

This is where a lot of handoffs quietly fail. The task moves but the scoreboard stays with you, so the person doing the work has no idea how they are doing and has to keep coming back to find out. That is not delegation. That is supervision with extra steps.

The pieces of the handoff that break most often are the boring ones. Somebody forgets to send the thing, a step gets skipped because it lived in your head, a client gets missed in the shuffle of the transition.

The follow up sequences and internal handoffs are worth automating before you hire rather than after, because you want to hand somebody a job with the repetitive parts already stripped out. Make.com is where I build those, and the rule of thumb is simple. If a step happens the same way every time and requires no judgment, it should not be in the job description at all.

For anything that runs through a pipeline, a real CRM matters more once a second person is touching client records. Go High Level handles that end to end if you want pipeline, follow up, and booking in one place instead of three tools taped together.

And for the relationship side, the part that genuinely is hard to hand off, clay.earth is useful for making sure the context on a client does not live exclusively in your memory of a conversation from March. That context is usually the actual reason you cannot let go of an account.

Write out last week. Mark each line E or D. Then circle every D that happens more than once a week.

That circle is your first job description. Not the interesting work. The circle.

Add up the hours in it. If it is four or more, you have enough to hire against right now, today, at ten hours a week, for less than you probably spend on software.

Then write three outcomes. Not tasks. What is true when this person is doing their job well.

My consultant friend eventually did this. Kept the delivery work he was good at, hired an operations contractor at twelve hours a week for the sludge, and got back about nine hours. He used those nine hours to build a productized version of his service, which he sold ten times over the following year at a margin his hourly work never touched.

The junior version of himself, for what it is worth, turned out to be a great hire. Just a year too early and pointed at the wrong half of the job.

Sunday we close this arc out with the honest test. Whether any of this actually worked, and whether the thing you have built can run for two weeks without you touching it. Most owners fail that test in about four hours, and the way you fail it tells you exactly what to fix next.

Reply with HIRE and I will send you the first hire scorecard. The E and D worksheet, the outcome based job description template, and the three week handoff checklist so you are not making it up as you go.

Talk Soon,
Dan
Dan Kaufman
Founder, Dead Simple Growth and Pinnacle Masters

P.S. If you are sitting there thinking you cannot afford to hire anybody right now, run the numbers anyway. Ten hours a week of decent operational help usually runs less than most owners spend on tools they signed up for once and never cancelled. That is not a reason to hire. It is just a reason to stop letting "I cannot afford it" end the conversation before you have actually checked.