# Prospera

> A sales CRM where the pipeline is the home screen and every deal carries its next move — Pipedrive-class, without the per-seat bill.

Source page: https://saascode.ai/products/prospera
Machine-readable record: https://saascode.ai/products/prospera.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $129 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Prospera is a sales CRM for a small-to-midsize business-to-business team: a visual kanban deal pipeline, contacts and companies, an activity timeline across all of them, and email sequences.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/prospera — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://prospera.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

2 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Salesperson** (`member`) — `user@demo.com` / `demo123`
  Works the pipeline: deals, activities and saved views.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every organisation, plans and settings.

Or open a role directly: https://saascode.ai/demo/prospera?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, manager, member, super_admin
- **tables: 66** — distinct CREATE TABLE statements across every applied migration
- **migrations: 58** — .sql files in supabase/migrations
- **page modules: 85** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 118,157** — lines of code (comments and blank lines excluded) across 867 TypeScript files (107,656) and 70 SQL files (10,501); node_modules and .next excluded
- **api route files: 199** — files named route.ts under src/app/api
- **http operations: 282** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 66 tables, 121 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.1 · built 2026-07-12

## Complete capability inventory

16 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Pipeline & contacts

- **Pipeline kanban + multiple pipelines** — A kanban board of deals by stage, dragged between columns. Not a dashboard of charts — the board is where the work happens, and a salesperson opening the CRM should land on their deals.
- **Contacts & companies** — People and the organizations they belong to, linked, each carrying its own history.
- **Polymorphic activities + tasks** *(seller-authored)* — Calls, emails, meetings, notes and tasks attach to whatever they concern — a deal, a contact, a company — and surface as one chronological timeline wherever it is relevant, so picking up an account from a colleague does not mean opening four records.
- **Deal-rotting alerts** — Deals that have gone quiet raise an alert after a configurable period without activity.
- **Import / export (Data Bridge)** — Contacts, companies and deals import from CSV, and export the same way.
- **Embeddable lead-capture forms** — Embeddable forms that create contacts and deals directly from a website. Included on every tier.

### Sequences & the copilot

- **Email templates** *(seller-authored)* — Reusable message templates sent from inside the CRM against the contacts already in it, so the outreach a team repeats does not get retyped and quietly drift from person to person.
- **Built-in reports/dashboards** — Built-in reports and dashboards on every tier — pipeline value, stage conversion, activity volume.
- **Email sequences + reply-stop** — Multi-step outreach cadences, sent from the CRM against the deals and contacts already in it.
- **Email tracking (click-primary)** *(seller-authored)* — Records opens and clicks against the deal the message belongs to, with clicks treated as the meaningful signal. It answers whether the message reached someone rather than whether it was sent.
- **Saved views (personal + shared)** — Saved views are filters kept and named, personal or shared. A manager shares a view to define what the team looks at — and, given the visibility model, a shared view is also how a rep is granted sight of records outside their own book.
- **Custom properties** *(seller-authored)* — Adds the fields a particular business actually sells on — a licence number, a renewal date, a territory — to contacts, companies and deals, so the CRM matches the operation instead of the operation bending to the CRM.
- **CRM AI assistant (grounded)** *(seller-authored)* — Answers questions grounded strictly on the team's own CRM data. Where the record holds no answer it declines rather than producing a plausible one, which is the difference between a useful assistant and a confident liar.
- **Lead scoring (rules + AI)** *(seller-authored)* — Scores leads by rules and by model, so a rep working a long list knows which twenty to call first. Ordering the list is the part that gets skipped when the list is long, and skipping it is what makes the list feel hopeless.
- **Custom report builder** *(seller-authored)* — Builds reports beyond the shipped set, so the question a particular sales operation cares about gets answered inside the CRM rather than in an exported spreadsheet that is stale the next morning.
- **Next-action copilot (differentiator)** — Grounded on the team's own CRM data. It surfaces the next concrete action on a deal — who to contact, about what, and why now — using the deal's own history rather than general sales advice.

## What each system gives the operator

*stated.*

- **Pipeline & contacts** — A salesperson opens the CRM and sees the work, not a dashboard about the work.
- **Sequences & the copilot** — The next move on a deal is proposed from that deal's own history.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Monday morning starts with a decision already made about who to call.

A CRM full of accurate data still does not tell a salesperson what to do on Monday morning. It reports what happened. The judgement about which of forty open deals deserves the next hour stays with the person, gets made in a hurry, and defaults to whoever emailed most recently. Deals that need attention but are quiet fall out of view entirely — not because anyone decided to drop them, but because nothing surfaced them and there was no time to go looking.

### Picking up a colleague's account does not start with an archaeology exercise.

Context in a CRM is usually filed by object rather than by relationship. The call is on the contact, the email is on the deal, the meeting note is somewhere a colleague put it, and reconstructing what has actually happened with an account means opening four records and holding the sequence in your head. Anyone picking up a deal from a colleague pays that cost in full, and the first customer conversation afterwards shows it.

### Deals are dragged between stages, not updated through a form.

CRMs get abandoned at data entry. If moving a deal forward means opening a record, changing a dropdown and saving, then the board is a reporting obligation rather than a tool — and it gets updated on Friday afternoon, from memory, badly. Everything downstream inherits that: the forecast is a week old, the manager's view is fiction, and the argument about whether the CRM is worth it starts again.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security. The three-tier visibility policy is enforced there, so it is not a swappable component.
- **Email provider** (required for sequences) — Outreach and notification delivery. The CRM itself works without it.
- **An AI provider key** (required for the copilot) — Everything else is unaffected.
- **A cron caller** (required) — Deal-rotting checks and sequence steps run on a schedule. Without it sequences do not advance and stale deals raise no alert.
- **A payment provider** (required to charge) — Configured by the operator, not hardwired.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 118,157 lines across the application and its database, 66 tables defined by 58 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Prospera demo runs the delivered release (v1.0.1), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 2 of them: Salesperson, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 85 page modules and 282 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Email provider, An AI provider key, A cron caller, A payment provider. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 58 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $129?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Prospera vs Pipedrive: Subscribing to a CRM or Launching One You Own](https://saascode.ai/inside/prospera-vs-pipedrive-subscription-or-owned-crm.md)
- [Prospera: a pipeline-first sales CRM that keeps every deal moving](https://saascode.ai/inside/prospera-pipeline-first-sales-crm-keeps-deals-moving.md)
- [Sales CRM Options, Organized by Where the Next Action Comes From](https://saascode.ai/inside/sales-crm-options-by-next-action-source.md)
- [What it took to build a sales CRM in one night](https://saascode.ai/inside/prospera-build-story.md)

## Links

- Catalog page: https://saascode.ai/products/prospera
- Product record: https://saascode.ai/inside/products/prospera
- Live demo: https://prospera.saascode.ai
- Every product: https://saascode.ai/llms.txt