Done-For-You vs Doing It Yourself: What It Really Takes

Doing it yourself fits when a capable operations person can carry the build, the target is narrow and you can protect four or five hours a week. Bring in help when those are missing or a past attempt faded. Either way, agree who owns which part before anyone starts.

I sell one of the two options in this post, so you should discount my opinion accordingly. What I can do is lay out the real costs of each route and the checks that tell you which one fits, and let you decide whether I've been fair.

What are you actually choosing between?

Both routes aim at the same result: a business that keeps selling, delivering and billing when you're out of reach. The method underneath is the same too. You list what would stop moving in a week when you're unreachable, then what else would slip over a month. Each item on that map gets a system at its center, meaning an owner, a written line for what they decide and a way to see that it's working. You work the map in order of revenue risk, beginning with whatever holds up a quote or an invoice.

The choice is about who does the building and how much of your week it uses. On the doing-it-yourself route, you run the interviews, write the rules and hold the rollout together while still running the business. On the done-for-you route, which is the side we offer at Systems to Scale, someone else carries most of that work and you keep the parts that only an owner can do.

How many hours does doing it yourself take?

People tend to picture DIY as "write some procedures." In practice it has stages, and the hours add up in places you don't expect. These are my planning estimates for a team of eight to fifteen, based on how these projects tend to go, not measured data, and your numbers will differ.

1. Find out what depends on you. What it involves: Two-week tally, sorting it, picking the first five decisions. Rough hours: 3 to 4.
2. Learn how the work actually runs. What it involves: Six or seven short interviews with the people who do it. Rough hours: 5 to 6.
3. Write the rules for the first five decisions. What it involves: Limits, outcomes, escalation format, checking edge cases with staff. Rough hours: 15 to 20.
4. Roll it out. What it involves: Telling the team, then redirecting questions you'd normally have answered, a few minutes at a time for about four weeks. Rough hours: 8 to 10.
5. Review and adjust. What it involves: Half an hour a week for eight weeks. Rough hours: 4.

Total rough hours: 35 to 44, over 8 to 10 weeks.

That's four to five hours a week. It doesn't sound like much until you look at a week that already runs fifty-five hours and is mostly interruptions. The harder question is where the hours come from. If the honest answer is evenings and weekends, the project will start well and fade in the third week, and that is the most common way I've seen DIY end.

The hours aren't even the hardest part. You're the person who has to step back and the person doing the stepping back, and you're badly placed to see your own dependencies. A decision you make on autopilot doesn't register as a decision, so it never appears on your list. Someone else asking "how did you know to say no to that?" is often what surfaces it.

What does done-for-you actually cover?

A person I know who runs a done-for-you service told me about an engagement that went badly, and when he looked closely the cause wasn't the work. He and the client had never agreed who owned what. The client assumed everything would be handled. He assumed the client would lead the rollout with their own team. Neither said so, and both were disappointed.

It's why I'd insist on spelling out the split before starting anything of this kind.

Someone else can:

• do the interviewing
• draft the rules
• build the tracker
• keep the calendar
• notice when you've answered something yourself that you'd agreed to hand off

Only you can:

• decide the limits
• tell your team the new rules are real
• hold the line when somebody asks you anyway
• answer escalations within the day

A provider can't do those for you, and anyone who says otherwise is selling something that won't hold. If you read the split and feel relieved at the first column and reluctant about the second, that tells you something too.

Which four questions tell you which route fits?

1. Can you find four or five hours a week that don't come out of your evenings, weekends or sleep? If you can, DIY is realistic on hours. If not, the plan will probably fail on arithmetic.
2. Have you taken your team through a change before and seen it stick for three months? If you have, you know how to do the hardest part. If your history is a string of new tools and procedures that faded, don't assume this one is different.
3. Is there somebody senior who would lead the rollout alongside you? A capable second-in-command changes the odds a lot, because they can enforce rules on days you're out.
4. When you learn something useful, what do you do with it? This is the one people skip. One owner told me plainly that her pattern was to take in a lot of information and then not act on it, and she asked for a week-by-week plan with someone checking in. It's more common than people admit. If you've watched the videos, read the books and nothing changed, more information won't change it either. Structure and someone else's calendar might.

When is doing it yourself the better choice?

If you have a capable operations person, a narrow target such as one or two decision types, and a team of eight or fewer, I'd usually say do it yourself. Start with the tally, write one limit, and tell the team this week. Paying someone to help with a job that's small enough to finish in a month is poor value. The same goes if your real problem is cash flow or a bad hire, since rules won't fix either, and you'd be better off dealing with those directly first.

When does neither route work yet?

If your only help is a part-timer, there's nobody to hand decisions to, and the work is deciding which role to fill first. If the business is in an active crisis, such as a cash shortage or a key resignation, systems work will lose to the fire every time. And some owners, if they're honest, don't want to let go of certain things, which is allowed. The work is to decide which things you're keeping, deliberately.

What mistakes sink either route?

The same few show up whichever way you go.

1. Starting with the team's procedures. Documenting how the front desk answers the phone feels productive and gives you no time back if that work never needed you. Start where work waits on you, as I lay out in how to systematize your business.
2. Handing off the whole map in one go. Ten half-built systems leave a team checking with you more than before. Finish one item before opening the next.
3. Calling it done when the documents exist. A written procedure with no owner and no exceptions rule keeps sending the unusual cases to your phone, which is the gap I describe in SOPs vs an Operating System.
4. Taking items back. If you step in each time someone handles something differently, the team learns that asking you still works, and the build stalls on either route.

Can you try DIY first and switch later?

If you're torn, try DIY for three weeks with a test written down in advance. By the end of week three you should have one written rule that people are using, and your tally for that decision type should be lower than when you started. If you have both, carry on alone. If you have neither, you've learned that the obstacle is probably time or follow-through rather than knowledge, and that's the point where outside help earns its place. If you'd like to talk it through, you can book a Planning Call, and I'll tell you if I think you should keep going alone.

What does done look like on either route?

The map you started with has an owner beside every item, and the items that touch revenue were finished first. Quotes, approvals and invoices move on days you're unreachable. A planned week away comes back with a short list of things that slipped, and the next round of work comes from that list. If you'd like to see what the done-for-you side asks of your calendar, what installing systems asks of you sets it out, and what owner dependency costs helps you put a number on staying where you are.

Frequently asked questions

Is done-for-you the same as paying someone to write SOPs?

It shouldn't be. A stack of documents written by an outsider leaves the exceptions with you. Done-for-you in the sense I mean happens inside your team: the provider interviews the people doing the work, drafts the rules with them and helps run the rollout, while you set the limits and keep the final say.

Can my operations manager lead the DIY build?

Often, yes, if two things are true. They need protected hours that don't get eaten by the work they already do, and they need authority you've backed in front of the team, so a rule they enforce on Tuesday doesn't get overturned by you on Wednesday. Without both, the build quietly comes back to your desk.

Still not sure which route fits?

If you're still weighing it, a Planning Call is a short conversation about which route fits your business. We'll look at your map, your hours and your team, and you'll leave with a recommendation either way.

Book a Free Call