Key takeaways
- Calendar sync is planned for a later release. Google Calendar support specifically is not yet decided.
- The point is to tie each founder meeting to its deal, so the brief, notes and follow-ups sit in one place.
- Delsivo reads nothing from any calendar today.
- Any future sync must be safe to retry, show conflicts for review and stop cleanly when you disconnect.
Planned feature: not in Delsivo yet, and details may change before it ships.
Is Google Calendar sync available in Delsivo?
No. Delsivo is at the design partner stage and nothing is generally available. Calendar sync sits in the PRD's later phase, alongside CRM sync and other network features. The PRD doesn't name a calendar provider, so we don't either: Google Calendar is a likely candidate for a fund team, but the choice will follow what design partners actually use.
We set out the intent and the limits in one place, so a fund evaluating Delsivo doesn't have to guess from a feature list.
What meeting sync would add to a deal
A founder meeting is where much of a deal's evidence changes. The deal record already plans to hold everything around it; a calendar connection would remove the step of telling Delsivo the meeting exists.
| Moment | Today (by hand) | With a future calendar sync |
|---|---|---|
| Meeting booked | An analyst notes the date on the deal | The event would appear on the matching deal |
| Before the call | Someone opens the deal and prepares a brief | The founder call preparation brief could be ready ahead of the event |
| After the call | Notes typed into the deal | Notes linked to the event that produced them |
| Stage | A person moves the deal to First meeting | Still a person: a calendar event never changes a stage |
How meeting events would be matched to deals
Matching is the hard part. An event title like "Intro call" says little; the attendee list says more. The likely approach is to suggest a deal when an attendee's email matches a founder or contact on it, and let an analyst confirm. That mirrors how Delsivo treats duplicates and claim updates: the system suggests, a person accepts.
- 1A team member connects their own calendar and chooses which events Delsivo may see.
- 2Delsivo suggests a deal for each event whose attendees match a founder on that deal.
- 3The team member confirms or dismisses the suggestion.
- 4Confirmed events show on the deal, linked to the brief and to any notes.
These steps describe a design to test, not a built flow. They may change after design partner interviews.
Rules any calendar connection must follow
The PRD sets three acceptance rules for every later integration, and a calendar sync would be held to all of them:
- Retries are idempotent: a dropped connection that retries never creates the same meeting twice.
- Conflicts surface for review: if an event and the deal disagree, a person sees both.
- Disconnecting stops future sync and keeps the history you were allowed to see. Nothing already on the deal is deleted.
Access would follow the same permission check as the rest of the workspace, so a meeting on a restricted deal stays visible only to people who can see that deal.