32 Hours a Month, Copy-Pasting Tracking Numbers. Nobody Questioned It.

The number landed in the middle of the screen: 32 to 43 hours a month.

One person. One task. Copy the tracking number from the warehouse system. Paste it into marketplace one. Copy it again. Paste it into marketplace two. Repeat for every order, every day, every week.

Nobody in the room said it was wrong. Nobody said 'that can't be right.' They just looked at it.

They already knew.

The thing about time vampires

A time vampire isn't hidden because it's complicated. It's hidden because it's obvious. So obvious that it becomes invisible.

This was a marketplace ecommerce operation. Multiple channels — Amazon, eBay, their own site, maybe one or two others. Orders come in. Warehouse picks and ships. Courier collects. Tracking number gets generated.

And then someone has to tell the customer where their parcel is.

The warehouse system knew the tracking number. The marketplaces needed the tracking number. But the systems didn't talk. So one person bridged the gap. Every single time.

Open the warehouse system. Find the order. Copy the tracking number. Open the marketplace. Find the same order. Paste the tracking number. Mark it shipped. Move to the next one.

1.5 to 2 hours. Every working day. Not because the task was hard. Because there were a lot of orders, and every single one required the same manual steps.

Why nobody questioned it

Here's the part that matters more than the number itself.

When this surfaced in the exercise, the response wasn't shock. It was recognition. A kind of tired nod.

'Yeah. That's just how it works.'

Not 'that's how we chose to do it.' Not 'we've been meaning to fix that.' Just — that's how it works. Present tense. Permanent tense.

The task had been there so long it had become load-bearing. Part of the identity of the operation. Of course someone does the tracking. Of course it takes time. Of course.

No one was hiding it. No one was protecting it. It simply wasn't a question anymore.

This is what acceptance looks like. Not a decision. An absence of decisions. The path of least resistance, sustained long enough that it calcifies into 'the way things are done.'

What the exercise actually surfaced

The exercise isn't clever. It doesn't do anything sophisticated. It asks questions — plain ones — about how the business actually operates. Where orders come from. Where they go. Who touches them, and how often.

Then it maps time to steps. Not in theory. In the reality of how many orders, how many channels, how many minutes per action.

The number didn't come from a consultant's estimate. It came from the person answering honestly about their own operation. The exercise just did the maths they'd never done.

32 to 43 hours a month. That's a full working week. Gone. Every month. To copy-paste.

Not to solve problems. Not to serve customers. Not to grow anything. To move a string of characters from one screen to another, because two systems that should talk don't.

The thing that wasn't broken

Here's where it gets uncomfortable.

This wasn't a broken process. The tracking numbers were getting entered. Customers were getting their updates. The marketplaces were happy. Performance metrics were fine.

From the outside, everything worked.

The exercise didn't find a failure. It found a cost that nobody was accounting for. Time disappearing into a gap between systems, every single day, without ever showing up on a report or a dashboard.

You can run like this for years. Plenty of businesses do. The question isn't whether it's sustainable — clearly it was. The question is what else that time could have been.

The moment in the room

When the number appeared, the reaction was quiet. Not defensive. Not surprised. Just — there it was.

Someone said something like, 'I knew it was a lot, but I didn't think about it in hours.'

That's the shift. Not learning something new. Seeing something familiar in a different frame.

A task that felt like 'part of the job' reframed as 'a full week every month, doing what a basic integration would do instantly.'

The exercise didn't tell them what to do about it. That's not the point. The point is they couldn't unsee it anymore. The accepted thing became a chosen thing — and choosing to keep it suddenly required justification it hadn't needed before.

How to run it yourself

The exercise is two prompts. You run them in your own AI — ChatGPT, Claude, whatever you use. It interviews you about your operation, then generates a five-minute review: where time leaks, where money leaks, the single points of failure nobody's named.

You keep everything. We never see your numbers, your processes, your answers. There's no login, no data capture, no follow-up sequence unless you want one.

Why give it away? Because an owner who's already seen their own biggest leak clearly is worth a hundred who haven't looked yet.

The link's below. Takes about fifteen minutes. You might find nothing surprising. Or you might find your own 32 hours, sitting in plain sight, waiting to be noticed.