Which AI model should I use?

The frontier model with long context for thinking and writing. A code-specific assistant for engineering. That's usually enough. Adding more tools rarely adds productivity — it adds context-switching cost.

How much should I pay for AI per month?

If AI saves you 90 minutes a day at a $300/hour rate, that's $450/day of value. Pay whatever buys that. Most founders under-pay because they treat AI as a $20 toy instead of as a tool with leverage proportional to model quality.

Will AI replace founders?

No. AI compounds founder judgment; it doesn't replace it. The bottleneck is taste and decision-making, both of which are still human.

All hubs

AI for founders — practical workflows, not hype

AI is not a magic productivity multiplier; it's a power tool. Used well, it compresses a week of solo-founder work into a day. Used badly, it generates beautifully written nonsense at scale. This guide is about using it well.

Last updated May 19, 2026

Who this is for

Solo founders and operators using AI to compress weeks of work.

What you'll learn

What AI is actually good at (and not)
AI workflows by founder function
Prompt patterns that produce useful output
Risks and the no-API-cost AI stack

Try the journey builder

What AI is good at (and not)

Good at:

First drafts of anything (emails, plans, docs, specs)
Research compilation (competitor lookups, market sizing summaries, regulation overviews)
Editing your own writing (cuts, sharpens, tightens)
Idea generation when you're stuck
Pattern recognition across a body of text

Not good at:

Customer conversations
The first formulation of a decision
Anything where being wrong damages a relationship
Strategy (it's great at execution, mediocre at compass-setting)
Numbers that need to be exactly right (always double-check)

The pattern: AI accelerates execution dramatically. It does not improve judgment.

Workflows by founder function

Customer conversations. Don't delegate. Do use AI to transcribe and synthesise after — patterns across 20 interviews become visible in 5 minutes.

Marketing content. AI drafts the first version at speed; you edit ruthlessly. The edit step is where leverage lives. Without it, you ship generic AI prose at scale.

Sales emails. Pattern templates with AI; personalise the first sentence by hand. The 5-second personalised opener is the difference between 2% and 12% reply rates.

Engineering. AI code assist works best when you have a clear spec. For ambiguous problems it can lead you down expensive rabbit holes.

Operations. Process docs, SOPs, weekly summaries are perfect AI territory.

Strategy. Use AI as a thinking partner, not an answer machine. "Argue against this decision" is a great prompt; "What should I do?" is not.

Prompt patterns that work

Three patterns that consistently outperform single-shot prompts:

Role + constraint + format. "Act as a senior operator. In 200 words, give me three sharp counters to the following argument: [...]"
Two-sided. "Write the optimistic case and the pessimistic case for [...]. Then pick the more likely one."
Worked example. "Here's a template I like for an investor update: [...]. Write one in this style for the following situation: [...]"

What doesn't work: vague open prompts ("write a marketing plan"), excessive politeness, asking AI for "the answer" without giving it constraints.

Risks and the no-API-cost stack

Risks:

Hallucinations in factual content. Always verify numbers, citations, legal references.
Voice drift if you let AI write everything — your work starts sounding generic.
Privacy. Don't paste customer data into general-purpose chatbots without checking the terms.
Strategic homogenisation. When everyone uses the same model, everyone gets the same advice. The edge is in editing.

No-API-cost setups (work today):

Run prompts in a single chat interface; copy the output into your tools.
Use deterministic templates and calculators where the inputs are structured.
Use the Business Idea Scorecard, Founder Journey Builder, and others on this site — they apply rules without ever calling a paid model.

Step-by-step action plan

Do these, in order

1Audit your week — list every task that took >2 hours
2For each, ask: can AI do the first 70%?
3Build a prompt library for the 5 tasks you do most
4Edit ruthlessly; never ship AI output unedited
5Use deterministic tools (calculators, scorecards) for anything numeric

Frequently asked questions

Which AI model should I use?: The frontier model with long context for thinking and writing. A code-specific assistant for engineering. That's usually enough. Adding more tools rarely adds productivity — it adds context-switching cost.
How much should I pay for AI per month?: If AI saves you 90 minutes a day at a $300/hour rate, that's $450/day of value. Pay whatever buys that. Most founders under-pay because they treat AI as a $20 toy instead of as a tool with leverage proportional to model quality.
Will AI replace founders?: No. AI compounds founder judgment; it doesn't replace it. The bottleneck is taste and decision-making, both of which are still human.

Related resources

AI Co-Pilots for Solo Founders

Prompt Library for Founders

RAG vs Fine-Tune — A Decision Frame

Related tools

Business Idea Scorecard

Founder Journey Builder

Related templates

Weekly Founder Review

Related courses

AI-Powered Business Growth

Related hubs

How to Start a Business

A practical, operator-grade guide to starting a business in 2026 — idea selection, validation, first customers, legal setup, cash flow, and the tools to use today.