Explore here
- Web app
- Internal tools
Build a CRM shaped like your pipeline, not someone else’s
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
- Web app
- Category
- Internal tools
- Stack
- React, TypeScript, Supabase
- Plans
- Free to start; database and sign-in from Lite
Postgres and auth on Supabase, wired up for you
Included in the first build
Row-level rules so reps see their accounts and managers see the team
Yours to keep
- 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
1. 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.
2. 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.
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.
3. 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 backendOne-click publishingCode you ownRow-level security checks
4. 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
5. What to build next
Once the first build lands, these are the prompts people send next.
- Add a weekly pipeline summary screen with totals by stage and by owner.
- Add an activity reminder: flag any deal with no note in the last fourteen days.
- Import our existing contacts from a CSV upload.
Works with the tools you already use
115 built-in connectors, from Vibely AI, Supabase, Stripe and GitHub to Slack, HubSpot, Shopify and Snowflake. Anything else is an API call in code you own.
Questions, answered.
Describe it. Watch it build.
Paste the prompt above and react to something running instead of writing a spec. The free plan needs no card, and the code is yours from the first build.