Use cases
Build a CRM with AI-assisted engineering
Get a CRM shaped to how your team actually sells — your objects, your stages, your rules — instead of bending your process around per-seat software.
Ciao is an AI-assisted engineering platform for building custom CRMs — contact and company records, pipelines, activity timelines and permissions — as real React, TypeScript and Supabase applications. Unlike off-the-shelf CRMs priced per seat, a Ciao-built CRM matches your sales process exactly, integrates with your own data, and ships through governed merges, automated QA and security testing, with 100% code ownership.
Published 2026-07-03 · Last updated 2026-07-03
When the standard CRM stops fitting
A CRM is the system of record for relationships: every contact and company, every deal moving through a pipeline, every call, email and meeting logged where the next person can find it. Off-the-shelf CRMs do this well for the average sales team — which is exactly the problem when your team is not average.
Recruiting firms track candidates and placements, not deals. Real estate teams track listings, buyers and viewings. Franchise groups route leads to franchisees. Manufacturers sell through distributors with deal registration. Teams like these end up paying per seat for modules they never open, while the parts that actually match their process live in spreadsheets on the side.
Building a custom CRM used to mean a year of development before anyone logged a call. With Ciao you describe your objects, stages and rules in plain language and get a working CRM in real code — then keep shaping it as your process changes, with QA and Guardrails standing between every change and your pipeline data.
What a CRM actually requires
Whatever the industry, the core is remarkably consistent:
- Contact and company objects — People linked to organizations, custom fields per record type, and clear ownership so every account has a name next to it.
- Pipeline stages — Explicit stages with per-stage requirements — you cannot mark a deal Proposal Sent without attaching the proposal.
- Activity timeline — Calls, emails, meetings and notes in one chronological view per contact and per deal, so handovers survive.
- Permission tiers — Reps see their own accounts, managers see their team, admins see everything and change configuration.
- Import that works — CSV import with field mapping, validation and a dry-run preview — because the first week is a migration, not a sale.
- Dedupe — Matching on email, company domain and fuzzy name, with a merge flow that preserves both records' history.
- Email logging — Messages logged against the right contact via a BCC address or inbox integration, not copy-paste.
- Tasks and reminders — Follow-ups with owners and due dates, surfaced on a today view your team will actually open.
- Reporting — Pipeline value by stage, conversion rates, activity per rep, and forecasts — from the same database, always current.
How a CRM build runs on Ciao
1. Describe your sales motion
Your objects, stages, required fields and who may see what — in plain language, not configuration screens.
2. Generate the schema
Contacts, companies, deals, activities and tasks land as a Supabase schema with relationships and row-level permissions.
3. Migrate your data
Build the CSV import with mapping, validation and dedupe rules tuned to your real data — test it against an export from the old system.
4. Wire the integrations
Email logging, calendar sync and billing or marketing connections through the integrations Block, inspectable in the full-stack console.
5. Test the paths that lose deals
QA replays cover stage transitions, permission boundaries and the import flow before every publish.
6. Govern customer data
Guardrails maps CRM data areas as protected zones, applies plain-English policies and records review on risky changes.
7. Deploy and iterate
Ship to Ciao cloud or your own cloud. Add a new stage, field or report by describing it — through the same governed loop.
Security and governance checklist
- ✓ SSO via SAML or OIDC for staff sign-in, with optional MFA
- ✓ Role-based access: rep, manager and admin tiers enforced in the backend
- ✓ Row-level ownership rules so territory and team boundaries hold in queries
- ✓ Append-only audit trail across prompts, merges, deploys and admin actions
- ✓ Guardrails review recorded before changes to customer-data code merge
- ✓ Security scanning with access-control probes against the live app
- ✓ Customer code never used to train models; zero-retention inference
- ✓ Full export — your pipeline data and the CRM code are both yours
CRM variations teams build
Sales pipeline CRM
Classic deals-and-stages with your qualification rules, quotas and forecast roll-ups built in.
Real estate CRM
Listings, buyers, viewings and offers — matching buyers to properties instead of forcing both into a generic deal object.
Recruiting CRM
Candidates, roles, interview stages and feedback forms, with placements tracked against client companies.
Donor CRM
Donors, gifts, campaigns and receipts for nonprofits, with giving history driving segments.
Partner and channel CRM
Deal registration, partner tiers and co-selling visibility without exposing your whole pipeline.
Franchise lead router
Central lead capture with territory rules routing each lead to the right franchisee, and conversion tracked both ways.
CRM requirements, covered
| Requirement | How Ciao covers it |
|---|---|
| Contacts, companies, deals | Generated Supabase schema with custom fields and relationships |
| Import and dedupe | Validated CSV import with mapping, dry-run preview and merge flows |
| Who sees what | Role tiers and row-level ownership rules enforced in the database |
| Email and calendar logging | Integrations Block wiring messages and events to the right records |
| Reporting | Live reports and dashboards on the same database — no export step |
| Safe changes | Guardrails policy review plus QA replays on pipeline-critical flows |
| Ownership and exit | Standard React, TypeScript and Supabase, exportable at any time |
Frequently asked questions
When does building a CRM beat buying one?
When your process diverges from the standard deal pipeline — different objects, unusual routing, industry-specific stages — or when per-seat pricing across a large team costs more than owning the software. If a standard CRM fits your motion well, buy it; Ciao is for the teams bending themselves around one.
Can we migrate data from our current CRM?
Yes. The import flow is built as part of the CRM: CSV import with field mapping, validation and dedupe against your real export, plus API-based migration where the old system allows it. You test the import on a copy before running it for real.
Can reps be limited to their own accounts?
Yes. Permission tiers are enforced with row-level rules in the backend — a rep's queries physically return only their records — and Security's access-control probes confirm the boundaries against the live app.
How does email logging work?
The common patterns are a BCC logging address that files messages against the matching contact, or an inbox integration through the integrations Block. Either way messages land on the activity timeline with the deal context attached.
Will a custom CRM keep up as our team grows?
The CRM is a standard React, TypeScript and Supabase application on infrastructure designed to scale — Kubernetes, isolated pods, multi-region support. Growth changes are prompts through the governed loop, not a re-platforming project.
What does it cost compared to per-seat CRM licenses?
There is no per-seat meter on the CRM you build — the economics shift with team size. Serious production programs start at USD 10,000 per year; sales can model that against your current CRM spend.