Linh Truong · Solo AI company · 2026

The One‑Person AI Company Playbook

How I run a solo AI business—strategy, stack, workflows, monetization, distribution, defensibility, finance, legal, and the habits that keep you from burning out. No hiring or fundraising required to start.

Author: Linh Truong, MA (Harvard), MBA Source: LinhTruong.com Email: Linh@Alumni.Harvard.edu For: Solo founders, indie hackers, consultants, creators Reading time: ~45 min Updated: May 2026

1 · The Thesis & 2026 Landscape

One operator can now serve thousands of customers at software margins—if you design for it. Cheap inference, agent runtimes, and composable SaaS collapsed the marginal cost of build, market, support, and ops. The unit of entrepreneurship is often one person plus an agent fleet.

10–100×
Productivity vs. 2022 solo founder
$0–$300
Typical monthly stack cost
7–30 days
Idea → paying customer
70–95%
Gross margin range

KPI bands are directional—verify in §17 before citing.

Why now (2026)

Inference

Cost collapse

Per‑token costs fell ~10× year‑over‑year. Tasks that were uneconomical in 2024 (long‑context research, agent loops, document generation) are now sub‑cent operations.

Agents

Long‑horizon work

Multi‑hour autonomous agents reliably handle research, coding, ops, and outreach. Operators design workflows, not tasks.

Distribution

Algorithmic reach

Short‑form video, AI‑native search (Perplexity, ChatGPT, Claude), and creator marketplaces give zero‑cost access to global niches.

Payments

Stripe‑class rails

One‑click global payments, subscriptions, tax, and invoicing — including USDC and embedded finance — work out of the box.

Talent surplus

On‑demand specialists

Fractional designers, lawyers, accountants, editors available hourly via Upwork, Contra, MBO — most of your "team" rents by the task.

Capital

Bootstrap viable

VC is no longer the default path. Solo businesses with $300K–$3M ARR are common, durable, and increasingly valuable to acquirers.

What I keep in mind

A one‑person AI company isn't a startup with fewer people. It's a different shape: one operator, an agent fleet, a sharp market, optimizing for cash and freedom—not scale at all costs.

2 · The Operating Model

Your company is a graph of seven loops. Most solo founders over‑invest in one (usually Build) and starve the rest. I keep all seven turning weekly, on a fixed cadence.

Diagram 2.1 — The Seven‑Loop Operating Model
Operator + Agent Fleet 1. Discovery customer interviews 2. Build ship weekly 3. Distribute audience + SEO + ads 4. Monetize price, package, close 5. Retain support + success 6. Automate agents + SOPs 7. Learn metrics + review

Weekly cadence (the heartbeat)

DayPrimary LoopOutput
MonDiscovery + Learn3 customer conversations, 1 metric review, 1 hypothesis updated
Tue–WedBuild1 shipped feature or new offer iteration
ThuDistribute3 content artifacts, 1 channel experiment
FriMonetize + RetainPipeline review, follow‑ups, support cleanup
Sat (½)Automate1 new SOP or agent, kill 1 manual task
SunOff / ReflectWeekly review (15 min), next‑week plan (15 min)

3 · The AI Solo Stack

The stack below is opinionated, current to May 2026, and tuned for cost, leverage, and exit‑optionality. Most categories have viable open‑source alternatives; the principle is to own your data and your distribution, rent everything else.

Diagram 3.1 — Layered Stack
Brand & Distribution Website (Framer/Astro) · Newsletter (Beehiiv/Kit) · X/LinkedIn/YouTube · Podcast · Community (Circle/Discord) Product Surfaces Web app · Slack/Teams app · API · Chrome extension · Mobile · Embeddable widget · Marketplace plugin Agent Layer Claude Agent SDK · LangGraph · Inngest/Trigger · n8n · MCP servers Model Layer Anthropic Claude · OpenAI · Google · OSS via Together/Groq · local Llama for privacy Application Runtime Next.js/Astro · Cloudflare Workers · Vercel · Supabase · Convex Data & Memory Postgres · pgvector/Pinecone · S3/R2 · DuckDB · Logs (Axiom/Datadog) Commerce & Ops Stripe · Lemon Squeezy · Outseta · Mercury/Wise · Notion · Linear · Plain Identity & Compliance Clerk/WorkOS · Vanta · Cloudflare · 1Password · audit logging The Operator (You) Strategy · taste · customer empathy · narrative · judgment · learning velocity — the only layer that doesn't commoditize.

Recommended starting kit (under $300/mo)

CategoryPickWhy~Monthly
Coding agentClaude Code (Opus 4.7)Best long‑context coding, agentic, plays well with subagents$100–200
HostingVercel / CloudflareZero‑ops, generous free tier, scales to millions$0–20
DBSupabase / NeonPostgres + auth + storage; pgvector built‑in$0–25
PaymentsStripeGlobal, taxes via Stripe Tax, B2B invoicing2.9% + 30¢
EmailResend / LoopsTransactional + lifecycle in one$0–20
NewsletterBeehiiv / KitBuilt‑in monetization, referral tools$0–49
Site/CMSFramer / AstroDesigner‑grade speed, SEO‑friendly$0–25
AnalyticsPostHog / PlausibleProduct + privacy; session replay; flags$0–30
Workflown8n / InngestDurable agent loops without infra$0–20
BankingMercury / WiseMulti‑currency, virtual cards, API$0

4 · Idea Selection & Validation

Most one‑person businesses die in week 12 because the founder picked a market that can't pay, won't switch, or doesn't exist. Use this two‑axis filter before writing a line of code.

Diagram 4.1 — The Solo‑Founder Idea Matrix
High pain / urgent Low pain Few competitors / niche Crowded / commodity SWEET SPOT Specific niche, paying now, no incumbent owns it DIFFERENTIATE OR DIE Need a 10× wedge, or strong distribution VITAMIN Cool, but hard to sell — avoid as first product GRAVEYARD Don't build — no urgency, no whitespace

The 7‑question idea screen

  1. Whose money? Name 10 specific people who would pay. If you can't, you don't have an idea — you have a daydream.
  2. Bleeding neck? Is the pain measurable in dollars, hours, or risk? Vitamins lose to painkillers every time.
  3. Budget already exists? Buyers replace line items 10× faster than they create new ones.
  4. Reachable channel? Can you find them in one place (subreddit, Slack, trade show, search query)?
  5. Repeatable wedge? What's the one promise that hits in <30 seconds?
  6. Solo‑doable? Is the v1 buildable in 4–6 weeks by one person with AI leverage?
  7. Compounding asset? Does each customer make the next one easier (data, brand, distribution)?

Validation in 14 days

Day 1–3
20 interviews
Day 4–6
Landing page
Day 7–9
Pre‑sell
Day 10–12
Concierge MVP
Day 13–14
Decide

Decision rule: if you can't get 3 paid pre‑orders (even $1 deposits) or 10 strong "I'd pay X for that" commitments by day 14, kill it and re‑enter the funnel. Sunk cost is the #1 solo‑founder killer.

5 · Monetization Models

Pick a model based on your energy budget and exit goals — not what's trendy. Most solo operators stack 2–3 of these in concentric rings (front‑end / core / back‑end).

ModelBest forMarginEffortCeilingNotes
Pure SaaSRepeatable workflow pain80–95%High (eng)$1M–$10M ARRBest long‑term asset; hardest first 6 mo
AI‑native productized serviceAgencies, consultants60–80%Medium$300K–$1MFastest to first $10K MRR
Info product / cohortExperts, creators85–95%Bursty$200K–$2MNeeds audience first
Newsletter + sponsorshipDomain writers80–90%Steady$100K–$3MCompounds slowly
Marketplace / directoryAggregators70–90%Front‑loaded$100K–$5MSEO + winner‑takes‑most
API / micro‑toolDevelopers70–90%Low maintenance$50K–$500KGreat as 2nd product
Affiliate / arbitrageSEO operators60–80%Variable$50K–$1MPlatform‑risk heavy

The pricing ladder

Diagram 5.1 — Concentric Pricing Rings
$10K+ $300–2K $29–99/mo Free / Lead magnet Newsletter · template · free tool · open‑source repo ↓ SaaS / membership · self‑serve ↓ Done‑for‑you / cohort / pro plan ↓ Enterprise / consulting / equity deals

Pricing principles

6 · Build: The 30‑Day MVP Loop

Goal: paying customer by Day 30. Not "launched," not "feature‑complete" — paid. Anything else is rationalization.

Diagram 6.1 — 30‑Day Build Loop
W1 Validate Interviews · LP · 3 pre‑orders W2 Concierge MVP Manual delivery, no code yet W3 Automate core Agent + UI for the 1 critical job W4 Launch + bill Stripe live · public launch · onboard Daily: 1 customer convo · 1 ship · 1 piece of content

The "one critical job" rule

Your v1 does one thing for one persona in one workflow. Examples that work:

Build principles for one operator

Boring stack, bold product

Use the most boring, well‑documented tools available (Next.js, Postgres, Stripe). Save your novelty budget for the customer‑facing magic.

Concierge before code

Deliver the first 5–10 customer results manually (or human‑in‑loop with AI). You'll learn the workflow before automating the wrong thing.

One agent, not ten

Start with one well‑scoped agent. Multi‑agent orchestration is seductive and almost always premature. Add agents only when a clear handoff emerges.

Evals from day 1

For every AI‑powered feature, maintain ≥30 example inputs with expected outputs. Run them on every prompt or model change. This is your only defense against silent regressions.

Cost telemetry early

Log token usage per user, per feature, per day. AI margin compression is silent — you'll feel it only when it's too late.

Ship daily, narrate weekly

Public changelog + weekly "what shipped" post. Builds trust, generates SEO, recruits early evangelists.

7 · Distribution & Growth

For a solo operator, distribution is not a department — it is half the company. If you can't get attention, you don't have a business; you have a hobby.

Diagram 7.1 — The Distribution Flywheel
Create in public build · teach · post Audience followers · email · DMs Customers paid · retained · referrers Insights pains · wins · stories

Channel selection

ChannelTime‑to‑signalCompoundingBest when
SEO + programmatic3–6 months★★★★★You have unique data or a niche tool
YouTube (long‑form)2–6 months★★★★★You can teach and tolerate camera
Short‑form (TikTok/Reels/Shorts)2–8 weeks★★★★Consumer or prosumer; visual product
X / LinkedIn2–6 weeks★★★B2B SaaS, consulting, info products
Newsletter3–12 months★★★★★Domain expertise; owned audience
Cold outbound1–2 weeks★★B2B, ACV > $3K, niche reachable
Paid adsDays★★Proven LTV/CAC > 3; not as first channel
Partnerships / affiliates1–3 months★★★Adjacent tools share your ICP
Communities (Reddit/Slack/Discord)2–8 weeks★★★Genuine participation, not posting
AI‑native search (LLM SEO)1–4 months★★★★Optimize for being cited by ChatGPT/Claude/Perplexity

Solo rule

Pick one primary channel (your "loud" channel) and one supporting channel for the first 6 months. Repurpose ruthlessly. Switching channels every month is the most common failure pattern in solo distribution.

The content engine (1 → 10 repurposing)

Diagram 7.2 — One pillar piece becomes ten
Pillar piece YouTube · essay · podcast 3 X/LinkedIn threads 5 short‑form video clips 1 newsletter issue 1 SEO blog post 1 lead magnet / template Funnel: opt‑in → trial → paid measured per piece, weekly

LLM‑era SEO (being the answer)

The fastest‑growing acquisition channel in 2026 is not Google — it's being cited inside ChatGPT, Claude, Gemini, and Perplexity answers. Optimize for:

8 · Daily Workflow & Time Design

You will out‑think, out‑ship, and out‑last competitors not by working more hours, but by spending your hours on irreversibly compounding work.

Diagram 8.1 — The Operator's Day (3 modes × 3 blocks)
Morning · MAKER (3–4h) Deep work · build · write · design · model training · 1 daily ship Midday · MANAGER (1–2h) Customer calls · email · agent reviews · ops · billing Late · MARKETER (1–2h) Content · DMs · community · partnerships · light analytics review Buffer 1–2h: walks, exercise, learning. Never schedule to 100% capacity.

Time philosophy

Asymmetric

Two‑way vs one‑way

Spend ≥60% of decisions on reversible bets executed fast. Reserve serious deliberation only for one‑way doors (pricing model, brand name, legal entity).

Compounding

Asset vs activity

Every Friday, ask: "What did I do this week that still pays me in 12 months?" If the answer is "nothing," redesign next week.

Energy

Cycles, not calendars

Track energy, not just time. Solo founders crash from energy debt, not workload. Sleep, training, and walks are P0.

The "Kill, Keep, Delegate" review (weekly, 20 min)

9 · Agentic Automation Blueprints

The point of a one‑person AI company is not "use AI." It is to convert every recurring task into a durable, monitored workflow that runs without you. Here are the canonical solo blueprints.

Diagram 9.1 — The Solo Agent Fleet
Operator strategy · review · escalations Research Agent market scans · competitor tracking daily digest in Slack Content Agent draft · repurpose · schedule always human‑reviewed Sales Agent enrich · personalize · follow up human signs every send Support Agent L1 replies · ticket triage escalates >0.3 risk score Ops Agent invoicing · reconciliation monthly close prep Product Agent PR review · refactors eval runs on every change Analytics Agent weekly KPI brief anomaly alerts Hiring Agent contractor sourcing brief + shortlist

Blueprint library

Daily morning brief (10 min to set up)

Agent: pulls overnight signups, revenue delta, support ticket queue, top‑3 competitor moves, your top KPI vs target. Delivers as one Slack/email message at 7:00 AM. Replaces 30+ min of manual checking.

Customer interview synthesizer

Agent: transcribes every Zoom call, tags by persona/pain/objection, appends to a "Voice of Customer" doc, and re‑clusters monthly. Output: a living taxonomy of pains you can paste into landing pages and ad copy.

Outbound personalization

Agent: takes a list of leads, enriches via web + LinkedIn + the prospect's last 30 days of public output, drafts a personalized message in your voice, queues for your one‑click approval. Send rates: 40–80% reply lift over generic templates.

Support deflection

Agent: classifies inbound, auto‑answers tier‑1 (docs‑answerable) questions, summarizes the rest for you with a draft reply. Tracks deflection rate weekly. Goal: 60–70% deflection without CSAT drop.

Content engine

Agent: takes weekly pillar piece, derives threads, scripts, blog post, and lead magnet variants. You approve a queue once a week. Schedules across platforms.

Finance close

Agent: reconciles Stripe → Mercury → bookkeeping software. Flags anomalies. Prepares a 1‑page month‑end P&L and a 13‑week cash forecast.

Agent governance (non‑negotiable)

Every agent has: (1) a written scope, (2) explicit "must escalate" triggers, (3) an evaluation set, (4) cost ceilings per run, (5) audit logs. An ungoverned agent is a liability factory.

10 · Defensibility & Moats

"AI is now a feature, not a moat." True. So what is the moat for a solo operator? Six options — most successful solo companies stack 2–3.

Distribution

Owned audience

An email list, YouTube channel, or community you built over years. The single hardest moat to replicate. Often the only real one for content/info businesses.

Brand & taste

Personal authority

You are recognized as the person for X. Compounds with content. Survives platform changes. Resistant to commoditization.

Workflow lock‑in

Embedded in operations

You're the daily tool. Switching costs (data, habit, integrations, billing) compound. Critical in B2B SaaS.

Proprietary data

Your own dataset

You collect (legally) what others can't: customer interviews, niche benchmarks, structured outputs. Improves your model and is hard to copy.

Network effects

Multi‑sided value

Marketplaces, directories, social tools. Rare for true solo plays but very durable when achieved.

Operator velocity

Compounding skill

You ship faster, learn faster, and have lower fixed costs. Not a moat at one snapshot — but a powerful moat over a 24‑month window.

The honest moat stack

For 90% of one‑person companies, the realistic moat is: narrow niche + audience + brand + velocity. Don't pretend your moat is your code or your prompts — it isn't. Build the durable ones early.

11 · Finance, Legal & Tax

Most solo founders treat this as overhead. Treat it instead as infrastructure for sleep. A well‑structured solo company is boring on purpose.

Entity & banking (US‑centric; consult a pro for your jurisdiction)

The solo P&L (target shape at $300K ARR)

Line% of revenueNotes
Gross revenue100%Net of refunds
– AI / infra costs5–15%Watch closely; alerts at thresholds
– Payment fees3–4%Stripe, PayPal
– Tooling / SaaS3–8%Audit quarterly; kill unused tools
– Contractors5–20%Designer, editor, legal, accounting
– Marketing0–15%Mostly content; ads only when LTV/CAC>3
Operator pay40–60%Pay yourself; "all in the business" is a trap
Retained / tax reserve10–20%Smooths bad months, funds bets

Legal & compliance baseline

Contracts

  • Terms of Service + Privacy Policy (start with a vetted template; have a lawyer review at $5K MRR).
  • DPA template for B2B customers (table‑stakes by 2026).
  • Independent contractor agreements (IP assignment + NDA) for every freelancer.
  • Acceptable Use Policy if you offer AI generation features.

AI‑specific

  • Clear data handling disclosure: what you log, retain, train on. Default: do not train on customer data.
  • Model provider terms compliance (output ownership, usage caps).
  • If serving EU/UK: GDPR + (where in scope) EU AI Act tier check.
  • If serving regulated industries (health, finance, legal): explicit "not advice" disclaimers and access controls.

Cash flow rules

12 · Risk, Compliance & Failure Modes

Top operational risks

  • Platform dependence — single‑channel acquisition, single model provider, single payment processor.
  • Margin compression — token costs creep, you don't reprice, you bleed.
  • Silent regressions — prompt change degrades quality; no evals catch it.
  • Outage exposure — provider downtime kills SLAs; no fallback model.
  • Agent misbehavior — autonomous action sends bad email, books wrong call, leaks data.

Mitigations

  • Two acquisition channels at all times; portable email list.
  • Multi‑provider routing (Claude primary, GPT/Gemini fallback) on critical paths.
  • Eval suite + canary deploy for prompt and model changes.
  • Status page + incident SOP, even at one customer.
  • Hard scopes, allow‑lists, dry‑run modes, audit logs for every agent action.

Common failure modes (in order of frequency)

  1. Building before selling. Six months of code, zero conversations. The cure: 20 interviews before line 1.
  2. Audience neglect. "Build it and they will come" is the loudest lie in solopreneurship.
  3. Feature creep instead of customer love. Each new feature is a slower path to product‑market fit, not faster.
  4. Pricing too low. $9/mo plans attract the worst customers and starve the business. Charge for value.
  5. No retention focus. A 5% monthly churn cap on a $50 ACV product makes meaningful growth impossible.
  6. Solo isolation. No peer feedback loop → bad decisions compound silently.
  7. Health collapse. The business outlives the founder. Or doesn't. Sleep is a P0 KPI.

The "Stop‑doing" list

Most solo founder progress comes from removing, not adding. Quarterly, run the list: features no one uses, channels with no conversion, tools you forgot you pay for, meetings that don't move metrics. Cut without sentiment.

13 · Psychology, Energy & Burnout

The hardest problem in a one‑person company is not the technology. It is the single point of failure that is you. Treat your nervous system as production infrastructure.

Identity

You are an operator, not a hero. Long, boring consistency outperforms sprints. Tie identity to process ("I ship daily") not outcome ("I'm a successful founder").

Loneliness protocol

Two weekly inputs minimum: a peer mastermind (3–5 founders) and one customer conversation. Loneliness is a tax on judgment.

Energy stack

Sleep ≥ 7h, strength training 3×/wk, walking 1h/day, sunlight before screens. Non‑negotiable. Caffeine after 2pm is a tax.

Money & meaning

Decide explicitly: lifestyle ($300K–$1M, freedom) vs growth ($1M+, optionality). Both are valid; mixing them silently is corrosive.

Sabbaticals

Plan one full week off per quarter, fully unplugged. Agents and SOPs let you actually take it. If you can't, fix the business — that's the bug.

Feedback diet

Limit input from random strangers on social. Curate 5–10 trusted critics. Loud opinions from people who haven't done it are noise.

"A one‑person business that breaks the person isn't a successful business. Durable solo operators design for a 10‑year run, not a 10‑month sprint."

14 · The 12‑Month Roadmap

Diagram 14.1 — From idea to $20K MRR
M1 Validate & pre‑sell 20 interviews · LP · 3 pre‑orders Target: $1K cash M2–3 Ship v1 + bill First 10 paying customers Target: $2K MRR M4–6 Distribution flywheel Pick 1 channel · publish weekly Target: $5K MRR M7–9 Automate & raise Agent fleet · price increase Target: $10K MRR M10–12 Compound 2nd product or annual plans Target: $20K MRR

Month‑by‑month focus

MonthPrimary KPIStop‑doingWin condition
1Customer conversationsWriting code3 pre‑orders or deposits
2Time‑to‑deliver valuePolishing UIFirst 5 paying customers
3Activation rateAdding features$2K MRR, <10% churn
4–6Channel signalSwitching channels1 working acquisition loop
7–9Gross marginCheap pricing$10K MRR, ≥80% GM
10–12Retention + LTVVanity follower counts$20K MRR, NRR ≥ 100%

15 · Metrics That Matter

Track few, track relentlessly. A solo operator with a clean weekly dashboard makes better decisions than a 50‑person team drowning in BI.

Diagram 15.1 — The One‑Page Solo Dashboard
GROWTH MRR · new MRR · expansion Trials → paid conversion Logo / revenue churn DISTRIBUTION List growth · open / CTR Top‑of‑funnel by channel CAC payback (weeks) UNIT ECON Gross margin · cost per request LTV / CAC Burn‑free runway (months) PRODUCT Weekly active · activation NPS · CSAT · support deflection Eval pass rate RISK Top‑10 customer concentration Channel concentration Incidents / SLO breaches AUTOMATION Manual hours / week Tasks owned by agents Agent error / escalation rate OPERATOR Deep‑work hours / week Sleep · training · walks Subjective energy score LEARNING Customer convos / week Experiments shipped Insights → backlog ratio NORTH STAR One number that captures sustainable progress — e.g., "weekly active paying customers", "automated tasks delivered", "qualified replies / week"

Healthy ranges (B2B SaaS, solo)

MetricYellow flagHealthyBest‑in‑class
Gross margin< 60%70–85%> 85%
Logo churn (monthly)> 5%1–3%< 1%
CAC payback> 12 mo3–6 mo< 3 mo
LTV / CAC< 33–5> 5
Trial → paid< 3%5–15%> 15%
NPS< 2030–50> 50
Agent escalation rate> 25%10–20%< 10%

16 · Master Launch Checklist

Before line 1 of code

  • Named the specific buyer persona (industry, role, pain, budget)
  • Talked to 20 of them; recorded objections and language
  • Landing page live with 1 promise + 1 CTA
  • At least 3 paid pre‑orders or deposits
  • Pricing hypothesis written down
  • Domain, brand, email all set up

Before public launch

  • Stripe live + tax configured
  • Terms, Privacy, AUP published
  • Onboarding email sequence (≥ 5 messages)
  • Eval suite covering top 30 use cases
  • Cost telemetry per user and per feature
  • Support address + 24‑hr response SLA
  • Status page + incident SOP drafted
  • Backup/export for customer data

First 90 days post‑launch

  • Weekly review ritual locked in
  • One acquisition channel showing signal
  • Activation rate measured + improving
  • 5+ written case studies / testimonials
  • 2 agents owning recurring tasks
  • Pricing tested with 2+ cohorts
  • 13‑week cash forecast updated monthly

Quarterly

  • Stop‑doing list executed (features, tools, channels)
  • Top 10 customer concentration reviewed
  • Model + provider risk audit
  • Personal compensation + tax reserve reviewed
  • Sabbatical week scheduled and taken
  • One bet renewed or killed explicitly

Closing

The one‑person AI company isn't a smaller startup. It's a different organism—agent‑augmented, close to customers, compounding on one operator's taste and judgment.

The work isn't glamorous: customer calls, weekly shipping, writing in public, watching the numbers, automating the boring parts, keeping judgment and care yourself. Do that for 24 months and you can own a profitable business that fits your life.

"The biggest unlock isn't doing the work of ten—it's building a business that fits your life."
— Linh Truong

17 · References & sources

Reading list behind the thesis KPIs, seven-loop model, solo stack, agent blueprints, monetization tables, legal notes, and metrics. Dollar ranges and percentages are planning bands—re-check vendor pricing and survey editions before you cite them.

Synthesis of public research and operator practice; diagrams are original unless noted. Not legal, tax, or investment advice—confirm statutes and filings with qualified professionals.

Solo AI era & economics (§1)

  1. Stanford HAI, AI Index Report. aiindex.stanford.edu
  2. McKinsey & Company, “The state of AI.” mckinsey.com/state-of-ai
  3. Epoch AI and provider pricing pages—inference-cost trends (~10×/yr claims in §1).
  4. Yao et al., “ReAct: Synergizing Reasoning and Acting in Language Models.” arxiv.org/abs/2210.03629

Product, discovery & build (§4–6)

  1. Ries, The Lean Startup. Validated learning and MVP loops (§6).
  2. Torres, Continuous Discovery Habits. Customer interviews and opportunity mapping (§4).
  3. Olsen, The Lean Product Playbook. Hypothesis-driven product process.
  4. Cagan, Inspired. Product discovery and outcome focus.

Stack, agents & automation (§3, §9)

  1. Zaharia et al., “The Shift from Models to Compound AI Systems.” BAIR blog
  2. Lewis et al., “Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks.” arxiv.org/abs/2005.11401
  3. Es et al., “Ragas: Automated Evaluation of Retrieval Augmented Generation.” arxiv.org/abs/2309.15217
  4. LangGraph documentation—orchestration. langgraph
  5. Anthropic, Claude & Agent SDK documentation—coding and agent harness (§3 stack table).
  6. Zheng et al., “Judging LLM-as-a-Judge with MT-Bench and Chatbot Arena.” arxiv.org/abs/2306.05685

Monetization, distribution & indie SaaS (§5, §7–8, §10)

  1. Walling, Start Small, Stay Small / The SaaS Playbook. Bootstrap SaaS and lifestyle-business economics.
  2. Shapiro & Varian, Information Rules. Pricing, versioning, and metering.
  3. OpenView, SaaS benchmarks (annual)—ARR, churn, margin bands in §5 and §15.
  4. MicroAcquire / Acquire.com—indie M&A context for §1 capital card.
  5. Godin, This Is Marketing—audience and distribution framing (§7).

Metrics & prioritization (§15)

  1. Amplitude, North Star Playbook. amplitude.com/north-star
  2. Rodden et al., HEART framework—experience metrics alongside business KPIs.
  3. Intercom, RICE prioritization—related to weekly ICE bets in workflow sections. Intercom blog

Finance, legal, risk & psychology (§11–13)

  1. IRS publications (U.S.) and a qualified CPA—for §11 tax and entity notes.
  2. Stripe Atlas guides—incorporation and payments.
  3. European Union, Artificial Intelligence Act (Regulation (EU) 2024/1689). EUR-Lex
  4. NIST AI Risk Management Framework (AI RMF 1.0). nist.gov/ai-rmf
  5. OWASP Top 10 for Large Language Model Applications. OWASP LLM Top 10
  6. GDPR (EU) and applicable U.S. state privacy laws.
  7. World Health Organization / occupational health literature on burnout—background for §13 psychology (not medical advice).

KPI strip (§1)

10–100× productivity, $0–$300/mo stack, 7–30 day idea-to-customer, and 70–95% gross margin are illustrative planning bands—not published industry averages. Ground your model in your telemetry; see sources above.