Is Your Business Too Unique for Systems?
Rarely. What makes a firm distinctive usually sits in a handful of decisions and client relationships, while most of the week repeats the same shapes every service business runs. Protect that distinctive part, write down how the repeating work gets done, and the business can stop needing you for both.
The owner of a seven-person firm sat with a blank pad and said, before we started, that their delivery was unlike anyone else's. He meant it as a reason to skip systems. We listed recurring tasks for two hours anyway. We got to 38.
Five were truly custom: the judgment calls only he could make on scope, pricing for oddball work, and two client relationships that depended on his name. The other 33 were versions of work every service business runs: how a lead enters, how a job gets scheduled, how a change request is logged, how an invoice leaves, how a callback is owned. He had been protecting all 38 as craft. Only five needed that protection.
Owners in very different industries say the same sentence: "Our business is too unique for systems." I used to argue with that. Now I agree with part of it. Unique is real. It is also small. In the lists I've run with firms of five or more people, the custom slice lands near that five-of-thirty-eight split, not half the week. The rest is intake, scheduling, follow-up, handoffs, exceptions, and money moving from quote to cash. That work looks different in a trades company than in a professional firm, and it is still the same shape. Treating 100 percent of the week as unique is what keeps you the bottleneck.
Why does "too unique" keep you the bottleneck?
When everything feels special, you never write the common path. You stay in the exceptions. Your team learns that the only safe move is to ask you. Standards never form because every job is framed as a one-off. Audits never happen because there is nothing to audit against. Failures sit unnoticed for weeks because "we don't do it that way here" covers the gap.
The more you insist the whole business is unique, the more ordinary the failures look when you finally map them. Missed follow-ups. Unowned exceptions. No standard for "done." Same gaps I see in firms that sell completely different things. The label changes with the industry. The hole does not.
How do you sort unique work from common work?
Do not start with software. Start with a sort.
List about 40 recurring tasks. Not projects. Recurring. Things that happen weekly or monthly whether you feel like it or not.
Tag each one in plain language:
- Custom means only this business, only this offer, or only you, so leave it alone for now.
- Common means intake, scheduling, follow-up, handoffs, billing, callbacks, so systemize these first.
- Judgment means a human call that can still follow a rule, so write the decision rule, not a 12-page SOP.
A larger team may show even more Common than you expect. If your list comes back 30 Custom, you are still protecting identity, not describing work. Re-tag with a harsh filter: if another firm in a different industry does a version of this, it is Common. When a tag sticks, ask it out loud. Tag Common and write the standard when another industry does a version of it; tag Judgment and write the rule when a trained lead could decide with one sentence. Tag Custom only when the customer is buying your name or your taste, and keep that list short.
Map with one cut only. By department, or by role, or by function. Mixing "Yard Operations" and "Receptionist" as top-level buckets creates a tangle you will abandon by week three. Pick one lens and stay on it long enough to see the gaps: no written standard for what good looks like, no audit that checks the standard, failures that sit for two or three weeks because nobody owned the check. You are not erasing craft by naming those gaps. You are stopping craft from covering the shared work that should not need you.
Writing those standards down is only half of it; SOPs vs an operating system explains why documents alone rarely change how work runs.
What goes wrong in a first sort?
An owner I worked with did the 40-task list in one sitting and tagged 22 items Custom. He was proud of it. We walked the list out loud. "Confirm next-day schedule with the field" was Custom because "our jobs are complex." That is Common with a Judgment rule for weather and parts. "Send the invoice within 48 hours of completion" was Custom because "our billing is weird." The weird part was two exception clients. The path for everyone else was Common.
We retagged. Custom dropped to six. He systemized Common first: a one-page intake checklist, a scheduling handoff with three required fields, a follow-up rule for quotes older than seven days. Judgment got decision rules: if the change adds under 10 percent to the quote and does not move the finish date, the lead approves; otherwise it comes to him with a recommendation attached.
Week four he tried to systemize one of the Custom items anyway, a proposal format he treated like a signature. The team produced stiff, identical proposals that lost two deals he would have won with his old messy version. We pulled that item back to Custom and left it. The win was not documenting his voice. The win was stopping him from claiming the invoice path was his voice too.
That failed attempt matters. Systemizing the product itself, or the craft people pay you for, is how you get brittle work and a team that sounds like a template. Systemize the path around the craft. Leave the craft until you have a different problem.
Under about three staff, a full 40-task sort can become theater anyway; a short list of who owns what and one weekly check is enough until handoffs actually break. Skip the exercise when cash is the crisis this month, or when you are tempted to document the proud craft first and leave invoice follow-up a mess. Stabilize money, systemize the admin around the art, and save the long sort for when the team is big enough that shared work actually stalls.
For what the owner has to put in once the sort turns into an install, read what installing systems asks of you.
How do you run the sort yourself?
- Block 90 minutes. Phone down.
- Write the 40.
- Tag fast, then retag once with the harsh filter.
- Circle the ten Common items that cause the most pings or the most rework.
- Build the lightest possible standard for those ten: what "done" means, who owns it, how it gets checked.
For Judgment items, write the rule in one sentence plus the escalation line. "If X, decide. If Y, bring me a recommendation by Thursday." Do not write a novel.
For Custom, write the name of the person who owns it today and leave it. Revisit in 90 days. Some Custom items become Judgment once you have language for them. Some stay yours forever, and that is fine if the list is short.
A useful check: if you disappeared for five workdays, which of the 40 would stall. If more than a handful would stall, you still have Common work living in your head. Do the check honestly. The items that would stall are usually the ones you have been calling unique because nobody else has a written path yet.
Owners stall the sort when they want the tags to feel flattering, or when they mix tools into it. I watched a firm rename a welcome email, a kickoff call, a shared folder, and a 30-day check-in into a "unique" onboarding sequence. Writing who owns each step and what "done" means cut their onboarding pings from about nine a week to two.
Another owner promised twelve screen recordings before we could map anything and delivered two. We ran a co-working session, pulled the rest live in 90 minutes, and moved on. He still has not switched platforms. The Common path is visible now. The tool change is still "next quarter," and the map has not died waiting for it.
Record the current path first. Tool changes later. Waiting for perfect capture is how Common stays invisible. The question left on his whiteboard that day was not which software to buy. It was which of the ten Common items he would finally put a name and a check next to before Friday.
Frequently asked questions
What if my clients say they hire us because we're different?
Ask them what, specifically. Their answers usually point at a person or a standard of finish, and rarely at how invoices go out. Keep whatever they name in the Custom pile with its owner, and make the paths around it dependable, since late paperwork wears down the same reputation that brought them in.
Can the work only I can do ever be handed off?
Some of it. Each time you make one of those calls, write a line on why you chose as you did. Over time the reasons tend to repeat, and a repeated reason can become a limit or a rule a trained lead can use. Whatever still resists a rule after that is worth keeping.
What if my team tags the list differently than I do?
Compare the two lists first. Where your team calls something Common that you tagged Custom, ask what they would need to run it, since they often see a repeat you have stopped noticing. Where they tag something Custom, it is usually a step only you have ever explained. Either gap is a line to write down.
How much of your week is really custom?
If you want help sorting Common from Custom without turning it into a binder nobody uses, start here: systemstoscalegroup.com/getstarted
