Mark runs a bowling chain.
Which one?
“If I tell you, my IT department will find this article. Let’s just say — if you’ve ever bowled in Europe, you’ve probably paid my rent.”
He’s never written a line of code.
The Frustration
His IT department moves at IT speed. Tickets. Sprints. Quarterly roadmaps. A form that should take a week takes a month. A dashboard that should exist doesn’t.
The systems look like 2005. Because they were built in 2005. And every change request sits in a backlog behind seventeen other change requests.
Most of those requests will never happen. Not “delayed” — never. Something more urgent always comes up. A server dies. A payment system breaks. A vendor changes their API. IT runs on firefighting and bare minimums. The “nice to have” list is where ideas go to die.
Mark knows exactly what he needs. He’s been running operations for years. What he doesn’t know is how to make a computer do what he wants.
Or didn’t.
30 Minutes
He opened Claude Code. Typed what he needed: a form to manage warehouse inventory. Sync stock levels on the website with what’s actually in production. Track what’s sold. Track what’s ordered. Show what’s left.
Not a technical spec. Just the problem, explained like he’d explain it to a new hire on their first day.
30 minutes later, he had a working form.
“You explain it like to a five-year-old. It does all the steps. Shows you what it’s doing. I kept waiting for it to break. It didn’t break.”
The form worked. Real data. Real sync. Real interface. Not a mockup — a functioning system.
His IT department quoted him six weeks for this. He did it during a lunch break.
The Loop
Then he asked: “Can we add analytics?”
Analytics appeared. Stock levels over time. What’s moving. What’s sitting.
Then he asked: “What else should we improve?”
It told him. He said yes. It improved.
“I ask what’s missing. It tells me. I say ‘do it.’ It does it. Then I ask again. I did this for an hour. I forgot to eat.”
That’s the loop. Describe what you want. It builds. Ask what’s missing. It tells you. Say yes. It adds.
No tickets. No sprints. No “we’ll discuss this next quarter” — which means never.
This isn’t just faster. These are things that would have never happened.
Analytics for a bowling warehouse? Not a priority. Improving something that already works? Backlog. The business runs on putting out fires, not lighting new ones.
Until now.
What This Means
The bottleneck was never the technology. The bottleneck was the people between the problem and the solution.
Mark knows his warehouse better than any developer ever will. He’s been running this business for years. He knows which numbers matter. He knows where the money leaks. He just couldn’t make a computer listen.
Now there are no people between.
His IT department didn’t know he built this. They still don’t.
“They’re going to see this system and ask who built it. I’ll say ‘contractor.’ Technically not a lie.”
The power is shifting. Not to people who can code. To people who understand the problem well enough to explain it clearly.
That’s always been the hard part. Now it’s the only part.
Numbers
| What | Before | After |
|---|---|---|
| Inventory form | 6-week estimate | 30 minutes |
| Analytics dashboard | Never (backlog) | +10 minutes |
| Iterations | Ticket per change | ”What else?” loop |
| Who built it | IT department | ”Contractor” |