01
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.
Use case — web app
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.
- Postgres and auth on Supabase, wired up for you
- 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 whenever you want it
- Change a stage or add a field by asking, not by filing a ticket
- Free plan, no credit card, unlimited projects
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.
What to build 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.
Web app
What the build actually consists of
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. If you need forecasting rollups across regions and a marketing automation suite, buy one — the argument here is fit and ownership, not feature count.
02
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.
03
Live, and still yours
Deployed to a URL on the first build, and exportable to GitHub whenever you want to continue in your own editor. Nothing about the data model is proprietary.
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 and a GitHub repository you control
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.
Start buildingFAQ
Questions, answered.
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 and continue in your own editor.
Can it email customers or sync with our inbox?+
Not out of the box, and we would rather say so than imply it. Vibely ships nine connectors — Vibely AI, Supabase, Stripe, RevenueCat, GitHub, Notion, Linear, Figma and Miro. 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.