TL;DR
To build a CRM with Claude, describe how your team sells: the stages, what moves a deal forward, and which follow-ups get missed. Claude builds accounts, contacts, deals, and a pipeline view in Postgres. floo hosts it behind invite-only sign-in, and a Monday job sends each rep their stale deals.
- Describe your process, not "a CRM." Fewer fields, more use.
- The signed-in rep becomes the deal owner automatically.
- The reminder job is what makes people keep it up to date.
Teams outgrow the spreadsheet pipeline before they need a full CRM suite. The gap is a tool with exactly their stages, their fields, and the one reminder that matters. That is a small app, and Claude can write it from a paragraph.
1. Describe how you sell
Build a CRM for our sales team. Accounts have a name, a domain, and an owner. Contacts belong to an account. Deals belong to an account and move through these stages: qualified, demo booked, proposal sent, won, lost. A deal has an amount, a close date, and a next step with a due date. Each rep sees their own pipeline by stage; the sales lead sees everyone's. Log every stage change with who made it and when. Every Monday at 9am New York time, email each rep their deals with a next step overdue or no activity in 14 days.
Notice what is missing: lead scoring, email sync, forecasting. Add them when someone asks, not before.
2. Host it
[app]
name = "crm"
access_mode = "accounts"
[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"
[managed.default]
type = "postgres"
[cron.stale-deals]
schedule = "0 14 * * 1"
command = "node scripts/stale-deals.js"
service = "web"
- Sign-in: the app reads
X-Floo-User-EmailandX-Floo-User-Role, so new deals get the right owner and the lead's admin role unlocks the team view. - Schedule:
0 14 * * 1is Monday 2pm UTC, 9am in New York in winter. - Email: store your email provider's key with
floo env set EMAIL_API_KEY --stdin --app crm.
Invite the team with floo apps invite rep@example.com --role member --app crm, or "Invite the sales team" in Claude chat.
3. Import what you have
Export accounts and deals from the sheet or the old tool as CSV and ask Claude for an import script. Run it against dev, check the pipeline totals, then run it on prod when the team switches.
Things to get right
- Keep the stage history. "When did this move to proposal?" is the question a pipeline review always asks.
- One owner per deal. Shared ownership means no owner.
- Make the next step required. A deal with no next step is the one that goes stale.
- Let Claude use it too. With the floo connector, "add a deal for Acme, $12k, demo booked" works from chat. See how to let Claude use an app it built.
For the dashboard that sits on top of this data, see how to build an internal dashboard with Claude.
Frequently asked questions
Can Claude build a CRM?
Yes, and it works best when you describe your own sales process instead of asking for a generic CRM. Name the stages, what moves a deal between them, and the follow-ups that slip. Claude builds the tables, the pipeline view, and the reminders. floo hosts it with Postgres and invite-only sign-in.
Is a Claude-built CRM better than buying one?
For a small team with a specific process, often yes: it has only the fields you use, it costs hosting instead of seats, and it changes the same day you ask. Buy one when you need deep email sync, dialers, or dozens of integrations out of the box.
How does the CRM know which rep is signed in?
On floo, an app with access_mode = "accounts" receives the signed-in person's email and app role in request headers. Claude uses them to set the owner on new deals and to show each rep their own pipeline.