The 90-Day Night Shift: What One Developer Actually Earned From Code Shipped Between 10 PM and 1 AM
Passive income content has a credibility problem. Every thread on r/webdev and every YouTube thumbnail promises that templates and micro-SaaS print money while you sleep. What those posts almost never include is the actual ledger — hours spent, revenue earned, refunds issued.
So we did it differently. We tracked one developer — let's call him Marcus, a full-stack dev from Columbus, Ohio with a day job — through a full 90-day build window. His hours: 10 PM to 1 AM, five nights a week. His goal: turn after-hours code into something that sells without him babysitting it.
Here's how it actually went.
Month One: Picking the Right Product (The Part Everyone Skips)
Marcus almost built another task management app. Instead, he spent his first eight sessions on research instead of code, which felt agonizing at the time.
His filter was simple: find problems he already had as a working developer, that other US-based freelancers and small agencies would pay to solve, and that could be sold as a product rather than a service.
He landed on a niche Notion-and-code hybrid: a set of pre-built client onboarding dashboards for freelance web developers, plus a small Stripe-backed plugin that automated proposal-to-contract handoffs. Boring? Maybe. But boring is where the money hides.
Month Two: Building in Three-Hour Chunks
Night sessions have a hard ceiling. Marcus learned quickly that three hours after a full workday is roughly the max before code quality tanks. His rules:
- Never start a session without a written task. Deciding what to build at 10 PM wastes the best 30 minutes of the night.
- Ship something small every session, even if it's just a landing page section or an API endpoint.
- Weekends off. Burnout was the biggest threat to the whole experiment.
The plugin took about 35 sessions. The dashboard templates took another 20. Total build time: roughly 165 hours.
Month Three: The Launch Nobody Noticed (at First)
Marcus launched on Gumroad with a $49 template pack and a $9/month plugin, then posted to a handful of communities — Indie Hackers, a couple of freelance Slack groups, one well-received Reddit post in r/freelance.
Week one: two sales. Total: $98.
He kept shipping small improvements and answering every support email within a day. Word of mouth in freelancer circles is slow but compounding. By week six, he was averaging a sale every other day.
The Actual Numbers
Ninety days from first session, here's the honest ledger:
- Template pack sales: 41 × $49 = $2,009
- Plugin subscriptions: 23 active × $9/mo = ~$207/month recurring
- Costs: ~$180 (hosting, Gumroad fees, one Figma template license)
- Net for the quarter: roughly $2,150
Divide that by 165 hours and you get about $13/hour — less than his day job pays. But here's the part that matters: the recurring revenue kept arriving in month four without a single new hour of work. By month six, the products were clearing $900/month on maybe four hours of maintenance.
What He'd Do Differently
Three things Marcus wishes he'd known:
- Distribution is half the product. He spent 90% of his time building and 10% marketing. The ratio should have been closer to 70/30.
- Sell to people who already trust you. His first ten sales came from people who'd followed his dev blog for a year. An audience, even a small one, is a launch asset.
- One product beats three ideas. He shelved two other concepts mid-build. That focus was the only reason anything shipped at all.
The Real Takeaway for Night Builders
The after-hours product path works — but not as a get-rich scheme. It works as a slow compounding asset built on top of skills you're already using during the day. Three hours a night, five nights a week, pointed at one sellable thing, beats every scattered side project you'll never finish.
The city's asleep either way. You might as well build something that keeps earning after you log off.
