The Lean AI Stack for a Solo Founder
You don't need fifteen AI subscriptions to run a one-person business. You need a small stack that covers the jobs you'd otherwise hire for. Here is the four-role setup I'd actually start with.
- #entrepreneurs
- #founders
- #tools
The trap for a solo founder is collecting tools. There is a shiny AI product launched every week, and each one promises to be the thing. Resist it. A one-person business does not need a tool zoo — it needs a small stack that covers the roles you would otherwise have to hire for, and the discipline to stop there.
Think in roles, not products
A startup, even a tiny one, has a handful of jobs that always need doing: building the thing, deciding what to build, talking to customers, and keeping the lights on operationally. Map your AI tools to those roles and the stack picks itself.
- The builder — a strong general assistant (a frontier chat model) for thinking through decisions, drafting, and coding. This is your most-used tool; pay for the good tier.
- The maker — whatever produces the actual output your business sells or markets: code in an AI-native editor, design in a tool like Canva, content in your writing tool of choice.
- The researcher — a citation-first tool for market and competitor questions you need to get right, not just fast.
- The operator — your workspace AI (notes, docs, simple automations) that keeps the boring recurring work from eating your week.
Four roles. Often three or four tools. That is a complete stack for most solo founders.
Where AI doesn't replace you
It will not decide what is worth building. The classic startup advice — talk to users, build something people want — is more important when AI makes building cheap, not less. When anyone can ship fast, judgment about what to ship is the moat. Keep that job for yourself.
This week
List the four roles above and write the single tool you use for each. If a role is empty, fill it. If a role has three tools, cut to one. A lean, deliberate stack beats an impressive-looking pile every time.
Sources
Keep reading
More guides like this one.
The AI Skill Worth Learning Now: Context Engineering
Prompt engineering was never really a job, and the models got good enough to do it for you. The skill that's actually sticking is context engineering. Here's what it is and how to start.
AI Certifications a Hiring Manager Actually Reads
As an EM who screens resumes, most AI certificates tell me nothing. A few tell me something useful. Here is the honest difference, and how to make any course actually count.
Context Engineering: The Skill That Outgrew Prompting
Clever prompts were the 2024 skill. The 2026 skill is managing what the model can see — its instructions, tools, history, and data — as a finite budget. Here is the shift, in plain terms.