// the studio log
honest writing about how the studio actually runs — what we shipped, what broke, what we learned. cynical-friend voice. real numbers. no marketing copy. closer to a working journal than a content strategy.
most of what gets published online about indie software is a victory lap with the receipts cropped out. this isn’t that. posts go up when something is true and worth saying, not on a content calendar. some weeks that’s nothing. when there is a post, it has the actual number in it.
if you crawled voiddo.com tonight you'd find 246 indexable URLs across five subdomains. fifteen blog posts, twenty-two tool pages, fourteen extension landings, eighty-something legal docs spread across the catalogue. nobody set a pageview target for any of them.
read the full thing
the studio's npm scope went from zero packages to twenty-five in about six weeks. last week the catalogue served 3,963 downloads — verifiable via the public npm API. the github repos that publish those packages have, between them, almost no stars. that gap is the post.
read the full thing
on february twenty-third we set a target. five thousand dollars of monthly recurring revenue across the entire vøiddo portfolio by july thirty-first. ninety-three days remain. the studio has shipped twenty-seven npm packages, fourteen extensions, twenty-two free tools — and earned exactly zero recurring revenue so far. this is the post about that.
read the full thing
looking for the technical changelog? archived here. it was getting in the way of the writing.
// the sunday digest
one short email a week. that's it.
every sunday at 19:00 local we send one email with the week's log entries — same cynical-friend voice, same real numbers, no marketing copy in between. unsubscribe link at the bottom. we will not sell your email. we will not stuff it with product launches.
// expected first send: sunday 2026-05-03 19:00 local. that's four days from now.