SaaS archetypes: the 22 proven product shapes, what each one is built around, and how naming yours tells you exactly what to validate before building.
Almost every SaaS idea is one of 22 proven archetypes — a marketplace, a CRM, a booking tool, a job board — and naming yours is the fastest shortcut in validation: it tells you what to build, who pays, and which risky assumption to test first. Your idea feels unique. Its shape almost never is.
Here is the full list of 22, how to find yours in one sentence, and why "my idea doesn't fit any of these" is a warning sign, not a badge of genius.
Why "what shape is my idea?" beats "is my idea new?"
First-time founders burn months worrying about originality. Buyers don't pay for originality — they pay for a problem solved. And under the surface, software products repeat: 80-90% of any SaaS is the same foundation — accounts, teams, payments, permissions, notifications — the same 18 systems every product needs. What actually differs between a CRM and a job board is a small set of core objects: what things the product stores, and what users do to them.
That small set is the archetype. Get it named early and two things happen: you stop designing from a blank page, and you inherit decades of evidence about how products of that shape make money.
The 22 SaaS archetypes
Each archetype below is defined by what it's built around — the core objects at the heart of its database:
| Archetype | Built around |
|---|---|
| Analytics | Data sources, events, dashboards |
| Community | Channels, posts, replies and votes |
| Content platform | Content items, categories and tags, versions |
| CRM | Contacts, deals, activities, automations |
| Dating / matching | Profiles, matches, conversations, safety tools |
| Directory | Listings, categories, reviews, claims |
| E-commerce | Products, variants, carts, orders, shipping |
| Events | Events, tickets, RSVPs |
| Food delivery | Restaurants, menus, orders, drivers |
| HR | Employees, job openings, candidates, onboarding |
| Inventory | Products, warehouses and stock, stock movements, purchase orders |
| Invoicing | Clients, invoices, recurring invoices, payments |
| Job board | Job posts, companies, applications, job alerts |
| Marketplace | Listings, transactions, reviews, messages |
| Newsletter | Posts, subscribers, editions |
| Portfolio | Projects, testimonials, contact submissions |
| Project management | Projects, tasks, project members |
| Q&A platform | Questions, answers, votes, reputation |
| Reviews | Review subjects, criteria, reviews, comparisons |
| Service booking | Services, availability, bookings |
| Social network | Profiles, posts, interactions, trending |
| Wiki | Pages, revisions, links |
Read the right-hand column slowly. A CRM is contacts, deals, and activities — everything else is decoration. A marketplace is listings, transactions, reviews, and messages. Twenty-two shapes, each a handful of objects. That's the whole secret.
How to find yours in one sentence
Describe your idea as: who does what to what thing. The thing gives it away.
"Freelance accountants send recurring bills to clients" — the thing is an invoice. Invoicing archetype. "HR managers post openings and screen applicants" — job posts and applications. Job board. "Independent coaches let clients grab a slot in their week" — availability and bookings. Service booking. "Vintage watch collectors buy and sell from each other" — listings and transactions between users. Marketplace.
If your idea seems to span two archetypes — a community with a job board, a directory with bookings — you're probably right, and there's a simple tiebreak: the archetype that carries the money is your real product. Build that one first; the other is a feature you add later.
What your archetype tells you to validate
This is why the exercise belongs in validation, not just architecture. Each shape has a known risky assumption, and it should be the first thing you test:
- Marketplaces, job boards, dating, food delivery live or die on two sides showing up. Your riskiest assumption isn't the product — it's whether you can bring supply and demand to the same place.
- Newsletters, content platforms, communities live or die on retention. Anyone can get a signup; the question is whether people come back next week.
- CRMs, invoicing, inventory, project management live or die on switching. Your buyer already manages this somehow — usually in spreadsheets. The test is whether the pain is bad enough to change habits.
- Booking, directories, reviews live or die on trust and liveness — empty calendars and stale listings kill them.
Name the archetype, and the first customer conversation writes itself. That conversation — not the code — is the actual work of validating a business idea.
You start 80% done, not from zero
Here's the practical payoff for a non-technical founder building with AI. Because every archetype shares the same 18-system foundation, and the archetype itself is a handful of well-understood core objects, you are never designing software from scratch. You're assembling a proven foundation — the pattern behind my own platform, which runs to 679 tables and 2M+ lines of code — and adding the thin layer that is genuinely yours: your niche, your workflow, your distribution.
Built from zero, that foundation takes 6-12 months. Assembled from proven patterns, weeks. The archetype isn't a limit on your ambition. It's the reason a solo founder can now ship what used to take a team.
Frequently asked questions
What if my idea doesn't fit any archetype?
Look again — it's usually a hybrid of two, and the one that carries the money is your product. If it genuinely matches nothing on the list, treat that as a red flag to investigate, not proof of brilliance: shapes that have never worked usually haven't worked for a reason. Double down on validation before writing a line of code.
Is it bad that my idea isn't original?
No — it's evidence. A proven archetype means proven willingness to pay. You don't compete on shape; you compete on niche, depth, and distribution: not "a CRM", but the CRM for one specific profession whose workflow you know better than anyone.
Which archetypes are easiest for a first-time solopreneur?
The ones with one paying side and few core objects: invoicing (clients, invoices, payments), service booking (services, availability, bookings), newsletter (posts, subscribers, editions), portfolio. Two-sided shapes — marketplaces, job boards, food delivery — are the hardest solo starts, because you must win two audiences at once.
Does the archetype change how I validate?
Completely. It names your riskiest assumption: two-sided shapes must prove both sides show up, content shapes must prove people return, workflow tools must prove buyers will leave their spreadsheets. Test that assumption first — before building anything.