Two weeks after her midnight Google search, something lands in Sam’s inbox that makes the whole thing worse.
It’s a PDF from Henderson’s. Not a purchase order. A vendor scorecard. Henderson’s does these quarterly, rating every supplier on three metrics: order accuracy, delivery timeliness, and invoice consistency. Sam has received these before. She usually skims them.
This time, she reads every line.
MapleCo’s order accuracy: 91%. The threshold is 95%. Below threshold.
Delivery timeliness: 87%. The threshold is 92%. Below threshold.
Invoice consistency: 94%. Threshold is 95%. Below threshold, but barely.
At the bottom, in a box that Sam has never seen populated before, there’s a note: “Suppliers scoring below threshold on two or more metrics for two consecutive quarters will be placed on Vendor Performance Review. Please contact your account representative to discuss a remediation plan.”
Sam stares at the screen. She’s below threshold on all three metrics. Henderson’s hasn’t said anything yet. They haven’t called. This isn’t a phone call. It’s a document. It’s data. And data, Sam is learning, is how large companies say “we’re watching” without raising their voice.
She puts the scorecard in a drawer. She doesn’t show it to Lisa. She doesn’t show it to anyone.
She will think about this later. Right now, she has forty-seven purchase orders in the shared inbox and no time to think about anything.
A week later, Sam does what every overwhelmed business owner does.
She hires someone.
His name is Jordan. He’s 26, sharp, genuinely eager, and desperate to prove himself. He came from a tech startup that folded three weeks before his rent was due. He took the MapleCo job because he needed to eat, not because he dreamed of maple syrup distribution. But he’s the kind of person who, once he’s in something, wants to make it better. “Good with computers,” Lisa said when she recommended him. He starts at $48,000 a year. Sam’s logic is simple: Lisa is drowning, so let’s add another pair of hands. More people, more capacity, problem solved.
For the first two weeks, it feels like the right call. Jordan picks things up fast. He starts processing POs alongside Lisa. The backlog shrinks. Sam feels a flicker of relief.
By week six, the flicker is gone.
Here’s what actually happened: Sam added a second person to a broken process. Jordan is now doing the same manual data entry that Lisa does, copying PO data from PDFs into QuickBooks, updating the spreadsheet, emailing tracking numbers. He’s faster than Lisa at typing but slower at judgment calls because he doesn’t have eight years of context about which customers are fussy about grades and which suppliers need a follow-up call on Wednesdays.
The bottleneck didn’t disappear. It got a second chair.
Sam is now paying $48,000 a year, plus CPP, EI, benefits, equipment, the three months of training time Lisa spent getting Jordan up to speed, to have two people doing the work that a well-designed system should be doing automatically. All-in, Jordan costs the business about $65,000 in year one. The error rate didn’t drop. The hours didn’t drop for Sam. And the Henderson’s account is still shaky because the fundamental problem, humans retyping data between disconnected systems, hasn’t changed.
Sam doesn’t realize this yet. She thinks she just needs to give Jordan more time.
Jordan, for his part, knows something is off. He’s not stupid. He can feel himself becoming another cog in a machine that doesn’t work, and it’s eating at him. He didn’t leave a startup to spend his days copy-pasting between browser tabs. He came here to matter.
Two months after hiring Jordan, Sam makes her second mistake.
She attends a virtual demo.
A software company, let’s call them CloudSyncPro, reaches out with a polished email about their “AI-powered supply chain platform.” The demo is impressive. Slick interface, animated dashboards, a salesperson who uses the word “seamless” eleven times in forty minutes. The platform promises to connect her ordering, inventory, shipping, and invoicing into a single unified system.
Sam is hopeful. This feels like the answer. Something purpose-built for exactly her problem.
CloudSyncPro costs $2,500 a month. That’s $30,000 a year. Sam signs the contract.
Six months later, the platform is shelfware.
Here’s what went wrong: CloudSyncPro was built for companies doing $200 million to $500 million in revenue with 200-person operations teams. It has features Sam will never use and is missing features she desperately needs. It doesn’t understand maple syrup grading. It doesn’t handle the specific way Henderson’s sends POs, as PDF attachments with a cover sheet that has to be ignored. It doesn’t connect natively to QuickBooks Online, only QuickBooks Enterprise, which is a different product. The “integration” they promised required a $15,000 custom setup fee that wasn’t in the original quote.
Buying a giant bottling line for a sugar shack doesn’t make you a bigger operation. It just makes you a sugar shack with expensive equipment gathering dust.
Sam asked “Should we use this AI platform?” when she should have asked “What specific problem am I trying to solve, and what’s the simplest way to solve it?”
The technology wasn’t the problem. The question was.
Ray, when he heard about CloudSyncPro, had offered his assessment in six words: “So it’s another thing that doesn’t.” He was not invited to the next software review meeting. He was, as it turned out, completely correct.
Sam’s third mistake is the one that almost breaks something for real.
Jordan, remember, the one who’s “good with computers,” comes to Sam with an idea. He’s been playing with Zapier and ChatGPT on his own time, and he thinks he can automate the purchase order email responses.
“Look,” he says, pulling up his laptop. “When a PO comes into the shared inbox, this Zapier zap detects the email, sends the PDF to ChatGPT to extract the order details, and then automatically sends a confirmation email back to the customer. I tested it with ten emails. It works.”
Sam is impressed. This is initiative. This is exactly the kind of thing she hired Jordan to do. And Jordan is practically vibrating with the need for this to be the thing that proves he was worth hiring.
“Ship it,” she says.
Jordan turns it on.
For three weeks, it works beautifully. Customers send POs by email, and within minutes they get a professional confirmation: “Thank you for your order. We’ve received your purchase order #4721 for 24 cases of Grade A Amber and 12 cases of Grade A Dark. Estimated ship date: Friday.”
Sam is thrilled. She tells Lisa this is the future. Lisa nods politely but says nothing. Lisa has seen “the future” before. It usually has a shelf life of about a month.
On a Sunday night at 2:14 AM, the carrier API that Zapier pings to estimate shipping dates goes down for maintenance. Zapier retries the failed step. The retry triggers the entire workflow from the start. For every PO that came in over the weekend, the confirmation email gets sent again. And again. And again.
Monday morning, Sam opens her inbox to find 47 emails from confused and angry customers who each received between three and eight identical confirmation emails overnight. Henderson’s procurement manager, the one who gave Sam the 90-day ultimatum, has forwarded the emails to his VP with a note that Sam will never see but can imagine.
Jordan is devastated. He didn’t know about retry logic. He didn’t know automations need error handling. He didn’t know that what works on ten test emails can detonate spectacularly on two hundred real ones. He sits at his desk looking like someone who just accidentally set fire to the very building he was trying to improve.
And here’s the part that nobody talks about: while Jordan scrambles to turn off the Zapier zap and Sam sends individual apology emails to her biggest customers, Lisa discovers something else. She looks at Jordan’s ChatGPT history and sees that for weeks, he’s been pasting actual customer purchase orders, complete with company names, contact information, order quantities, and pricing, into ChatGPT to test his extraction prompts.
Customer data. In a public AI tool. With no policy, no guidelines, and no one who thought to ask whether that was okay.
Lisa mentions it quietly to Sam. “We don’t really have a process for this,” she says. “We don’t have a process for any of this. We have a habit, and the habit doesn’t include a section on what Jordan is allowed to paste into the internet.”
Sam doesn’t even know what a data processing agreement is yet. She will.
The next morning, Sam sits in her office with the door closed.
She adds up the damage.
Jordan’s salary and onboarding: $65,000 and counting. The CloudSyncPro license she’s still paying for: $30,000 a year. The courier she paid out of pocket for the Mrs. Chen reshipping: $180. The customer credits she’ll have to issue for the email fiasco: maybe $2,000. The time she and Lisa spent cleaning up the mess: at least 20 hours between them.
But the real cost isn’t in dollars. It’s in trust. Henderson’s is quieter than usual. Mrs. Chen hasn’t placed an order this month. And Sam, who built MapleCo’s reputation on personal relationships and reliability, feels like she’s watching both erode.
She tried hiring. It didn’t fix the process.
She tried buying technology. It didn’t fit the business.
She tried building it herself with duct tape and AI. It blew up at 2 AM on a Sunday.
Three swings. Three misses. All of them reasonable decisions made by a smart person, and all of them wrong because they started from the wrong place.
Sam didn’t start by understanding her actual problem. She started by grabbing the nearest thing that floated. When you’re drowning, you don’t analyze the current. You just grab.
That Friday, Sam calls Gerald. Not for accounting advice. Just to vent.
Gerald, being Gerald, listens patiently and then says: “Have you called that automation fellow I mentioned?”
Sam sighs. “Gerald, I just spent $30K on software that doesn’t work and had a robot email-bomb my customers at 2 AM. I’m not exactly in the market for more technology.”
“He’s not technology,” Gerald says. “He’s a person. A weird one. But the good kind of weird. He fixed my dental client’s invoicing problem in three weeks, and that practice had been a mess for years.”
Gerald sends Sam a link. She clicks it. She reads a blog post by some guy named Oscar who apparently built his first automation bot in a video game when he was 12 and got banned for it.
Despite herself, she laughs. She reads another post. Then another.
At 11 PM, because this is apparently the only time Sam has to herself, she fills out a contact form on the DigitalStaff website. A chat window pops up. A chatbot named Winston asks if he can help.
“I’m a maple syrup company,” she types, feeling ridiculous. “And I think my business is falling apart.”
Winston’s reply is immediate: “You’re not the first person to tell me that at 11 PM on a Friday. That’s usually when business owners finally have time to think. Can I ask what’s eating up most of your time right now?”
Sam blinks. That’s actually a good question.
She types for ten minutes straight.
Monday morning. Sam’s phone rings. The caller ID says London, Ontario.
“Sam? It’s Oscar. From DigitalStaff. I read what you sent Winston on Friday night.”
Sam braces for the pitch. She’s expecting buzzwords. She’s expecting “AI-powered solutions” and “digital transformation” and “seamless integration.”
Oscar says: “Tell me about the last invoice that made you want to throw your computer out the window.”
Sam blinks. And then she talks. For forty-five minutes, she talks. About Lisa, about Jordan, about the six browser tabs, about Henderson’s, about the POs that arrive as PDFs and the tracking numbers she can’t find and the bank reconciliation that only Lisa understands and the month-end that eats her weekends.
Oscar doesn’t interrupt. He asks sharp questions: “How many POs per week?” “What format do Henderson’s send?” “When you say Lisa enters them, you mean line by line into QuickBooks?” But mostly he just listens.
At the end, Sam waits for the pitch.
Instead, Oscar says: “You don’t have a technology problem, Sam.”
“I’m sorry?”
“You have a process problem that technology can solve. But only if we understand the process first. Everyone who tried to help you so far, the new hire, the software vendor, even Jordan with his Zapier thing, they all started with a tool and worked backwards to your problem. That’s why none of it stuck.”
Sam is quiet for a moment. “So what do you start with?”
“I start with the dumbest possible question: What are you actually doing, step by step, right now? Not what you think you’re doing. Not what you wish you were doing. What actually happens when a purchase order hits your inbox at 9 AM on a Tuesday?”
“I told you. Lisa opens the email…”
“No. Slower. What email client? Where’s the inbox? Is it shared? Who sees it first? Does the subject line tell you anything? Is the PO always a PDF? Is it always an attachment, or sometimes inline? Does it always have the same fields?”
Sam has never thought about her business at this level of detail. It’s like someone asking her to describe how she breathes.
“That,” Oscar says, “is why discovery comes first. Every client tells me their process is simple. Discovery proves them wrong every time. That’s not a bad thing. That’s the whole point.”
Sam hangs up and sits with a strange feeling she can’t name.
Nobody has talked to her about her business like that before. Not the CloudSyncPro salesperson, who talked about features. Not Jordan, who talked about tools. Not even Gerald, who talks about numbers.
Oscar talked about her process. The actual, step-by-step, mundane, boring, real-life sequence of things that happen when a purchase order arrives. And he didn’t do it to sell her anything. He did it because, and she’s starting to understand this, you can’t fix what you don’t see. And you can’t see what you’ve never been asked to describe.
It sounds so obvious. Sam can’t believe she missed it three times.
But here’s the thing: almost everyone does.
Oscar’s job, Sam is starting to realize, is to help you see clearly first. Then help you build something that actually works.
She picks up her phone and schedules a discovery session.