I used to treat distribution as a second job. Build the thing all day, then at night go figure out how to tell people about it — write the post, cut the clip.
Backwards. By the time you're "done" building, you're tired, and nobody does their best selling exhausted.
Here's the flip: the building is the distribution. Not a metaphor for it. The thing itself.
Two jobs, one energy budget
The old model treats the product and the audience as separate problems, solved in sequence — ship, then market. It fails for a specific reason: it asks you to be a different person after hours than you were all day. Builder by day, promoter by night.
The audience was never really for a product anyway. It's for the way you build — the decisions, the wrong turns.
Nobody else builds quite the way you do. That's the actual asset. The product is downstream of it.
Sixteen thousand commits, no announcement
The clearest example is OpenClaw, an open-source agent project that racked up something like sixteen thousand commits in four and a half months. People didn't share a launch post. They shared the number.
The commit count became the highlight reel. Velocity was the pitch. The product was almost incidental to the story of the pace.
I don't have that project's head start — no prior following, no name recognition walking in the door. So the lesson isn't "go viral off your commit count."
It's smaller and more useful than that: the log of the work, honestly kept, is already a story. You don't have to invent one on top of it.
Capture, don't create
The rule I'm trying to hold myself to: I don't make content. I capture work I was already doing.
Recorder on. Screen and voice, while I build something I was building anyway — no separate shoot, no script. I already narrate out loud anyway.
The weekly version is supposed to fit under two hours. Capture costs almost nothing — it's just leaving the thing running while you work. Clipping the raw footage down to something watchable is maybe thirty minutes.
Posting one clip plus one short note about the actual decision behind it is another twenty. That's the loop. Repeat.
The same footage, twice the doors
One edge I haven't used yet: working bilingually could turn one raw capture into two clips instead of one — same footage, same decision, a different room hears it.
A clip about tracking cash tips doesn't belong on a general feed anyway. It goes to the corners of the internet where gig workers already are, in whichever language they use there.
Whether the bilingual version would double anything, or just double the editing queue, isn't something I've tested yet. But it's the one distribution edge that's genuinely mine — nobody's out-executing a bilingual build log by being better at English.
Bookkeepa ran thirty split tests before "gig workers" narrowed down to, specifically, Uber drivers — the one segment where the economics actually worked. I haven't run thirty tests on who'd watch a build log in two languages.
I have a hunch that bilingual systems-building is a narrow lane nobody else is standing in. A hunch isn't evidence. It's just a bet with better odds than the average one.
Publishing past the plateau
The unglamorous stat: the first thousand followers takes six to twelve months of just showing up.
Nearly every founder who eventually broke through has an ugly month-four graph to point at — flat, or worse.
The difference between the ones who made it and the ones who didn't wasn't the hook, or the platform, or luck. The quitters stopped around week sixteen, right when it stops feeling like it's working. The others kept posting anyway.
That's not a strategy so much as a schedule. Leave the recorder on, ship the clip, repeat, past the point where it feels pointless — that's the whole edge, and it's sitting there for anyone willing to be boring about it for a year.
Several different things running in parallel, more shipped most weeks than makes it onto camera. The velocity was never the missing piece. The missing piece is the muscle that doesn't get tired of going unnoticed.
