# How to Bootstrap a SaaS Without VC: A Step-by-Step Guide

> How to bootstrap a SaaS without funding: validate and pre-sell, build on free tiers, compare Stripe, Paddle and Lemon Squeezy fees, and follow a 90-day plan.

- Canonical: https://zeroraised.com/blog/how-to-bootstrap-a-saas
- Published: 2026-11-04T09:27:18Z
- Author: ZeroRaised Team (https://zeroraised.com/blog/authors/zeroraised)
- Publisher: ZeroRaised (https://zeroraised.com/)
- Section: Growth
- Tags: bootstrapping, saas, revenue, launch-guide

To bootstrap a SaaS, pick a problem that people already pay to solve. Pre-sell a solution before you write much code, ship the smallest version someone will pay for, run it on free tiers, and charge from the first day. Win your first ten customers by hand, then commit to one distribution channel. Fund the gap with revenue, savings, consulting or grants, and keep your job until revenue covers your living costs.

This guide walks through each step in order. Where we quote a price, fee or limit, it comes from the vendor's own page, checked on 4 Nov 2026, and the advice in between is ours.

## TL;DR

- **Validate with money, not compliments.** Fathom says it "started with a tweet and a screenshot", after which "hundreds of people were offering to pay us for the real thing" ([Fathom](https://usefathom.com/about)). A paid pre-order or pilot is stronger proof than a waitlist.
- **Your first stack can cost almost nothing, but read the limits.** Cloudflare Workers allows 100,000 free requests per day ([Cloudflare](https://developers.cloudflare.com/workers/platform/pricing/)), and Neon's free plan does not pause for inactivity ([Neon](https://neon.com/pricing)). Vercel's Hobby plan, by contrast, is "for personal, non-commercial use" ([Vercel](https://vercel.com/pricing)).
- **Merchants of record cost more and take tax off your plate.** Paddle charges 5% + 50¢ per checkout transaction ([Paddle](https://www.paddle.com/pricing)). Lemon Squeezy charges 5% + 50¢, plus 1.5% for non-US and 0.5% for subscription payments ([Lemon Squeezy fees](https://docs.lemonsqueezy.com/help/getting-started/fees)). Stripe's processing fees are lower, but you remain the seller ([Stripe](https://stripe.com/pricing)).
- **Expect a slow start.** Plausible says it took 324 days to reach its first $400 MRR, then reached $1M ARR in June 2022 as "a completely independent, self-funded and bootstrapped team of four" ([Plausible](https://plausible.io/blog/open-source-saas)).
- **Quit the day job at ramen profitability, not before.** Paul Graham defines it as making "just enough to pay the founders' living expenses" ([Paul Graham](https://paulgraham.com/ramenprofitable.html)).

**Disclosure:** ZeroRaised publishes this guide and is a launch site for bootstrapped products. Facts come from the linked sources as checked on 4 Nov 2026; ZeroRaised has no commercial relationship with the companies named.

**Bootstrapping a SaaS** means building and growing a subscription software business with customer revenue and the founders' own money, without selling equity to venture capital investors.

## What does bootstrapping a SaaS actually involve?

A funded startup spends investor money to find customers. A bootstrapped one has to find customers to stay alive. That one difference changes almost every decision: what you build first, how you price, which tools you choose and when you stop doing the work you are paid for.

It also changes what counts as success. Plausible's about page says the company is "self-funded and profitable, with no outside investors and no plans to sell", that it crossed $1 million in annual recurring revenue in 2022, and that it is now "a team of 10" ([Plausible](https://plausible.io/about)). 37signals, the company behind Basecamp, writes: "We have no investors, no board of directors, no eyes on an exit" ([37signals](https://37signals.com/01)). Neither is a unicorn, and neither needs to be.

If you are still choosing between the two paths, our [bootstrapping vs venture capital comparison](https://zeroraised.com/blog/bootstrapping-vs-venture-capital) sets out the trade-offs. The rest of this guide assumes you have chosen to bootstrap.

## Step 1: Pick a problem people already pay to solve

The easiest SaaS to bootstrap replaces something that customers already spend money or staff time on. An existing budget is the strongest signal you will get before writing code. It means the pain is real, someone has authority to pay, and you are asking them to switch rather than to start spending.

Look for these patterns:

- **A spreadsheet or manual process run by a paid employee.** Hours of wages are a budget, even if no software line exists yet.
- **An incumbent tool that customers complain about.** Plausible pitched itself as a simpler, privacy-focused alternative to Google Analytics, and its 2021 post is titled "How we bootstrapped our Google Analytics alternative to $500k ARR" ([Plausible](https://plausible.io/blog/bootstrapping-saas)). An incumbent with unhappy users proves the market exists.
- **A narrow job in a niche you know.** If you have worked in an industry, you already know its workarounds and its buyers' language.

Avoid buyers who expect free software, year-long procurement cycles and ideas that need network effects before anyone gets value.

**Your test for this step:** write one sentence naming the customer, the job and what they pay today. "Accounting firms with 5 to 20 staff spend about two hours per client each month chasing documents by email." If you cannot fill in the last part, keep looking.

## Step 2: Validate and pre-sell before you build

Interviews tell you whether a problem exists. Only payment tells you whether your solution is worth money. Bootstrappers cannot afford to spend six months building something nobody buys, so move to a payment request as early as you can.

A practical sequence:

1. **Talk to 15 to 20 people in the target group.** Ask about the last time the problem happened, what they did and what it cost. Do not pitch. Our guide to [validating a SaaS idea before building](https://zeroraised.com/blog/how-to-validate-a-saas-idea-before-building) has question scripts.
2. **Write a one-page offer.** Who it is for, the outcome, the price, what is in version one and the delivery date.
3. **Ask for money.** Offer a discounted founding price, a paid pilot or a refundable pre-order. You do not need a website: Stripe says Payment Links let you "create a full payment page in just a few clicks and share the link with your customers, no code required" ([Stripe Payment Links](https://stripe.com/payments/payment-links)).
4. **Set a threshold in advance.** For example: "If five of my twenty interviewees pay a deposit within two weeks, I build it." Write it down before you start so you cannot move the goalposts.

Public demand works too. Fathom's about page says the product "started with a tweet and a screenshot" and that "soon hundreds of people were offering to pay us for the real thing" ([Fathom](https://usefathom.com/about)). Showing the product before it existed let its founders measure demand cheaply.

If nobody pays, that is a result, not a failure. Change the customer, the problem or the price and run the test again. It costs far less than building the wrong product.

## Step 3: Scope the smallest version someone will pay for

The minimum version of a bootstrapped SaaS is the smallest thing that delivers the outcome you pre-sold. It is not a prototype, and it is not version one of your roadmap.

Cut ruthlessly:

- **Keep:** the core job, sign-in, billing, one way to get data in, one way to get results out, and a support email address.
- **Defer:** team accounts, roles and permissions, integrations nobody has asked for, mobile apps, dark mode, a public API and admin dashboards (use your database console).
- **Fake behind the scenes:** onboarding, data imports and reports can be done by hand for the first customers. If ten customers need help, do it yourself and learn what to automate.

Give yourself a fixed time box, typically four to eight weeks of evenings and weekends for a solo founder with a job. If the scope does not fit, cut scope, not the deadline. Plausible's founder built the product alone at first: the about page says "Uku Taht started Plausible in December 2018, building it alone" and that "paid subscriptions launched in 2019" ([Plausible](https://plausible.io/about)).

## Step 4: Build on a cheap stack, and read the free tier limits

Free tiers mean a SaaS can run for close to nothing until it has paying customers. The catch is in the terms: commercial-use rules, pausing, usage caps and what happens when you exceed them. This table shows what each vendor's own page said on 4 Nov 2026.

| Need | Option and free allowance | Limit that matters | First paid step |
|---|---|---|---|
| Frontend hosting | [Vercel](https://vercel.com/pricing) Hobby: $0, 1M function invocations and 100 GB fast data transfer per month | "Personal, non-commercial use" only, and Hobby cannot buy extra usage | Pro at $20 per month, with $20 of included credit |
| Serverless backend | [Cloudflare Workers](https://developers.cloudflare.com/workers/platform/pricing/) Free: 100,000 requests per day | 10 ms of CPU time per invocation | $5 per month minimum, 10 million requests included |
| Postgres and auth | [Supabase](https://supabase.com/pricing) Free: 500 MB database, 50,000 MAUs, 1 GB file storage | Free projects pause after 1 week of inactivity; 2 active projects | Pro from $25 per month |
| Postgres | [Neon](https://neon.com/pricing) Free: 100 projects, 1 GB storage per project, 100 CU-hours per project | No inactivity pause, but compute suspends if you use up CU-hours or 5 GB egress | Launch plan, pay as you go; Neon estimates about $15 per month for a small database |
| Authentication | [Clerk](https://clerk.com/pricing) Hobby: 50,000 monthly retained users per app | 7-day session lifetime, up to 3 social connections | Pro at $25 per month, or $20 billed annually |
| Transactional email | [Resend](https://resend.com/pricing) Free: 3,000 emails per month | 100 emails per day | Pro at $20 per month for 50,000 emails |
| Product analytics | [PostHog](https://posthog.com/pricing.md) Free: 1M events, 5,000 session recordings, 1M feature flag requests, 1,500 survey responses per month | Allowance resets each month | Usage-based above the free amount |
| Background server | [Render](https://render.com/docs/free) Free web service: 750 instance hours per month | Spins down after 15 minutes without traffic and takes about a minute to wake | Paid instance (check Render's pricing page) |

Three practical rules follow from those limits:

1. **Check commercial-use terms before you charge anyone.** Vercel's FAQ says Hobby is for personal, non-commercial use, so a paying SaaS on Vercel needs Pro.
2. **Avoid anything that sleeps for your customer-facing path.** A Render free service that takes about a minute to spin up, or a Supabase project paused after a week of no activity, is fine for a staging site and bad for a paying customer's first impression.
3. **Pick boring, well-documented tools you already know.** The cheapest stack is the one you can ship and debug alone at 11pm.

A realistic early budget, then, is a domain, one paid hosting plan once you charge customers, and transaction fees. Our [free tiers dataset](https://zeroraised.com/data/free-tiers) compares more hosting and database plans on commercial use, and ZeroRaised's [guide to free startup perks without VC](https://zeroraised.com/blog/free-startup-perks-without-vc) covers credit programs that do not need an investor.

## Step 5: Take payments: Stripe or a merchant of record?

You need to decide early who legally sells your software. With a payment processor such as Stripe, you are the seller. You collect the money, and you are responsible for registering for, charging and filing sales tax, VAT and GST wherever you are required to. With a **merchant of record** (MoR) such as Paddle, Lemon Squeezy or Polar, the provider resells your product to the customer and takes on that tax liability, for a higher fee.

Here is what each provider's pricing page said on 4 Nov 2026.

| Provider | Model | Headline fee | Extras to budget for |
|---|---|---|---|
| [Stripe](https://stripe.com/pricing) (UK page) | Processor: you are the seller | 1.5% + 20p for standard UK cards; 3.15% + 20p for international cards | +2% for currency conversion; £20 per dispute received; [Billing](https://stripe.com/billing/pricing) 0.7% of billing volume; [Tax](https://stripe.com/tax/pricing) 0.5% per transaction (no-code) where registered |
| [Stripe Managed Payments](https://support.stripe.com/questions/managed-payments-pricing) | MoR run by Stripe | 3.5% per successful transaction | Charged on top of normal Stripe processing fees; Billing fees apply separately for subscriptions |
| [Paddle](https://www.paddle.com/pricing) | MoR | 5% + 50¢ per checkout transaction | No monthly fees; bespoke pricing for products under $10 |
| [Lemon Squeezy](https://docs.lemonsqueezy.com/help/getting-started/fees) | MoR | 5% + 50¢ | +1.5% for non-US transactions, +1.5% for PayPal, +0.5% for subscription payments; 1% per Stripe payout to non-US bank accounts |
| [Polar](https://polar.sh/) | MoR | 5% + 50¢ on the free Starter plan | Lower rates on paid plans, from 3.80% + 40¢ on Pro at $20 per month |

Stripe's own pages were served in pounds sterling from our location, so the card rates above are UK rates. US founders should open [Stripe's pricing page](https://stripe.com/pricing) from their own country to see local rates.

### What the fees look like on a real subscription

**Illustrative example.** Take a £20 or $20 monthly subscription. The numbers below apply only the fees listed above and ignore currency conversion and disputes.

- **Stripe, UK seller, standard UK card, Stripe Billing and Stripe Tax:** 1.5% + 20p (50p) plus 0.7% Billing (14p) plus 0.5% Tax (10p) comes to about **74p, or 3.7%**. With an international card at 3.15% + 20p, the total is about **£1.07, or 5.4%**. You still need to register and file tax returns yourself.
- **Paddle:** 5% + 50¢ on $20 is **$1.50, or 7.5%**.
- **Lemon Squeezy, US customer, subscription:** 5% + 0.5% + 50¢ on $20 is **$1.60, or 8%**. A non-US customer adds 1.5%, making **$1.90, or 9.5%**.

The fixed 50¢ hurts most on cheap plans. On a $5 plan, Paddle's fee is 75¢, or 15%. That is one reason to avoid very low prices, covered in the next step. You can test your own prices with our [payment fee calculator](https://zeroraised.com/tools/payment-fee-calculator).

Stripe makes its own comparison on its Managed Payments pricing page, saying other merchants of record have an "all-in effective cost" that "typically ranges from 7-9%" ([Stripe](https://support.stripe.com/questions/managed-payments-pricing)). Treat that as a competitor's claim, although it roughly matches the illustrative maths above.

### Which should a solo founder choose?

Our recommendation: **if you sell to consumers or small businesses in many countries and do not want to deal with tax registrations, start with a merchant of record.** The extra few per cent buys you hours of compliance work you would otherwise do yourself. **If you sell mostly in your own country, or to large companies that expect proper invoices from a local supplier, Stripe is usually cheaper.** Read our [merchant of record vs payment processor guide](https://zeroraised.com/blog/merchant-of-record-vs-payment-processor) for the tax detail and our guide on [how to sell software online](https://zeroraised.com/blog/how-to-sell-software-online) for the full checkout setup.

Two developments matter in 2026:

- **Stripe now offers its own merchant of record.** Stripe's docs say Managed Payments is for selling "digital products such as SaaS, software, and digital content or downloads" and excludes physical goods, professional services and live events ([Stripe docs](https://docs.stripe.com/payments/managed-payments)). It is available to businesses in a list of supported countries, including the US, Canada, the UK, most of the EU, Australia, Japan and Singapore, after an eligibility review ([Stripe eligibility](https://docs.stripe.com/payments/managed-payments/eligibility)).
- **Lemon Squeezy is moving its users towards it.** In a January 2026 update, Lemon Squeezy's CEO acknowledged "slower support responses and less frequent product updates" while the team built Stripe Managed Payments, and said: "Our goal is to provide Lemon Squeezy users an easy way to migrate to Stripe Managed Payments" ([Lemon Squeezy](https://www.lemonsqueezy.com/blog/2026-update)). The post gives no shutdown date. If you choose Lemon Squeezy today, expect a migration later.

Whichever you pick, keep your customer list in your own database, so the provider is never your only record of who pays you.

### Do you need a company first?

Often not on day one, especially with a merchant of record, but local rules vary, so ask an accountant before revenue starts. For a US company, Stripe Atlas charges a US$500 one-time setup fee, then US$100 a year ([Stripe Atlas](https://stripe.com/atlas)).

## Step 6: Set a price that can support you

Bootstrapped founders tend to underprice. Low prices feel safe, but they need far more customers to reach the same income, and fixed fees take a larger share of each payment.

Our pricing rules for a first SaaS:

- **Anchor on the value or the alternative.** If your tool saves an accountant two hours a month, compare the price with two hours of their billable rate, not with other apps.
- **Start with two or three plans.** One plan is fine at first; three is the most a new customer can compare quickly.
- **Charge monthly and offer an annual option.** Annual prepayment gives a bootstrapper cash up front, which is runway you do not have to borrow.
- **Avoid prices so low that fees dominate.** As the example above shows, a $5 plan loses 15% to a 5% + 50¢ fee.
- **Raise prices for new customers as the product improves.** Keep early customers on their founding price as a thank-you.

Our full guide on [how to price a SaaS product](https://zeroraised.com/blog/how-to-price-a-saas-product) covers value metrics, tiers and when to raise prices.

## Step 7: Win your first 10 customers by hand

The first ten customers will not come from a launch, SEO or ads. They come from you, one conversation at a time. That is fine: at this stage you need learning more than scale.

Work through these sources in order:

1. **Everyone who paid or nearly paid in Step 2.** Deliver what you promised, on time.
2. **Your interviewees who did not pay.** Show them the working product and ask again.
3. **Your network.** Former colleagues, clients and people in your industry. Send personal messages, not a newsletter blast.
4. **Communities where your customers already gather.** Forums, Slack and Discord groups, subreddits and industry associations. Help first, follow the rules of each space, and mention your product only where it answers the question.
5. **Direct outreach.** A short, specific email to a named person about a problem you can see they have. Our [founder-led sales guide](https://zeroraised.com/blog/founder-led-sales-strategy) has templates.

Plausible's early history shows what this looks like in practice. Its founders write that they "launched the public beta on Indie Hackers", that "all the early users came from these updates", and that they had "60 active beta users" by May 2019 ([Plausible](https://plausible.io/blog/open-source-saas)). Their first paying subscriber arrived on 14 May 2019 ([Plausible](https://plausible.io/blog/bootstrapping-saas)).

For each of the first ten customers, do the onboarding yourself on a call. Watch where they get stuck. Ask what nearly stopped them buying. That list becomes your next month of product work.

## Step 8: Launch on directories and communities

A launch is a burst of attention, not a growth strategy. It helps with early users, feedback and backlinks, and it is free. Plan it once the product works and you have handled a few customers.

Know the rules of the main venues before you post:

- **Show HN.** Hacker News says Show HN "is for something you've made that other people can play with". It asks makers to "make it easy for users to try your thing out, ideally without barriers such as signups or emails", and says: "Don't post landing pages or fundraisers" ([Hacker News](https://news.ycombinator.com/showhn.html)). Have a demo or free tier ready.
- **Product Hunt.** Product Hunt says it is free to use, that company accounts are prohibited, and that you "cannot ask people directly to upvote your product" ([Product Hunt](https://www.producthunt.com/launch)). It suggests 12:01 am Pacific Time for makers planning ahead, and recommends posting your own product rather than finding a hunter ([Product Hunt help](https://help.producthunt.com/en/articles/479557-how-to-post-a-product)).
- **Smaller directories and launch sites.** These send less traffic each, but they add up, and many accept submissions on any day. Our list of [where to launch a SaaS](https://zeroraised.com/blog/where-to-launch-a-saas) compares them, and the [launch sites directory](https://zeroraised.com/launch-sites) lists current options.

Stagger launches over a few weeks rather than firing everything on one day. You can fix problems between launches and reply properly to every comment.

## Step 9: Commit to one distribution channel

After the first launches, pick one channel and work it every week for at least three months. Splitting a few hours a week across six channels usually produces nothing measurable in any of them.

Choose based on where your buyers look for solutions:

| Channel | Works best when | Weekly commitment (our estimate) | Typical time to results |
|---|---|---|---|
| Content and SEO | Buyers search for the problem by name | 1 to 2 useful articles | Months |
| Building in public | Your buyers are other makers or developers | Several posts with real numbers | Weeks to months |
| Cold outreach | Few, identifiable, high-value B2B buyers | 20 to 50 personal emails | Weeks |
| Communities | Buyers gather in specific forums or groups | Several helpful answers | Weeks |
| Integrations and marketplaces | Your tool plugs into a platform buyers already use | One-off build, then listing upkeep | Weeks after approval |

Plausible chose content. Its founders say they have "a $0 paid advertising budget" and no affiliate program ([Plausible](https://plausible.io/blog/bootstrapping-saas)), and the about page says the company has "never spent a cent on advertising, affiliates or paid endorsements" ([Plausible](https://plausible.io/about)). One April 2020 post brought "more than 25,000 people" to the site on the day it was published ([Plausible](https://plausible.io/blog/open-source-saas)). That came after more than a year of steady writing.

For more options that cost time rather than money, see our list of [free marketing channels for bootstrapped makers](https://zeroraised.com/blog/free-marketing-channels-for-bootstrapped-makers).

## Step 10: Fund the runway without VC

A bootstrapped SaaS still needs money: for your rent while revenue grows, and for the tools and fees above. These are the realistic sources, roughly in the order we would use them.

### Customer revenue

The best money is from customers. Annual plans, paid pilots and setup fees all bring cash forward. A paid onboarding package for business customers can cover months of hosting.

### Savings

Most bootstrappers spend some. Be honest about how much. Plausible's founders write that they were "down more than $50,000 in personal savings" at one point in building the company ([Plausible](https://plausible.io/blog/open-source-saas)). Before you start, set a number you are prepared to lose and a date by which revenue must reach a set level.

### A day job or part-time work

Keeping a job is the most common way to fund a SaaS. It is slower, but it removes the pressure that pushes founders into bad decisions such as cheap pricing or rushed launches.

### Consulting and freelancing

Selling your skills by the hour can fund the product and keep you close to customers if you consult in the same niche. Paul Graham warns that sliding into consulting is the main danger for a ramen-profitable startup, because it can quietly replace the product ([Paul Graham](https://paulgraham.com/ramenprofitable.html)). Cap consulting at a fixed number of hours a week and protect product time in your calendar.

### Grants

Grants are non-dilutive, but they are competitive and often limited to research-heavy products.

- **United States:** SBIR describes itself as providing "equity free funding through federal agencies to American small businesses", funded through 11 participating federal agencies ([SBIR](https://www.sbir.gov/about)). Applicants must be a for-profit US company with fewer than 500 employees, owned and controlled by US citizens or permanent residents. Phase I typically runs 6 to 12 months with awards of $50,000 to $323,000 ([SBIR](https://www.sbir.gov/apply)).
- **United Kingdom:** Innovate UK describes itself as "the UK's innovation agency". Its open competitions on 4 Nov 2026 were sector-specific, including a UK and Netherlands quantum technology call for a share of up to £1.5 million ([Innovate UK](https://www.ukri.org/councils/innovate-uk/)). A general business SaaS may not fit current calls, so check the list before planning around one.

Grants take time to apply for and to arrive. Treat them as a bonus, not a runway plan. Our guide to [ways to fund a product without venture capital](https://zeroraised.com/blog/ways-to-fund-a-product-without-venture-capital) covers revenue-based financing, crowdfunding and other non-equity options in more depth.

## Step 11: Track five numbers every week

Bootstrappers need fewer metrics than funded startups, but they need to check them every week. Put these five in a spreadsheet each Monday:

1. **Monthly recurring revenue (MRR).** Total monthly subscription revenue, with annual plans divided by 12.
2. **New paying customers this week.** And where each came from.
3. **Cancelled customers this week.** And the reason each one gave. Our guide on [reducing SaaS churn](https://zeroraised.com/blog/how-to-reduce-saas-churn) explains how to collect reasons.
4. **Activation.** The share of new sign-ups who complete the core job at least once. Define the event precisely.
5. **Cash and runway.** Money in the bank, monthly costs, and months left at the current rate.

Add one input metric: the hours you spent on distribution this week. If that number is near zero, MRR will follow.

Plausible's published milestones show why patience matters. The company reported $64 MRR in May 2019, $403 MRR in February 2020, $4,062 in August 2020, $11,303 in January 2021 and $42,624 in October 2021 ([Plausible](https://plausible.io/blog/open-source-saas)). The early numbers looked tiny, and the curve only bent upwards after more than a year.

Some companies publish these numbers, as Simple Analytics does on its public [open dashboard](https://dashboard.simpleanalytics.com/open). Publishing yours is optional; tracking them is not.

## Step 12: Decide when to quit the day job

Paul Graham's July 2009 essay defines the milestone: "Ramen profitable means a startup makes just enough to pay the founders' living expenses." He argues that "the main importance of ramen profitability is that it buys you time", and that once there, "survival is the default, instead of dying" ([Paul Graham](https://paulgraham.com/ramenprofitable.html)). Note that he wrote it for startups that may raise later. For a bootstrapper it is simply the point where the business can pay you.

**Illustrative example.** Say your personal living costs are £2,500 a month and your plan costs £20 a month. Using the Stripe example above, you keep roughly £19.26 per UK customer before tax on your income. You need about 130 paying customers to cover living costs, plus a buffer for churn and tax. At a £60 plan, the same target needs about 43 customers. Run your own numbers in our [ramen profitability calculator](https://zeroraised.com/tools/ramen-profitability-calculator).

Our suggested rule for leaving a job: quit when **either** MRR has covered your living costs for three months in a row, **or** you have at least 12 months of personal runway in savings and MRR has grown for six consecutive months. Quitting with no revenue and a vague hope is the riskiest version of bootstrapping.

## What do real bootstrapped SaaS companies show?

These examples use only what each company or founder says on its own pages. For more, see our collection of [bootstrapped SaaS examples](https://zeroraised.com/blog/bootstrapped-saas-examples).

| Company | What it says about funding | Published numbers | Lesson |
|---|---|---|---|
| [Plausible Analytics](https://plausible.io/about) | "Self-funded and profitable, with no outside investors" | $1M ARR crossed in 2022; 22,000+ paying subscribers; team of 10 | Slow early growth, then content compounding |
| [Fathom Analytics](https://usefathom.com/about) | "Customer-funded" and "proudly bootstrapped (zero investors)" | Started in 2018; "thousands" of paying customers | Pre-sell with a public demo |
| [Pieter Levels](https://levels.io) | "All bootstrapped without funding and just me coding everything on my laptop" | Business revenue "about $200K-$250K/mo" ([levels.io](https://levels.io/passed-10m-revenue-investment-gains), Sep 2026) | Several small products, run solo |
| [37signals (Basecamp)](https://37signals.com/01) | "We have no investors, no board of directors, no eyes on an exit" | Says it has been "profitable every year" ([37signals](https://37signals.com/04)) | Profit as a design constraint |

Two points stand out. First, none of these companies grew fast at the start; Basecamp's founder writes that about a year after release it was generating more revenue than their web design business ([Basecamp](https://basecamp.com/about)), so for its first year the product grew alongside an existing service business. Second, each one kept a small team and a long horizon: Plausible's founders wrote for more than a year before their content paid off, and Levels runs several products on his own.

## The 90-day plan to bootstrap a SaaS

This plan assumes a solo founder with a job and about 10 to 15 hours a week. Stretch it if you have less time; do not skip the payment steps.

| Weeks | Focus | Output | Done when |
|---|---|---|---|
| 1 to 2 | Problem and customer | List of 30 target customers; 15 interviews booked | You can write the one-sentence problem with what buyers pay today |
| 3 to 4 | Validation and pre-sale | One-page offer; Stripe Payment Link or MoR checkout | At least 3 to 5 deposits or paid pilots, or a decision to change the idea |
| 5 to 8 | Smallest paid version | Core job, sign-in, billing, support email on a commercial-use host | Pre-sale customers are using it |
| 9 to 10 | First 10 customers | Personal onboarding calls; fixes from their feedback | 10 paying customers, or 10 serious trials with a clear blocker list |
| 11 | Launch | Show HN, Product Hunt and 5 to 10 directories, staggered | Every comment answered; sign-up sources tracked |
| 12 to 13 | One channel and review | Channel chosen and first weekly output shipped; metrics sheet set up | You have 4 weeks of data and a written keep, change or stop decision |

At day 90 you will have one of three outcomes: paying customers and a channel that shows signs of life, which means keep going; interest but no payment, which means change the price, customer or offer; or neither, which means stop and pick the next problem. All three are useful, and none needed an investor.

## What mistakes sink bootstrapped SaaS founders?

1. **Building for months before asking for money.** The longer you build in private, the more it hurts to learn nobody will pay. Pre-sell first.
2. **Pricing too low.** Cheap plans need many customers and lose a bigger share to fixed fees. A 50¢ fee is 10% of a $5 plan before the percentage part.
3. **Running a commercial product on a non-commercial plan.** Vercel's Hobby terms exclude commercial use ([Vercel](https://vercel.com/pricing)). Upgrade before you charge.
4. **Ignoring sales tax because "the processor handles it".** A processor does not file your returns. Stripe Tax calculates and collects only "where you're registered to collect taxes" ([Stripe Tax](https://stripe.com/tax/pricing)). If that sounds like too much, use a merchant of record.
5. **Chasing every channel at once.** Pick one, measure it for three months, then decide.
6. **Treating a launch day as the strategy.** Launches bring a spike. Steady customers come from the channel you work every week.
7. **Quitting the day job too early.** Use ramen profitability or a written runway plan, not optimism.
8. **Letting consulting take over.** If paid client work fills every week, the product stalls. Cap hours and protect product time.
9. **Depending on one provider with no exit plan.** Lemon Squeezy's own update says users are being offered a path to Stripe Managed Payments ([Lemon Squeezy](https://www.lemonsqueezy.com/blog/2026-update)). Keep your customer data exportable.

## Checklist: bootstrap a SaaS from zero

**Before you build**

- [ ] One-sentence problem statement including what customers pay today
- [ ] 15 to 20 customer interviews completed and notes saved
- [ ] One-page offer with price and delivery date
- [ ] Payment link or MoR checkout created
- [ ] Pre-set validation threshold written down, and met

**Building**

- [ ] Scope cut to the core job, sign-in, billing and support
- [ ] Host that allows commercial use chosen
- [ ] Free tier limits noted: pausing, caps, overage behaviour
- [ ] Payment model chosen: Stripe (you handle tax) or merchant of record
- [ ] Pricing set with two or three plans and an annual option
- [ ] Customer data stored in your own database

**Getting customers**

- [ ] First 10 customers onboarded personally
- [ ] Reasons for buying and nearly not buying recorded
- [ ] Launch posts prepared for Show HN, Product Hunt and directories
- [ ] One distribution channel chosen with a weekly target

**Running the business**

- [ ] Weekly sheet: MRR, new customers, cancellations, activation, cash
- [ ] Personal runway number and deadline written down
- [ ] Ramen profitability target calculated
- [ ] Consulting hours capped, if any
- [ ] Accountant consulted on company structure and tax

## Where ZeroRaised fits

ZeroRaised is a launch directory for products built without institutional VC or accelerator equity, which makes it one of the places to list a bootstrapped SaaS during Step 8. You can [submit your product](https://zeroraised.com/submit) for free. If you want our latest guides on pricing, launching and funding without investors, [join the ZeroRaised newsletter](https://zeroraised.com/newsletter).

A listing is one small launch among many. We do not promise traffic, sign-ups or revenue; the steps above are what produce those.

## Sources

- [Fathom Analytics about page](https://usefathom.com/about), checked 4 Nov 2026
- [Plausible Analytics about page](https://plausible.io/about), checked 4 Nov 2026
- [Plausible: How we built a $1M ARR open source SaaS](https://plausible.io/blog/open-source-saas), checked 4 Nov 2026
- [Plausible: How we bootstrapped our Google Analytics alternative to $500k ARR](https://plausible.io/blog/bootstrapping-saas), checked 4 Nov 2026
- [37signals: no investors](https://37signals.com/01), checked 4 Nov 2026
- [37signals: profitable every year](https://37signals.com/04), checked 4 Nov 2026
- [Basecamp about page](https://basecamp.com/about), checked 4 Nov 2026
- [Pieter Levels homepage](https://levels.io), checked 4 Nov 2026
- [Pieter Levels: passed $10M revenue and investment gains](https://levels.io/passed-10m-revenue-investment-gains), checked 4 Nov 2026
- [Simple Analytics open dashboard](https://dashboard.simpleanalytics.com/open), checked 4 Nov 2026
- [Stripe pricing](https://stripe.com/pricing), checked 4 Nov 2026
- [Stripe Billing pricing](https://stripe.com/billing/pricing), checked 4 Nov 2026
- [Stripe Tax pricing](https://stripe.com/tax/pricing), checked 4 Nov 2026
- [Stripe Managed Payments pricing](https://support.stripe.com/questions/managed-payments-pricing), checked 4 Nov 2026
- [Stripe Managed Payments docs](https://docs.stripe.com/payments/managed-payments), checked 4 Nov 2026
- [Stripe Managed Payments eligibility](https://docs.stripe.com/payments/managed-payments/eligibility), checked 4 Nov 2026
- [Stripe Payment Links](https://stripe.com/payments/payment-links), checked 4 Nov 2026
- [Stripe Atlas](https://stripe.com/atlas), checked 4 Nov 2026
- [Paddle pricing](https://www.paddle.com/pricing), checked 4 Nov 2026
- [Lemon Squeezy pricing](https://www.lemonsqueezy.com/pricing), checked 4 Nov 2026
- [Lemon Squeezy fees](https://docs.lemonsqueezy.com/help/getting-started/fees), checked 4 Nov 2026
- [Lemon Squeezy 2026 update](https://www.lemonsqueezy.com/blog/2026-update), checked 4 Nov 2026
- [Polar](https://polar.sh/), checked 4 Nov 2026
- [Vercel pricing](https://vercel.com/pricing), checked 4 Nov 2026
- [Cloudflare Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/), checked 4 Nov 2026
- [Supabase pricing](https://supabase.com/pricing), checked 4 Nov 2026
- [Neon pricing](https://neon.com/pricing), checked 4 Nov 2026
- [Clerk pricing](https://clerk.com/pricing), checked 4 Nov 2026
- [Resend pricing](https://resend.com/pricing), checked 4 Nov 2026
- [PostHog pricing](https://posthog.com/pricing.md), checked 4 Nov 2026
- [Render free instances](https://render.com/docs/free), checked 4 Nov 2026
- [Paul Graham: Ramen Profitable](https://paulgraham.com/ramenprofitable.html), checked 4 Nov 2026
- [SBIR about](https://www.sbir.gov/about), checked 4 Nov 2026
- [SBIR apply](https://www.sbir.gov/apply), checked 4 Nov 2026
- [Innovate UK](https://www.ukri.org/councils/innovate-uk/), checked 4 Nov 2026
- [Hacker News Show HN guidelines](https://news.ycombinator.com/showhn.html), checked 4 Nov 2026
- [Product Hunt launch guide](https://www.producthunt.com/launch), checked 4 Nov 2026
- [Product Hunt help: how to post a product](https://help.producthunt.com/en/articles/479557-how-to-post-a-product), checked 4 Nov 2026

## Frequently asked questions

### Can you bootstrap a SaaS with no money at all?

Close to it. Free plans from Cloudflare Workers, Supabase, Neon, Clerk, Resend and PostHog cover a first version, and merchants of record such as Paddle and Lemon Squeezy charge per transaction with no monthly fee. Expect to pay for a domain and, once you charge customers, for a hosting plan that allows commercial use.

### Should a bootstrapped SaaS use Stripe or a merchant of record?

A merchant of record such as Paddle (5% + 50¢) or Lemon Squeezy (5% + 50¢, plus 1.5% for non-US and 0.5% for subscription payments) sells to the customer and handles sales tax and VAT. Stripe's processing fees are lower, but you are the seller and must register and file taxes yourself, unless you use Stripe Managed Payments, which adds 3.5% per transaction.

### How long does it take to bootstrap a SaaS to profitability?

There is no standard timeline. Plausible's founders say it took 324 days to reach their first $400 in monthly recurring revenue, and the company crossed $1 million in annual recurring revenue in 2022, about three years after paid plans launched in 2019.

### When should I quit my day job to work on my SaaS?

A sound rule is to wait until the product is ramen profitable, which Paul Graham defines as making just enough to pay the founders' living expenses, or until savings cover a runway you have written down. Quitting before customers pay is the riskiest version.

### Are there grants for bootstrapped software founders?

Some. In the US, SBIR offers equity-free federal funding to small businesses through 11 agencies, with Phase I awards typically $50,000 to $323,000. In the UK, Innovate UK runs funding competitions, although its current ones are aimed at specific deep tech sectors.