# Build a CRM shaped like your pipeline, not someone else’s

> Describe your sales process and get a working CRM: contacts, deal stages, activity history, role-based access and a live URL. React and TypeScript you own.

Canonical: https://vibely.sh/use-cases/crm
Last updated: 2026-10-30

Most small teams do not outgrow their CRM — they outgrow the shape of it. The stages are wrong, half the fields are dead, and the part that actually matters lives in a side spreadsheet nobody else can see. A custom CRM is not a big build: it is contacts, a pipeline, activity history, and permissions. Vibely produces all four from a description, on a Postgres database via Supabase, deployed to a URL your team can open the same afternoon.

| Platform | Category | Stack | Plans |
| --- | --- | --- | --- |
| Web app | Internal tools | React, TypeScript, Supabase | [Free to start; database and sign-in from Lite](https://vibely.sh/pricing) |

- Included in the first build: Postgres and auth on Supabase, wired up for you
- Yours to keep: Row-level rules so reps see their accounts and managers see the team
- Deploys to a live URL — nothing for your team to install
- React and TypeScript you own, synced to GitHub on Lite, Pro and Business
- Change a stage or add a field by asking, not by filing a ticket
- Free plan, no credit card, unlimited projects

## Who this is for

This is for a team of two to twenty whose pipeline does not fit the template, and whose alternative today is a shared sheet with colour-coded rows. It also suits freelancers and agencies tracking clients, who want a client management app that matches how they work. If you need forecasting rollups across regions and a marketing automation suite, buy one — the argument here is fit and ownership, not feature count.

## Start with this prompt

Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.

```text
Build a CRM for a five-person sales team.

Screens: a pipeline board with the stages New, Qualified, Proposal, Won and Lost where I can drag a deal between columns; a contacts list with search and a filter by owner; and a contact detail page showing the company, deal value, and a timeline of notes and calls.

Data: companies, contacts, deals and notes in Supabase. Sign-in with email. A rep sees the deals they own; a manager sees everyone’s.

Start with about twenty realistic seed records so I can see it working.
```

## What the build actually consists of

### Screens that match the day

A pipeline board you can drag deals across, a contact record with the full activity history, and a list view with the filters your team argues about — search, owner, stage, last touched.

### A real database, not a sheet

Postgres on Supabase with contacts, companies, deals and notes as actual tables and relations, plus authentication and row-level rules so a rep sees their accounts and a manager sees the team’s.

### Live, and still yours

Deployed to a URL on the first build, and exportable to GitHub on Lite, Pro and Business whenever you want to continue in your own editor. Nothing about the data model is proprietary.

Built on: [The Supabase backend](https://vibely.sh/features/database), [One-click publishing](https://vibely.sh/features/publishing), [Code you own](https://vibely.sh/features/code), [Row-level security checks](https://vibely.sh/features/security)

## What you get

- A pipeline board with your stages, drag to move a deal
- Contact and company records with full activity history
- Notes and next steps attached to the record, not to someone’s inbox
- Sign-in with roles, so access is scoped rather than trusted
- A live URL, plus a GitHub repository you control

## What to build next

Once the first build lands, these are the prompts people send next.

1. Add a weekly pipeline summary screen with totals by stage and by owner.
2. Add an activity reminder: flag any deal with no note in the last fourteen days.
3. Import our existing contacts from a CSV upload.

## Connectors this build uses

[Supabase](https://vibely.sh/connectors/supabase), [GitHub](https://vibely.sh/connectors/github)

## FAQ

### Can I move our existing CRM data in?

Yes — ask for a CSV import screen and describe your columns. Because the data lands in your own Supabase Postgres database, you can also load it with SQL or the Supabase dashboard directly, and export it the same way whenever you want.

### What happens when the process changes?

You describe the change in the same conversation — a new stage, a required field, a different permission rule — and review the result. If the app has outgrown that workflow, sync the repository to GitHub (on Lite, Pro and Business) and continue in your own editor.

### Can I build a personal CRM for my own contacts?

Yes. The same build scales down to one person: contacts, a note and activity history on each one, and a live URL only you sign in to. Start with a prompt like “Build a personal CRM for my freelance clients: a contact list, a notes timeline on each contact, and a reminder for anyone I have not spoken to in a month.” For the client-facing side, see the client portal use case.

### Can it email customers or sync with our inbox?

Yes, through connectors. Gmail and Outlook connect your inbox, and Resend, Brevo, Mailgun and Loops send transactional email from the app — all among the 115 connectors on the connectors page. Anything beyond those is an API call you or the agent writes in your own code, which is possible because the output is a normal application rather than a closed configuration.

### Is our customer data safe here?

Every build runs in its own isolated cloud sandbox, so Vibely never needs access to your environment or an inbound connection to your network. The database is your own Supabase project; the row-level rules that scope access are in your code where you can read and tighten them.

## Related

- [A client portal with your name on it](https://vibely.sh/use-cases/client-portal) - One login per client for projects, files, updates and approvals — instead of a folder of links and a long email thread.
- [The internal tool your team keeps asking for](https://vibely.sh/use-cases/internal-tools) - Dashboards, admin panels and workflow apps with a real database, roles and a live URL — instead of another shared spreadsheet.
- [A SaaS MVP people can sign up for](https://vibely.sh/use-cases/saas-mvp) - Accounts, a Postgres database and a live URL, so the first version is in front of real users in days rather than a quarter.
- [See every use case](https://vibely.sh/use-cases)
- [Browse app templates](https://vibely.sh/templates)
