Indie hacker

Without outside money, every decision must pay for itself in cash. That pushes an indie hacker toward small, sharp products with a clear buyer and a price from day one, not large unproven bets.

The main benefit is freedom. A small, profitable business can change direction, close a product or start another without answering to anyone.

The trade-off is real. Growth is usually slower and the ceiling lower than a funded competitor could reach, and one person carries support, sales and development. That suits someone who values independence over scale.

• Start with a narrow problem that a specific group already pays to solve.
• Ship a small version quickly and charge for it as soon as it works.
• Keep costs low enough that a handful of customers covers them.
• Find buyers before building too much. Distribution-first thinking matters because nobody finds a product that has no audience.
• Share progress where it helps, as marketing and accountability (build in public).
• Say no to features and customers that need a team to support.

The phrase became common through the Indie Hackers community, where solo makers share their revenue and methods openly. An indie hacker is usually a developer, designer or marketer who builds a product, often software, and sells it directly. Typical products are a niche tool, a template pack, a newsletter, a plugin or a small subscription service. The term overlaps with bootstrapping and Micro-SaaS.

The tools that make this possible are cheaper than ever. AI coding assistants, no-code builders and payment services let one person do work that once needed a team.

• Building for months without asking anyone to pay.
• Tracking followers and traffic when revenue is the number that funds the next month.