Before you build anything, run the audit: is this a revenue problem or a cost problem, where’s the real bottleneck, what breaks if you get hit by a bus, and does the user ever feel the machinery? These are the exact four passes I run on my own portfolio before I let myself build — and the ones I once ran for a friend who thanked me and built anyway.
This is the “bottleneck audit” that was on the coming shelf — it grew up into the whole audit.
A friend — sharp, capable, someone I genuinely like — came to me wanting to build something. Custom infrastructure, from scratch, for a project the market had almost certainly already solved for a few dollars a month. He asked what I thought.
So I walked him through the audit below: the same four passes I run on my own portfolio before I’ll let myself build anything. It’s not a “no” machine — it’s a “where does the money and the risk actually live” machine. This guide is that audit. What happened after him, I’ll tell you at the end.
They look identical from the inside and need opposite fixes. If a unit of work already clears $40 net, you don’t scale it by burning twenty unbillable hours to shave $2 off the cost — you scale it by running more units. And the real arbitrage in service work was never reselling raw compute or raw hours; it’s the authority, trust, and managed convenience you stack on top of cheap, boring, reliable infrastructure. Buy the dependable commodity. Sell the judgment.
A workflow moves at the speed of its narrowest point and nowhere else. Most over-engineering is someone lovingly rebuilding a part that already works while the actual gridlock sits untouched. Rule: build custom only where the market genuinely fails your specific bottleneck. If your output queue is choking, writing software to clear that exact chokepoint is worth every hour. Standing up a custom server just to host a brochure site is a hazard cosplaying as an upgrade. Then contain the input — batch it, box it, set the operating windows — so the engine never stalls waiting on you.
Anything live, commercial, or load-bearing has to survive a bad day. A system with a bus factor of one — it halts the instant the only person who understands it is unavailable — is fundamentally unsellable, because clients aren’t buying compute, they’re buying insurance. The most effective setups are boring and modular: legible under pressure, offline-capable, repairable by someone who isn’t you. Push the fragile, baseline-stability liability onto enterprise failovers, and save your cleverness for the part that’s actually yours.
The infrastructure should be invisible to the person on the other side. They don’t care about the purity of your tech stack; they care that the storefront never went down and the music never dropped out during the transition. Every crash, cold-start delay, and moment of dead air spends trust you can’t easily earn back. Judge the whole system by one question: does the audience ever feel the machinery? If they do, the machinery lost — no matter how elegant it was to build.
the cheapest build is the one the audit talks you out of
Find where the money actually lives.
Only the narrowest point matters.
Clients buy insurance, not compute.
The machinery should be invisible.
Here’s the honest ending. I ran the audit clean. He listened, thanked me — and built the custom thing anyway.
That’s allowed. It’s his business, his money, his reps to buy, his version of the story to write. “Ask someone who’s done it” was never the same as “do what they say.” An audit is a gift, not a verdict, and the person holding it always gets the last word.
It’s also, I’ll admit, frustrating — because I could see the bottleneck from across the room, and watching someone spend months clearing a chokepoint a nine-dollar tool would’ve handled has its own small ache. But that frustration is mine to manage, not his to absorb. Maybe he learns something I couldn’t have taught him. Maybe he’s right and I’m wrong. Either way the map was the gift; the walk was always going to be his.
So: if you run this audit and it tells you not to build — sit with that before you build anyway. And if you build anyway? Come tell me what I got wrong. I mean it.
Every box above is doable solo — I’m not gatekeeping, the whole guide is free on purpose. But solo means you pay full tuition on each lesson: the wrong first hire, the package priced from fear, the move made a year too late. Fail-fast keeps the tuition survivable; it never makes it free.
A mentor doesn’t do the work for you. They’ve already eaten those mistakes, so you get to skip the drafts that only teach you what not to do. The guide hands you the map; someone who’s done it hands you their reps.
That’s the oldest shortcut there is — ask someone who’s been down the road before. Me, or anyone in your corner who has. (No one on your bench yet? Guide No. 6 is about building it.)
the checklist is free. the reps behind it weren’t.
Ask someone who’s done itThat’s the best possible time to run the audit with a second set of eyes. If you want to pressure-test a build before you sink months into it — revenue or cost, the real bottleneck, the bus factor — that’s a conversation I’m always glad to have.