One person, no sales calls
Every stage has a result that should stop you
Recurring job
A need that comes back every month
Reachable buyer
Found and sold without a call
Price math
The customer count your price needs
Support budget
Minutes per customer you can carry
First subscriber
A payment before the build
Smallest build
The one workflow they paid for
To start a SaaS business alone, pick a job your buyer has every month, name where you can reach that buyer without a sales call, and do the price math before you write code. Then sell the first subscription before you build, ship the one workflow it paid for, and budget support before the customer count turns it into a job. Each of the 7 stages below has a result that should stop you, and meeting it early is the cheap way to meet it.
The stages, and the result that should stop you at each
A SaaS business is software someone pays for again and again, so every stage asks the same question from a different side: will this buyer keep paying, and can one person keep delivering? The table is the whole path on one screen. Each row links the guide that covers that stage in depth.
| Stage | What you decide | Stop when | In detail |
|---|---|---|---|
| Pick a recurring job | A job the buyer has every week or month, not once | The problem is solved once and the buyer has no reason to renew | One-time problem or subscription |
| Name a buyer you can reach | Who pays, and where you can reach them without a sales call | You cannot name a place where these buyers already gather | Selling SaaS without sales calls |
| Do the price math | The price, and how many customers it needs to reach your target | The customer count is more than your channel can bring in | How many customers you need |
| Budget the support | How many support minutes per customer you can afford | Support at your target customer count is already a job | Will it be support-heavy |
| Check what you depend on | Which platform, API or AI provider the product leans on | One provider's rule change would end the product | Platform risk |
| Sell before you build | The costly action that counts: a pre-order, a deposit, a paid pilot | The action has not arrived by the deadline you set in advance | Will people pay for it |
| Build the smallest version | The one workflow the first customers paid for | The scope keeps growing before anyone has used the first workflow | What to build first |
The price decides how many customers you have to find
Before any code, turn the goal into a customer count. The table holds one monthly revenue target, $5,000, and asks how many paying customers three prices need to reach it.
| Price per month | Customers needed |
|---|---|
| $9 | 556 |
| $29 | 173 |
| $99 | 51 |
At $9 a month you need 556 customers; at $99, 51. The cheap price does not make the business easier. It multiplies the people you have to find, onboard and support without a sales team. The pricing guide for small SaaS covers how to choose the number, and the customers-needed tool runs your own.
Budget support before you have customers
Support grows with every customer you add, so it is the cost that decides whether one person can keep the business. Estimate the minutes each customer needs in a month and multiply by the count from the price table. If the answer is already a job at your target, lower the minutes before you launch: self-serve setup, written answers and a narrower promise. The support-heavy guide shows how to estimate it.
Sell without calls, or decide now that you will make them
Selling without sales calls means the page, the price, a short demo and the onboarding have to carry the whole sale in writing. That works for a buyer who already understands the problem and can try the product alone. It fails for a buyer who needs a meeting to trust you, to get approval or to see how the product fits their setup.
Decide which one you are building for before the first line of code. If the promise needs a meeting to be understood, the positioning is not self-serve yet. The guide to selling SaaS without sales calls shows what the page and the trial have to do instead.
Check what the product leans on
A Shopify app, a browser extension or a thin layer over one AI model can reach buyers quickly, because a platform brought them. The same platform can change its fees, its rules or its own features. In our own Discovery runs, the screen every candidate idea passes through, platform dependence was named in 19.8% of the ideas the gate stopped: 140 of 706, measured on 2026-09-06.
That share describes how our gate behaves, not how often platform businesses fail. The practical test is simpler: name the export path your customers keep if the platform turns against you, and the way you can reach them that the platform does not control. If you cannot name either, the platform-risk guide explains what to change.
Get the first subscriber before the code
The first subscriber is the first real evidence. A waitlist signup shows interest; only a payment shows the price works. Offer the outcome with the real price, ask for a pre-order, a deposit or a paid pilot, and set the number and the deadline before you ask. If the payment does not come, you learned it for the cost of a page instead of a product. The guide on whether people will pay compares what each signal proves.
The business side is smaller than it looks
A few things have to exist before the first charge, and none of them needs a large budget:
- A way to take payment. A merchant of record sells on your behalf and handles sales tax and VAT in many countries. We sell WhittleOS that way, as one person.
- A legal form. Whether you need a company before the first charge depends on where you live. The LLC guide covers the US case; an accountant covers yours.
- Terms and a privacy policy. Customers and payment providers will ask for both.
If you already have the idea, check it against these stages before you build. If you do not have one yet, the free founder read starts from your time, skills and tolerance for calls instead of from a list.
Common questions
Can one person start a SaaS business?
Yes, if the product serves a recurring job, the buyer can be reached and sold without meetings, and support per customer stays small enough to carry at the customer count your price requires. Check all three before building.
Should I build the SaaS product before finding customers?
No. Offer the outcome at the real price and ask for a pre-order, deposit or paid pilot first. A payment answers whether the price works; a waitlist signup only shows interest.
Do I need a company before I charge for a SaaS product?
It depends on where you live. A merchant of record can handle payments and sales tax for you, and the legal form is a question for local rules and an accountant, not a reason to delay testing demand.
Read next
- Can your SaaS sell without demos or sales calls? →
- How many customers you need, and how many one person can carry →
- What to build first — and the case where you should not be asking yet →
- Micro SaaS ideas, each tied to a recorded problem and its source →
- What is SaaS? A one-person product from buyer to support →
- How to start a startup: the first month before a larger build →

