Key takeaways
- No CRM connection exists today, and none is promised for a specific product.
- CRM import, export and sync are planned for a later release (PRD FR09 and FR24).
- Delsivo keeps the evidence record; your CRM keeps relationships. A sync would link the two.
- Retries must be safe, conflicts shown for review, and disconnecting must keep local history.
Planned feature: not in Delsivo yet, and details may change before it ships.
Does Delsivo connect to my CRM?
Not today. Delsivo is at the design partner stage, and the product facts say plainly that it is not a CRM replacement at first and that CRM import and export come later. We won't name a CRM until a connection to it is built, because a list of logos on a roadmap page reads like a promise.
If your fund runs on a CRM now, you can still use Delsivo for what happens between application and decision, and keep relationship history where it is.
What each tool would own
| Record | Kept in your CRM | Kept in Delsivo |
|---|---|---|
| Relationships and contact history | Yes | Only founders and contacts on a deal |
| Applications and decks | Optional link | Yes, with versions and slide citations |
| Thesis fit, evidence and readiness | A summary field, if you want one | Yes, criterion by criterion with sources |
| Claims and evidence labels | No | Yes |
| Stage and decision | Mirrored, if you choose | Yes, with the reason and who decided |
Rules for CRM sync for venture funds
The PRD sets acceptance rules for every later integration. A CRM sync would have to meet each of them before it ships:
- Idempotent retries: a sync that fails halfway and retries never creates a second deal or contact.
- Conflicts surface for review: if your CRM and Delsivo disagree about a field, a person sees both values and picks one.
- Disconnect stops future sync without deleting authorized local history.
- Referral details are shared only in the fields your fund chooses, as the sourcing requirement asks.
Overwrites follow the same rule as founder answers in the first release: a change to a mapped field needs approval, and the earlier value is kept.
How CRM providers will be chosen
- 1Ask each design partner fund which CRM, if any, it uses and what it would sync.
- 2Pick the first provider from those answers, not from a wish list.
- 3Agree the field mapping with the funds that will use it.
- 4Build it against the rules above, then publish an integration page that says exactly what it does.
Until then, CSV import and export is the planned way to move records between tools.