SaaS examples: 13 real products and how each one charges
SaaS (software as a service) is software you use in a browser or app and pay for on a recurring basis instead of installing it. Familiar examples are Slack, Notion, Figma and Calendly. Micro SaaS examples are smaller products built by one person or a tiny team for a narrow need, such as Plausible, Fathom, Carrd, Buttondown and Tally. Most charge per user, per usage volume, or by tier.
What counts as a SaaS product?
A SaaS product is software that the vendor runs and you reach over the internet. You do not install it or maintain a server. You sign up, use it, and pay on a recurring schedule, usually monthly or yearly. That recurring payment is the difference from selling a one-off licence, and it is why SaaS builders think so much about retention: the revenue only continues while customers keep finding the product useful.
A micro SaaS is the same model at a smaller scale. One person or a very small team builds it, it solves a narrow problem for a specific group, and it stays small on purpose. There is no official size threshold. The term is a convenient label for products a solo builder can realistically ship and run, which is why this page splits the examples into two groups.
Every price and plan below comes from the product’s own pricing page, checked in October 2026. Plans change, and some pages show different currencies by country, so open the link before you rely on a number. Revenue is left out unless the company published it itself, in which case the source is linked.
| Model | How it charges | Example on this page |
|---|---|---|
| Per seat | Each person who uses the product costs a fixed amount each month | Slack, Linear, Figma, Calendly |
| Usage volume | The price steps up with how much you use it (pageviews, tasks, credits) | Zapier, Plausible, Fathom, Bannerbear |
| Audience size | The price follows the number of subscribers or contacts | Buttondown |
| Flat annual fee | One low price for a year, with a free version to start | Carrd |
| Free with paid extras | The core is free; branding removal, domains or limits are the paid part | Tally, Basecamp |
What are the best-known SaaS examples?
These seven are products most people have met. They are large, with big teams, so you will not copy them. They are worth studying for the shape of the business: what the free plan gives away and what the paid plan locks.
01 Slack
Team messaging organised into channels, with search and integrations with other tools.
- Pricing model
- Per user each month, with a free plan to start
- What the free plan limits
- Free workspaces delete data after one year; paid plans keep it by default (per Slack’s pricing page)
- Lesson
- A free plan with a limit on history makes people upgrade once the tool matters
Slack shows the classic per-seat arrangement: the team grows, the bill grows. The free tier is real enough to adopt, but the history limit means value builds up exactly where the paywall is. For a small product, the same idea works with any limit that gets tighter as usage grows.
Smallest version of this idea: a channel-based chat for one narrow group, such as a single neighbourhood association or a club. Extension: per-group billing instead of per-user.
02 Notion
A workspace of pages and databases for notes, documents and project tracking.
- Pricing model
- Per seat each month; Free, Plus, Business and Enterprise plans
- Discount
- Paying yearly saves up to 20%, per the pricing page
- Lesson
- A flexible blank-page product spreads by templates and word of mouth
Notion sells a toolbox rather than a single workflow, which is hard to copy at small scale. What a solo builder can borrow is the packaging: a free plan for personal use that makes individuals into advocates, and team features behind the paid plans.
Smallest version: one database template for a single job, such as a freelancer’s client tracker. Extension: sharing with a client view.
03 Figma
A browser-based design tool where several people edit the same file at once.
- Pricing model
- Per seat, billed annually or monthly, with a free plan
- Seat types
- Full seats and Collab seats; on a paid plan, others can view and comment on files without extra seats, per the pricing page
- Lesson
- Cheap or free seats for people who only look make sharing easy and keep the paying core small
Figma’s split between people who create and people who only comment is a pricing idea worth copying. The reviewers, clients and developers who view files become the audience that brings in the next paying designer.
Smallest version: a tool where one person creates and many can view without an account. Extension: a paid seat only for people who edit.
04 Calendly
A scheduling link that lets other people book time on your calendar without email back-and-forth.
- Pricing model
- Per seat, with an always-free plan
- Who pays
- The host needs a seat; invitees do not, per the pricing page
- Lesson
- Every invitee sees the product, so each booking is also a small advertisement
Calendly’s growth mechanism is built into the product: the person receiving a link experiences the tool without signing up. When the user’s customer is also the next prospect, you get distribution without a marketing budget.
Smallest version: a booking page for one profession, such as driving instructors or tutors. Extension: payments at booking.
05 Linear
Issue tracking and project planning for software teams, known for speed and a narrow focus.
- Pricing model
- Per user each month, billed yearly or monthly; a free plan exists
- Plan structure
- A free tier, then paid tiers adding features, per the pricing page
- Lesson
- Opinionated software for one kind of team can stand next to broad tools
Linear’s approach is the opposite of Notion’s: a tool with firm opinions about how software teams plan work. It is a reminder that a narrower product, for a specific team type, can compete with something much more general.
Smallest version: a tracker that handles one workflow for a very small team, such as bug reports from a single app. Extension: import from the tool people use now.
06 Zapier
Connects web apps so an event in one triggers an action in another, with no code.
- Pricing model
- Usage tiers measured in tasks each month, with a free plan
- Tier shape
- Plans step up through task bands from 100 per month upwards, per the pricing page
- Lesson
- Charging by usage ties the bill to the value the customer receives
Task-based pricing means a customer who automates one small thing pays little and a customer who runs their business on it pays more. It scales with value, though it also means customers watch their usage closely.
Smallest version: a connector between two specific tools for one audience. Extension: a template library of ready-made connections.
07 Basecamp
Project management and team communication aimed at small companies and clients.
- Pricing model
- Subscription plans with a 30-day trial and one free project
- Free offer
- One project free for personal use; the free plan is limited to one project, per the pricing page
- Lesson
- A free tier can be as small as a single project and still let people judge the product
Basecamp shows that a free plan does not have to be generous to work. One project is enough to learn whether the tool fits your habits. For a small builder that is useful: a limit costs you little and still lets people test the product.
Smallest version: a single-purpose project board for one kind of client work. Extension: a paid plan when someone needs a second project.
What are some micro SaaS examples?
These products are smaller or more focused, and each does one job. They are the closer reference if you are a solo builder. Looking for a problem of this shape? The board holds many that fit: a changelog your users actually read and a phone number for your side project are both posted there as small, single-purpose tools.
01 Plausible Analytics
Lightweight, privacy-friendly website analytics, positioned as an alternative to Google Analytics.
- Pricing model
- Tiers by monthly pageviews, with a 30-day free trial and no card required
- Published figures
- Plausible states on its about page that it passed USD 1 million in annual recurring revenue in 2022 and is self-funded with no outside investors
- Lesson
- A narrow rival to a giant, plus open-source code and a public dashboard, builds trust
Plausible is open source and publishes the analytics of its own site at plausible.io/plausible.io. It is a good template for how a narrow product takes on a giant on one trait, here privacy, and it is also one of the few where the company itself publishes how it is funded.
Smallest version: a script and a single dashboard that answers three questions about a site. Extension: goals and referrer reports.
02 Fathom Analytics
Privacy-focused website analytics, sold as a GDPR-compliant alternative to Google Analytics.
- Pricing model
- Plans by monthly pageviews across all your sites
- Entry price
- Plans start at USD 15 a month for up to 100,000 pageviews, with a 7-day free trial, as of October 2026
- Lesson
- Every plan has the same features; only volume differs
Fathom keeps pricing plain: pick your traffic, get everything. That removes a whole class of feature-gating decisions and keeps the pricing page short. It also means support questions are about usage, not plan limits.
First version: one script tag and a page that counts visits. Extension: email reports.
03 Carrd
A builder for simple, responsive one-page sites.
- Pricing model
- Free to start; a paid Pro plan billed yearly
- Price
- Pro is listed at USD 19 a year as of October 2026, per the Carrd Pro page
- Lesson
- A very low annual price can work when the product is narrow and easy to explain
Carrd’s paid features are the ones people need when a page becomes serious: custom domains, more sites, removing the “Made with Carrd” mark and forms. The free plan lets someone finish a whole page before they ever pay.
First version: one page type, such as a link-in-bio or a waitlist. Extension: forms and custom domains as the paid layer.
04 Buttondown
Newsletter software for sending email to a subscriber list.
- Pricing model
- Priced by audience size; you pay for active subscribers
- Free tier
- Nothing for the first 100 subscribers, per the pricing page
- Lesson
- A free allowance sized to a beginner’s audience grows with the customer
Buttondown charges for active subscribers rather than every contact, which feels fairer to the writer and lines the bill up with real sending. The free allowance fits someone starting a newsletter, so customers arrive early and stay as they grow.
First version: a sign-up form plus a way to send one email to a list. Extension: paid subscriptions for readers.
05 Tally
A form builder where you type your questions and get a shareable form.
- Pricing model
- Free with unlimited forms and submissions; paid plans add branding control and more
- Paid extras
- Hiding branding and hosting forms on your own domain, per the pricing page
- Lesson
- A generous free plan plus paid white-labelling lets users spread the product for you
Tally gives away the core job and charges for polish: your own branding and domain. People who share forms publicly are the main source of new users, so the free tier doubles as marketing.
First version: a form with a few question types and an email on each response. Extension: logic jumps and a custom domain.
06 Bannerbear
An API that generates images and videos automatically from templates.
- Pricing model
- Credit-based plans; the trial starts with 30 API credits
- Entry
- Free trial with no credit card, then plans sized in API credits, per the pricing page
- Lesson
- A developer-facing API product sells by volume to a small, technical audience
Bannerbear is the shape of a product a solo developer can ship: a clear input (a template and data), a clear output (an image) and a price that follows usage. The audience finds it through the problem, not through brand.
First version: one endpoint that turns a title into a social card. Extension: a visual template editor.
What do these SaaS examples have in common?
- A free way in. Nearly every product here lets you try it without a card. A free plan, a trial or a free allowance removes the first objection.
- A price that follows value. Seats, pageviews, tasks, credits and subscribers are all ways to make the bill grow when the customer gets more out of the product.
- One clear job. Even broad products start from a single story: send a message, book a meeting, count visits.
- Growth built into use. Invitees see Calendly, form fillers see Tally, readers see Buttondown. The product spreads while it is used.
- A point of view. Plausible and Fathom stand for privacy, Linear for speed and focus, Carrd for simplicity.
Two small analytics companies, Plausible and Fathom, serve the same niche and charge by pageviews. A crowded niche is not a reason to stay out: each has its own tone and audience. Before you drop an idea because a competitor exists, read how that competitor charges and who it ignores. List three products in any category you like, write down each pricing model and one thing each leaves out, and that gap is where a new product starts.
The small products are the realistic model for a solo builder: one problem, one buyer, one price you can explain in a sentence.
How do you go from SaaS examples to your own product?
- Pick a narrow buyer. Write down who they are and what they do each week. The guide to picking your first SaaS idea helps with this step.
- Choose one job. Describe it as one sentence: “For [buyer] who [problem], this [does one thing].”
- Check that someone pays today. Look for spreadsheets, manual work or tools they use badly. Money already changing hands is the best sign.
- Pick a pricing model from the table above. The micro SaaS pricing guide walks through the choice.
- Build the smallest version. Use a prompt that states the user, the screens and the done-when check. The guide to building a SaaS covers the stack.
For raw material, read the micro SaaS ideas list or browse the ideas on the board. Each board idea has a generated build prompt you can copy into Claude Code, Cursor or Lovable. If you already have an idea you will never build, post it.
Frequently asked questions
What are examples of SaaS?
Slack, Notion, Figma, Calendly, Linear, Zapier and Basecamp are widely used SaaS products. Smaller examples include Plausible, Fathom, Carrd, Buttondown and Tally. All run on the vendor’s servers, are used through a browser or app, and charge on a recurring basis or by usage.
What are micro SaaS examples?
Fathom Analytics, Carrd, Buttondown, Tally and Bannerbear are micro SaaS examples: small products that do one job for a narrow audience. Plausible began the same way. There is no official definition, but one person or a tiny team can build and run each of them.
How do SaaS companies make money?
SaaS companies charge a subscription that renews monthly or yearly. The amount usually depends on seats, usage volume or audience size. Many also run a free plan to let people try the product, then charge for limits, extra features, branding control or higher volume.
What is the difference between SaaS and micro SaaS?
Micro SaaS is SaaS built and run by one person or a very small team for a narrow niche. It has the same recurring-revenue model as larger SaaS, but a smaller feature set, lower prices and a deliberately limited goal, so it can be maintained without a big team.
Can you build a SaaS product without coding?
You can build a first version without writing code yourself by describing it to an AI coding tool and testing what comes back. You still need to check the result carefully, protect user data and handle payments properly. Start with a very small product so you can verify all of it.
How much does a SaaS product cost to run?
Costs depend on the product, so no honest single figure exists. For a small product they are typically hosting, a database, email sending and a payment provider’s fees. List each line from the vendors’ own pricing pages before you set your price, and include your time.
Created with AI assistance and edited for this site. Examples are illustrative and do not represent customer research. About the publisher.