Module 04 — Calendar

Walk into every meeting informed.

Not just the name and the time. Everything.

Five minutes before the call. Frantic.

You know who you're meeting. You know when. But there's a gap between knowing the calendar entry and being prepared for the conversation inside it.

The scramble is real — re-reading old emails, trying to remember what was discussed last time, wondering what they wanted to follow up on. That's not preparation. That's triage. Ask Claude who you're meeting and what you should know — SoY surfaces everything relevant from every module, without you having to look it up.

T-minus 5 minutes
1:55 PM — Marcus Webb, Meridian CEO
  • Frantically opening Gmail to find the last thread
  • Trying to remember what you committed to last time
  • Scrolling back through old notes to find what he wanted to discuss
  • Checking the project status so you don't look out of the loop
  • Wondering if there was something you were supposed to send him
This is what preparation looks like without SoY. Triage dressed as readiness.

Ask before you walk in.

Claude knows your calendar. It knows who you're meeting, when, and everything SoY has on them. These are the queries you'll actually run.

What's on my calendar this week?
Who am I meeting tomorrow and what should I know going in?
Generate prep notes for my 2pm with Marcus
What meetings do I have with Rebecca this month?
Anything I should prepare for Friday?

Every layer of context, in one ask.

Ask Claude to prep you for a meeting. It draws from all connected modules — emails, contacts, projects, previous conversations, open commitments — and assembles the brief. This is what you get.

Pre-meeting brief · Generated by SoY
2pm — Marcus Webb
Meridian CEO · 60 min · Video call
Relationship health
  • Feb 18 — "Looked at the proposal, a few questions on the data pipeline section"
  • Feb 12 — "Happy to do a call next week, send me a few times"
  • Feb 6 — "Good to meet at the summit — let's follow up properly"
  • You said you'd send the revised data pipeline spec by Feb 21 Yours
  • Marcus said he'd loop in his CTO before this call Theirs
  • You offered to send two case studies from similar deployments Yours
  • Proposal sent Feb 15. Last updated Feb 18 (v2 with revised timeline)
  • Outstanding: data pipeline section questions from Marcus
  • Next step: alignment call → revised proposal → legal review
  • Summit intro (Feb 5): Marcus mentioned frustration with current vendor, wants dedicated support
  • Intro call (Feb 13): Discussed timeline, he has a board update in Q2 — wants this live by then
Has the CTO had a chance to look at the data pipeline spec?
Is the Q2 board update timeline still the main forcing function?
What would make this an easy yes at the decision stage?

Past 7 days. Next 14 days. Always current.

The sync window is intentional — enough history to understand recent meeting patterns, enough future to prepare in advance. When you ask about your calendar, SoY pulls the latest and matches attendees to your CRM contacts.

Past window
7 days back
Recent meetings are already in context. Commitments from last week's calls are tracked. You can ask what was covered.
Future window
14 days ahead
Two weeks of upcoming meetings loaded. Ask for prep briefs for anything on the calendar. Get ahead before the day starts.
Attendees link to CRM contacts — no manual tagging. Anyone in your SoY contacts database who appears as a meeting attendee gets their event attached to their record on sync.
Calendar events trigger cross-module synthesis. The meeting is the moment — SoY assembles email history, project context, commitments, and relationship data around it. The event is the trigger; the intelligence comes from everywhere else.
Sync runs on open. When you view your calendar in SoY, the sync updates. Nothing to initiate, nothing to schedule.

The calendar entry becomes a full record.

Calendar and Conversations work together. After a meeting, run /import-call and paste the transcript. Commitments are extracted and linked. The calendar event stays connected — so when you look back, you see the prep brief, the transcript, and everything that came out of it.

Not just a calendar entry. A complete meeting record with a before, a during, and an after.

Before
Pre-meeting brief generated
Claude assembles email history, open commitments, project status, and suggested questions from all connected modules.
During
The meeting happens
You're informed going in. No scrambling. You can actually be present.
After
Import the transcript
Paste the transcript via /import-call. Commitments extract and link. Topics tag. The transcript connects to the calendar event. Relationship context updates.
Future
Full record, always accessible
Next time you meet Marcus, the brief includes what happened last time. The loop closes.

You asked who you're meeting.
It gave you the full picture.

One prompt, five minutes before a call. The brief assembled itself from everything SoY already had.

Your prompt
"Who am I meeting at 2pm and what should I know going in?"
Event: Q2 planning call
Attendee: Rebecca Chen
Duration: 45 min
Pre-meeting brief — assembled from SoY
Rebecca Chen, VP Product at Meridian. 8 meetings logged, relationship score 84/100. Last contact: 6 days ago (email, re: timeline).
You owe Send revised roadmap deck by end of this week
You owe Intro to the analytics team contact you mentioned on Jan 14
Feb 14 — she flagged the handoff timing. "Concerned about March 1."
Feb 10 — you sent the scope doc. No reply yet on section 3.
Feb 6 — scheduling thread.
3 decisions involve Rebecca: pricing model (Jan 12), timeline (Jan 28), team structure (Feb 3). Revisit on pricing is overdue by 11 days.
March 1 concern she raised. Whether you can deliver the roadmap deck before the call. The overdue pricing revisit.

Walk in informed. Every time.

Free during early access. Works with Claude today.