JOURNAL
2026: Can Indie Developers Still Make Money?
The Playbook
So what do you actually do with all of this? Here's the version I'm trying to live by, not some generic listicle.
Validate before a line of code. I don't mean "think about whether it's a good idea." I mean real validation: a landing page, a waitlist, five actual conversations with people who'd use it, and if you can get them, pre-sales. Money before code. If I can't get five humans to say they'd want the thing, I just saved myself a year. This is the step I always want to skip, and it's the step that kills a project in a week instead of a year.
Distribution first. I'm learning the audience is the real asset, not the code. Build where people already are, and start planting the audience long before there's anything to sell, because distribution is a habit you practice for months, not a switch you flip at launch. A hundred people who already trust you are worth more than a thousand who never heard of you. One's an asset, the other's a number on a vanity dashboard.
Niche down to a small, boring, paying problem. Small enough that I can understand it fully. Boring enough that nobody's chasing it with venture money. Paying enough that the person on the other end has a budget line and a reason to spend it. If the problem excites me more than it excites the customer, I'm building for the wrong person. If the product is a game, the receipts on which genres actually keep paying are in Evergreen or Evergrave. I'm keeping that note for myself.
Time-box the v1 to two weeks, and kill fast. Two weeks forces the sharp, small, finished thing instead of the feature blob I always drift toward. If nothing bites in a reasonable window, bury it and move on. The graveyard is a place you walk through, remember. I'm telling myself that as much as you.
Track profit and time-to-first-payment, not MRR screenshots. This one deserves its own sentence, because I get seduced by screenshots too. There's a whole culture of faked revenue screenshots out there. I'm not participating in it. The only metrics that count are money that actually landed and how long it took the first real customer to pay. Everything else is theater.
Run on the $0 stack: Cloudflare Pages, Supabase, R2, Workers, Resend, Lemon Squeezy, PostHog. The cost of entry is zero dollars and a monthly habit of watching the dashboards. A $0 bill is a feature. It keeps failure cheap and iteration free. That's huge for someone like me.
Underneath all the tactics sits a tempo I'm aiming for. Small sharp things, shipped regularly, each one a bet I can afford to lose. A product is a portfolio position, not a life's work. Right now that means tiny tools for me, the kind I can finish in a weekend and ship before the itch to add one more feature kicks in. The day I stopped treating any single build as the one that has to work is the day building got fun again. Funny how that works.
The honest version of my plan, right now, is small. A tiny tool here, a blog post there, a waitlist that might hold three people. Not a platform. Not a world. Small and boring is my whole strategy, and it's the first plan that doesn't scare me.
And underneath all of it, three principles holding the whole thing up for me. Inspiration is cheap; focus is what costs. Shipping ugly beats not shipping. Going deep beats going broad. The Playbook is just those three sentences wearing work clothes, I earned them the hard way.
The playbook isn't a shortcut to winning, I've found. It's a way to lose cheap and learn fast.
The Math of Quitting Your Job
So when do you actually quit and go full-time? I ask myself this with a spreadsheet in one hand and a fantasy in the other. Here's the honest arithmetic I've pieced together.
Replace salary with profit, not revenue. A thousand dollars of revenue is not a thousand dollars of money, remember. I have to say that to myself a lot. The payment fees, the taxes, the refunds, they all eat first. If I quit my job for revenue, I've quit for a number I never actually got to keep. Then add the things a job quietly pays for: taxes, and health insurance if you're somewhere that doesn't hand it to you, and the months where nothing sells. The number you need is bigger than the number you want. Mine definitely is.
Expect churn. Consumer products bleed a few percent of their subscribers every single month. That's not a bug, it's gravity. You have to replace that few percent before you can even call yourself flat. I see founders celebrate their first hundred subscribers and never ask what next month's bill for losing them looks like. I don't want to be that founder.
And then the rule itself. Don't quit on hope, quit on evidence. That's my mantra now. The evidence bar I keep hearing from people who've done it without wrecking themselves: side profit at roughly 80 to 100 percent of your salary, held for six straight months, or twelve to eighteen months of runway saved in the bank. Not one good month. Six straight. A spike is hope. Six months is evidence. I'm holding myself to that.
The math is cold, but the feeling underneath it isn't. The first thousand dollars of side profit feels like a miracle, and you'll want to quit your job the day it lands. I know I will. That's the exact moment to reread this section. A single good month is a spike, and spikes feel like forever and last like weather. I'm trying to wait for the pattern.
The stages matter too. Nights and weekends at one or two hours a day, which is what a real job leaves you. Then bridge income, some freelance or part-time work that patches the gap while the product grows. Then, and only then, full-time. People skip straight to the third stage because the middle one is unglamorous, and the middle one is the one that keeps you alive. I'm in that unglamorous middle and trying to respect it.
And yeah, some people genuinely have to jump. Burnout, a visa deadline, an opportunity cost that won't wait. I respect that. I just want us to call it what it is: a risk you're choosing, not a plan. There's a difference between leaping because the evidence says it's time and leaping because the waiting hurts. I've felt that second kind of hurt.
If the math says stay put, that's not a failure of nerve. I'm telling myself this daily. It's the plan working. The nights-and-weekends stage exists so you can keep your runway while the product proves itself, and if it never does, you lost weekends, not years. Skipping the stages is how people sprint at a wall until they break. Slow and alive beats fast and broken every single time. (o´・_・)っ
I'll quit when the numbers stop being a story I tell myself and start being a story the bank agrees with.
Evergreen or Evergrave: 10 Genres That Keep Paying, and 10 That Will Eat You Alive
Aug 14, 202620 MIN READ3 CHAPTERSThirty Cents a Million: DeepSeek V4.1 Flash and the Collapsing Cost of Intelligence
Sep 12, 202620 MIN READ5 CHAPTERSLet It Be: My First Programming Lesson Came from a Beatles Song
Aug 11, 20269 MIN READ2 CHAPTERSAgent Time: Turning AI Idle Hours into the Ultimate Life-Lever
Sep 20, 20267 MIN READ1 CHAPTERThe Case of the Missing Thinking Toggle: ZCode, DeepSeek, and a Rename That Broke the Mapper
Sep 13, 20263 MIN READ1 CHAPTER