Business Ideas for Developers 2026: 30 You Can Ship Solo

What should a developer build to sell, rather than to enjoy building?

The ideas that work for solo developers share a shape: a narrow, boring, expensive problem inside an existing workflow, owned by someone with a budget and no engineering team. Internal tooling for a specific vertical, integrations between two systems that both exist but do not talk, compliance and reporting automation, migration and tooling, and workflow apps that sit on top of a platform with a marketplace all qualify. What fails, repeatedly, is the general-purpose developer tool with no buyer, the consumer app with no distribution, and the clone of a product whose moat is its sales team. A useful test before writing code: can you name three specific companies with the problem, and reach a decision-maker at each this week?

• Platform marketplaces (Shopify, Slack, Atlassian, Chrome) supply distribution you cannot buy
• Vertical + boring beats horizontal + exciting for solo economics
• If your buyer is another developer, expect low willingness to pay and high support load

How much of a software business is actually coding?

Less than most developers expect, and the imbalance is the main reason technical founders stall. Once a product is live, the recurring work is distribution, support, billing, onboarding documentation, churn interviews and pricing changes — code becomes maintenance plus a small stream of high-leverage features. Budget realistically: a first sellable version of a narrow B2B tool is typically four to twelve weeks of part-time work, while reaching consistent revenue takes six to eighteen months of consistent selling. The productive adaptation is to treat distribution as an engineering problem with its own iteration loop — pick one channel, instrument it, and improve it weekly — rather than retreating into the codebase whenever sales feel uncomfortable.

How do you pick one idea from a list like this?

Rank the shortlist against your own constraints rather than the market average. Score each option on four axes: cash needed before the first sale, weeks to first paying customer, whether you already have access to the buyer, and how much of the work you can do without hiring. An idea that scores well on access and time beats a higher-margin idea you cannot reach a buyer for, because the second one burns runway during the discovery phase. Take the top three, then spend a week talking to five potential buyers of each before committing capital — the ranking almost always changes once real buyers answer.

• Cash before first sale is the single strongest predictor of survival
• Buyer access you already have collapses the discovery phase from months to days
• Test the top three with five conversations each before spending anything

What does it realistically cost to start, and how long until revenue?

Most options in this category split into three tiers. Service-led ideas start at roughly $0–2,000 (tools, insurance, a landing page) and can reach first revenue in 2–6 weeks because you are selling time before product. Productised and digital ideas typically run $1,000–10,000 and take 2–5 months, since you must build before you can charge. Inventory, licensed or venue-based ideas start at $10,000+ and rarely see profit inside a year because working capital, compliance and location costs all land before the first customer. Pick the tier that matches your runway, not the one with the best headline margin.

• Service tier: $0–2k, first revenue in 2–6 weeks, margin grows with specialisation
• Digital/productised tier: $1k–10k, 2–5 months, margin scales after break-even
• Inventory or licensed tier: $10k+, 9–24 months, needs working capital planning

How do you validate demand before you build anything?

Demand validation is about getting evidence of payment intent, not enthusiasm. Three cheap tests, in order of strength: take pre-orders or deposits, sell the service manually before automating it, and run a paid landing page for a fixed budget and measure cost per qualified lead. Surveys and "would you use this?" conversations produce false positives because saying yes is free. Set the kill criterion before you start — for example, five paying customers in 30 days or a cost per lead below your target — and honour it. The most common pattern in startup failure data is not a bad idea but a founder who never defined what "no" looked like.

• Deposits and pre-orders are the only signal that reliably survives contact with reality
• Deliver manually first; automate only what you have already sold twice
• Write the kill criterion before the test, not after the result