**PRD: Two-way calendar sync (Google + Outlook)**

**Owner.** Anjali (PM) + Vikram (Eng lead)
**TL;DR.** Today our scheduler reads availability from Google/Outlook but writes back nothing. Users get a calendar invite from us *and* one from their attendee, leading to duplicate events 38% of the time (per support tickets). This PRD is for adding write-back so a single accepted booking creates exactly one calendar event on both sides.

**Problem.** Duplicate events are our #1 support ticket category (24% of inbound). Users perceive it as unreliability and 11% of trial-to-paid churn cites "calendar issues" in exit interviews.

**Target users.** Account executives and customer success managers booking 5–15 meetings/week, primarily on Google Workspace (62%) or Microsoft 365 (35%).

**Scope (in).** OAuth-based two-way sync with Google Calendar and Microsoft 365. Writing the event on accept. Updating the event on reschedule. Removing the event on cancel. Time-zone correctness.

**Scope (out, this release).** Three-way sync with Apple iCloud Calendar (4% of users — defer). Conference-bridge auto-creation (Zoom, Teams, Meet) — separate spec.

**Success metrics.**
  - Duplicate-event support tickets down 80% within 60 days of launch (baseline: 240/month)
  - Trial-to-paid conversion lift of at least 4pp (baseline 22%)
  - Less than 1% sync failure rate measured by an end-to-end probe

**Dependencies.** Auth team needs to add Google Calendar + Outlook OAuth scopes to our consent screen (4 days). Infra team needs to provision a separate webhook intake service to handle bidirectional updates (2 weeks).

**Open questions.**
  - Conflict resolution: if user reschedules in *both* tools before sync, who wins? My recommendation: our system is source-of-truth.
  - Token revocation: if a user revokes our calendar access mid-cycle, do we cancel or freeze existing events? Need product call by end of week.

**Rollout.** Internal eat-our-own-dogfood for 2 weeks. Then 5% of new signups for 4 weeks. Then 100%.

✦ Claude Opus 4.7 · grounded in your files + site · memory on

Pairs well with

Product works best alongside these 3.

Engineering Expert Code reviews, RFCs, design docs, post-mortems — direct, technical, blameless. Designer Expert Design critiques, research synthesis, accessibility audits, UX copy. Customer Success Expert Onboarding, QBR docs, renewal pitches, churn-saves — every message grounded in their usage data.

Put Product on your team.

Plus 18 other experts. One subscription. No setup.

Start free →