Build tools that work without you

The real test of a foundation isn't what you can build with it — it's what people do with it when you're gone.

The real test of a platform isn't what you can build with it — it's what people build when you're not in the room
An ads guy turned a week of work into a few hours on Backflip without needing a single explanation from its creator
A completely non-technical friend shipped his own websites, because good structure closes the gap between "I have an idea" and "I can ship it"
If a tool only works when you're driving it, you built a demo, not infrastructure
Measuring yourself by your own output is the flattering metric; measuring by other people's capability is the honest one
The output worth tracking isn't the repo — it's who got faster, braver, or finally started

Build the builders, not just the thing.

I built Backflip to solve my own problem: a foundation I could stand projects up on fast, without re-solving the same infrastructure decisions every single time. That's the version of the story I usually tell.

Here's a different one.

The ads guy

A friend who works in ads asked me to help him look at some tooling for his job. I pointed him at Backflip and left him to it.

A few weeks later he told me he'd built his own ads management tool on top of it. Work that used to take him a week now takes him a few hours.

He didn't need me in the loop. He didn't even really need me to explain the platform beyond a nudge in the right direction.

The non-technical guy

Another friend — genuinely non-technical, no background in this at all — started building his own websites on Backflip.

Not because I taught him to code. Because the platform put enough structure around the hard parts that "I have an idea" was suddenly close enough to "I can ship it."

That gap is where most people quit. Closing it is the whole job.

The actual test

Neither of these people needed me in the room.

That's the real test of whether you've built a foundation or just a clever trick only you know how to use. If the thing only works when you're driving, it isn't infrastructure. It's a demo.

It's tempting to measure a tool by what you can do with it. That's the easy metric, and it's the flattering one. The more interesting measure is what other people can do with it once you're gone.

A 10x on a task someone used to dread. A first website from someone who would never have started otherwise. Neither of those shows up if you're the only person who ever touches the thing you built.

Building the builders

This is the first entry in what I want to make a recurring series. Not "here's what I shipped" — there's enough of that on the internet already. More like: here's who became more capable because of it, and what that actually looked like.

The output I care about isn't the repo. It's the person who got faster, or braver, or finally started.

Building the builders, not just the thing.

What have you built that works best when you're not in the room?