How to build a bootstrapped B2B SaaS company

You build a bootstrapped B2B SaaS by solving one painful, narrow problem for a specific buyer, charging from day one, and compounding distribution through founder-led sales, integrations, and content. It’s viable: Mailchimp was bootstrapped for two decades before its $12B acquisition by Intuit, and Basecamp has remained a profitable, self-funded business for years. (investors.intuit.com)

Key takeaways

• Pick a tiny ICP and one job-to-be-done; pre-sell to 5–10 buyers before writing production code.
• Start paid from day one; keep pricing simple (seat or tier) and add usage-based elements later.
• Choose a billing stack you can run yourself (Stripe Billing) or outsource (Merchant of Record like Paddle/Lemon Squeezy). Fees differ materially; model them early.
• For distribution, stack channels: founder-led outbound, integrations marketplaces, review sites, and one flagship content pillar.
• Track only a few metrics at first: CAC payback months and LTV; they steer almost every decision. (startups.com)

Roadmap at a glance (0–24 months)

• Months 0–1: Problem interviews, pre-sell 5–10 annuals; build clickable prototype; validate pricing.
• Months 2–4: Ship an MVP that solves a single workflow end-to-end; put buyers on a paid pilot.
• Months 5–9: Founder-led sales; build 2–3 integrations your ICP already uses; publish your first distribution-quality guide.
• Months 10–15: Harden onboarding, instrument analytics, pursue marketplace listings; hire first CS generalist.
• Months 16–24: Add one scalable channel (SEO or integrations marketplace), consider light compliance (SOC 2) if mid-market deals demand it. (drata.com)

1) Choose a painfully narrow problem and pre‑sell it

• Declare an ICP with budget and an urgent job. For example: “RevOps leads at 50–300‑employee SaaS companies who need reliable Salesforce→billing sync.”
• Run 10 discovery calls to map the current workflow, tools, and failure points; end each with a paid pilot ask (discount for early access, fixed start date).
• Pre‑selling is a proven path. ConvertKit’s founder documented turning a stalled side project into meaningful MRR by selling one creator at a time and doing unscalable outreach. (nathanbarry.com)

Questions to ask in those calls

• “What’s broken in your current process? What have you already tried?”
• “If I fixed only X and Y in two weeks, would you pay $Z to start next month?”
• “Who signs? What security/IT review blocks a purchase here?”

2) Build the thinnest possible product to deliver one outcome

Recommended starter stack (cheap, fast, proven):

• Frontend/hosting: Vercel Pro for collaborative previews and instant deploys. (vercel.com)
• Database/auth/file storage: Supabase Pro (predictable entry price with usage add‑ons). (supabase.com)
• Product analytics: PostHog or Mixpanel (pick one; instrument activation and retention events on day one). [Add whichever you choose later; this line is guidance, not a claim.]

Architecture rule of thumb

• One core table per primary object your user manipulates.
• One “events” table (or analytics SDK) for activation, aha moment, and retained usage.
• One background worker queue. Keep the scope brutally small until paying users demand more.

3) Pick a billing model you can actually operate

There are two sane paths for a bootstrapped B2B SaaS:

• Stripe Billing: You operate payments and remain the merchant of record (you own tax registrations, filings, chargebacks). Pay‑as‑you‑go pricing is 0.7% of Billing volume; card processing (e.g., 2.9% + 30¢ in the U.S.) is separate. Subscription plan tiers exist for predictable monthly pricing. (stripe.com)
• Merchant of Record (MoR): Outsource payments, global taxes, and some billing support to a provider. Lemon Squeezy lists 5% + $0.50 per transaction and acts as MoR; Paddle markets an all‑inclusive MoR fee, commonly shown as 5% + $0.50. (lemonsqueezy.com)

Stripe vs MoR: quick comparison

Option	Who files/remits taxes	Typical published fees	You should choose it if
Stripe Billing	You	0.7% of Billing volume + processing (e.g., 2.9% + $0.30 for cards in US)	You want maximum control over checkout, already do business in a handful of countries, or your buyers demand custom quotes/terms. (stripe.com)
Lemon Squeezy (MoR)	Provider	5% + $0.50 per transaction	You want to sell globally fast with minimal tax ops; your ACV supports the MoR take-rate. (lemonsqueezy.com)
Paddle (MoR)	Provider	Paddle publicly positions an all‑in fee commonly referenced as 5% + $0.50	Similar to Lemon Squeezy; also strong for desktop/in‑app software sellers. Confirm current commercial terms with Paddle. (paddle.com)

Pricing checklist

• Start simple: good/better/best tiers or per‑seat. Add usage‑based components once you see clear variable value (e.g., events, messages, credits). Industry data shows rising adoption of usage‑based and hybrid pricing; don’t force it from day one. (techcrunch.com)
• Model fees early: at $49/mo, a $0.50 fixed MoR fee is ~1% absolute margin drag before the percentage cut. At $499/mo it’s negligible; at $9/mo it dominates.
• Annualize cash: offer 10–20% off for annual prepay to reduce CAC payback months (see the CAC payback section below). (startups.com)

4) Founder‑led sales that actually convert

Tools that are simple and affordable:

• Lead data and sequencing: Lemlist (email sequencing with enrichment add‑ons) or Instantly (cold email at volume). Use their cheapest tier until you prove reply‑to‑demo conversion. (lemlist.com)

Cold email template you can steal Subject: Quick win for {Company}’s {team}

Hi {First}, We help {ICP} cut {pain} from {current workflow} by {short how}. It takes one week to pilot and we’ve seen {specific result} for companies like {credible peer}. If I send a 3‑minute Loom walking through {Company}’s setup and where we slot in, would you watch it?

If yes, I’ll send it over and we can decide if a 15‑minute call is worth scheduling.

Best, {You}

Make the list by hand. 25 perfect targets beats 500 generic ones. In replies, book to a call within minutes, not hours; speed wins.

5) Integrations as a distribution channel

Integrations create pull when your product appears where buyers already work:

• Slack App Directory: free to list; follow Slack’s review guidelines and distribution checklist. (api.slack.com)
• Microsoft Teams Store: publish through Microsoft AppSource; adhere to Teams Store validation guidelines. (learn.microsoft.com)
• HubSpot App Marketplace: meet listing and updated certification requirements announced in 2026. (developers.hubspot.com)
• Salesforce AppExchange: expect a security review; Salesforce documents an initial $2,700 USD fee for paid apps and a 4–6 week review timeline. Free apps have the fee waived. Plan for the review up front. (partners.salesforce.com)

Practical tip: Start with 1–2 integrations your first 10 customers already use, then earn the marketplace listing once you have a few reference installs.

6) Launch moments that compound

• Product Hunt: it’s still useful for early awareness if you have a clear one‑line promise, a short demo video, and a maker’s first comment ready. Use Product Hunt’s official launch guide and checklist pages. (producthunt.com)
• Review sites: create free vendor profiles on G2 and let your first 25 customers leave reviews; upgrade only if you see real pipeline from the platform. (G2’s FY26 pricing guide documents a Free tier.) (sell.g2.com)

7) Onboarding and activation

• Kill time‑to‑first‑value: default to sample data and a single CTA.
• Don’t over‑engineer tours; in most products, the fewer steps and the more user‑initiated the better. Instrument activation so you can A/B test specifics in context rather than guessing.
• Add one lifecycle email: an activation nudge triggered by “signed up but didn’t complete setup in 24h.”

8) The only two financial metrics you need at first

• CAC payback period (months): how long it takes gross profit from a new customer to cover CAC. Formula: CAC ÷ monthly gross profit per customer. Under 12 months is excellent; 12–18 months is healthy. (startups.com)
• LTV (lifetime value): a simple and widely used model is LTV = ARPA × Gross Margin ÷ Customer Churn Rate. This is directionally useful for pricing and acquisition spend. (chartmogul.com)

Example

• If ARPA is $200/mo, gross margin 80%, monthly logo churn 3%, then LTV ≈ $200 × 0.8 ÷ 0.03 = ~$5,333.
• If your fully loaded CAC is $2,500, gross margin per month is $160, payback ≈ $2,500 ÷ $160 ≈ 15.6 months.

9) Security and compliance (only when the deal needs it)

Enterprise and some mid‑market buyers will ask for a SOC 2 report. You don’t need it on day one, but if it repeatedly blocks deals, plan for it. Drata’s own Type 2 guide cites typical audit fees for small to midsize companies of $12,000–$20,000, with larger organizations much higher. Expect 6–12 months total timeline to be safely through a Type 2. (drata.com)

What to do now

• Maintain a one‑page security overview (data flow, hosting regions, encryption, sub‑processors, backup/restore RPO/RTO, contact).
• Add SSO/SAML and audit logging toggles in your roadmap once mid‑market requests start landing.

10) A lightweight analytics setup

• Track: sign‑up source, activation event, weekly active teams, and expansion signals (additional seats, integrations connected).
• Review weekly: activation rate, conversion to paid, and reasons for loss/churn.

11) Pricing you can explain to a CFO

• Keep pricing inputs observable: seats, connected accounts, documents processed, GB stored.
• Publish a monthly price; offer annual prepay discount; write an honest “which plan should I choose?” explainer.
• If usage is core (events, API calls), tie it to value and cap surprises with budgets/alerts. Adoption of usage and hybrid models has increased in recent years; it works when value scales with use. (techcrunch.com)

12) Set up a founders.page as your public proof and contact hub

• What to include: all products you’ve shipped (even small tools), live links, a 60‑second demo video, milestones (first 10 customers, first integration, first enterprise logo), your GitHub activity, and a “Book a call” link (Calendly or similar). This gives prospects a single link that proves momentum, not just promises.
• How you’ll use it: link it in cold emails, your marketplace listings, and your email signature; add it to review site profiles and your docs footer.
• Why it helps: buyers vet founders as much as products in early stage B2B; a clean public page with your work and milestones increases reply rates and trust.

Take 3 minutes to create your free founders.page and add it to your next five outbound emails.

13) Your first distribution flywheel

• Outbound → reference calls: Close your first 5–10 with founder‑led outreach; ask each new customer for a 90‑day results debrief.
• Integration → marketplace: Build one integration your first cohort begged for; ship the listing after you have 3–5 happy installs. Slack/Teams/HubSpot docs above make expectations clear, and Salesforce documents the security review fee and timeline. (api.slack.com)
• Content → compounding demand: Publish a definitive how‑to for your ICP’s core workflow using your tool in context. One great guide beats ten listicles.

14) Core stack you can afford from day one

• Hosting and DB: Vercel + Supabase Pro $25/mo org plan to start, with usage‑based add‑ons as you grow. Supabase documents the Pro plan and how billing and overages work; check current limits and credits. (supabase.com)
• Billing: Stripe Billing if you’re comfortable owning tax/regional complexity; else a Merchant of Record (LSQ or Paddle) if you want speed to global sales and built‑in tax management. Fees linked above. (stripe.com)
• Sales: Lemlist or Instantly at entry tier until you see repeatable reply→demo→close. (lemlist.com)

15) Examples that prove bootstrapping works

• Mailchimp: bootstrapped since 2001; acquired by Intuit in 2021 for about $12B in cash and stock. (axios.com)
• Basecamp/37signals: privately held, bootstrapped, shipping since 2004. (basecamp.com)
• Ahrefs: profitable and “without a dollar of outside funding.” (ahrefs.com)

16) Templates to copy

Positioning one‑liner

• For {ICP} who struggle with {pain}, {Product} is a {category} that {primary outcome}. Unlike {status quo/competitor}, it {differentiator tied to your architecture or workflow}.

Pricing explainer (short)

• Starter ($X/mo): For teams piloting one workflow. Up to N seats, A integration, B reports.
• Growth ($Y/mo): For teams rolling out to a department. Up to N seats, A+B integrations, SSO, priority support.
• Annual plan: two months free; budgets and usage alerts included.

Changelog cadence

• Every Friday: what shipped; every month: what’s next; always include a short Loom.

17) When to add process and people

• First CS hire when you can no longer do onboarding and support within normal working hours.
• First SDR when you can hand them a list, a script, and a calendar that routinely turns replies into meetings.
• First PM when you’re repeatedly choosing between sales‑driven asks and foundational quality/scale work.

Further reading on founders.page

• If you’re still choosing your path, read [What is bootstrapped SaaS? Definition, examples, playbook] (founders.page). It contrasts VC and bootstrapped trade‑offs.
• Once you have a personal proof hub, consider a directory or two from [Best Founder Directories of 2026: 9 Compared]. These can drive warm discovery when the fit is right.
• Still solo? Shortlist options from [Best platforms to find a co‑founder in 2026].

Final checklist before you ship

• Ten interviews with clear, priced pains; two buyers pre‑committed.
• A working path to first value in <15 minutes with sample data.
• A price you can say out loud without explanation.
• Stripe or MoR wired; invoices tested; dunning emails turned on. (stripe.com)
• One integration your cohort asked for, documented.
• A founders.page link in your email signature and marketplace profiles, with a 60‑second demo video.

If you do just these, you’ll have a real B2B SaaS, not a demo. Keep it narrow, keep it paid, and build distribution into the product itself.