Every owner we talk to who’s been burned tells the story the same way. There’s a pause, a small laugh that isn’t really a laugh, and then something like “we tried that once.”
October seems like the right month to collect a few of them. All of these came from conversations with business owners over the past several months. Names and industries are gone, and everyone involved survived. Mostly.
The one who vanished
A design firm needed outside help and tried four times to find it. The fourth was the memorable one. Work was underway, deadlines were live, and the person simply stopped replying. No handover, no files, no explanation. The owner eventually accepted that the work was gone and started over.
Four attempts is what makes this a horror story rather than bad luck. By the end, the team had spent more time recruiting and re-briefing than the work itself would ever have taken.
The one who quit mid-project
Another owner had a contractor step away partway through a project. To her credit, she refunded what she’d been paid, which is more than many would do.
The refund didn’t help much. The money was never the expensive part. The project had a date attached, the date didn’t move, and the owner absorbed the work herself while looking for a replacement.
The one who needed teaching
One owner told us he ended a working relationship after a couple of months because he’d spent the entire time training someone in things she should have arrived knowing. The tasks weren’t exotic. They were the standard motions of his industry, the vocabulary and the rhythms that anyone working in it would recognize.
He described the experience as hiring help and getting homework.
The one who was really an internship
A version of the same story, with a longer arc. An owner spent months teaching a junior hire his business, his clients, his systems and his standards. It worked. She got good.
Then she left, taking everything he’d taught her to the next place. He’d paid for the privilege of training someone else’s future team member, and he was back at the start with nothing documented.
The one whose emails he had to rewrite
An overseas assistant was hired for a communications-heavy role. The work itself was fine. The written English was not quite right for the audience, so every outgoing message needed the owner’s eyes on it before it went anywhere.
He didn’t say a word against her. She was capable and she was trying. The role just needed a level of written fluency that hadn’t been tested before she started, and checking every email cost him more time than writing them would have.
Honorable mention: the agency that ghosted the client
One owner described contacting a staffing agency, having a conversation, and then hearing nothing. No follow-up, no proposal. He’d gone looking for help and couldn’t even get someone to sell it to him.
What actually went wrong
Read those back, and one thing stands out. None of them involve a bad person. Not one of these owners described someone lazy or dishonest. The designer who disappeared was probably drowning somewhere else. The contractor who quit refunded the money. The assistant who needed teaching was willing, and the one who left had become genuinely good.
Every one of these is a mismatch that nobody checked for in advance.
Here’s what would have caught each one.
Vanishing and quitting mid-project. Both are continuity failures, and they’re the reason we don’t place individual freelancers and walk away. When someone becomes unavailable, whether they give notice or not, there has to be someone else who can pick the work up and a record of where things stood. If your arrangement has no answer to “what happens if this person disappears on Tuesday,” that’s the gap. The planned version of the same problem, where someone gives notice and you still lose what they were holding, is covered in when your right hand steps back.
Arriving without the basics. This one is a scoping failure before it’s a hiring failure. If the work requires fluency in your industry, that has to be tested rather than assumed, and it has to be in the brief from the start. Vague roles attract people who match the vagueness. Working out what kind of support the job actually calls for is step two of how to actually delegate.
The accidental internship. The fix here isn’t keeping people forever, because you can’t. The fix is that what you teach ends up written down somewhere that isn’t one person’s memory. Then their departure costs you a person instead of a system. Our post on reading your own delegation list covers the related question of which work needed that level of experience in the first place.
Written fluency. Easily the most avoidable of the five. A short writing sample in the actual context of the role, drafting a reply to a real client email, surfaces this in about ten minutes. It’s a standard part of how we assess anyone who will write on an owner’s behalf.
The agency that never replied. We’d like to say something clever here, but honestly, just answer your email.
The pattern underneath
The common thread in all five is that the checking happened after the hire instead of before it. The owner found out what the role really required by watching someone fail at it, which is the slowest and most expensive way to learn it.
That’s the part worth taking into next year. Not “don’t delegate,” which is how these stories usually get told. What went wrong each time was the matching, and matching is a thing you can get right on purpose.
If you have a story of your own, we’d honestly love to hear it. We collect these.
Book a discovery call
