Skip to content
Topics

Indie Dev with AI: Build, Ship, Monetize Solo

Guides for building, shipping and monetizing your product solo with AI: from idea and spec to implementation, deployment, growth and revenue.

27 articles

Sort articles to find what you need

Articles in Indie Development

What AI Did to IT Freelancers: 5 Studies on How Getting Chosen Changed

What AI Did to IT Freelancers: 5 Studies on How Getting Chosen Changed

The question "will AI take my job" no longer fits this story. Siddiq and Zhang at UCLA Anderson followed 49,610 freelancers and 2.26 million contracts on Upwork from January 2021 to March 2026, and what they found was not a change in whether the work exists but a change in how you get chosen: the weight clients put on human-capital signals fell 7.8% while the weight on price rose 1.1%, and contract counts fell 7.0%. Verified credentials, work history, portfolio and client ratings all lost their power to predict who wins the contract, and the decline is steeper the more recent you look, at -10.1% on signals and +1.8% on price over the most recent four quarters. At the same time the supply side is moving the other way: Upwork reports that the freelance share of skilled US knowledge workers went from 28% to 38% in a single year, with 58% of full-time employees considering the switch. Two paradoxes sit at the center. First, experience is a shield in employment and not in contract work, because Stanford finds employment for workers aged 22 to 25 in AI-exposed occupations about 19% lower with no comparable gap for the experienced, while an Organization Science study of freelancers finds the drop largest among the most experienced. A company hires a role; a client buys a deliverable. Second, the work has not disappeared, the middle has: Management Science reports postings most open to automation down 21%, with the jobs that remain more complex and better paid. The article uses only peer-reviewed papers, preprints and official platform research, each checked against the publisher itself, flags Upwork as an interested party, corrects the widely repeated claim that its February release reported a 44% hourly premium (it does not mention one), and carries the researchers own caveats, including Stanford stating that some of the timing is driven by factors other than AI. Three forecasts come with confidence labels and falsification conditions, and the closing chapter on what to do is labeled speculation.

Marketing for Indie Devs When No One Uses What You Built: How to Get Your First 100 Users [2026]

Marketing for Indie Devs When No One Uses What You Built: How to Get Your First 100 Users [2026]

The most common failure in indie development is "I built it but no one uses it." But the real bottleneck isn't building skill—it's marketing. "Build something good and they'll come" is a fantasy. Build in Public to gather prospects before you build; get the first 10 by hand from people near you (do things that don't scale); find the first 100 by contributing where they gather (communities, social media) so they discover you; and create steady traffic with SEO/AEO/LLMO. This article lays out that order—using AI as your prep hand—from an indie developer's point of view.

Building an MVP Solo with AI: A Practical Guide to Narrowing to One Feature and Shipping Fast [2026]

Building an MVP Solo with AI: A Practical Guide to Narrowing to One Feature and Shipping Fast [2026]

The biggest reason indie projects never get finished is "over-building." Piling on feature after feature makes it complex, and it vanishes before it ever launches. The one way to avoid that is to narrow the smallest product that conveys value—the MVP—to a single feature and ship it as fast as possible. This article explains, from the point of view of an indie developer who makes AI their partner, the right way to see an MVP, scope decisions for cutting features, two routes to build fastest with AI (vibe coding where you write no code, and the hands-on AI-editor route), judging "finished," and getting one person to use it after launch.

Monetization and Pricing for Indie Developers: Landing Your First Paying Users [2026]

Monetization and Pricing for Indie Developers: Landing Your First Paying Users [2026]

An indie product's price is easier to set when the floor comes from per-user AI API cost and payment fees, and the ceiling from the value the customer gets. This article compares fees at Stripe, Paddle, Lemon Squeezy, Stripe Managed Payments, Gumroad, the App Store and Google Play, shows what you keep from a $10/month subscription and how a Merchant of Record changes tax handling, derives a minimum price and usage cap from Claude and Gemini API prices, and covers the official tools for raising and testing prices, all with official prices as of November 2026.

The Complete Roadmap to Solo Development with AI [2026]: From Idea to Launch and Monetization

The Complete Roadmap to Solo Development with AI [2026]: From Idea to Launch and Monetization

Now that AI has a hand that writes code, one person can build a product and ship it. But the information is scattered by stage, so it is easy to get lost about where to start. This article is a full map (roadmap) from idea to design to implementation to launch to monetization, organizing solo development into five phases (Decide, Prepare, Build, Ship, Grow) and, for each stage, showing what to do and which tools to use, then sending you to a dedicated guide for the parts that need a deeper dive. It guides you along two lanes: a Beginner route where you barely write code, and a Hands-on route where you write code in an AI editor, so following whichever fits gets you to something that works without detours. It gathers spec-driven development, AI app builders, Claude Code and Cursor, wiring in AI features (API, RAG, gateway), deploy, SEO/AEO traffic, monetization, cost management, and five pitfalls of solo dev with AI onto one page, with links into the existing hands-on guides.

What Is an LLM Gateway (Proxy)? One API for Every Provider — 2026 Guide

What Is an LLM Gateway (Proxy)? One API for Every Provider — 2026 Guide

You built on OpenAI, then wanted to try Claude and compare Gemini — and lost hours to the different SDKs, formats, and error handling per provider. An LLM gateway (AI gateway / LLM proxy) is a relay you slot between your app and the providers: it exposes one OpenAI-compatible API to reach every model and takes over the cross-cutting chores — fallback, cost tracking, virtual keys, caching, rate limiting, and observability. This guide covers why you need one, what a gateway really is, the three types (self-hosted proxy = LiteLLM / hosted = OpenRouter / SDK = Vercel AI SDK), how to choose among LiteLLM, OpenRouter, and the Vercel AI SDK, minimal setup code that only swaps the endpoint, and the limits — a hop of latency, the gateway as a new failure point, fees (OpenRouter charges 5.5% on purchases), feature loss, and privacy.

What Are Claude Code Permission Modes? Manual, Accept Edits, Plan, Auto, Bypass

What Are Claude Code Permission Modes? Manual, Accept Edits, Plan, Auto, Bypass

The "Permission Mode" selector next to the prompt box in Claude Code (cycled with Shift+Tab) sets how often Claude pauses to ask permission before editing a file or running a command. This guide covers what permission modes are (the oversight-vs-autonomy tradeoff; with v2.1.283 or later, terminal and VS Code sessions start in Auto on every plan (earlier, only on Pro, Max, Ultra, and Team), while claude -p and the Agent SDK start in Manual; protected paths like .git and .claude are never auto-approved outside bypass), the five selector modes (Manual = default, reads only auto-approved; Accept edits = acceptEdits, auto-approves edits and common filesystem commands such as mkdir, rm, and mv inside your working dir; Plan = plan, explores and proposes a plan without editing; Auto = auto, a separate classifier blocks dangerous actions while running everything else without prompts; Bypass permissions = bypassPermissions, nearly everything with no checks, isolated environments only) plus a sixth, dontAsk, which never appears in the Shift+Tab cycle and is set by flag or in settings, how to switch (Shift+Tab cycles Manual, Accept edits, and Plan, with Bypass and Auto joining after Plan when available; the --permission-mode flag; and defaultMode in settings, where auto and bypassPermissions don't take effect from project settings), auto mode in depth (the classifier's allow/block defaults, available by default on Team and Enterprise unless an admin turns it off, supported models Opus 4.6+, Sonnet 4.6+, or Fable, conversational boundaries honored as block signals, and the 3-consecutive / 20-total block fallback), which mode to use when and safety (bypass has no prompt-injection protection so it's isolated-only; Auto is the right answer for everyday prompt fatigue; hooks still run in bypass; with bypass available in a terminal, plan mode doesn't stop edits), and how permission mode relates to the effort setting (permission mode = how much it asks, effort = how hard it thinks). Based on the official docs and the desktop app's UI as of October 5, 2026.

What Is Claude Code's "Effort" Setting? A Guide to Faster vs Smarter

What Is Claude Code's "Effort" Setting? A Guide to Faster vs Smarter

That "Effort" slider next to the model name in Claude Code — the Faster-to-Smarter dial — sets how much work (thinking, tool calls, and response text) the AI puts into each reply. This guide covers what effort is; the slider's 5 levels and labels (the API has 5 levels, low to max; the slider reads Low, Medium, High, Extra, Max, where "Extra" = xhigh and the top effort is "Max"); what persists (low–xhigh are saved per model when you confirm with Enter, Max is session-only); model support and auto-downgrade (xhigh needs a relatively recent model such as Fable 5.1, Opus 5.5, or Sonnet 5.5; Opus 4.6 and Sonnet 4.6 have no xhigh and downgrade to high; the legacy Haiku 4.5 has no effort control while Haiku 5.5 supports every level; Claude Code's default varies by model: medium on Opus 5.5, Sonnet 5.5, and Haiku 5.5, high on Fable 5.1); how to set it (/effort slider and direct values, /effort auto, /model, --effort, the CLAUDE_CODE_EFFORT_LEVEL env var as highest priority, the modelSettings and effortLevel settings, and skill/subagent frontmatter); a quick-reference table; an in-depth look at Ultracode (not an effort step but an on/off switch that works at any level and has Claude build multi-agent dynamic workflows on its own; limited to xhigh-capable models; turned on with /effort ultracode, the Tab key, or "ultracode": true in settings; when to use it, cost cautions, and what changed in v2.1.284); and related features (ultrathink, /fast). Based on official docs (as of September 2026) and the live UI.

What Are Claude Code Hooks? Run Shell Commands Deterministically

What Are Claude Code Hooks? Run Shell Commands Deterministically

Claude Code hooks make Claude Code itself run your commands at defined points, every time. This guide tables all 33 events in the official Hooks reference (when each fires, whether exit code 2 blocks it, and what JSON it can return), explains the three-level settings.json format, matcher rules, locations, default timeouts, and exit codes 0, 2, and 1, and gives six ready-to-use examples with settings and scripts in the official style: blocking dangerous commands, protecting files, formatting after edits, notifications, re-injecting context after compaction, and requiring passing tests. It ends with a troubleshooting table and safety notes such as workspace trust in -p runs.

You've hit your session limit / 5-hour limit in Claude Code: Fixes

You've hit your session limit / 5-hour limit in Claude Code: Fixes

Claude Code's "You've hit your 5-hour limit · resets 3:45pm" means your plan's 5-hour usage window ran out; it is not a bug. Before v2.1.312 (October 27, 2026) it read "You've hit your session limit", and around 2025 "Claude usage limit reached". This article lists every limit message (5-hour, weekly, Opus, Sonnet, Fable and monthly spend limit, with old and new wording), how limits differ on Pro, Max and Ultra (verified Ultra accounts have no 5-hour limit), where to see what is left (/usage, the status line, Settings → Usage), your options when you hit a limit (wait for automatic continue, usage credits, a limit reset, switching models, an API key or an upgrade) and what to check before switching to an API key, all checked against the official changelog, error reference and help center.

What Is Spec-Driven Development (SDD)? The Four Steps, Tools, and How It Differs from Vibe Coding

What Is Spec-Driven Development (SDD)? The Four Steps, Tools, and How It Differs from Vibe Coding

In an era where AI writes the code, the higher-value skill is shifting from "writing code" to "writing the spec" — and the practice that captures it is spec-driven development (SDD). SDD puts the spec at the center of the project as the source of truth, and an AI agent derives the design, breakdown, and implementation from it instead of coding right away. The key is that each step leaves a document (often Markdown) that the next step reads. This beginner-friendly guide covers what SDD is (the spec is canonical; code is a derivative), why it matters now (it prevents vibe coding's "three-month wall" of technical debt and requirements drift at the design stage), the basic four steps (Specify → Plan → Tasks → Implement), the main tools (GitHub Spec Kit with 140,000+ stars and 30-plus supported agents, AWS Kiro with its Requirements → Design → Tasks flow and Auto router, plus BMAD, OpenSpec, Tessl, Google Antigravity, and Cursor), when to use it versus vibe coding (a hybrid: vibe to explore, spec-driven to ship, with mandatory human review), and how to try it today. In the AI age, the people who rise are those who can define precisely what to build, not those who write code fastest.

The First Step to Earning From Home With AI, From Zero — A No-Face-to-Face Start for Hikikomori and NEETs

The First Step to Earning From Home With AI, From Zero — A No-Face-to-Face Start for Hikikomori and NEETs

Going outside is hard, talking to people is tough, and you are not working right now. This guide sets out the decisions and calculations for starting to earn a small income from home with AI, through written messages only. It compares five ways to start (bidding for jobs, listing a service, digital products, ebooks, stock content) by how much contact with people they need and their first hurdle, calculates take-home pay from the official fees of Upwork, Etsy, Gumroad and Amazon KDP, and checks it against AI subscription costs. It also covers the AI disclosure rules of Adobe Stock and KDP, a 30-day plan, the scam signs listed by the FTC, and what to check on taxes and dependents.