0

๐Ÿฆธ The Solo-Founder Playbook: Zero to Hero - Part 3 ๐Ÿš€

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

  1. โšก Read This First
  2. ๐Ÿง  The Solo-Founder Mindset
  3. ๐ŸŽฏ Picking The Right Idea
  4. ๐Ÿ” Validation Before Code
  5. ๐Ÿ› ๏ธ Building the MVP โ€” The 6-Week Rule
  6. ๐Ÿ“ฃ Distribution-First Operating Mode
  7. ๐Ÿ’ฐ Pricing & Money
  8. ๐Ÿ‘ฅ First 10 โ†’ 100 Customers (Founder-Led Sales)
  9. ๐Ÿ” Iteration, Feedback & Roadmap Discipline
  10. ๐Ÿค– The AI-Leveraged Solo Stack
  11. ๐Ÿ—๏ธ Operating Cadence
  12. ๐Ÿง˜ Sustainability โ€” Burnout, Loneliness, Energy
  13. ๐Ÿ“ˆ The Growth Stage (10K โ†’ 100K โ†’ 1M MRR)
  14. ๐Ÿ‘จโ€๐Ÿ’ผ When (and How) to Hire or Outsource
  15. ๐Ÿ’ต Funding Paths
  16. โš–๏ธ Legal, Tax, Admin Minimum Set
  17. ๐Ÿšช Exit Paths
  18. โš ๏ธ The Anti-Pattern Catalog
  19. ๐Ÿ—บ๏ธ The Phased Roadmap ($0 โ†’ $1M ARR)
  20. ๐Ÿ“‹ Cheat Sheet & Resources
  21. ๐Ÿงฉ Appendix: Category Adaptations

Section 1 -> 9 Read Part 1 here https://viblo.asia/p/the-solo-founder-playbook-zero-to-hero-part-1-pPLkN37ZJRZ

Section 10 -> 18 Read Part 2 here https://viblo.asia/p/the-solo-founder-playbook-zero-to-hero-part-2-kNLr3DwEVgA

19. ๐Ÿ—บ๏ธ The Phased Roadmap ($0 โ†’ $1M ARR)

A realistic, opinionated month-by-month roadmap. Adjust to your idea, but use as a default.

Phase 0 โ€” Idea & Validation (Weeks 0โ€“6)

Goal: prove someone will pay before you write production code.

  • [ ] Pick ICP (two adjectives + noun + verb).
  • [ ] Run 20 customer discovery calls.
  • [ ] Build landing page with Stripe checkout.
  • [ ] 50 cold outreaches.
  • [ ] Goal: 5+ paid pre-orders or 3+ signed LOIs.

Decision gate: If โค๏ธ pre-orders or no clear channel, pivot or kill. Don't proceed to build.

Phase 1 โ€” MVP (Weeks 7โ€“14)

Goal: ship a v1 that the pre-order list pays for.

  • [ ] Pick boring stack, set up monorepo.
  • [ ] Build 1 core workflow end-to-end.
  • [ ] Stripe + auth + basic onboarding.
  • [ ] Beta launch to pre-order list (week 13).
  • [ ] First 5โ€“15 paying customers.

Decision gate: If activation rate <30% or churn >10%/mo, fix product before scaling distribution.

Phase 2 โ€” Founder-Led Sales (Months 4โ€“9)

Goal: $5Kโ€“$10K MRR. Find product-channel fit.

  • [ ] 100 cold outreaches per month.
  • [ ] 1 long-form post per week.
  • [ ] 1 customer interview per week.
  • [ ] Onboard each new customer personally.
  • [ ] Iterate weekly; ship a visible change every Friday.

Decision gate: $5K MRR with sub-5% monthly churn = product-channel fit. Move to Phase 3. Otherwise stay here, fix the leak.

Phase 3 โ€” Repeatable Acquisition (Months 9โ€“18)

Goal: $10K โ†’ $30K MRR. Industrialize the channel.

  • [ ] Hire customer support contractor (10โ€“20 hr/wk).
  • [ ] Double down on best channel (probably SEO + 1 social).
  • [ ] Raise prices 20โ€“30% with grandfather.
  • [ ] Build self-serve onboarding so 70%+ of new customers don't need a call.
  • [ ] Quarterly customer interviews continue.

Decision gate: $30K MRR with sub-3% monthly churn and CAC payback <6mo = scaling readiness.

Phase 4 โ€” Scale or Coast (Months 18โ€“36)

Goal: $30K โ†’ $100K MRR.

  • [ ] Hire content / SEO contractor.
  • [ ] Add second channel that complements primary.
  • [ ] Build expansion revenue (annual upgrades, seat add, upsell).
  • [ ] Add 2nd ICP only if first is saturating.
  • [ ] Decide: stay solo, hire team, or sell.

Decision gate: $1M ARR with healthy retention. Now choose your endgame.

Phase 5 โ€” Endgame (Year 3+)

Three paths:

  • Stay solo, lean. Continue. Compounding takes you to $2โ€“5M ARR over 3โ€“5 more years.
  • Build a team to grow faster. Hire 3โ€“5 people, target $5M+ ARR.
  • Sell. Prepare for 6 months, list, close in 4โ€“9 more.

All three are good. None are failures. The mistake is not deciding.


20. ๐Ÿ“‹ Cheat Sheet & Resources

The 20 commandments

  1. Distribution > product.
  2. Validate before you build.
  3. Six-week MVP, not six-month.
  4. Boring tech, opinionated product.
  5. One channel, perfected, before two.
  6. Tier pricing, raise prices yearly, push annual.
  7. First 10 customers manual, no exceptions.
  8. Customer conversations forever.
  9. Say no 5x more than yes.
  10. Ship something visible every week.
  11. Use AI as default, not as novelty.
  12. Batch by hat, not by topic.
  13. Friday review, monthly metrics, quarterly retrospectives.
  14. Sleep + exercise + community + therapy.
  15. Don't mix burnout with strategy.
  16. Don't hire too early, prefer contractors.
  17. Don't raise unless you can articulate why.
  18. Don't sell out of boredom.
  19. Don't compare to funded teams.
  20. Don't substitute motion for progress.

The minimum-viable solo founder reading list

Pick one per category. Don't read all. Apply.

  • Mindset: The Almanack of Naval Ravikant (Eric Jorgenson).
  • Product: The Mom Test (Rob Fitzpatrick).
  • Distribution: Traction (Gabriel Weinberg & Justin Mares); Building a StoryBrand (Donald Miller).
  • Sales: Founding Sales (Pete Kazanjy, free online).
  • Pricing: Monetizing Innovation (Madhavan Ramanujam).
  • Indie path: Just Fing Ship* (Amy Hoy); Make (Pieter Levels).
  • Cashflow: Profit First (Mike Michalowicz).
  • Burnout: Burnout: The Secret to Unlocking the Stress Cycle (Emily & Amelia Nagoski).

The solo founder community list

  • Indie Hackers โ€” community + interviews.
  • MicroConf Connect โ€” paid Slack, very high signal.
  • Hacker News โ€” for distribution and news.
  • Founder.io / Lenny's community โ€” paid, more PMM-leaning.
  • Local founder dinner โ€” find or start one. Cannot be replaced by online.

The dashboard you should be able to pull up in 10 seconds

Build it once, look at it weekly:

  • MRR / ARR
  • Net new MRR this month
  • Customers (total, new, churned)
  • Activation rate (signup โ†’ first value)
  • Top of funnel (organic visitors, signups)
  • Cash balance / months of runway
  • Top 3 retention cohorts month-over-month

If any of those feel hard to pull, your analytics setup is the next thing to fix.

The "I'm stuck" decision tree

Use when you don't know what to do next:

  1. Is there a customer waiting for me? (support, demo, follow-up.) โ†’ Do that first.
  2. Is the next $1K MRR closer through sales or marketing? โ†’ Do that.
  3. Is there a feature blocking churn or upgrade for a real customer? โ†’ Ship it.
  4. Is the channel performing? โ†’ If no, fix it. If yes, scale it.
  5. Am I overthinking? โ†’ Pick the easier of two reversible options. Ship it. Iterate Friday.

The most important meta-rule: when you don't know what to do, do something the customer can see this week. Customer-visible motion compounds. Internal motion does not.


Final Word

You picked the hardest game in tech: building a software business alone. The advantages are real (speed, focus, ownership, optionality) but so is the cost (loneliness, burnout risk, every decision yours, every failure yours).

The founders who win solo are not the most talented or the most funded. They are the ones who:

  1. Pick a focused niche where they have an unfair advantage.
  2. Validate ruthlessly before they build.
  3. Build a single channel into a compounding asset.
  4. Charge a fair price for real value.
  5. Listen to customers without becoming their puppet.
  6. Take care of their own energy as if it were the company's most important asset (it is).
  7. Stay in the game for 5+ years.

Most solo founder failures are not strategic failures. They're stamina failures. The strategy in this playbook is well-known; the execution is where 90% of founders fall short. The ones who don't fall short don't read 50 books or run 50 experiments. They run one focused experiment, week after week, year after year.

You don't need to be a genius. You need to be a runner.

Now ship something today. The first version of anything is always wrong. Wrong in production beats right in your head.

๐Ÿš€


21. ๐Ÿงฉ Appendix: Category Adaptations

The main playbook is SaaS-shaped. This appendix translates it for the eight other categories solo founders most commonly build in. For each: what carries over, what's different, what to read instead, and a category-specific roadmap.

What carries over to every category

If you take nothing else from this appendix: ยง2 (Mindset), ยง11 (Cadence), ยง12 (Sustainability), ยง14 (Hiring), ยง16 (Legal/admin), and ยง18 (Anti-patterns) apply universally. The mindset of a solo operator, the importance of validation, the discipline of distribution-first, and the danger of burnout do not care whether you ship .exe files, vegetables, or LP tokens.

What changes by category: the MVP shape, the monetization model, the sales motion, the metrics, and the exit math. Those are the parts this appendix rewrites.

21.1 ๐ŸŽฎ Indie Games

The fundamental difference: games are sold once (or with one DLC), not subscribed to. Revenue is launch-spike-shaped, not annuity-shaped. There is no MRR; there is launch revenue + long tail.

What's different from the main playbook:

Topic SaaS playbook says Indie games reality
MVP timeline 6 weeks 6โ€“24 months (vertical slice in ~6 months)
Validation Pre-sell with Stripe Steam wishlists, demo on Steam Next Fest, Kickstarter for ambitious projects
Primary KPI pre-launch Pre-orders Wishlist count (target: 7K+ before launch for healthy day-1 sales)
Distribution SEO + cold outbound Steam algorithm, streamers, niche subreddits (r/IndieDev, r/IndieGaming), TikTok dev-logs, IndieDB
Pricing $29/$79/$199 monthly $4.99โ€“$29.99 one-time + DLC + maybe Game Pass deal
Refund window Generous goodwill policy Steam mandates 2hrs played / 14 days. Refund rate >8% = the game has a problem
Sales motion Founder-led demos Trailer + Steam page + screenshots โ€” your store page is your sales pitch
Exit 3โ€“6x ARR Studio acquihire, IP sale, publisher signing, or just keep operating

The "one weird trick" for solo game devs: the Steam page is your product. Many indies build the game first and the Steam page last. Reverse it. Build the Steam page (capsule art, trailer storyboard, tagline, genre tags) in week 1. If that page does not generate >300 wishlists per month organically once posted, the game is wrong before you've shipped a level.

Solo-game-dev-specific roadmap:

  • Months 0โ€“3: prototype + Steam page live + first trailer. Target 1K wishlists.
  • Months 3โ€“9: vertical slice (one polished hour). Demo at Steam Next Fest. Target 5Kโ€“10K wishlists.
  • Months 9โ€“18: full content. Streamer outreach. Target 20K+ wishlists.
  • Launch day: typical Steam conversion is ~10% wishlistโ†’purchase in first week. 20K wishlists ร— 10% ร— $15 = ~$30K launch revenue. (Steam takes 30%.)
  • Long tail: 1.5โ€“3x launch revenue over 2โ€“3 years if reviews are 80%+.

Read instead:

  • Chris Zukowski โ€” How To Market A Game (howtomarketagame.com), the canonical resource.
  • Ryan Clark โ€” GDC talks on indie revenue distribution.
  • Jason Schreier โ€” Press Reset, Blood, Sweat, and Pixels (industry reality).
  • Derek Yu โ€” Spelunky book (solo dev mindset).
  • Subreddit: r/gamedev, r/indiegames.

Avoid the SaaS trap of: subscription pricing (most indie games fail with subscriptions), feature creep (scope-cut ruthlessly โ€” see Stardew Valley's 4-year solo dev as the cautionary maximum), and ignoring the publisher path (a small indie publisher takes 30โ€“50% but unlocks console + marketing โ€” often worth it for solo).

21.2 ๐Ÿ›’ Physical-Goods Ecommerce (fruit, vegetables, vehicles, anything you ship)

The fundamental difference: you have inventory, COGS, shipping, and returns. Gross margins are 20โ€“60% (vs. 70โ€“95% for SaaS). Cashflow becomes the dominant problem โ€” not revenue, not product.

What's different from the main playbook:

Topic SaaS playbook says Ecommerce reality
Stack Next.js + Postgres Shopify (or WooCommerce, BigCommerce). Do not custom-build.
MVP 6-week build 4โ€“8 weeks: storefront + first products + supplier deal + shipping setup
Validation Pre-sell on landing page Pre-launch Instagram + Shopify pre-orders, or test ads โ†’ cost-per-acquisition under target
Primary metric MRR Contribution margin per order (revenue โˆ’ COGS โˆ’ shipping โˆ’ fees โˆ’ ad spend). If this is negative, scale = death.
Pricing Tiered subscription Cost-plus markup, typically 2.5โ€“4x landed cost depending on category
Distribution SEO + outbound Meta/TikTok ads (still dominant), influencer/UGC, organic content (TikTok especially), eventually Amazon
Founder-led sales Demos Customer service via DM, abandoned-cart emails, post-purchase upsells
Cashflow Stripe daily Inventory ties up cash 30โ€“90 days before revenue arrives โ€” primary failure mode
Exit multiple 3โ€“6x ARR 2โ€“4x SDE (seller's discretionary earnings). Lower than SaaS because operationally heavier.

The thing that kills 80% of solo ecommerce founders: they don't track unit economics. They see $100K in revenue and assume they're winning. Then COGS, ad spend, fees, and returns net out to -$5K and they fold. Build the contribution-margin spreadsheet on day 1, before your first product is sourced.

Niche ecommerce specifics (your fruit/vegetable/vehicle examples):

  • Perishables (fruit, vegetables, fresh food): cold-chain shipping is brutal. Most solo founders fail here. If pursuing: start with shelf-stable variants (dried, jams, sauces, freeze-dried), validate the market, then expand to fresh. Or sell within driving distance only (local CSA model). National fresh ecommerce solo is essentially impossible without 7-figure capital.
  • High-ticket physical (vehicles, equipment, art, jewelry): $1K+ AOV (average order value) means 1 sale = real revenue. Sales cycle is long, customer service is intensive, returns are catastrophic. Lead-gen + offline close often beats pure ecommerce. Build a content site, capture leads, close on phone/email, ship.
  • Niche consumer goods (specialty teas, hot sauces, niche apparel): the standard Shopify + Meta ads + influencer playbook works, but margin discipline is everything. Aim for 65%+ gross margin pre-shipping.

Solo-ecommerce-specific roadmap:

  • Weeks 0โ€“4: product validation. 1 product, 1 supplier (Alibaba, faire.com, or local). Sample order, photograph, list on Shopify. Spend $500 on test ads. Target: contribution margin >$15/order. If not, change product or supplier.
  • Months 1โ€“3: scale ad spend with positive contribution margin. 3โ€“5 SKUs.
  • Months 3โ€“6: launch email/SMS flows (Klaviyo). Abandoned cart, browse abandonment, post-purchase. Target: email = 25โ€“35% of revenue.
  • Months 6โ€“12: brand building. UGC/influencer pipeline. Repeat-customer rate >25%. AOV optimization.
  • Year 2: Amazon, retail wholesale, or expand SKUs. Hire fulfillment (3PL) before you hate your life.

Read instead:

  • Andrew Youderian โ€” EcomCrew podcast and Reddit r/ecommerce.
  • Profit First for Ecommerce (Cyndi Thomason).
  • DTC Newsletter (Web Smith, 2PM, Lenny's DTC content).
  • Shopify's Compass content (free, surprisingly good).
  • 4 Hour Workweek (Tim Ferriss) โ€” supplier sourcing chapters still apply.
  • For consumer brand strategy: Hooked (Nir Eyal), This Is Marketing (Seth Godin).

Avoid: building your own ecommerce platform (Shopify wins, full stop), free shipping at low AOV (kills margin), launching with 50 SKUs (start with 1), ignoring email/SMS until "later" (it's 30%+ of revenue immediately).

21.3 ๐Ÿช Marketplaces & Two-Sided Platforms

The fundamental difference: chicken-and-egg. You have to recruit both supply and demand from zero. The product alone is worthless without liquidity. Most marketplaces fail not because the product is bad but because they couldn't bootstrap one side.

What's different from the main playbook:

Topic SaaS playbook says Marketplace reality
Validation Pre-sell to one buyer LOIs from 5+ supply and 5+ demand-side participants for the same constrained vertical
MVP 6 weeks 8โ€“16 weeks. The product is the matching, the trust, the payment rails.
Primary metric MRR GMV (gross merchandise value) and take rate (your %). Revenue = GMV ร— take rate.
Distribution SEO + outbound Both sides simultaneously. Cold-recruit supply, then run paid ads + content for demand.
Pricing Subscription tiers Take rate (10โ€“25% typical), listing fees, lead fees, or subscription for "pro" sellers
Sales motion Founder-led Founder-led for supply side first (manual recruitment of first 50 sellers)
Cold-start strategy Channel Single-player mode first โ€” your product must be useful to one side even when the other side is empty (e.g. inventory-management for sellers, scheduling for service providers)
Trust/safety Email + Stripe KYC, escrow, dispute resolution, ratings โ€” ALL on you from day 1
Exit multiple 3โ€“6x ARR 4โ€“8x revenue, sometimes higher. Marketplaces command premium when sticky.

The Cold Start Problem (the single most important concept for marketplace founders):

  1. Pick a "hard side" to bootstrap first. For most marketplaces, supply is harder to recruit than demand. Solve their workflow first; you become a SaaS for them, then you turn on the marketplace.
  2. Geographic constraint or vertical constraint, never both relaxed. Airbnb started in NYC. Uber started in SF. DoorDash started Stanford. Tightly constrained marketplaces hit liquidity 10x faster than horizontal ones.
  3. Manually match the first 100 transactions. Yes, by hand. Yes, in a spreadsheet. The "marketplace" can be 100% manual matching for months โ€” you're learning the matching algorithm, not coding it yet.
  4. Solo founders should not build horizontal marketplaces. The capital and team required to break out of cold-start is structurally too high. Vertical, niche, geographically-constrained marketplaces are the solo path. Pieter Levels' Nomad List (digital-nomad-vetted apartments + community) is the canonical solo example.

Solo-marketplace-specific roadmap:

  • Months 0โ€“3: pick the smallest viable wedge. Manually recruit 20 supply-side participants. Build "single-player" tool that helps them whether or not demand exists.
  • Months 3โ€“6: open demand-side. Manually match first 50 transactions. Charge a take-rate from day 1 (do not "do it free for now" โ€” sets a bad precedent).
  • Months 6โ€“12: automate matching. Hit liquidity threshold (varies by category โ€” for service marketplaces, ~20 active suppliers + ~100 monthly buyers in a single geo).
  • Year 2: expand geo or category. Network effects compound.

Read instead:

  • Andrew Chen โ€” The Cold Start Problem (the only book you need).
  • Sangeet Paul Choudary โ€” Platform Revolution.
  • Lenny Rachitsky's marketplace deep-dives (Substack).
  • a16z marketplace content โ€” Li Jin, Sarah Tavel writeups.
  • Boris Wertz โ€” Version One Ventures marketplace handbook.

Avoid: building a 100% automated marketplace before you've manually matched 50 transactions, "we'll worry about take rate later" (you'll never raise it), launching nationally (geo-constrain), and trying to be Uber-for-X without Uber's capital.

21.4 โœ๏ธ Creator / Info Products / Audience-First

The fundamental difference: the product is your audience and the secondary product is whatever you sell to them. Distribution comes first by 12โ€“24 months. This is the highest-leverage category for non-technical solo founders in 2026.

What's different from the main playbook:

Topic SaaS playbook says Creator reality
Order of operations Build product โ†’ distribute Distribute first โ†’ product emerges from audience
MVP Software A newsletter, podcast, YouTube channel, or X account
Pre-product time 6 weeks 12โ€“24 months of content before first $1
Primary metric MRR Email list size, engaged followers, podcast downloads
Pricing Subscription tiers Multi-tier: free content (top of funnel) โ†’ paid newsletter ($5โ€“$30/mo) โ†’ cohort course ($300โ€“$3000) โ†’ coaching ($1Kโ€“$10K/hr) โ†’ community ($30โ€“$200/mo)
Distribution SEO + outbound Native to platform: YouTube โ†’ YouTube. X โ†’ X. Content + cross-platform.
Sales motion Demos Sales-via-content. Webinar funnel for higher tickets.
Exit Sell SaaS Audiences rarely sell well. Some monetize forever; some converted into SaaS or community products that do sell.

The 1000-true-fans math: 1000 people paying you $100/year = $100K/year. Solo, sustainable, repeatable. The internet's gift to creators.

The creator product ladder (canonical for solo creators):

  1. Free content โ€” newsletter, podcast, YouTube. Top of funnel.
  2. Low-ticket digital product โ€” $20โ€“$50 ebook, template pack, checklist. Builds buyer list.
  3. Mid-ticket course / cohort โ€” $300โ€“$3000. The bread and butter.
  4. High-ticket coaching / consulting โ€” $1Kโ€“$10K. Time-bounded, high-margin.
  5. Community / membership โ€” $30โ€“$200/mo. Recurring, defends against churn.
  6. Software/SaaS spin-off โ€” eventually, an audience-driven SaaS where conversion is 30%+ instead of 1%.

Justin Welsh's playbook ($5M+ solo): newsletter (free) โ†’ courses ($150โ€“$300) โ†’ community ($300/yr). Daniel Vassallo: courses โ†’ community โ†’ consulting. Pieter Levels: products tied to community.

Solo-creator-specific roadmap:

  • Months 0โ€“6: publish weekly. One platform. No product yet. Goal: 1000 email subscribers.
  • Months 6โ€“12: drop a $30 product. Goal: 5000 subscribers, 200 buyers.
  • Months 12โ€“24: launch a $300โ€“$1000 cohort/course. Goal: 10K subscribers, 100 cohort buyers = $30Kโ€“$100K.
  • Months 24+: community + coaching + maybe a software product. Multi-six-figure.

Read instead:

  • Justin Welsh โ€” Solopreneur Playbook (his newsletter).
  • David Perell โ€” writing as a solo creator path.
  • 1000 True Fans (Kevin Kelly, original essay, 30 min read).
  • Show Your Work (Austin Kleon).
  • The Embedded Entrepreneur (Arvid Kahl) โ€” audience-first SaaS.
  • Tiago Forte โ€” Building a Second Brain (creator workflow).
  • Nathan Barry โ€” Authority.

Avoid: trying to monetize before 1000 subscribers (kills audience momentum), spreading across 5 platforms simultaneously (one platform first), and building software before you have an audience to sell to (you're now in normal SaaS land with extra steps).

21.5 ๐Ÿ’ธ Fintech / Trading Platforms

The fundamental difference: regulation makes solo founding here hard, sometimes impossible. Money transmission, broker-dealer, custody, KYC/AML โ€” these are not "we'll figure it out later" items. They're required day 1 in most jurisdictions.

What's different from the main playbook:

Topic SaaS playbook says Fintech reality
MVP Ship, iterate You cannot "just ship" a money-handling product. Compliance from day 1 or you go to jail.
Stack Next.js + Stripe Build on top of licensed BaaS: Alpaca, Plaid, Lithic, Wise APIs, Marqeta, Stripe Connect, Synapse. Never custody money yourself.
Validation Pre-sell LOIs + bank/BaaS partnership conversations before product.
Primary metric MRR AUM (assets under management), TPV (total payment volume), interchange/spread revenue, take rate
Compliance Add SOC 2 later KYC/AML day 1. Money transmitter license per US state ($1M+ to acquire all 50). MiCA in EU. SEC/FINRA registration if securities.
Time to market 6 weeks 6โ€“18 months even building on BaaS. Solo plus a fractional compliance officer is the minimum team.
Exit 3โ€“6x ARR Often higher (5โ€“10x revenue) but acquirer due diligence is brutal โ€” clean compliance = required, not optional.

The two solo-survivable fintech archetypes:

  1. Wrapper / aggregator on top of licensed providers. You're a software company that sits on top of a licensed bank, broker-dealer, or custodian. Examples: a niche budgeting app on top of Plaid; a vertical tax-loss harvester on top of Alpaca; a cross-border invoicing tool on top of Wise. You handle UX + workflow; they handle the regulated part. This is the only solo-viable path.
  2. Pure SaaS sold to fintech companies. You don't move money; you sell software to people who do. Tools for banks, RIAs, insurers, accountants. Standard B2B SaaS playbook applies โ€” this is just vertical SaaS for fintech, and the main playbook works.

The trading platform specifically:

  • Equities/options: broker-dealer license + clearing relationship = $5M+ + 18 months. Not a solo project. Build on Alpaca/DriveWealth.
  • Crypto: money transmitter licenses + state-by-state + MiCA. Hard. Build on Coinbase Prime, Fireblocks, or skip custody entirely and aggregate exchanges (no custody = much lighter regulation, e.g. analytics tools, signal services).
  • Forex / CFDs: even harder. Skip unless this is your industry.
  • Signal / analytics / tooling for traders: standard SaaS. โœ… Solo-viable.

Solo-fintech-specific roadmap:

  • Months 0โ€“2: legal/regulatory mapping. Hire a fintech lawyer for $3Kโ€“$5K initial scope. Identify which BaaS partner makes you legal.
  • Months 2โ€“4: sign BaaS partner agreement. (Yes, they vet you. Plan for 4โ€“8 week sales cycle.)
  • Months 4โ€“9: build with compliance baked in (KYC flow, AML monitoring, audit logs from day 1).
  • Months 9โ€“12: launch to constrained beta. Watch transaction velocity, fraud rate, edge cases.
  • Year 2+: scale carefully. Every new geo = new compliance review.

Read instead:

  • Simon Taylor โ€” Fintech Brainfood newsletter (the canonical industry source).
  • This Week in Fintech โ€” Nik Milanoviฤ‡.
  • The Pulse of Fintech (KPMG quarterly).
  • Lex Sokolin โ€” Future of Finance writings.
  • a16z fintech content โ€” Angela Strange's "every company will be a fintech."
  • For trading specifically: Trading Systems and Methods (Perry Kaufman) for domain depth.

Avoid: custodying money yourself (licensure trap), launching before legal review (federal crimes are not metaphors), and "we'll add KYC later" (you won't be in business).

21.6 ๐Ÿ“ฑ Mobile Apps (Consumer)

The fundamental difference: distribution is gated by Apple and Google. ASO (App Store Optimization) replaces SEO. IAP (in-app purchases) replaces Stripe. Your platform can ban you on a Tuesday.

What's different from the main playbook:

Topic SaaS playbook says Mobile reality
Stack Next.js React Native, Flutter, Expo, or native (Swift/Kotlin)
Distribution SEO + content ASO (keywords in title/subtitle), paid (Apple Search Ads, TikTok), influencer/UGC
Pricing Stripe subscriptions In-app subscriptions (Apple/Google take 15โ€“30%), freemium with paywalls
MVP 6 weeks 8โ€“12 weeks (longer due to platform review, IAP setup)
Primary metric MRR DAU/MAU, retention curves (D1/D7/D30), trialโ†’paid conversion, LTV/CAC
Sales motion Founder-led B2B Self-serve only, no humans in the loop. Onboarding is the sales motion.
Cold-start Manual outreach Paid acquisition (~$2โ€“$10 CPI for utility, $20+ for finance/fitness)
Exit 3โ€“6x ARR 3โ€“6x ARR, but app businesses are seen as more fragile (platform dependence) โ€” sometimes lower

The solo-mobile reality:

  • The category that minted the most solo millionaires in 2024โ€“2025 (productivity apps with viral TikTok loops, AI-powered consumer apps, niche fitness/health apps).
  • Also the category with the highest failure rate โ€” the App Store is a graveyard.
  • Single biggest predictor of success: a TikTok/Instagram organic engine + paid acquisition + clear monetization day 1.

Subscription pricing canonical structure:

  • 3-day free trial (or 7-day) โ†’ annual ($39โ€“$99) is the dominant pattern.
  • Monthly option exists but is anchored high to push annual ($9.99/mo vs $49.99/yr).
  • Lifetime option for power users at 3โ€“5x annual.
  • Onboarding paywall is the conversion engine. Every screen of onboarding is optimization surface area.

Solo-mobile-specific roadmap:

  • Months 0โ€“3: ship to TestFlight. 100 beta users. Get D7 retention >25%.
  • Months 3โ€“4: App Store launch. Onboarding paywall optimized through 5+ iterations.
  • Months 4โ€“9: organic + paid loop. TikTok/Reels content. Goal: $5K MRR with positive LTV/CAC.
  • Months 9โ€“18: scale paid. Goal: $50K MRR.

Read instead:

  • Mobile Dev Memo (Eric Seufert) โ€” paid acquisition canon.
  • Phiture โ€” ASO + retention deep dives.
  • Sub Club podcast (RevenueCat) โ€” subscription mobile economics.
  • App Profits โ€” Steve P. Young.
  • AppFigures, Sensor Tower data tools.

Avoid: ignoring D1 retention (<40% = the app is broken), free apps without monetization plan (you'll have users and no revenue), platform-feature dependence (Apple/Google can replicate any utility app in OS-native features).

21.7 ๐Ÿงฐ Browser Extensions / Developer Tools / Open-Source-as-a-Business

The fundamental difference: the audience is technical and skeptical. Trust is earned through code transparency, GitHub stars, and content โ€” not sales calls.

What's different from the main playbook:

Topic SaaS playbook says Dev tools reality
MVP 6 weeks 4โ€“8 weeks (the dev audience is forgiving of rough UX, harsh on broken core functionality)
Validation Pre-sell Open-source the core, gauge GitHub stars + community engagement
Primary metric MRR GitHub stars + active installs + (eventually) paying teams
Pricing Tiered SaaS Free for individuals, paid for teams. The "team plan" pattern. Or: open-core (free OSS + paid hosted/enterprise features).
Distribution SEO + outbound HackerNews + dev Twitter + Reddit (r/programming, r/webdev) + dev podcasts + technical blog
Sales motion Founder demos Self-serve until $30K MRR. Then PLG โ†’ enterprise upsell when teams grow.
Cold-start 100 emails Show HN launch + technical blog post + GitHub repo public
Exit 3โ€“6x ARR 3โ€“8x ARR โ€” dev tools sometimes get tech-strategic premiums (acquired for talent + product)

The OSS-as-business archetypes (2026):

  1. Open-core: OSS engine + paid hosted/enterprise features. (PostHog, Supabase, Cal.com, Posthog, Linear-clone-ish.)
  2. Source-available + paid license for commercial use. (Sidekiq, Redis, MongoDB-style.)
  3. Free OSS + paid SaaS hosted version. (GitLab, n8n.)
  4. Pure OSS + sponsorship/consulting. Rarely scales solo to 7-figures.

The HackerNews launch playbook:

  • Title: "Show HN: {project} โ€“ {one-line description}."
  • Post Tuesday or Thursday morning ET.
  • Pre-warm: ask 5 trusted dev friends to comment honestly (not vote โ€” comment).
  • First comment = OP comment with technical detail, why you built it, what's missing.
  • Be online for 4โ€“8 hours to answer questions.
  • Realistic outcome: 30 stars + 200 visitors (failed launch) up to 5K stars + 50K visitors (front page win).

Solo-dev-tools-specific roadmap:

  • Months 0โ€“3: ship OSS + technical blog. Target 500 GitHub stars + 50 active users.
  • Months 3โ€“9: free hosted version. Self-serve. Target $5K MRR from teams.
  • Months 9โ€“18: team features, SSO, enterprise plan ($500+/mo). Target $30K MRR.
  • Year 2: PLG โ†’ enterprise upsell. Hire DevRel/community contractor.

Read instead:

  • Joseph Jacks โ€” Open Source Software's Singular Decade and OSS Capital writings.
  • Adam Jacob (Chef) โ€” OSS commercialization talks.
  • Heavybit's Developer Marketing podcast.
  • Working in Public (Nadia Eghbal).
  • Mikkel Svane (Zendesk founder) on PLG.
  • PLG with Wes Bush โ€” Product-Led Growth book.

Avoid: pure OSS without monetization plan (you'll have a thriving project and no income), aggressive dual-licensing changes (community backlash is real โ€” see ElasticSearch, MongoDB, Redis controversies), and selling to developers instead of teams (developers don't have purchasing power; their managers do).

21.8 ๐ŸŽ“ Vertical Services / Productized Services

The fundamental difference: you're selling a delivered outcome (often human-powered or AI-augmented), not software access. Margins are lower than SaaS but startup time is dramatically faster.

What's different from the main playbook:

Topic SaaS playbook says Productized service reality
MVP 6 weeks of building You can sell day 1. Product is the service description.
Validation Pre-sell Sell, then deliver manually first 10 times. Then automate.
Primary metric MRR Active retainer count, gross margin per delivery, hours-per-delivery (decreasing over time = automation success)
Stack Next.js Notion + Airtable + Stripe + Calendly + Zapier. Custom code only when retainer count justifies it.
Pricing Tiered SaaS Productized retainers ($500โ€“$5000/mo for one specific outcome) or fixed-scope projects ($1Kโ€“$50K per project)
Sales motion Founder demos Discovery call โ†’ scope โ†’ proposal โ†’ start. 7โ€“14 day sales cycle.
Distribution SEO + content LinkedIn + niche communities + warm referrals (60%+ of revenue at maturity)
Exit 3โ€“6x ARR 1โ€“3x SDE โ€” services sell for less than SaaS, but you can take cash out monthly

The productized-service archetype: Brett Williams' DesignJoy ($2M+ solo running unlimited-design subscriptions). Pick a specific output (logos, landing pages, video edits, content briefs), package it as a flat monthly fee, deliver 100 โ†’ automate as you go.

Why this is a great solo on-ramp:

  • Cashflow positive immediately.
  • No 12-month "build before revenue" hole.
  • Forces you to learn customer pain in detail.
  • Naturally evolves into SaaS or info product (you sell the playbook you developed).

Solo-service-specific roadmap:

  • Month 1: define ONE service. Price it. Build a 1-page landing site. Offer to first 5 prospects at 50% off.
  • Months 1โ€“3: deliver manually. Learn the workflow. Document everything. Goal: $5Kโ€“$10K MRR from retainers.
  • Months 3โ€“6: identify automation candidates (templates, AI, contractors). Reduce hours-per-delivery by 50%.
  • Months 6โ€“12: raise prices, scale to $30K MRR with same hours.
  • Year 2: decide โ€” stay services (lifestyle), productize as software, or sell methodology as info product.

Read instead:

  • Brian Casel โ€” Productize podcast and book.
  • Brett Williams (DesignJoy) โ€” Twitter and interviews.
  • The Win Without Pitching Manifesto (Blair Enns) โ€” pricing services.
  • Rocket Fuel (Wickman) โ€” ops for scaling small services.
  • Built to Sell (John Warrillow) โ€” how to make a service business sellable.

Avoid: scope creep (always fixed-scope, always), hourly billing (race to the bottom), and undercharging (services chronically underpriced โ€” start at 2x what feels comfortable).

21.9 Decision matrix: which category fits which solo founder?

Founder profile Best-fit category Why
Strong B2B domain (worked in industry 5+ years) Vertical SaaS (main playbook) You know the buyer, the workflow, the budget
Technical, no audience, no domain Dev tools / OSS Code is the credibility; HN + Twitter is the channel
Non-technical, good writer/speaker Creator / info products โ†’ eventually SaaS Audience is the moat
Designer / video editor / writer Productized service Cashflow day 1; evolves to product later
Game designer, artistic vision Indie games One-shot launches; passion project has commercial path
Operator with capital ($50K+) Niche ecommerce Inventory game requires capital; margins demand discipline
Industry insider with marketplace insight Vertical marketplace Cold-start solvable only with domain knowledge
Existing audience + iOS skills Mobile consumer app TikTok organic + IAP monetization
Finance background + tech skills Fintech wrapper Compliance literacy is the moat

The wrong category for your skills = 5x harder. The right category = 5x easier. Audit honestly before you commit 12 months.

21.10 What stays the same across all categories

Even with all the tactical differences above, these principles apply universally:

  1. Validate before you build. The mechanism differs (Steam wishlists, Stripe pre-orders, LOIs, audience growth), but the principle is identical.
  2. One channel, perfected, before two. Whether SEO or HackerNews or TikTok or Steam, focus wins.
  3. Distribution is the product. Across every category in this appendix, the founders who win are the ones who picked a channel and built it into a compounding asset.
  4. Stamina, not strategy, decides. Every category has a wall (the 6-month wall in SaaS, the 12-month audience wall for creators, the wishlist wall for game devs). Survivors break through; quitters don't.
  5. Customer conversations forever. Whether players, customers, sellers, traders, or readers โ€” talk to them weekly. Stop talking and you plateau.

Cross-category, the meta-skill is the same: be a focused, sustainable, compounding operator who picks the right game for their advantages and plays it for 5+ years. The category is the lane; the playbook is the driving.

๐Ÿš€

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! ๐Ÿ˜ƒ


All Rights Reserved

Viblo
Let's register a Viblo Account to get more interesting posts.