Learning Path
SaaS Validation and Pricing Path
A software business is a subscription business, and the mistake is building it before anyone has paid for it. This path teaches the SaaS discipline in order: what a SaaS is and is not, validation without building, micro-SaaS ideas, MVP scope, pricing models, and the first ten customers — won by hand, with the billing, tax and refund rules attached.
How this path works. Each lesson below is a short summary of the topic it links to, with an exercise that proves you can do the work. Work through them in order, do the exercise, and mark each lesson complete when you have read the guide and done the work. The two-question check under each lesson is for yourself — it is not scored and it is not a certificate. Your progress is stored only in your own browser, in local storage — no account, nothing sent to us. Completing this path gives you no certificate and no qualification, and it promises no income: the proof is the finished work from the capstone lesson, not a certificate.
What you will learn
- What a SaaS business is — and what it is not.
- Validate without building: ten interviews and a pre-payment test.
- Micro-SaaS ideas, and how to pick one honestly.
- MVP scope: what to build first, and what to cut.
- Pricing models, and the first ten customers by hand.
Your progress
0 of 6 lessons complete.
The lessons
Read each lesson summary, then open the full guide it links to. The summaries are written for this path — they do not repeat the guides, they prepare you for them.
Lesson 1: What a SaaS business is — and what it is not
SaaS means software as a service: a tool people pay to use every month, instead of buying once. The business is the subscription — recurring billing, keeping customers paying, supporting them when it breaks — and not the launch. A SaaS is also not an app idea, not a website, and not a one-off product: it is a promise repeated monthly, with the costs and the support load that go with it.
This lesson defines the model precisely: who pays, what they pay for, and what the business must do every month to keep them. You will learn why the first question about a SaaS is never what it does, but who pays for it monthly and why they keep paying — and why a tool nobody will subscribe to is a project, not a business.
Exercise: Describe one SaaS idea in one sentence: who pays monthly, for what, and why they keep paying.
Check yourself — two questions on this lesson
1. What is a SaaS business?
Software people pay to use every month — the business is the subscription.
2. What is a SaaS not?
Not an app idea or a one-off product — it is a monthly promise with support.
Lesson 2: Validate without building — 10 interviews + pre-payment test
The strongest validation for a software idea costs nothing and takes two weeks: ten interviews with people who have the problem, and a pre-payment test at the end. The interviews ask what the problem costs them now and what they have already tried; the pre-payment test asks the only question that cannot be faked — will you pay for this before it exists? A yes is validation. A no is the cheapest failure you will ever have.
This lesson runs both steps: what to ask in the interviews, what counts as a yes, and how to run the pre-payment test without taking money dishonestly — a refundable deposit, a founding price, a written delivery date. You will learn why building before this test is the most expensive way to discover nobody wants the product.
Exercise: List ten people with the problem you would interview, and the question each must answer.
Check yourself — two questions on this lesson
1. What are the two validation steps?
Ten interviews, then a pre-payment test.
2. Why is a pre-payment test decisive?
It is the only question that cannot be faked — money is the honest vote.
Lesson 3: Micro-SaaS ideas — and how to pick one honestly
A micro-SaaS is a small software business: one tool, one problem, a small team — often one person. The good ideas are boring and specific: a invoicing tool for one trade, a booking page for one kind of clinic, a report builder for one kind of shop. The bad ideas are big and vague: a platform for everyone, a tool that does everything. Honesty in picking means checking whether you can reach the customers, whether they pay for software already, and whether the problem is painful enough to pay for monthly.
This lesson picks your micro-SaaS idea with the honest test: is the problem real, is it painful, can you reach the people who have it, and do they already pay for tools? You will learn why a small idea with ten reachable customers beats a big idea with none, and why the idea you can sell by hand is the idea to build.
Exercise: Score three micro-SaaS ideas on problem, pain, reach and willingness to pay — and pick one.
Check yourself — two questions on this lesson
1. What is a micro-SaaS?
A small software business: one tool, one problem, often one person.
2. What is the honest picking test?
Is the problem real, painful, reachable, and already paid for?
Lesson 4: MVP scope — what to build first (and what to cut)
The minimum viable product is the smallest version that solves the core problem for real users — not the smallest version of your dream, and not a rough draft. Scope is the decision of what to build first and what to cut: the core job stays, the nice features wait, and the list of what you will not build is as important as the list of what you will. Every feature you cut is a week you get back.
This lesson scopes your MVP: the core job, the features that serve it, and the cut list — written down, so the scope cannot quietly grow. You will learn the rule that protects the build: if a feature does not serve the core job for the first ten customers, it waits. A small product that works beats a large one that never ships.
Exercise: Write your MVP scope: the core job, three features that serve it, and five that wait.
Check yourself — two questions on this lesson
1. What is an MVP?
The smallest version that solves the core problem for real users.
2. Why keep a cut list?
So scope cannot quietly grow — every feature cut is a week back.
Lesson 5: Pricing models — flat vs tiered vs per-seat vs usage vs freemium vs trial
Software pricing has five shapes, and the shape decides the business. Flat is one price for everyone; tiered splits features by price; per-seat charges by user; usage charges by what is consumed; freemium gives the base away and charges for more; a free trial gives everything for a set time, then asks for payment. Each shape fits a different product, and the wrong shape is the most expensive mistake a SaaS makes — a flat price on a product whose costs grow with use will lose money on its biggest customers.
This lesson compares the five models on your product: what each earns, what each costs to run, and the benchmarks problem — pricing benchmarks are published as tables with no source, so this path does not offer one as a fact. You will learn the beginner's rule: start with a simple flat or tiered monthly price, set from your costs and the value per customer, and change it with evidence, not with a table.
Exercise: Price your product as flat and as tiered, and write why one fits better.
Check yourself — two questions on this lesson
1. What are the five pricing models?
Flat, tiered, per-seat, usage, and freemium — plus a free trial.
2. Where should a beginner start?
A simple flat or tiered monthly price, set from costs and value.
Lesson 6: First 10 customers — by hand, then the billing, tax and refund rules
The first ten customers are found by hand, not by advertising: the people you interviewed, the businesses you audited, the ones who said yes to the pre-payment test. Hand-selling ten customers teaches you what the product must do and what it can cost, and ten paying customers are the proof that lets you build more. No marketing channel is needed for ten — and no marketing channel can replace them.
This lesson ends with the rules that surround the sale: billing that is clear about the monthly charge, tax that depends on where the customer is, and refund terms that promise only what you can honour. Never promise uptime or results you cannot deliver — the refund rule is the one customers remember. It is the capstone: a validation worksheet for one idea, with interview notes, a pre-payment result, and a kill or continue decision.
Exercise: Capstone: complete a validation worksheet for one idea — interviews, pre-payment test, score, and a kill or continue decision.
Check yourself — two questions on this lesson
1. How are the first ten customers found?
By hand — from the interviews and the pre-payment test.
2. What must billing and refunds promise?
Only what you can honour — never uptime or results you cannot deliver.
Try the tools
These free tools let you practise what the lessons describe — everything runs in your browser, and nothing you type is sent anywhere.
- Startup Cost Calculator — total the cost of starting the software
- Business Model Comparison — compare SaaS with other models
- Sales Target Calculator — work out how many customers the plan needs
Check what you learned
6 questions, all based on the lessons above. Answer them all, then check your score — each answer explains itself, so a wrong answer teaches as much as a right one. The quiz is practice, not a test: there is no pass mark and no certificate.
Answer all 6 questions, then check your score.
Download your notes
Download a plain-text summary of this path: the lesson list, which lessons you marked complete, and your quiz score. The file is generated on your device — nothing is uploaded.
Key terms in this path
The terms this path uses are defined in the Glossary, each with an example. If a lesson uses a word you do not know, look it up there first.
Frequently asked questions
Can I start a SaaS business without coding?
Yes, using no-code tools — and this path shows the validation first. But a SaaS is a subscription business, and the work is not the building: it is the validation, the pricing, and keeping customers paying.
What is an MVP?
The smallest version of the product that solves the core problem for real users. It is not a rough draft — it is the fewest features that deliver the result, with everything else cut.
How do I validate a SaaS idea?
Ten interviews with the people who have the problem, then a pre-payment test — if nobody will pay before it exists, the idea is not validated. The validation lessons show both steps.
What pricing model suits a beginner SaaS?
A simple flat or tiered monthly price, set from your costs and the value per customer. Usage pricing and freemium are harder to run well, and the pricing lesson compares all five honestly.
Do I need customers before I build?
Not all of them — but the first ten should be found by hand before the full build, because their payments and their problems decide what gets built. A product built in private is a guess.