Self-updating CRMAI-native · no data entry
Companies, contacts and deals build themselves from your email, calendar and Stripe, and stay current on their own. Nobody types them in — and a deal only counts as won when the money arrives.
Gmail · Outlook · Stripe · nothing to import
| Deal | Company | Stage | Deal Value | Owner | Subscription | Cash Collected | Health |
|---|---|---|---|---|---|---|---|
| Linear — 8 seats | Proposal | $23,040 | JJayYour mailboxThe thread with Sarah Chen started hereOwner follows the mailbox | — | — | 78 | |
| Notion Labs — team plan | Closed WonSStripeInvoice paid Aug 14Verified by Stripe | $52,800 | MMaya | Active | $52,800 | 91 | |
| Figma — expansion | Negotiation | $33,000Email from Elena Voss“We’re budgeting $33k for year one.”Jul 12 | JJay | — | — | 84 | |
| Ramp — annual plan | Closed Won | $62,400 | MMaya | Cancels Oct 3 | $57,200SStripe2 payments · 1 refundRefunds come off the total | 41 | |
| Deel — enterprise | Demo | $96,000 | JJay | — | — | 71 | |
| Mercury — annual plan | Closed Won | $17,400 | JJay | Active | $17,400 | 88 | |
| Retool — 12 seats | Qualified | $28,800 | MMaya | — | — | 52 | |
| Sentry — expansion | Proposal | $58,320 | MMaya | — | — | 62 | |
| Vanta — pilot | Qualified | $14,400 | JJay | — | — | 57 | |
| 24 count |
A self-updating CRM builds and maintains its own records from the activity it can see — email, meetings and payments — instead of depending on people to type them in. Dopia is an AI-native CRM that works this way: it creates companies, contacts and deals from your inbox, calendar and Stripe account, keeps each one current as things happen, and has its assistant ask before it changes anything you wrote yourself.
01Who fills it in
“Updates itself” is an easy claim to print. This is the version you can check: the default columns, the source behind each one, and the rule it follows. The last row is yours on purpose.
| Column | On | Written by | The rule |
|---|---|---|---|
| Companies & contacts | The records | MailCalendar | Anyone you have written to or sat in a meeting with. A newsletter never becomes a person. |
| Owner | All three | MailCalendar | Whoever’s mailbox or calendar the record came from — not whoever connected first. |
| Outreach Status | Contact | MailCalendar | Contacted → Replied → Meeting Booked, as it happens. It only moves forward, and Not a Fit or Do Not Contact stay where you put them. |
| Deals | The records | MailCalendarStripe | A thread that reads like an opportunity, a booked meeting with nothing to file under, or a subscription. |
| Stage | Deal | StripeYou | Closed Won when an invoice is paid. Closed Lost when a trial ends without one. A closed deal is never reopened by a sync. |
| Subscription · Cash Collected | Deal | Stripe | Read straight from Stripe. Refunds come off the total; a second currency is shown, never converted. |
| Lifecycle | Company · Contact | Stripe | Customer on the first payment. Churned customer when the subscription ends — the deal itself keeps its history. |
| Health · Next check | Deal | Memory | Read from everything the deal has been through, with the sources behind it. The deal sets its own date to look again. |
| Deal Value | Deal | MailStripeYou | An amount named in the conversation, or one taken from your Stripe prices. Never a number made up to fill the column. |
| Your own fields and notes | Anything | You | Yours. The assistant can propose a change — anything that replaces what you wrote waits for your approval. |
Which mail and meetings are allowed to become records at all — and which never are — is its own story: how Dopia reads your email and calendar.
02What counts as won
In most CRMs a deal is won when someone drags it into the last column. In Dopia a paid invoice does it — and what you expected and what you collected stay in separate columns, so a refund or a cancellation shows up where it happened instead of quietly padding the number.
On the record
1 payment · 1 refund
The deal stays won — it was. Whether Northwind is still a customer lives on the company, where a cancellation can say so.
Read-only access to Stripe · how the Stripe connection works
03When it disagrees with you
A CRM that writes itself is only worth having if you can still trust what you typed into it. When the assistant reads something that contradicts a value someone set, it brings you the change instead of making it.
Why
Bradley’s email this morning moved the rollout to 30 seats and pushed signature to mid-October.
Field changes (crossed-out values will be replaced)
Empty field?
Filled on its own.
Something you wrote?
Shown as a change, and waits for you.
Same name, no email in common?
It asks whether you meant the existing record.
How does it know it’s the same person?
By email, domain, phone or profile URL — never by a name alone.
A paid invoice?
The one thing that does not ask. Money closes the deal, whatever the stage said.
04When nothing happens
A system that reacts to what arrives never notices what didn’t. Every deal in Dopia sets its own next check — a date, and the reason for it — and when that day comes and nobody has written, the quiet is read like any other event.
Suggestions
Ask Nadia how the board meeting landed
She set the 19th as the restart point; nothing has come in since Sep 8.
The draft is written, not sent. Nothing leaves your name until you press the button.
05Built your way
Your own fields, grid or card views, filters saved for the team — and the same records open to the agents you already run.
Acme Corp — Q3 rollout
GreenLeaf — team plan
Lumen Labs — platform pilot
Add a field of any kind
Grid or cards, filtered and sorted the way you read it, saved as a view your teammates open into.
Claude, Codex or any MCP client can read and write these records under scopes you grant: connect an agent to your Dopia CRM.
06Side by side
Typing into a database was the right design when typing was the only way anything got recorded — it is why every CRM worked that way for twenty years. Once the mail, the meetings and the payments can be read directly, the work moves.
| A CRM kept by hand | Dopia | |
|---|---|---|
| A new contact | Typed in after the call, if someone gets to it | Appears the first time you write to them or meet |
| A new deal | Created when someone remembers to | Born from the thread, the meeting or the subscription |
| Closed Won | A card dragged into the last column | An invoice Stripe says was paid |
| Revenue | Whatever the deal was said to be worth | Expected and collected in separate columns, refunds netted out |
| A deal going quiet | Noticed at the next pipeline review | Its next check fires, and the silence is read |
| Duplicates | Found and merged by hand | Matched on email, domain, phone or profile URL |
| What you wrote | Whatever the last person to edit it left | Never replaced by the assistant without your approval |
Where the records come from, and where they go
No. Connecting a mailbox and its calendar is the only setup step. Companies, contacts and deals are built from conversations you have already had, and columns such as Owner, Outreach Status, Last Outreach, Subscription, Cash Collected and Lifecycle keep themselves current from then on. You can still edit anything, and the fields you add yourself stay yours.
Three ways. After your mail is imported, Dopia reads each company’s history and turns the conversations that still read like live opportunities into deals, with the messages that show why. A meeting that has no open deal to file under can open one — a booking through your scheduling link, for example. And every Stripe subscription becomes a deal of its own.
When Stripe says so. With Stripe connected, a paid invoice moves the open deal to Closed Won, and a trial that ends without a payment closes it as Closed Lost. Payments and refunds are kept on the deal as Cash Collected, next to the Deal Value you expected, so the two never blur into one number. A closed deal is never reopened by a sync. Without Stripe connected, you mark deals won yourself.
Not without asking. Background sync fills a record’s fields when it creates the record, and after that only keeps its own columns — such as Outreach Status and Last Outreach — current. When the assistant reads something that contradicts a value already set, it shows you the change, old value crossed out and new value beside it, and waits for your approval. The one deliberate exception is money: a paid Stripe invoice closes the deal on its own.
Records are matched on what actually identifies them — an email address, a company domain, a phone number or a profile URL — and never on a name alone. When a new record would only share a name with an existing one, Dopia asks whether you meant that record or want a new one.
Yes. Add fields of any common type — text, number, currency, single or multi select, date, email, phone, URL, checkbox, relation, user or attachment — and view each table as a grid or as cards, with the columns and filters you choose saved as a view your teammates can open.
There is no import step. Dopia builds your companies, contacts and deals from the mail, meetings and payments behind them rather than from a spreadsheet export. Agents connected to Dopia over MCP — Claude, Codex or any MCP client — can also create and update records, with the same duplicate matching.
No. Dopia does not run cold outreach or send anything as you on its own. It keeps the record, notices what has changed and what has gone quiet, and prepares the next move; anything addressed to a customer is drafted for you to approve.
Dopia has a Free plan with a monthly credit allowance and no credit card required. Paid plans are priced per seat with pooled monthly credits, and new workspaces start on a full-featured trial. Current prices are at dopia.ai/pricing.
Connect your email, calendar and Stripe, and come back to companies, contacts and deals that keep themselves — with a won column that only counts money.
Gmail · Outlook · Stripe · free to start