A pipeline you design
Your own stages, colours and order. Drag a deal anywhere in a column and it stays where you put it.
AI assistant built in
The CRM your team
The CRM your team
actually owns.
Design your own pipeline and decide exactly who can see each field. Leads from a public form land as real deals, and SWARECO AI answers questions about them using only what each person is allowed to see.
Illustrative screen. No real customer data.
Connects to the tools your team already uses
Gmail
Calendly
REST API
MCP
Cloudflare Turnstile
Your Anthropic key
A complete CRM, not a database with a form on top
Contacts, deals, meetings, files, conversations and reporting, with an assistant that works across all of it.
Leads that become deals
A public form creates the contact and opens the deal. There is no inbox to triage in between.
SWARECO AI
Ask about your own records, see what it read, and approve every change before it is made.
Field-level control
Hide deal size or a phone number from any role you choose. It stays hidden in forms, lists, filters and history alike.
Works with your tools
Gmail, Calendly, a REST API and MCP. Each one creates or updates real CRM records, not a feed to look at.
An assistant that shows its work, and asks first
SWARECO AI answers from your own records, tells you what it read, and changes nothing until you say so.
Ask in plain English
Questions about your own contacts, deals, appointments and comments. Start from a saved skill if you like.
See what it read
Chips list the lookups it really made, and warnings are computed from your data rather than guessed.
Approve every change
Changes arrive as cards. Nothing is written until you click Confirm, and history says who did it.
Chats that flag what needs you
Start several at once. Anything waiting on you gets a count on the button, a toast and a bell notification, and a pending change also sends an email by default.
Skills your team shares
Saved instructions for work you repeat. Pick a chip or type a slash command, and admins decide who can use each one.
Oversight for admins
Every conversation is reviewable, with the lookups it made and the changes it applied. Export to CSV, and choose how long chats are kept.
A lead becomes a deal without anyone moving it
Publish a form and share the link. Everything after the click happens on its own.
A visitor sends your form
Build it from your standard and custom fields, add file uploads, and turn on Cloudflare Turnstile. It lives at its own public link.
The contact is matched or created
Duplicate protection on email and phone means a returning lead is not entered twice. Uploads land as virus-scanned files on the contact.
A deal opens on your pipeline
Every submission opens an opportunity against the right offering, ready to drag through your own stages.
Email and meetings attach themselves
Gmail replies thread against the contact. Calendly bookings become a confirmed appointment, assigned to whoever hosted it.
Everything lands on the record
Forms, email, meetings and changes made by people, the API, MCP or SWARECO AI all show up in one timeline on the contact, with where each one came from.
- Gmail threads attach to the contact as a conversation
- A Calendly booking becomes a contact, a deal and a confirmed appointment
- An assistant's changes carry its label, (MCP) or (Assistant), next to the person who approved them
- Fields your role cannot see are left out of the timeline entirely
Stages that match how you actually sell
Most CRMs hand you someone else's sales process. Here the pipeline is data: you name the stages, pick their colours, set their order, and mark which ones count as open or closed.
- Drag-and-drop kanban with independent per-column pagination
- List, kanban, calendar and agenda views of the same pipeline
- A stale-deal counter that surfaces anything untouched for a week
- Deal value in real money, with per-role visibility
- Deal A was created last month and won this month. Counted.
- Deal B was created this month and is still open. Not counted.
- Deal C was created and won last month. Not counted.
“Won this month” counts the deals that actually crossed into Won this month — not the ones created this month. Historical state is materialised as your records change, so a comparison against last quarter means what it says.
Illustrative deals.
Decide who sees each field
Hide a value like deal size or phone number from anyone below a role you choose. The rule holds in forms, lists, filters and history alike, so a hidden field cannot leak through a side door.
There are four roles — member, admin, owner and account owner — and every field can set its own floor.
Admin view
- Stage
- Deal value
- Phone
Member view
- Stage
- Deal value
- Hidden
- Phone
- Hidden
Bring your own assistant
The CRM runs a remote MCP server, so an assistant such as Claude Code can look things up in your CRM and, if you allow it, create and update records. It acts as you, within your permissions.
- A new connection is read-only. Anything that changes data needs an extra confirmation.
- Every call is checked as you, at the moment it is made.
- No delete tool and no delete permission, so no instruction can reach one.
A few things it can do
- Look up contacts
- Read your deals
- Book appointments
- Add comments
- Attach files
And the rest of a working CRM
Each one aware of the others, and all of it scoped to your account alone.
- Contacts
- Duplicate protection on email and phone, international number handling, and search that reaches every custom field.
- Appointments
- Meetings on any contact or deal, with a real status lifecycle and list, day, week, month and agenda views.
- KPIs
- Build your own metrics and compare periods against a true point-in-time history, not a guess derived from created dates.
- Files
- Attach documents to a contact or deal. Every upload is virus-scanned, type-checked and size-capped.
- Conversations
- A shared inbox view, with threaded conversations on every contact.
- Notifications
- In-app, email and realtime notifications you control per event, with a daily digest for new contacts.
Questions people ask before they trust an AI with their CRM
Does SWARECO AI change my data on its own?
No. It proposes a change as a card, and nothing is written until the person chatting clicks Confirm. The CRM checks the record and their permission again at that moment, and a card left alone for 15 minutes expires.
Can it delete anything?
No. There is no delete tool and no delete permission, for SWARECO AI or for assistants connected over MCP, so no instruction can reach one. It also cannot reach another account, change records in bulk, or send email.
Whose AI account does it use?
Yours. SWARECO AI runs on your account's own Anthropic API key, so model use is billed to you, with a monthly dollar budget you set. The key is encrypted at rest, and only its last four characters are ever shown.
Who can see what it reads and says?
It sees only what the person asking could see, and fields hidden from their role are left out. Admins and owners can review conversations in an AI activity log, and you choose how long conversations are kept.
Can I connect my own AI assistant?
Yes, over MCP. A new connection is read-only, write permissions need an extra confirmation, and every call is checked as you, when it is made. Changes appear in history as Your Name (MCP).
What happens when someone fills in a public form?
The contact is matched by email or phone, or created. A deal opens against the right offering in your first open stage, and any files they uploaded are virus-scanned and attached to the contact.
Security that survives every release
Multi-tenancy is a property of the data model here, not a filter someone remembered to add.
Per-account
Every record belongs to an account, and every lookup is scoped through it.
4 roles
Member, admin, owner and account owner — plus per-field visibility floors.
Encrypted
Integration tokens and secrets are encrypted at rest; API keys are stored only as digests.
Scanned
Every uploaded file is virus-scanned, type-checked and size-capped.
See it against your own pipeline
We'll walk you through contacts, deals, capture forms and reporting — and answer the awkward questions about permissions and data separation.