You can set up a working CRM with AI in one afternoon by following one rule: ask for a plan first, review it, and approve the smallest useful pieces one at a time. Describe your business in plain language; the AI proposes fields, stages, and views; you stay in control of what actually gets created.
CRM projects fail for a predictable reason: they start with software and try to bolt the business on afterwards. Working with AI flips that. You start by describing how your business actually runs — and the structure gets derived from your words. Here's what that looks like in practice, with a real example you can adapt.
Describe your business like you'd brief a new hire
Open your workspace chat and write three or four sentences about how customers actually flow through your business. No jargon, no feature requests — just the truth of how the work happens. Take a small landscaping company as our running example:
The prompt
"We're a landscaping company. Leads come from our website form, phone calls, and referrals. We visit the property, send a quote within 3 days, and follow up twice if we don't hear back. Jobs are either one-off projects or monthly maintenance contracts. Set up our CRM for this — suggest stages, fields, saved views, and follow-up tasks. Don't apply anything yet."
Notice the last sentence: "Don't apply anything yet." That's the most important phrase of the afternoon. You want a reviewable plan, not surprise changes — the same advice the set-up-CRM-with-AI guide leads with.
Review the plan it proposes
For a brief like that, a good setup plan comes back looking something like this:
Proposed pipeline stages
- New lead → Site visit booked → Quote sent → Follow-up → Won / Lost
Proposed fields
- Lead source (website / phone / referral) — so you learn which channel pays
- Job type (project / monthly maintenance) — your two business models behave differently
- Property address and quote amount
- Quote sent date — what the follow-up clock runs on
Proposed views and tasks
- Saved view: "Quotes awaiting reply" — quote sent, no response, sorted by days waiting
- Saved view: "Maintenance renewals due" — contracts ending in the next 60 days
- Task template: follow-up at day 3 and day 7 after every quote
Your job at this step is editorial, not technical. Cross out anything you wouldn't actually use. The classic failure mode is approving a dozen fields that feel thorough on day one and are empty by week three — a field nobody fills in is worse than no field, because it teaches your team the CRM is optional.
Approve the smallest useful piece first
Don't approve the whole plan in one click, even if it all looks right. Start with one saved view or one field, see it appear, and check it against real life. A good first approval is the "Quotes awaiting reply" view — it's immediately useful the same afternoon and touches nothing else. Then approve the fields it depends on, then the stages, then the task templates. Each approval is small enough to undo mentally, and ten minutes in you'll trust the process enough to move quickly.
If a suggestion overlaps something you already have — say it proposes a "Source" field and you already track "How did you hear about us" — don't accept a duplicate. Ask it to map to the existing field instead. And if a change affects how your whole team works, have an admin look before it applies; fields and layouts are easy to adjust early and painful to untangle later.
Load your contacts and test on ten real customers
Import your contacts — a spreadsheet export from wherever they live today is fine — and then resist the urge to backfill everything. Pick ten real, current customers and walk them through your new setup: set their stage, fill their fields, open their customer 360 view and check the picture makes sense. Ten honest records will teach you more about your setup than a thousand imported rows. If the import surfaced duplicates, merge them now while the list is still short.
Make it the team's habit, not your hobby
A CRM only works if updating it is easier than avoiding it. Two things make that true. First, keep one view per daily question — "who do I follow up with today?" should be one click, not a filter expedition; that's what saved views are for. Second, let the follow-up tasks come to your team instead of relying on memory — the day-3 and day-7 quote follow-ups from the plan become automatic, and if you later want the sequence to trigger itself end to end, that's a CRM workflow away.
That's the afternoon. Not a migration project, not a consultant engagement — a conversation, a plan, a handful of careful approvals, and ten test records.
Key takeaways
- Plan first, apply second: end every setup prompt with "don't apply anything yet."
- Describe the business, not the software: lead sources, stages, follow-up habits — in plain sentences.
- Approve small: one view, then its fields, then stages. Never the whole plan in one click.
- Fewer fields, always: an unfilled field trains your team to ignore the CRM.
- Test on ten real customers before you trust it with all of them.
Frequently asked questions
Do I need to clean up my contacts before starting?
No — set up the structure first, then import. It's easier to judge what's worth cleaning once you can see contacts inside real views, and duplicate merging is simpler when you know which fields matter.
What if the AI's plan doesn't match how we work?
That usually means the brief was too thin. Add the missing truth — "most of our leads go quiet for months and come back" — and ask again. The plan is a draft of your own description; sharpen the description and the plan follows.
Can AI change my CRM without me knowing?
Not if you work plan-first: changes are proposed, you review and approve them, and team-wide changes deserve an admin's eyes before applying. The approval step is the point — keep it.
We're two people. Is a CRM overkill?
Two people forget follow-ups exactly like ten people do. A minimal setup — one pipeline, four fields, one "follow up today" view — pays for itself with the first quote that doesn't slip through.
How do I migrate from a spreadsheet without losing data?
Export the spreadsheet, import it as contacts, and map columns to the fields from your approved plan. Anything that doesn't map cleanly belongs in notes, not in a new field invented to hold it. Keep the spreadsheet as a backup until the team has lived in the CRM for a month.
The best CRM is the one your team actually updates — and the fastest path there is a setup derived from how you already work. Brief it like a new hire, review like an editor, approve like a skeptic. The help center has the click-by-click version of every step when you need it.