// log entry · revenue
the $5k mrr challenge: 93 days remaining.
on february twenty-third, 2026 we wrote a number on a whiteboard. five thousand dollars of monthly recurring revenue across the entire vøiddo portfolio by july thirty-first. that gives us a hundred and fifty-eight days. tonight is day sixty-five of that runway. ninety-three days remain.
runway elapsed → 65 / 158 days (41%)
runway remaining → 93 days
mrr today → effectively zero
this is the post about that gap.
what we shipped to chase it.
in those sixty-five days we shipped a portfolio. not a product — a portfolio. the inventory tonight:
- 27 npm packages under
@v0idd0, doing 3,963 downloads a week - 22 free developer tools at
tools.voiddo.com - 14 browser extensions — 4 live across chrome/firefox/edge, 3 drop-ready, 7 in development
- 3 flagship products with their own subdomains:
scrb(e-commerce description generator),rankd(game-ranking accuracy verdicts),verdict(in waitlist mode) - 2 shipped browser games at
games.voiddo.com
that is roughly two hundred thousand lines of code, two hundred and forty-six indexable urls, and zero recurring revenue.
why the number is still zero.
three reasons, and we should be honest about each of them.
most of the catalogue is free on purpose. the npm packages are free forever. the twenty-two developer tools are free forever. the browser extensions have a free tier that does the obvious thing. that is the funnel, not an accident. someone uses cronwtf at 3am to debug a cron expression, and three weeks later their team needs scrb for their shopify store. or they don't. that's the bet. we are sixty-five days into a bet that needs ninety more.
the paid surfaces went live recently. scrb and rankd have been billable for less than a month. the four monetised extensions are still in chrome web store review or just-published. paddle takes ninety days from first sale to wire money to a new merchant. the calendar is doing some of the work for us, but it is also doing some of the work against us.
we have not actually asked anyone to buy anything. there is no email funnel that ends in "and now you should pay us". there is no in-product cap-hit screen that says "you have used the free tier, here is the upgrade". those things are being built this week. they should have been built first. they were not. that is the actual mistake of the runway so far.
what the next ninety-three days look like.
the studio's plan, in the order it will happen:
weeks 1–2 (now – may 13). stop shipping new products. finish the lifecycle email pipeline that ties scrb signups, free-tool signups, and extension installs to a paid offer. wire verdict waitlist to a real first-mover discount. ship the $0.99 starter-lite entry tier the studio has been afraid of. acquisition first, optimisation later.
weeks 3–6 (may 14 – jun 10). first measurable revenue from the existing catalogue. annual plans for power users at amplified pricing. a heavy-user offer at the cap-hit moment. one paid extension launch per week, not three. backlog mode, not calendar mode.
weeks 7–13 (jun 11 – jul 31). compound. the lifecycle pipeline runs against an installed base of free users that is now three months larger. we add an affiliate program with thirty percent rev share so the developer-tools audience can sell scrb for us. we look at the number every monday and decide what is moving it.
the math we tell ourselves.
$5,000 mrr at our blended price points is roughly two hundred paying users — some at $9.99 starter, some at $24.99 pro, a small number at $49.99 business. against an audience of, eventually, a hundred thousand free users a month from the long tail, that is a 0.2% conversion rate. that is not a heroic number. that is a tuesday number.
the question is not whether 0.2% is achievable. the question is whether we can get the audience to a hundred thousand monthly free users by july thirty-first. tonight the answer is "the trajectory is right but the runway is tight". we will know more in two weeks. we will know everything in thirteen.
why we are writing this in public.
three reasons.
one, accountability. saying a number out loud makes it harder to drift. two, calibration: someone reading this post who has done it before will email us with one specific thing we have wrong, and that email will be worth more than a month of our own analysis. three, honesty: the studio has been writing marketing copy that says "we ship a lot" while the bank balance is the bank balance. the log is the place where the writing matches the bank balance.
the next entry in this series will be on monday, may 26 — thirty days from now. it will have an actual revenue number, even if the number is small.
fifty-eight days after that, we will know whether we made it.