Đã đăng vào khoảng 4 giờ trước 41 phút đọc

🦸 The Solo-Founder Playbook: Zero to Hero - Part 1 🚀

MayFest2026

A deep, opinionated, practical guide for the human running a software business alone. Hard-won lessons, decision frameworks, and the actual mechanics of going from idea → first dollar → first $10K MRR → first $1M ARR — without a co-founder, without a team for as long as possible, and without burning out.

If you read only one section first, read §2 Mindset, §4 Validation, and §6 Distribution-First. The rest are optimizations on those three.

Companion to 🚀 The SaaS Template Playbook 📖 (how to build), and 🤖 The AI SaaS Playbook (Practical Edition)📘 (how to add AI). This document is for the solo founder, not about them.

📋 Table of Contents

⚡ Read This First
🧠 The Solo-Founder Mindset
🎯 Picking The Right Idea
🔍 Validation Before Code
🛠️ Building the MVP — The 6-Week Rule
📣 Distribution-First Operating Mode
💰 Pricing & Money
👥 First 10 → 100 Customers (Founder-Led Sales)
🔁 Iteration, Feedback & Roadmap Discipline
🤖 The AI-Leveraged Solo Stack
🏗️ Operating Cadence
🧘 Sustainability — Burnout, Loneliness, Energy
📈 The Growth Stage (10K → 100K → 1M MRR)
👨‍💼 When (and How) to Hire or Outsource
💵 Funding Paths
⚖️ Legal, Tax, Admin Minimum Set
🚪 Exit Paths
⚠️ The Anti-Pattern Catalog
🗺️ The Phased Roadmap ($0 → $1M ARR)
📋 Cheat Sheet & Resources
🧩 Appendix: Category Adaptations

1. ⚡ Read This First

Five truths that will save you 12 months of wasted motion:

Distribution kills you, not product. 99% of solopreneurs cite marketing/distribution as their #1 problem; 72% of successful indie hackers say distribution — not product — was the deciding factor. If you cannot get attention, the best product on earth is invisible. Build for a channel before you build with a stack.
Validation > velocity. The cost of building the wrong thing is now lower than ever (AI), but the cost of believing in the wrong thing is the same as it always was: 6–18 months of your life. Always pre-sell or pre-commit before you write production code.
Boring tech wins. Your edge is not your stack. It is your taste, your speed of iteration, and your distribution. Pick the most boring, well-documented, AI-friendly stack you know and never look at it again.
You are not a startup. You are a leveraged human. Stop trying to act like a 20-person company with one employee. Ruthlessly cut everything that does not directly produce revenue, retention, or distribution. Most "startup advice" is for venture-funded teams of 10–50; ignore 80% of it.
Your scarcest resource is energy, not time. A burned-out founder shipping for 80 hours a week loses to a rested founder shipping for 30. The single biggest predictor of solo-founder failure in 2025–2026 surveys is not strategy — it is burnout (54% burnout rate, 75% anxiety episodes). Treat sustainability like infrastructure, not a luxury.

The rest of this playbook is the implementation of those five truths.

Who this is for

You are building (or want to build) a software product alone — SaaS, micro-SaaS, AI agent, content business with software, or vertical tool.
You are bootstrapping or planning to. (VC-seeking solo founders: §15 covers you, but most of this still applies.)
You are technical or non-technical — both paths are addressed.
You have 6–24 months of runway (savings, side income, part-time job) and are willing to spend it deliberately.

Who this is not for

You want to build a hardware company, a deep-tech company, or anything requiring upfront capital >$50K.
You want to raise a Series A in 12 months. (Possible solo, but a different game — covered briefly in §15.)
You're looking for "passive income" or "make money while you sleep." This is not that. This is operating a business as a single person, which is unromantic, hard, and rewarding. Not passive. Ever.

A note on category bias

The main 20 sections are written with a B2B / B2C SaaS bias — that's where the author's hard-won lessons live, and it's the modal solo-founder business in 2026. The mindset, validation, distribution, and sustainability material applies to almost any solo software business; the tactical specifics (pricing structures, MVP timelines, sales motion, exit multiples) are SaaS-shaped.

If you're building indie games, physical-goods ecommerce, marketplaces, creator/info products, fintech/trading platforms, vertical AI services, mobile apps, browser extensions, or open-source-as-a-business, read the main playbook for the operator scaffolding (~60–70% applies cleanly), then read §21 Appendix: Category Adaptations for what changes in your specific category and the canonical resources to pair this playbook with.

2. 🧠 The Solo-Founder Mindset

The mindset shift is the highest-leverage move you will make. Most failed solo founders failed at the mental layer first; the product failed because of it.

2.1 Identity reframe

You are not "between jobs," "side-projecting," or "trying entrepreneurship." You are the CEO of a one-person software company. That language change matters because:

It forces you to think in terms of P&L from day one (revenue, cost, margin), not just shipped features.
It collapses the false hierarchy between "real work" (coding) and "support work" (sales, marketing, ops). All of it is your job. All of it is the work.
It primes you to make CEO decisions: what gets done, what gets killed, what gets ignored. Solo founders die from accepting too many "should-do"s.

Practical: write your one-line company description and pin it. Update it monthly. "I run X — a Y for Z that does W. We make $N MRR." If you can't fill in the blanks, that's the first problem.

2.2 The four hats — and how they fight

You will wear four hats simultaneously and they actively interfere with each other:

Hat	Mode	Time horizon	Output
Builder	Deep focus, flow	Hours–days	Features, fixes, infra
Marketer	Outward, performative	Days–weeks	Content, audience, channels
Seller	Conversational, energetic	Hours–days	Calls, demos, closed deals
Operator	Maintenance, admin	Continuous	Cashflow, support, bookkeeping, taxes

The hats fight because each demands a different brain state. A morning of customer support kills your afternoon of deep coding. A day of cold outreach destroys your appetite for product reflection. Solution: batch by hat, not by topic. See §11 for the operating cadence.

The single most common mistake: assuming "I'll just code today" and ignoring marketing for a month. The product gets better; the business does not. Your weekly schedule must touch all four hats.

2.3 The three voices

Every solo founder has three internal voices. They all lie in different ways.

The Hype Voice — "this is going to be huge!" Lies upward. Talks you into building features no one asked for, raising prices without data, going wide instead of deep.
The Doom Voice — "no one will ever pay for this, you're an impostor." Lies downward. Talks you out of cold outreach, out of price increases, out of shipping the imperfect thing.
The Operator Voice — "what does the data say? what did the customer say? what's the next reversible bet?" Lies the least. Cultivate this one.

Practical: when you catch yourself acting on Hype or Doom, write down the decision and revisit in 24 hours. Most regretted decisions happen within 90 minutes of an emotional trigger (a churned customer, a viral post, a hacker news ranking).

2.4 Reversible vs. irreversible decisions

Jeff Bezos's two-way / one-way door framing is especially important solo:

Two-way doors (reversible): pricing, copy, landing page, feature scope, blog tone, tool choice, even tech stack early on. Decide fast, ship in a day, undo if wrong. Solo founders waste months agonizing over reversible decisions.
One-way doors (irreversible): co-founder equity, fundraising, public commitments to enterprise customers, company name, legal entity. Decide slowly, get advice, sleep on it.

Audit your last 10 big decisions. If >7 were one-way doors, you're not moving fast enough. If <2 were one-way doors, you're avoiding the hard structural decisions.

2.5 The compounding loop

Your only sustainable advantage as a solo founder is compounding. You cannot out-build a 50-person team. You cannot out-market a brand with $10M in ad budget. You can compound:

An audience — every email subscriber, follower, and Discord member compounds. Lose 0% per year if you stay active.
SEO surface area — every long-form post you ship is an asset that earns interest forever.
Customer relationships — every champion at a B2B account is a 5–10 year relationship if treated well.
Product depth — every shipped, polished feature compounds your moat against shallow clones.
Personal craft — every sales call, every cold email, every landing page makes the next one better.

Anything that does not compound is rented. Rented things include: paid ads (stop and traffic dies), influencer collabs (one-shot), platforms you don't control (the day TikTok bans your account), and partnerships dependent on a single relationship. Build a rented-to-owned ratio of <30% in your top-of-funnel by year 2.

2.6 The honest reality

Things you will feel that the Twitter version of solo founding never mentions:

Days where you cannot tell if you're winning. Revenue is up but a customer churned. Traffic spiked but no signups. You shipped a feature but it broke something else. This is normal. Use lagging indicators (monthly MRR, cohort retention) for confidence; daily indicators are noise.
The 3-month wall. Around month 3, the initial energy fades, you have ~10 customers, growth feels slow, and the doubt sets in. Most solo founders quit here. Surviving the wall is mostly mechanical (shipping cadence, cashflow runway, reduced expectations) — not motivational.
The success disorientation. Around your first $5K MRR, you'll feel oddly empty. Your goal got smaller than your ambition. Reset your goals upward and downward simultaneously: bigger revenue target, smaller weekly scope.
Decisions you can't unmake. You will hire a contractor that doesn't work out. You will sign a customer at half-price who consumes 10x your support. You will ship a feature that becomes a maintenance tax forever. These are not failures, they are the cost of operating. Forgive yourself faster than you used to.

3. 🎯 Picking The Right Idea

The most important decision in your solo founder career, and the one most founders speed through. Spend 2–6 weeks on this. Yes, really.

3.1 The Five-Filter Idea Test

Run every idea through these. If it fails any one, kill it.

#	Filter	Pass test
1	Pain Severity	Can you find 20 people in 1 week who are already paying money or burning hours on this problem?
2	Reachable Market	Can you describe a single channel (subreddit, conference, newsletter, tag on X) where 10K+ of these people gather?
3	Willingness to Pay	Will at least 3 of those 20 prospects pre-commit money (Stripe pre-order, signed LOI, deposit) before any product exists?
4	Solo-Buildable in 12 Weeks	Can a competent version 1.0 of the product be built by you alone in ≤12 weeks of your real availability?
5	You Care for 5 Years	Will you find this domain interesting enough to live in for half a decade? Solo + bored = death.

A common mistake: passing filter 1 (real pain) but failing filter 2 (reachable). If your customer is "small business owners," you have no channel. If your customer is "DAM administrators in mid-market manufacturing," you have a LinkedIn list and a conference.

3.2 Where to look for ideas

In rough order of return-per-hour-spent:

Your last job. What workflow did you watch your team waste hours on every week? You already know the buyer, the language, the budget cycle, and the integrations they use. This is the highest-EV idea source for technical founders. ~50% of best B2B SaaS comes from this.
Tools you already pay for and hate. Find the form you fill in every Tuesday and dread. The annoyance is data.
Communities you're already in. Read the "what tool do you use for X?" threads in Discords, subreddits, Indie Hackers, niche Slacks. Three weeks of lurking will find you a solid #ideas list.
Existing winners with clear gaps. Take a $1B+ public SaaS (HubSpot, Asana, Salesforce). Find a job-to-be-done they do badly. Build the laser-focused replacement for one segment. ConvertKit was Mailchimp for creators. Linear was Jira for fast teams.
Adjacent moves from a successful indie hacker's audience. If a creator has 10K followers asking about X, and X has no good tool, you have buyers waiting.
The "boring SaaS" library. Government contracts, compliance reporting, restaurant inventory, dental practice booking, chimney sweep scheduling. These businesses pay $100–$1000/mo and switch tools rarely. They are unsexy and durable.

What not to do:

Open Twitter and brainstorm. You'll generate 30 "interesting" ideas and execute none.
Pick a "passion" with no buyer in mind. Passion alone is suicide; passion + buyer is a moat.
Pick whatever's hot this week (today: AI agents, vertical AI, ambient AI, AI tutors). The hot thing has 100 competitors by the time you ship.
Pick consumer social. Consumer requires distribution scale you don't have solo.

3.3 Niche depth > niche breadth

The 2026 market data is unambiguous: micro-niches grew 340% vs. broad-market platforms (Gartner Q4 2025). For a solo founder this is doubly true because:

A narrow niche has a discoverable channel (filter 2).
A narrow niche tolerates an opinionated product (you don't need to support 200 features for 200 use cases).
A narrow niche has lower competitor density per customer.
A narrow niche compounds: every customer becomes a referrer, every blog post ranks faster, every feature update lands harder.

Heuristic: define your customer in two adjectives + a noun + a verb. "Independent psychotherapists who do telehealth and need note-taking." Not "healthcare professionals who want better workflows." Always two adjectives + a noun + a verb.

Start narrow. You can go broad later (most ICPs widen 3–5x by year 3); you cannot go narrower later without major repositioning.

3.4 The "fund yourself" idea filter

A practical extra constraint most playbooks miss: the idea should fund itself within 6 months at $5K MRR or pre-sell into $30K+ of LOIs. Anything that requires 18 months of pure burn to validate is not a solo-founder idea. It's a venture-funded idea that has not raised yet.

Examples:

✅ B2B SaaS, $50–$500/mo, single-tenant problem (e.g. invoicing, scheduling, reporting): founder gets to 10 paying customers in 8–12 weeks → $5K MRR.
✅ Vertical AI tool with thin wrapper around clear workflow (e.g. AI sales prospecting for solar installers): can pre-sell 5 contracts of $500/mo before a line of code.
⚠️ Marketplace: chicken-and-egg; possible solo (Pieter Levels' Nomad List) but only with strong content/audience moat. Not a starter project.
❌ Consumer subscription app at $5/mo: requires 1000+ users for $5K MRR, which requires distribution scale not available solo.
❌ API platform with no UI: developers are the worst customer segment for unknown solo founders (low willingness to pay, high support burden, technical scrutiny).
❌ AI-only "feature" (e.g. summarize my emails): OpenAI/Anthropic launches it as a free feature in 6 months. You need workflow, integrations, vertical knowledge, and AI — not AI alone.

3.5 The unfair advantage audit

Before committing, list your unfair advantages for this specific idea. You should have at least two:

Domain insider — you've worked in or with this industry for 3+ years.
Audience seed — you already have ≥500 newsletter subscribers, Twitter followers, or Discord members in the target segment.
Technical edge — you can build the hardest part 5x faster or 10x better than competitors (rare; do not over-claim this).
Distribution channel ownership — you run a podcast, newsletter, community, or course that the buyers consume.
Geographic/language arbitrage — you can serve a market under-served by English-only US-focused tools (e.g. Vietnamese accounting, German freelancer tax filing).
Capital cushion — 12+ months of runway. (This is real, but the weakest of the advantages — it buys patience, not winning.)

Two real advantages = green light. One = yellow, proceed cautiously. Zero = pick a different idea.

3.6 Sanity-check with three calls

Before committing, do three calls:

One target customer. 30-min discovery call. Ask: "How are you solving this today? How much would it be worth to you if it were solved? Walk me through the last time you had this problem."
One operator who tried this idea. Find someone who tried something similar (failed or succeeded) and ask why. 80% of "great ideas" have a failed version on Crunchbase or Indie Hackers from 2018.
One person from an adjacent successful product. If your idea is "Calendly for X," find a Calendly-adjacent founder and ask what would make that idea work or fail.

If you cannot get three calls in two weeks, your ICP is too vague or you're scared of selling. Both are problems to fix before writing code.

4. 🔍 Validation Before Code

The fastest way to lose 6 months is to write code before validation. The fastest way to lose 6 weeks is to validate something nobody actually buys.

4.1 The validation hierarchy

From weakest to strongest signal:

Signal	What it proves	Effort	Reliability
Survey / "would you use this?"	~Nothing	Low	⭐
Email signup on a landing page	Mild curiosity	Low	⭐⭐
Click on "Buy" button (fake door)	Active interest	Low	⭐⭐⭐
LOI / signed letter of intent	Verbal commitment	Medium	⭐⭐⭐⭐
Stripe deposit / pre-order	Real money	High	⭐⭐⭐⭐⭐
Recurring monthly payment from a stranger	Real product-market fit	High	⭐⭐⭐⭐⭐⭐

Rule: never use weak signals to make strong commitments. Survey results justify more research, not building a product. Pre-orders justify building a product.

4.2 The Pre-Sell Validation Recipe

The single highest-EV validation method. Works for B2B and B2C.

Step 1 — One-page landing site (1 day).

Hero: problem → solution → outcome. Three sentences.
Mechanism: 3 short paragraphs of "how it works."
Proof: testimonials (use the discovery interview quotes; ask permission), or "as featured in" placeholders ("featured in: your Slack channel").
CTA: "Get early access — pay $X now, locks in $Y/mo lifetime." Stripe Payment Link.
Tools: Carrd, Framer, or just a Vite + Tailwind one-pager. No CMS. No blog. No /pricing page.

Step 2 — 50 manual outreach messages (3 days).

25 cold (LinkedIn + cold email).
25 warm (existing network + community DMs).
Personalized. "Hey {name}, saw you posted about {problem} last week. I'm building {one sentence}. Pre-order is live; happy to walk you through it."
Goal: 3+ paid pre-orders → green light to build.

Step 3 — Prove the channel (1 week).

1 long-form post in a relevant community (subreddit, IH, LinkedIn) describing the problem (not selling).
1 short-form thread (X/LinkedIn) with the same content compressed.
Track: what % of visitors landed → clicked CTA → paid.
A working channel: ≥1% of qualified visitors pay. <0.5% means either copy is wrong or product-market wrong.

Step 4 — Decide.

5+ paid pre-orders + a working channel → build.
0–2 pre-orders → kill or pivot the messaging. Do not "build it anyway and they'll come."
Lots of interest, no money → pricing too high, value prop unclear, or it's a "nice to have" not a "must have."

4.3 The Mom Test (and how to use it solo)

Rob Fitzpatrick's The Mom Test is required reading. The TLDR for solo founders:

Talk about the customer's life, not your idea. "Walk me through last Tuesday."
Ask about specifics in the past, not opinions about the future. "How did you handle X last quarter?" not "Would you use a tool that does X?"
Look for evidence of pain — money already spent, hours wasted, workarounds built. People will lie about loving your idea. They cannot lie about what they paid for last year.
Press for commitment. Time, money, reputation. "Would you join a beta? Could you intro me to your finance lead? Could you pre-pay $200 for a 6-month plan?"

A polite "yes" on a discovery call is the most dangerous data point in startup history. Ignore it. Look only for "how can I get this today?" or actual money.

4.4 The 100-customer-conversation rule

Run 100 customer conversations (not "interviews" — conversations) in the first 90 days. They can be:

30-min discovery calls (highest value)
DMs in communities (medium value)
Replies to your posts (low value but cheap)
Comments on related posts (cheap, broad)

You will learn more from conversations 60–100 than 1–60, because by then you can pattern-match. Do not stop early. You will think you "know the customer" by call 20. You don't.

4.5 What validation does not validate

It does not validate that you can build it. (You probably can; AI coding has made build risk near-zero.)
It does not validate that you can market it. (Distribution is its own validation — see §6.)
It does not validate retention. Pre-orders prove willingness to pay once. Retention requires actual usage.
It does not validate scale. A signal at 5 customers does not mean a signal at 500.

These four risks remain after pre-sell validation. Do not be lulled. Move to the next stage with appropriate humility.

4.6 When to skip validation

Two cases:

You are the customer. You have spent 2+ years feeling this exact pain. You know 50 other people with the same job. Skip pre-sell, build a personal-use prototype in 1 week, then go straight to step 4.2.
The idea is so cheap to build that validation costs more than the build itself. Single-page Chrome extensions, simple AI wrappers, basic command-line tools. Just ship and see. Even then, validate the channel before committing to the niche.

For everything else: validate first.

5. 🛠️ Building the MVP — The 6-Week Rule

If your MVP takes more than 6 weeks of focused calendar time, the scope is wrong. Cut it.

5.1 The 6-week budget

Week	Output
1	Onboarding flow + auth + data model. The customer can sign up and see an empty state.
2	The single workflow that defines the product. Half-polish.
3	The second-most-used workflow + payments + pricing page.
4	Polish, basic analytics, error handling, friction removal.
5	Beta launch to pre-order list. Daily fixes from real usage.
6	Public launch + first cohort onboarding. Ship the obvious gaps.

This is aggressive. It works if scope is severely cut. It fails if you treat the MVP as a product. The MVP is a pre-product — a wireframe that takes payment.

5.2 What to cut

Solo founders cannot afford to ship the standard SaaS feature set in v1. Cut all of these from your MVP:

❌ Multi-tenancy with workspaces and roles. Single-user accounts only. Add team features when 30% of customers ask.
❌ SSO / SAML. Email + password only. Add Google OAuth in week 4 if needed.
❌ Granular permissions. One role: admin.
❌ Mobile responsive on every page. Mobile-friendly landing page yes; mobile responsive dashboard no.
❌ Localization / i18n. English only, even if your customers aren't English-first. Ship the second language at month 6+ once one market is locked.
❌ Usage-based billing. Flat per-seat or per-month. Add metering when revenue justifies engineering for it.
❌ Custom domains. White-label / custom domain support is a $200+/mo upgrade reason; do not give it away.
❌ Audit logs / compliance UI. Ship logs to your monitoring tool; surface them in product when an enterprise customer asks.
❌ A "Settings" page with 12 toggles. No toggles. Make decisions for the user.
❌ Webhooks, public API, integrations beyond the 1 most-requested. Each integration is 2 weeks of build + lifetime maintenance. Only ship integrations where the customer cannot use the product without it.
❌ A blog with 30 posts on day 1. Distribution is critical (§6) but day-1 blog content rarely moves needle. Start with 3 deep posts and grow.

What to keep:

✅ One workflow, end-to-end, polished.
✅ Payments. Working from day 1. (Stripe Checkout + Customer Portal — 2 hours of integration.)
✅ Onboarding that gets the user to first value in <5 minutes. This is the single highest-leverage 4 hours of work in your MVP.
✅ Email — receipts, password reset, daily/weekly digests if relevant. Use Resend or Postmark; cheap and reliable.
✅ Basic analytics — page views, signups, conversions. PostHog free tier or Plausible.
✅ A way to talk to users. Intercom is overkill. Use Crisp (free tier), Help Scout, or a support@ email.

5.3 The "boring stack" picks

Choose the stack that gives you the highest ship-to-debug ratio. Recommendations as of 2026, optimized for solo + AI-pair-programming velocity:

Web app frontend:

Next.js 15 + TypeScript + Tailwind — for full-stack with React, max AI-assistance, max docs, max hireable. Good for product UI.
Astro + React islands — for content-heavy SaaS where most pages are marketing.
SvelteKit + TypeScript — if you already know Svelte and value fewer LoC. Otherwise pass.

Backend:

Next.js API routes / Server Actions for monolithic apps. One framework, one repo, one deploy.
Hono on Cloudflare Workers for AI-heavy / edge-streaming products.
FastAPI (Python) if your product is ML/AI-heavy and you want native Python ecosystem (HuggingFace, scikit-learn).
Go + chi if you want long-term reliability and you already know Go. Worse AI assist, better runtime.

Database:

Postgres — only this. Skip Mongo, Firebase, Dynamo. You will hit Postgres scale (10M+ rows) far before solo bottlenecks become DB-shaped.
Hosted: Supabase (also gives you auth + storage + realtime; great solo stack), Neon (serverless Postgres, cheap branches), or RDS for control.

Auth:

Supabase Auth if you're on Supabase.
Clerk if you want best-in-class UX in 1 day, willing to pay $25–$100/mo at scale.
Auth.js (NextAuth) if you want self-hosted.
Avoid rolling your own. Auth bugs are the only category where one bug ends your company.

Payments:

Stripe — Checkout + Customer Portal + Subscriptions. Works in 50+ countries. Don't overthink this.
Paddle / LemonSqueezy — if you're outside the US/EU, want them to handle sales tax & VAT (worth it: solo founders should not be doing global tax filings). Slightly higher fees, much less admin.
Indie hackers in non-major countries: Paddle/LS hands down. Stripe sales tax is a side job you do not want.

Hosting / Infra:

Vercel for Next.js (best DX, scales to thousands of $/mo at midsize).
Railway / Render / Fly.io for backends + Postgres if you want one provider.
Cloudflare if you're cost-sensitive at scale.
Avoid AWS/GCP raw until you're at $50K+ MRR. The complexity is not worth it solo.

Email:

Resend for transactional. ConvertKit / Beehiiv for marketing/newsletter.

Observability (free tiers):

Sentry for errors. PostHog for product analytics. Plausible for marketing analytics. Better Stack or Healthchecks.io for uptime.

The whole stack costs $0–$50/month at <100 users. By the time you outgrow free tiers, you should be at $1K+ MRR.

5.4 Code velocity habits

Solo founders ship 5–10x faster than teams not because they're better, but because they have zero communication overhead. Habits that compound that advantage:

Boring DB migrations. Use one migration tool (goose, Prisma, Drizzle, Alembic). One direction: forward. Never edit applied migrations.
One environment until 50 customers. Production is the staging environment. Yes, really. The audit log that catches a problem is more useful than a staging environment that's always 3 days out of date. Add staging when you have a customer who will fire you for a 5-minute outage.
Feature flags for everything risky. PostHog flags or a 30-line homemade flag table. You ship faster knowing you can flip a switch.
AI-pair-programming as default. Cursor, Claude Code, Cody, or GitHub Copilot — pick one and never write code without it. The 2026 productivity gap between AI-paired and unpaired solo founders is now 3–5x on routine work.
Tests for the spine, not the skin. Tests on payments, auth, billing, and core data integrity. No tests on UI buttons (yet). Ratio target at MVP: 30% of code is non-trivial business logic, 90%+ of that is tested. Everything else: optional.
Dependency hygiene. Update weekly with Renovate or Dependabot. Two minutes of merging beats two hours of major-version pain.
Two repos max. One frontend, one backend. Or one monorepo. Resist the microservices urge until you literally cannot ship without splitting.
Boring deploys. Push to main → CI runs → deploy. No release branches, no environment promotions. Solo founders should have <5 minutes from commit to production.

5.5 The MVP launch checklist

Before announcing publicly:

[ ] Pricing page with 1–3 plans. Decision: annual discount? (Recommended: 2 months off.)
[ ] Stripe in live mode. Test 5 charges, including refund.
[ ] Email deliverability (SPF/DKIM/DMARC set up; 4 transactional emails ship without going to spam).
[ ] Onboarding gets a stranger to the "aha" moment in <5 minutes. (Test with 3 strangers — friends, sibling, your discord server — and watch them.)
[ ] Cancellation works. Yes, test it. No, don't make it hard. The "cancel" button should be one click, two max.
[ ] Receipts work. Look like your brand, not Stripe's.
[ ] Support inbox alive. A support@ email or Crisp widget. Reply within 24h SLA — it's free trust at this stage.
[ ] Status page if your product has any uptime promise. (Cron-monitor of your /health endpoint to a public page.)
[ ] Terms of Service + Privacy Policy. Use Termly or a $300 one-time lawyer review. Every commercial SaaS needs these.
[ ] Domain on email is not gmail. Buy a domain ($10/yr). It is the cheapest credibility upgrade in commerce.
[ ] One demo video — 2 minutes max — embedded on the landing page.
[ ] Analytics tracking signups, activations, payments. You should be able to answer "how many people signed up yesterday" in 10 seconds, by month 1.

Skip everything else.

6. 📣 Distribution-First Operating Mode

The single most under-respected truth in solo founding: distribution is a product. It has design, iteration, retention, and scaling. Treat it that way or you'll have an excellent invisible product.

6.1 The distribution decision: which channel before which feature

Before you write code, choose one primary distribution channel. Not three. One. Common choices:

Channel	Time-to-first-customer	Time-to-compound	Solo-suitable?	Best when
SEO / long-form content	6–12 months	Excellent (3+ years)	⭐⭐⭐⭐⭐	You can write or teach a niche topic.
X / Twitter (build in public)	2–8 weeks	Good (audience compounds)	⭐⭐⭐⭐⭐	You enjoy posting daily and have a strong narrative.
LinkedIn (B2B)	4–12 weeks	Very good for B2B	⭐⭐⭐⭐	You sell to a defined job title.
YouTube	6–18 months	Excellent (compounds forever)	⭐⭐⭐	You're comfortable on camera, willing to invest in production.
Newsletter	3–6 months	Excellent	⭐⭐⭐⭐	You can write a useful weekly piece and have a topic.
Cold outbound (email/LinkedIn)	1–4 weeks	Linear (does not compound)	⭐⭐⭐	High-ticket B2B ($500+/mo).
Paid ads (Meta/Google)	1–4 weeks	None	⭐⭐	High LTV (>$500), proven funnel. Not for week 1.
Community participation (Reddit/Discord/Slack)	2–8 weeks	Good	⭐⭐⭐⭐	You're a real participant, not a marketer.
Product Hunt / Hacker News launch	1 day spike	None on its own	⭐⭐⭐	Tactical boost; never a strategy.
Partnerships / integrations	1–6 months	Good if exclusive	⭐⭐⭐	You can integrate into a larger platform's marketplace.
Referrals from existing customers	After ~50 customers	Excellent	⭐⭐⭐⭐⭐	You have happy customers and design for it.

Pick the one channel where (a) your customers gather, (b) you can produce content native to that channel, (c) it compounds. For most B2B solo founders: SEO + LinkedIn + cold outbound. For most consumer solo founders: X + YouTube + Reddit. For dev tools: X + GitHub + content.

6.2 Build in public — done right

"Build in public" is now the default mode for indie hackers, but most do it wrong (vanity metrics, motivational drivel). Done right, it is the highest-EV solo distribution strategy in 2026.

Done right:

Post 3–5x per week on one platform. Consistency > virality.
Mix the four content types: insight (a hard lesson), behind-the-scenes (a real screenshot or metric), opinion (a take on the niche), launch (a new feature). Roughly 40/30/20/10.
Be specific. "MRR up 12% this week, here's the 3 changes that drove it" beats "Big day for [company]!"
Ship with the customer in mind. Every post should answer: "why does my target customer care about this?" If the answer is "they don't, but other founders do," that's audience-building, not customer-building. Both are useful but don't confuse them.
Include the work. Screenshots, code, dashboards, dunked invoices. People follow the work, not the personality.

Done wrong:

Daily MRR screenshots with no insight.
"Hot take" engagement bait.
Reposting other people's content with a quote.
Posting only when you launch.

The compounding effect is real: solo founders who post 4x/week consistently for 18 months reliably hit 10K+ followers in their niche. 10K followers in a B2B niche is roughly $100K ARR of latent demand at any given moment.

6.3 SEO for solo founders — the playbook

SEO is the single highest-EV channel because it compounds while you sleep, but it has a brutal lag. Start month 1 even if results are 6 months away.

Step 1 — Pick 50 long-tail keywords your customers Google.

Use Ahrefs, SE Ranking, or Google itself ("People also ask"). Look for 50–500 monthly volume keywords with clear commercial intent.
For a niche tool: target keywords like "how to {workflow} for {industry}", "alternatives to {competitor}", "{competitor} vs {category}".

Step 2 — Write 3 deep posts per month, minimum 1500 words.

Each post should be the best resource on the internet for its keyword. If you can't make it the best, pick a different keyword.
One opinionated article > five generic articles. Google's 2024–2025 helpful-content updates rewarded original takes; 2026 is even more original-leaning.
Include screenshots, a real example, a downloadable artifact (template, checklist, calculator).

Step 3 — On-page basics.

Title tag with primary keyword, under 60 chars.
One H1, hierarchical H2/H3.
Internal links to 3–5 related posts.
A clear CTA at the end of every post (not just "Sign up" — "Try the {feature} on a free 14-day trial" with a relevant in-context offer).

Step 4 — Programmatic SEO if relevant.

For tools with a "directory" angle (e.g. vendor lookup, location-based services), build a programmatic SEO surface: 1 page per entity, deduplicated, useful, not spam. Nomad List is the canonical example. This can 10x organic surface area in a quarter.
Risk: Google flags low-effort programmatic pages. If your generated pages don't look like a hand-written page, don't ship them.

Step 5 — Backlinks.

Mostly through becoming a trusted source. Niche podcasts, guest posts, partnerships. Don't buy backlinks; the cost is your domain reputation.
An underrated tactic: "expert roundups" — answer 3-question journalistic surveys (HARO/Connectively, SourceBottle, Featured.so). Each answer is a potential DR60+ backlink.

Step 6 — Patience.

Post 1: ranks in 2–8 weeks for low-competition long-tail.
Posts 1–10: build domain authority. ~3–6 months to first 1000 organic visitors/month.
Posts 10–50: organic compounds. 12–24 months to 10K+ visitors/month.
The wall: months 3–6 are dead silent. This is normal.

Hard truth: SEO is the highest-leverage channel and it works. It also requires you to write 100+ posts before it dominates your funnel. Nobody told you it would be a 1-year sprint. It is.

6.4 Cold outbound — the tactical version

For B2B, cold outbound is the fastest way to your first 10 customers. It is also the most demoralizing if done wrong.

The 100-email template:

Target: 100 prospects in your ICP with named contacts, real email addresses (Apollo, Hunter, LinkedIn Sales Navigator).
Personalization minimum: mention a specific thing from their LinkedIn post / company news / website. Generic templates are spam.
Subject: under 5 words, lowercase, conversational. "quick q on {their workflow}", "{name}, two-minute idea", "saw your post on {X}".
Body: 4 sentences max.
1. The personalized hook ("saw your post about X").
2. The pain you've heard from people in their role.
3. What you're building (one sentence).
4. Specific ask (15-min call this week, Tuesday or Thursday).
No links in the first email. No pitch deck. No "we'd love to chat about your goals." Just the human ask.
One follow-up after 3 days, even shorter. A second follow-up after 7 days. Then stop.

Realistic conversion: 5–15% reply rate, 30–50% of replies become calls, 10–30% of calls become customers. So 100 emails → 5–15 replies → 2–8 calls → 0–3 paying customers. Replicate at scale.

What to never do:

Use "we" before you have a team.
Send via marketing automation tools (Mailchimp, Klaviyo). They go to spam. Use Gmail / Outlook / Mixmax / Smartlead via your domain inbox.
Ask for a 30-min meeting. Ask for 15.
Pitch via PDF. Pitch via conversation.
Buy a list. Build it manually (or with Apollo + LinkedIn) for the first 500 prospects.

6.5 The community participation rule

Communities (Reddit, Discord, Slack, niche forums) are the highest-trust acquisition channel and the easiest to ruin. Three rules:

20:1 give-to-take ratio. 20 helpful, no-link replies for every 1 self-promotional one.
Be a real person. Username = your real name or close. Bio mentions your work. No "growth hack" framing.
Earn the right to talk about your product. When someone asks "what's a good X?", reply with the best honest answer (not always you). When you're consistently helpful for 3 months, your name becomes a brand. Then mentions of your tool feel earned.

Communities give 30–50% conversion when you're trusted and 0% when you're not. There is no middle.

6.6 The audience-first vs. product-first decision

Two valid solo founder paths:

Audience-first (Justin Welsh, Pieter Levels, Daniel Vassallo): build an audience first, then launch products to them. 12–24 months of content before the first product. Higher patience, much higher LTV per customer when you do launch.

Product-first (most B2B SaaS): find a niche, build the product, distribute to that niche. Audience emerges as a side effect of distribution.

You probably know which one fits you in 5 seconds. Don't fight it. Both work. The mistake is doing audience-first as a side project while doing product-first as your main job — you do both badly.

6.7 Distribution KPIs you actually need

Solo founders drown in vanity metrics. The only ones that matter monthly:

MRR / ARR — the primary scoreboard.
New paying customers / month — leading indicator of MRR.
Top of funnel: organic traffic + signups / month — leading indicator of new customers.
Activation rate — % of signups who reach the "aha" moment in first session. Below 30% = product/onboarding broken.
Logo churn / month — % of customers who churn. Above 5%/mo = product/fit broken.
CAC payback — months to recoup acquisition cost. Should be <12 months for a healthy SaaS, months for content-driven solo SaaS.

What to ignore: followers, impressions, "engagement rate," website visitors. These are correlated with revenue but not causal — revenue is the only causal metric.

7. 💰 Pricing & Money

You will undercharge. Every solo founder undercharges. The cure is not a percentage; it's a different mental model.

7.1 The pricing reframe

You are not pricing your product. You are pricing the value you deliver to the customer minus the alternative they would otherwise use. Repeat that phrase until it lives in your head.

If your product saves a 50-person team 10 hours per week at $50/hr, you deliver $26,000/year of value. Charging $99/mo ($1,188/year) is 0.05x. A reasonable bracket is 5–10% of value delivered, so $130–$260/mo. You are charging $99 because you saw a competitor at $99 — not because the value is $99.

Three frames to break low pricing:

Pricing relative to alternative: what would it cost them to hire someone? to buy three tools? to do nothing for another year?
Pricing relative to ROI: "this saves you $X/yr → so $Y/mo is a Z% return" — where Z is 5x+.
Pricing relative to budget heuristics: B2B ICPs have rough monthly tool budgets (e.g. $100–$500/seat for ICs, $500–$5K/mo for tools used by departments). Aim for the bottom of those brackets, not below.

7.2 Pricing structures

For solo SaaS, pick one structure and stop reading about pricing for 6 months:

Structure	Example	When to use	Avoid when
Flat-rate per user	"$49/user/mo"	Most B2B SaaS, multi-user products	Price-sensitive customers who hate per-seat
Flat-rate per workspace	"$99/mo for the team"	When teams onboard collaboratively	Sales-led / enterprise (leaves money on table)
Tiered	"$29 / $79 / $199"	Most SaaS; segment by feature/usage	When tiers confuse buyers; <2 plans usually wrong
Usage-based	"$0.001 per API call"	Developer/API products, infra	When usage is unpredictable to the buyer
Hybrid (base + usage)	"$50/mo + $0.01/call"	Best of both for AI products	When billing complexity scares solo founders (it should)
Lifetime deal (one-time)	"$199 once"	LAUNCH ONLY, on AppSumo etc.	As your primary model — kills MRR; good for early funding

Solo founder default: 3-tier pricing, monthly + annual, with annual offering 2 months free. This is boring, it works, it is what every YC SaaS does, ship it.

7.3 The "good / better / best" tier design

Cap your pricing tier discussion to 90 minutes:

Good ($X): the entry point. Solves one specific problem. Constraints (e.g. seat count, usage cap) push to upgrade.
Better (3x $X): the target plan. Most customers should land here. Includes the killer feature.
Best (10x $X or "contact us"): anchors the perception of value. Most customers won't take it, but it makes Better look reasonable.

Common mistake: pricing the middle tier such that the entry tier is a great deal. Customers will flock to Good and you'll never make money. Restrict Good aggressively. Make Better the obvious choice.

7.4 The "raise prices, lose less than you think" rule

Every solo SaaS at <$30K MRR is undercharging. Common case studies show 30–50% price increases lose <10% of customers and yield 20–35% revenue lift overnight.

Rules for raising prices:

Grandfather existing customers for at least 12 months on the old price. (Some founders grandfather forever — this is fine and worth the ill-will avoidance.)
Announce 30 days before. Email, in-app banner, and a public post explaining why (more support, better infra, more development, more integrations).
Offer a "lock in current price" annual upgrade window. Customers who commit to annual at the old rate are your most loyal. Reward them.
Watch churn for 60 days. If sub-2% above baseline, you set the right new floor. If 5%+, the value perception is broken — fix that, don't roll back.

Heuristic: raise prices 10–20% every 12 months until customers start meaningfully resisting. You'll know you've gone too far when calls turn into negotiations or churn ticks up.

7.5 Annual contracts > monthly when possible

Annual billing is cashflow heaven for solo founders. Why:

12 months of cash upfront → no panic about runway.
Lower churn — once they've paid for the year, they stay through low-engagement weeks.
Forecasting is dramatically easier.
Lets you discount aggressively to win the deal without ruining your ARPU.

How to push annual:

Default to "billed monthly" toggle visible. Annual saves "X% — 2 months free."
In sales calls: anchor on annual price first. "$1,200/yr" lands different than "$120/mo × 12."
For B2B with finance teams: annual is easier to expense than monthly recurring. Many finance leaders prefer it.

7.6 Free trial vs. free tier vs. paid only

The hardest decision in solo SaaS pricing.

Model	When	Risk
14-day free trial, no card	Most B2B, low-trust segment	Highest signup volume, lowest conversion (~3–8%)
14-day free trial, card up front	High-intent B2B, "professional" markets	30–50% lower signups but 20–30% conversion
Free tier	Network-effect products, dev tools, content	High support cost forever, ~1–3% upgrade rate
Paid only (with money-back guarantee)	Proven product, niche premium	Smallest funnel, highest qualification

Default for solo SaaS: 14-day free trial, card up front. Your time is the bottleneck. Filter for serious buyers. You can switch to no-card later if conversion is too low.

Avoid free tier in your first year unless network effects make it core. Free users consume support, file bug reports, and post angry reviews — solo founders cannot afford that without revenue.

7.7 Payment hygiene — the boring details that save your business

Failed payments: retry 4x over 14 days (Stripe Smart Retries does this), then dunning email sequence (3 emails over 7 days), then suspension. Don't immediately delete the account — many recoverable.
Refunds: generous. If a customer asks within 30 days, refund. The bad-PR cost of refusing is much higher than the lost revenue.
Chargebacks: dispute every illegitimate one. Stripe gives you a clear dispute UI; takes 10 minutes per case. Win rate around 30–50%, but losses also count toward chargeback ratios that can lock your Stripe account.
Sales tax / VAT: if you're selling globally, use Paddle or LemonSqueezy. If Stripe, use Stripe Tax (additional 0.5–0.7% fee, but tax filing across jurisdictions is automatic). Solo founders should never be doing manual VAT registration in 27 EU countries.
Currency: charge in USD by default unless your ICP is non-US (then EUR or GBP). Multi-currency is a year-2 problem.

7.8 The "money in the bank" ladder

Track these monthly:

MRR — recurring revenue committed monthly.
ARR — MRR × 12. The standard solo founder mental anchor: $1K MRR = $12K ARR. $10K MRR = $120K ARR. $83K MRR = $1M ARR.
Net New MRR = New MRR + Expansion - Churn - Contraction. The single most important monthly number.
Cash balance / runway in months. If your cash balance / monthly burn < 12 months, you're in cashflow trouble — adjust burn or accelerate sales.

Solo founders should never be in a position where they can't cover 6 months of operating expenses. That panic produces bad decisions: cheap pricing, premature hiring, fundraising at bad valuations.

8. 👥 First 10 → 100 Customers (Founder-Led Sales)

The first 100 customers are the hardest. This section is the playbook for getting there.

8.1 The first 10 are manual, and that's the point

You are not "scaling sales" yet. You are hand-building relationships that teach you the buyer, the workflow, the objections, and the words. Every minute you save here costs you a year later.

Mechanics for the first 10 customers:

List 100 named prospects in your ICP. Apollo, LinkedIn Sales Navigator, hand-curated. Real names, real emails, real role titles.
Reach out one by one. No automation. (See §6.4.)
Schedule discovery calls — not demos — first. 15-min discovery → if mutual fit, 30-min demo. Discovery teaches you. Demo sells.
Demo is conversational, not scripted. Open the app, log in, walk through their use case. Yes, you literally type their data into your product live. They feel ownership.
Close on the call. "Want to start the trial today? I can set you up in 5 minutes." Do not "send a follow-up with details" — that kills momentum. Set expectations and start the trial in real time.
Stay in their inbox during the trial. Day 1 ("how was setup?"), day 3 ("any blockers?"), day 7 ("what's been useful?"), day 13 ("ready to upgrade?"). One-line emails, not marketing automation.
Ask for the upgrade explicitly. "Want me to switch you to the paid plan?" Do not assume they will self-serve.

Conversion expectations:

100 cold outreaches → 8–15 calls → 3–5 trials → 1–3 paying customers (first month).
This is normal. Cold outbound conversion is brutal. The number of activities matters more than the conversion rate.

8.2 Founder-led sales scripts (because solo founders need a script for everything)

Discovery call (15 min):

0–2 min: pleasantries, restate why they took the call.
2–10 min: their world. "Walk me through how you're solving this today. What's not working? What's the workaround? How much time/money is this costing?"
10–13 min: a 90-second pitch back. "Based on what you said, here's how I'd think about a tool that helps. Does that match?"
13–15 min: clear next step. "Want to do a demo Thursday at 10am or 2pm?"

Demo (30 min):

0–3 min: confirm what they need to see.
3–25 min: walk through the product with their data and their use case. Not a feature tour; their workflow.
25–28 min: pricing & objection handling.
28–30 min: close. "Trial starts now. I'll send the link as soon as we hang up."

Common objections:

"I need to think about it." → "Sure — what specifically? Pricing, fit, or timing?" Force specificity.
"It's too expensive." → "Compared to what?" Listen, then anchor on the alternative cost.
"We're using {competitor}." → "What do you wish {competitor} did better?" Their answer is your sales pitch.
"I need to talk to my team / boss." → "Totally fair. What would they need to see? Want me to send a 5-min recording?" Then send a Loom of the demo within an hour.

8.3 Selling without a sales background

Most solo founders are technical and uncomfortable selling. Three reframes:

Sales is teaching, not pushing. You're teaching the buyer how to solve their problem. They are paying for you to teach them. This frame fits engineering brains.
The customer already has the problem. You are not creating pain; you are pointing to existing pain and offering a path. Your job is to be honest about whether you fit.
Disqualify aggressively. A bad-fit customer is worse than no customer — they consume support, complain, and churn. The best sales call ends in "we're not a fit" 30% of the time. That's healthy.

If you absolutely hate sales: assign yourself 3 hours of sales work per week (Tuesday + Thursday, 90 min blocks) and treat it like CrossFit. You won't love it; you'll just do it.

8.4 Self-serve onboarding for customers 11–100

Around customer 10, you'll feel the bottleneck: you're spending all your time onboarding. Two things to ship:

Asynchronous onboarding flow:

Welcome email with a 2-minute video walkthrough.
In-app checklist with 5 steps to first value.
Template gallery — pre-filled examples your customer can clone instead of starting from blank.
A Loom recording library answering the top 5 questions.

Self-serve sales:

Public pricing page (no "contact us" until you have an enterprise tier).
Self-serve signup (no manual approval).
Self-serve plan upgrades.
Self-serve cancellation. (Yes, even though it hurts. The friction you save customers is karma you collect.)

You'll still talk to every customer in person until ~50–100 customers. But the load should drop from 4hr/customer to 30min/customer by automation.

8.5 The "dogfood-then-sell" loop

If you're a good fit for your own ICP, use the product yourself daily. The number of solo SaaS founders who don't use their own product is shocking. Reasons to dogfood:

You will catch onboarding friction in real time.
You will see your product the way a customer sees it.
You will write better marketing copy from real workflow language.
You will have a working demo at all times.

Even if you're not the customer (e.g. you're building for dentists), force yourself to use the product weekly with a stand-in account. Half-build is the death of momentum.

8.6 The customer interview cadence (forever)

After every 5 new customers, schedule 30-min "how's it going" calls with 2 of them. Free, casual, no agenda. Topics:

"What did you expect when you signed up?" (Mismatch = fix marketing.)
"What was the most confusing part?" (Onboarding friction.)
"What are you actually using it for?" (Often different from your assumptions.)
"What would make you tell a friend?" (Hidden value.)
"What would make you cancel?" (Existential risks.)

You will learn more here than from any analytics dashboard. Continue this practice forever, even at $1M ARR.

8.7 The upgrade and expansion playbook

After customers have used your product 60–90 days, expansion (upsell, cross-sell, seat add) becomes the highest-margin revenue you can earn. Tactics:

Usage-based triggers: when they hit 80% of a plan limit, in-app banner offers the upgrade. Email follow-up day 1, day 7. Don't surprise-charge; do prompt-warmly.
Annual prompt: at month 8 of monthly billing, prompt the annual upgrade. "Lock in $X/yr instead of $Y/mo — save $Z." This converts 20–35% of healthy monthly customers.
Power-user moments: detect when a customer is a power user (high seat count, high feature adoption, high frequency) and personally email them with a custom plan offer. These customers are at-risk of either expanding hugely or churning to a competitor.
Champion expansion in B2B: when one team is happy, ask for a warm intro to the next team. "Who else at $company struggles with this?"

Net Revenue Retention (NRR) above 100% means your existing customer base grows without new customers — the holy grail of solo SaaS economics.

9. 🔁 Iteration, Feedback & Roadmap Discipline

Most solo founders fail by either (a) listening to every customer and building a swiss-army knife, or (b) ignoring all feedback and building their fantasy product. Neither works. The discipline is in the middle.

9.1 The feedback hierarchy

Not all feedback is equal. Rank requests by these signals:

Multiple unrelated paying customers asking for the same thing within a quarter. → Build it.
One paying customer asking with a willingness to pay extra. → Build a v0 and charge for it.
One paying customer asking with strong reasoning. → Add to backlog, revisit if 2nd customer asks.
Free user / trial user asking. → Politely thank them, log it, do not act.
Random hacker news / Twitter critique. → Read once, do not respond, do not act.
You wishing the product had X. → Most dangerous. Ask 5 customers; if they don't agree, kill it.

Most solo founders reverse this list and build (6) and (5) instead of (1) and (2). Your feedback hierarchy is the single highest-leverage prioritization tool you have.

9.2 Saying no — the kindest skill

Saying yes to everything is the most common solo founder mistake of year 2. Polite "no" templates:

"Great idea. It's not on the near-term roadmap, but I'm tracking it — if we hear this from more customers, it'll move up."
"I want to make sure I understand: when you say X, are you trying to do Y? I'd love to dig in before committing." (Often Y is already supported a different way.)
"That's outside the scope of {our positioning}. Have you tried {actual right tool}?" (Sending people away builds enormous trust.)

You should be saying no 5–10x more often than yes. If you find yourself saying yes by default, you have a discipline problem.

9.3 The roadmap that actually works

Rotating quarterly themes, weekly priorities, daily ships:

Quarter: one big theme (e.g. "Q1 2026: Improve activation rate from 28% → 45%"). Everything ladders into it.
Month: 2–3 medium-size deliverables (e.g. "redesign onboarding," "ship the new template gallery," "10-day email drip").
Week: ~5 specific tickets / customer-facing changes.
Day: the next 1–3 ships.

Document quarterly themes publicly (a /changelog or roadmap page). Customers love seeing direction; competitors learning is irrelevant — execution is what matters and you can ship faster.

Anti-pattern: Trello / Linear with 200 tickets in a "backlog" you never look at. Limit your active backlog to 20 items. If you can't say it's important enough to be in the top 20, kill it. Use a "kill file" for everything else.

9.4 Shipping cadence

Solo founders should ship something visible to customers every week. Not a feature every week, but something — a fix, a copy change, a new template, a Loom, a blog post, a newsletter. Visible momentum compounds trust.

Monday: plan the week. 5 things you'll ship.
Tuesday–Thursday: build mode.
Friday: ship + write the changelog post + share on socials.

Two-week sprints are too long for solo. One-week sprints with a public Friday post is the right cadence.

9.5 The "kill it" decision

Some features should die. Triggers to kill a feature:

Less than 5% of paying customers use it.
It's the source of 20%+ of your support tickets.
Maintenance has held you up from shipping new things twice in a row.
The competitor it was built to neutralize has moved on.
A new approach (often AI-enabled) makes it obsolete.

Killing a feature is hard psychologically — you remember building it. But every feature has a maintenance tax forever, and as a solo founder you cannot afford a maintenance budget growing linearly with feature count. Kill 1–2 features per year on principle.

9.6 The half-life of opinions

A surprising solo founder rule: your opinions about your product, market, and roadmap have a 90-day half-life. Things you were certain about in January will look obviously wrong by April. Build that into your process:

Re-read your own positioning every 90 days. Update.
Re-evaluate your top 3 features every 90 days. Are they still doing the job?
Re-check your pricing every 6 months.
Re-check your ICP every 6 months.

Founders who hold onto early decisions 18 months too long are the ones who plateau at $20K MRR. Founders who rev decisions every quarter — but stay disciplined about reversibility — break through.

(...to be continued...) Read Part 2 here https://viblo.asia/p/the-solo-founder-playbook-zero-to-hero-part-2-kNLr3DwEVgA

If you found this helpful, let me know by leaving a 👍 or a comment!, or if you think this post could help someone, feel free to share it! Thank you very much! 😃

Android iOS JavaScript ReactJS