How Indie Developers Make Money: A Practical Breakdown

Indie developers earn in two broad ways: selling their time (freelancing, contracting, consulting) or selling products (apps, SaaS, templates, courses). Most sustainable solo careers mix both — time-based income pays the bills while product income compounds slowly in the background. Below is a realistic breakdown of the main revenue streams, what each actually demands, and how to combine them without burning out.

Selling Products: Apps, SaaS, and Digital Goods

Product income is the dream because it decouples earnings from hours worked — but it's also the slowest to materialize. The main formats:

• Micro-SaaS. A small subscription tool solving one narrow, painful problem (an analytics widget, a scheduling tool, a niche API wrapper). Recurring revenue is the appeal; churn, support, and marketing are the ongoing cost. Narrow beats broad: a tool for one specific audience is easier to market solo.
• Mobile and desktop apps. One-time purchases or subscriptions through app stores. Store fees take a cut, and discoverability is hard without App Store Optimization or an outside audience — but a well-reviewed niche utility can sell steadily for years.
• Paid templates, boilerplates, and starter kits. SaaS boilerplates, UI kits, Notion templates, and code snippets sell well because they save other developers time. Low support burden, but they need refreshing as frameworks evolve.
• Plugins and extensions. Building on ecosystems people already pay inside — Shopify, WordPress, Figma, VS Code, Chrome — gives you built-in distribution and an audience actively looking for solutions.
• Games. Steam and itch.io make solo publishing viable. Earnings vary wildly; most indie games earn little, while standouts do very well. Treat it as a passion-plus-lottery-ticket category unless you have marketing discipline.

The common thread: distribution matters more than code. A mediocre product with an audience outsells a great product nobody finds.

Selling Time: Freelancing, Contracting, and Consulting

This is where most indie devs actually earn most of their money, especially early on.

• Freelance platforms (Upwork, Toptal, Contra) offer fast access to clients but take fees and push rates down. Best used to build a portfolio, then move clients direct.
• Direct contracting through your network, referrals, or content pays better and builds long-term relationships. One or two retainer clients can fund years of product experiments.
• Consulting and audits — code reviews, performance audits, architecture advice, AI-integration consulting — command higher rates than implementation work because you're selling judgment, not hours.
• Collaboration and revenue splits. Some solo devs partner up: one builds, one markets, and they split revenue. Put the split in writing before the first commit, however friendly the arrangement.

The trap to avoid: client work expanding until product work never happens. Many indies deliberately cap client hours (e.g., three or four days a week) to protect building time.

AI, Content, and Newer Income Streams

The current landscape has opened doors that barely existed a few years ago:

• AI-powered tools and wrappers. Building focused products on top of LLM APIs — writing assistants, code tools, domain-specific chatbots — is one of the most active indie niches right now. Margins depend heavily on API costs, so price with usage in mind. Thin wrappers are easy to clone; defensibility comes from workflow depth, niche data, or audience.
• Sponsorships and open source. GitHub Sponsors, Open Collective, and corporate sponsorship reward maintainers of widely used projects. Reliable only for a minority, but "open core" (free tool, paid hosted or pro version) is a proven model.
• Content and audience. Technical newsletters, YouTube devlogs, blogs, and courses earn via ads, sponsorships, and course sales — and double as the marketing engine for everything else you sell. Many indie devs report their audience, not their code, was the real unlock.
• Crypto and blockchain work. Smart contract development, security auditing, and protocol grants (from ecosystem foundations) can pay well because the skills are scarce and the stakes are high. Be selective: work only on projects you'd stake your reputation on, and treat token-based compensation as speculative, not salary.

A Realistic Path: Stacking Income Streams

Almost nobody goes from zero to full-time product income in one jump. A common progression:

1. Stabilize with freelance or part-time contract work covering living costs.

2. Build in public — share progress on a blog, X/Twitter, or a devlog to grow an audience while you build.

3. Ship something small — a template, plugin, or micro-tool — to learn pricing, support, and marketing with low stakes.

4. Reinvest what works: double down on the product or channel showing traction, and let the rest go.

5. Diversify deliberately — two or three streams is resilient; six half-maintained ones is chaos.

Quick FAQ

• Do I need an audience first? No, but it makes everything easier. Building one alongside your product is the pragmatic middle path.
• Is passive income real? Semi-passive at best. Every product needs updates, support, and marketing — just less than a job.
• How long until product income replaces a salary? It varies enormously; think in years, not months, and plan finances accordingly.

Conclusion

Indie developers make money by combining time-based work (freelancing, consulting) with product bets (SaaS, apps, templates, AI tools) and audience-driven income (content, sponsorships). The pattern behind most success stories is unglamorous: stable client income, small shipped products, consistent public sharing, and patience. Pick one product bet and one income stabilizer, protect your building time, and let compounding do the rest.