How Indie Developers Make Money: What Works & What Doesn't

Most advice about indie developer income is either survivorship bias ("I built an app in a weekend and quit my job") or vague hustle talk. Here's a grounded breakdown of the revenue models solo developers actually use, which ones tend to compound, and which ones quietly burn months of effort — including where AI and crypto realistically fit in.

What Actually Works for Most Solo Developers

The common thread in the models below: someone pays you directly, repeatedly, for solving a specific painful problem.

• Niche B2B SaaS. Small subscription tools aimed at businesses — not consumers — remain the most reliable path to recurring revenue. Businesses pay for time saved and have budgets; consumers churn. The narrower the niche, the easier it is to reach buyers and the less likely a big player will bother competing.
• Paid developer tools, plugins, and extensions. Plugins for established ecosystems (IDE extensions, CMS plugins, Figma or Shopify add-ons, game engine assets) let you piggyback on someone else's distribution. The marketplace brings buyers; you bring a focused solution.
• One-time-purchase desktop and mobile apps. Less fashionable than SaaS, but simpler: no server costs to speak of, no churn management. Works best for utilities people search for by name of the problem.
• Freelancing and consulting as a funding engine. Not passive, but it's the fastest money in this list and the most common way indie devs fund their product work. Specialists (a stack, an industry, a migration type) charge meaningfully more than generalists.
• Templates, boilerplates, and starter kits. Selling a well-documented codebase that saves other developers weeks of setup is a proven model — especially for auth, billing, and AI-app scaffolding.
• Sponsored open source. Sponsorships and paid support tiers around a genuinely useful open-source project can work, but usually only after the project has traction. Treat it as a slow-compounding asset, not a launch strategy.

What Usually Doesn't Work

These aren't impossible — they're just where solo developers most often lose a year.

• Consumer apps monetized with ads alone. Ad revenue requires enormous traffic. A solo app without a distribution plan almost never gets there, and per-user ad income is tiny compared to even a cheap subscription.
• "Build it and they will come." The most common failure mode isn't bad code; it's zero distribution. If you can't name where your first 100 users will come from, the product isn't ready to build.
• Cloning a crowded category. Another generic to-do app, note tool, or AI chatbot wrapper competes on marketing budget — the one resource a solo dev doesn't have.
• Speculative crypto projects as a business plan. Launching a token or NFT project is not a product business; it's a bet on market timing with real legal and reputational risk. The durable money in blockchain for solo devs has been in the picks-and-shovels layer: audits, tooling, infrastructure, and contract work for funded teams.
• Chasing every trend simultaneously. Six half-finished projects earn less than one finished one. Portfolio breadth comes later, after one product carries itself.

Where AI Fits — Honestly

AI has changed indie development in two ways, one overhyped and one underrated.

Overhyped: thin wrappers around a model API. If your product is "a prompt plus a textbox," the platform vendors can absorb it in a release cycle, and users can replicate it in a chat window.

Underrated: AI as a force multiplier for you. Solo developers now ship faster — boilerplate, tests, marketing copy, support drafts — which shrinks the time from idea to paying customer. The winning AI products from indie devs tend to embed a model inside a workflow the developer deeply understands (a niche industry's document processing, a specific dev-tooling pain), where the moat is the workflow knowledge, not the model.

If you sell AI-powered features, watch your unit economics: inference costs scale with usage, so price accordingly or cap usage tiers.

How to Choose Your Model

A quick filter that saves months:

1. Start from a problem you've personally had or been paid to solve. Familiarity with the buyer beats familiarity with the tech.

2. Prefer boring, reachable audiences. Can you find these people in a specific subreddit, forum, marketplace, or industry group? If not, distribution will be your bottleneck.

3. Charge from day one. Free tiers delay the only real validation signal: a stranger paying.

4. Stack models over time. Many sustainable indie incomes are hybrids — consulting that funds a SaaS, a newsletter that markets a template, an open-source tool that feeds paid support.

FAQ

Do I need an audience first? No, but you need access to one — a marketplace, a community, or an SEO niche. Building a personal audience helps but is its own multi-year project.

Is freelancing a distraction from products? Only if it's random work. Freelancing in the same niche as your product is paid customer research.

Conclusion

Indie developers who earn consistently do a few unglamorous things: pick a narrow paying audience, charge real money early, ship one thing to completion, and use trends like AI as leverage rather than as the product itself. The models that fail share one trait — they depend on scale, luck, or hype that a solo developer can't manufacture. Choose the boring, direct path: a specific buyer, a painful problem, a price tag.