Sam’s alarm goes off at 5:47 AM. Not because she’s a morning person. Because she learned the hard way that if she doesn’t get to her inbox before the order desk arrives at 8:30, the day is already on fire before it starts.
She rolls over, grabs her phone, and sees fourteen new emails. Three are from Henderson’s, the US grocery chain that accounts for 30% of her revenue. The first one is a purchase order. The second is asking for a tracking number on last week’s shipment. The third is a reminder about the tracking number they asked about in the second email.
Sam doesn’t have the tracking number. The tracking number is in a spreadsheet that Lisa updates manually after checking the carrier’s website. Lisa isn’t in yet. Sam opens the carrier website on her phone, tries to log in, gets the password wrong twice, gives up, and makes a note to check it when she gets to the office.
She hasn’t had coffee yet. The day is already winning.
By 9:15 AM, Sam is sitting at her desk with six browser tabs open.
Tab one: QuickBooks Online. Tab two: her email. Tab three: the supplier portal where she coordinates orders with her producers in Quebec. Tab four: a Google Sheet that tracks order status, received, ordered from supplier, shipped, invoiced, because no single system tracks the full pipeline. Tab five: the carrier website. Tab six: a shared Google Drive folder where the order desk saves PDF purchase orders that arrive by email.
This is Sam’s operating system. Not software. Sam.
She copies a PO number from an email, switches to the Google Sheet, pastes it in, switches to the supplier portal, types in the order, switches back to the sheet, updates the status, switches to QuickBooks, creates a sales order, manually enters the line items, double-checks the exchange rate because Henderson’s pays in USD, makes a note to follow up on the CFIA export certificate that customs held up last week, realizes she typed the wrong quantity on line three, deletes it, retypes it, and then does it all again for the next order.
She does this forty to sixty times a week. Personally. Because she doesn’t trust anyone else to get Henderson’s pricing right.
The order desk does it too. Between them, the team spends roughly 25 hours a week on data entry, copying numbers from one screen and typing them into another screen. Not analyzing. Not strategizing. Not building relationships with buyers. Just moving data that already exists in one system into another system that refuses to talk to the first one.
Sam didn’t build Maple Syrup Co. She inherited it, in a sense. MapleCo was founded in 1978 as a practical Quebec packing and distribution operation. By the time Sam came aboard as owner twelve years ago, it was a respected independent supplier with a national reputation, around 45 employees, and roughly $50 million in annual revenue selling branded, private-label, and foodservice maple products across Canada and the US. It had grown through grit, relationships, and a simple promise: commercial-scale maple with human-scale service.
But the systems never grew with it.
When MapleCo was twenty customers and fifty orders a month, a spreadsheet and someone’s memory were enough. Now it’s two hundred customers, five hundred orders a month, and three different product lines including seasonal gift baskets that make November and December a logistical nightmare. The same approach that worked at $10 million is now held together with duct tape and institutional knowledge at $50 million.
Sam is pretty sure her inbox breeds at night.
Here’s the thing about Lisa.
Lisa has been with MapleCo for eight years. She was originally hired for the order desk. She knows the business better than anyone, which suppliers are consistently late, which customers always dispute invoices, which products have tight margins that can’t absorb shipping cost increases. She knows that Mrs. Chen at Golden Dragon Restaurant Supply always orders Grade A Dark but actually prefers Grade A Amber and just doesn’t know the difference. She knows that Henderson’s procurement system sends purchase orders as PDFs but their remittance advices come as CSV files attached to emails with no subject line.
Lisa is brilliant. She could be running operations strategy, analyzing margins, building supplier relationships, negotiating better rates.
Instead, she spends 80% of her day retyping numbers from PDF purchase orders into QuickBooks. Line by line. Field by field. Every single order.
She’s not doing this because she’s bad at her job. She’s doing this because the systems around her were never set up to do it any other way. She once described her role to a friend at a party and the friend said, “So you’re like a very expensive USB cable between two computers that won’t talk to each other.” Lisa laughed. Then she stopped laughing.
Lisa is too valuable to lose. She’s also too valuable to waste.
And then there’s Ray.
Ray Beaulieu has managed MapleCo’s warehouse and logistics for fifteen years. He was there before Sam. He’ll probably be there after the building itself crumbles. Ray does not care about software, dashboards, or whatever “the cloud” is. Ray cares about whether pallets are stacked correctly, whether the Grade A Amber is separated from the Grade A Dark (because if you mix them, someone eventually ships the wrong one and then everyone has a bad week), and whether the truck shows up on time.
Ray’s view of the office is simple: they send him paperwork, some of it is correct, and he ships things. When the paperwork is wrong, he calls Sam. When Sam doesn’t answer, he calls Lisa. When Lisa doesn’t answer, he makes his best guess and hopes nobody notices.
Ray has seen three different “new systems” come and go in his fifteen years. The fax machine is still the most reliable technology in his building, and he will defend this position with the calm certainty of a man who has never once had a fax machine crash, reboot, or ask him to update its software.
Ray is not opposed to change. He is opposed to nonsense. This is an important distinction that most consultants fail to make.
Here’s what Sam’s week looks like.
Monday: Process weekend purchase orders. Chase tracking numbers for Friday’s shipments. Reconcile last week’s payments against invoices. Realize two payments don’t match because someone typed the wrong invoice number. Spend an hour finding the discrepancy.
Tuesday: Send out this week’s supplier orders. Manually re-enter every line item from the customer POs into the supplier’s web portal. Follow up on three late shipments by calling the carrier. Update the spreadsheet.
Wednesday: Process more POs. Create invoices in QuickBooks for everything that shipped. Manually email each invoice to each customer. Realize one invoice went out with last month’s pricing because the price sheet update never made it from the Google Sheet to QuickBooks.
Thursday: Customer calls. Wrong grade of syrup shipped. Sam tracks it back through the chain: the PO said Grade A Amber, someone entered Grade A Dark in the supplier order, the supplier shipped what was ordered, and the customer got the wrong product. Fifteen minutes of data entry error. Two hours of phone calls, a reshipped order, and a credit note to fix.
Friday: Month-end approaches. Lisa starts the bank reconciliation, matching every payment in the bank account to an invoice in QuickBooks. This takes two full days because their biggest customers pay multiple invoices in a single wire transfer with a cryptic reference number. Lisa has a colour-coded system in the spreadsheet that only she understands. Sam once asked her to explain it and Lisa said “just don’t touch columns M through Q.”
And underneath all of this, every single day: emails. The shared inbox is a river. Purchase orders mixed with tracking requests mixed with payment confirmations mixed with supplier quotes mixed with spam. The order desk triages it manually. They do their best. Things still fall through the cracks.
Sam works sixty hours a week. Lisa works close to fifty. They’re not lazy. They’re not bad at their jobs. They’re running a $50 million business on systems that were designed for a $10 million business, and the gap between those two things is eating them alive.
Sam can’t remember the last time she took a real vacation.
She tried once, two years ago. A week in BC with her family. On day two, Lisa called because Henderson’s sent a rush order and Lisa wasn’t sure about the pricing for the new bulk line. Sam spent forty-five minutes on the phone from a campground in Tofino walking Lisa through a spreadsheet she could barely see on her phone screen. On day three, a payment came in that didn’t match any open invoice, and only Sam knew that it was an advance deposit for a custom gift basket order that she’d agreed to verbally and never entered into the system.
By day four she was answering emails from the cabin. By day five she gave up pretending and just worked from her laptop at the kitchen table while her daughter watched TV.
But here’s the part Sam won’t say out loud, not yet: some small, stubborn part of her needs it to be this way. If the business falls apart without her, that means she matters. That means she’s essential. That means the thing she built (or inherited, or grew, or held together with her bare hands for twelve years) is real and important and hers.
She confuses being essential with being effective. It’s the survival rule that built the company. And it’s the same rule that’s now choking it.
One Tuesday in October, Sam stays late.
Not because she has to, although she does, but because she got an email at 4 PM from Mrs. Chen at Golden Dragon. A shipment arrived with the wrong grade. Again. Grade A Dark instead of Grade A Amber. Mrs. Chen is polite about it, because Mrs. Chen is always polite, but there’s a line in the email that lands like a punch: “This is the third time this year. We love your product, Sam, but we need to be able to count on the order being right.”
Sam could delegate this. She could forward it to the order desk and deal with it tomorrow. Instead, she drives to the warehouse at 6 PM, pulls the right case herself, and arranges a same-day courier to Mrs. Chen’s warehouse in Markham. She pays for the courier out of her own pocket. She writes a personal apology note and tucks it into the box.
Ray is still at the warehouse when she arrives. He watches her pull pallets and says nothing for a while. Then: “This is the third time this quarter, Sam.”
“I know.”
“I flagged it both times before. Sent emails.”
“I know, Ray.”
“Emails that nobody answered because the inbox is where information goes to be forgotten.”
Sam doesn’t have a response to that, because Ray is right. She loads the courier van and drives home.
She doesn’t have to do any of this personally. She does it because she gives a damn. Because she knows that MapleCo’s reputation was built on relationships like this one, and every time the systems fail, it’s those relationships that take the hit.
On the drive home, she does the math. The wrong-grade error wasn’t a mystery. She traced it in five minutes: the PO said Amber, but when the order was entered into the supplier system, someone typed Dark. A typo. One field, one letter different, one distracted moment in the middle of entering the twentieth order that afternoon.
The error cost Sam a courier fee, a credit note, an hour of her evening, and a small chip off the trust she’s built with her best restaurant customer. The error was caused by a human being asked to manually retype data from one screen into another screen, for the twentieth time that day, while also answering the phone and sorting the shared inbox.
This isn’t a people failure. It’s a system failure.
Sam pulls into her driveway at 8:30 PM. Her daughter’s hockey practice ended an hour ago. Her husband handled it.
She sits in the car for a minute, engine off, and thinks: There has to be a better way to do this.
At their quarterly review, Sam’s accountant, a methodical man named Gerald who has never once been excited about anything in the twenty years Sam has known him, says something that Sam almost doesn’t hear.
They’re going over the numbers. Revenue is up 18%. Margins are steady. Cash flow is “manageable,” which is Gerald-speak for “not great.” He points out that accounts receivable days have crept up: invoices are going out slower, which means payments are coming in slower. He points out that the shipping error rate has doubled since last year.
Sam nods. She knows all of this. She lives it.
Then Gerald puts down his pen, takes off his glasses, and says:
“Sam, you didn’t build this business to be its best employee. You built it to be its owner.”
Sam blinks.
“Your revenue is up, but your margin per hour of your time is going down. You’re working more hours for less return. That’s not a growth problem. That’s a process problem.”
Sam nods again, but this time something snags. She doesn’t respond. She writes it down in her notebook, and they move on to tax planning.
She doesn’t realize it yet, but Gerald just told her the theme of the next six months of her life.
That night, Sam can’t sleep.
She lies in bed and runs the numbers in her head. She works sixty hours a week. If she paid herself what she pays Lisa, $55,000 a year, her hourly rate would be about $18. She doesn’t pay herself $55,000. She pays herself more. But the math doesn’t care about her salary. The math cares about what she’s doing with her time.
She spends at least 15 hours a week on data entry. Another 10 on chasing tracking numbers, reconciling payments, and fixing errors. That’s 25 hours a week, more than half her time, on work that doesn’t require her expertise, her relationships, or her judgment. Work that a well-designed system should be doing automatically.
Sam picks up her phone. It’s 11:47 PM. She types into Google: “how to automate my business.”
She gets two million results and none of them feel real. Lots of promises about “digital transformation” and “AI-powered solutions” and “unlock your business potential.” Her eyes glaze over.
She opens ChatGPT. Types: “I run a distribution business and I’m spending too many hours on manual data entry. How do I automate this?”
She gets a decent answer. Generic, but decent. Use Zapier. Try QuickBooks integrations. Consider RPA software. Explore AI tools.
She screenshots it. Closes her phone. Goes to sleep.
She doesn’t do anything about it for three weeks, because she’s too busy doing the manual work that needs automating.
The fix starts with asking a different question. Not “What technology should we buy?” but “What problem are we actually trying to solve?”