Client meeting prep eats partner time. Someone pulls last quarter's deck from Notion, scans the Calendly invite, and starts a Google Doc at 10 p.m. Dock runs that loop as one workflow. An agent reads the Notion history and Calendly agenda, drafts a prep brief, posts it to a Dock row, and the named account team approves before the call.
Notion, Calendly, and Google Workspace stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
The Dock surface
One workspace, called Client Meeting Prep. Each row is one upcoming meeting.
| Meeting | Calendly link | Notion client page | Draft brief | Drafted by | Approver | Status |
|---|---|---|---|---|---|---|
| Northwind QBR, Jun 3 | cal.ly/nw-qbr-jun3 | notion/northwind | docs/nw-qbr-prep | agent:prep-bot | partner:r.okafor | Approved 17:42 UTC |
| Sterling roadmap, Jun 4 | cal.ly/sterling-rm | notion/sterling | docs/sterling-prep | agent:prep-bot | mgr:l.chen | Awaiting review |
| Halberd kickoff, Jun 5 | cal.ly/halberd-kick | notion/halberd | docs/halberd-prep | agent:prep-bot | partner:s.gupta | Edits requested |
The row is the single artifact. Open it and you see what the agent read, what it drafted, who signed off.
One worked workflow
Calendly fires a webhook 36 hours before a confirmed meeting. The prep agent reads the invite, pulls the matching Notion client page (history, open issues, last meeting notes), and re-reads the live Google Doc for partner annotations since the last call. It drafts a brief: attendees and roles, three discussion threads, two risks, one recommended ask. The Dock row updates with the doc link, source pointers, and the agent's name. The account team owner gets a Slack ping. The approver reads the brief, edits in Docs, and marks the row Approved. If they mark Edits requested, the agent re-reads the doc, incorporates the edits, and re-submits.
Why it matters
Source Global Research tracks client expectations in professional services and finds that buyers reward firms who show preparation and continuity across engagements. Bain argues that the quality of every client interaction compounds into retention. Prep is where that compounding starts. The current pattern hides who did the prep, what they read, and which version went into the room. Dock makes the prep an attributable artifact. The agent reads and drafts. The named account team owns the decision.
See the consulting and agencies pillar for the full surface map. The research workflow applies the same architecture to primary-source work, and the design workflow handles creative review. Attribution mechanics come from agent identity; rotation from the agent identity lifecycle. The AI meeting prep pattern explains why the row is the unit of work.
Start one cluster
Pick your three highest-stakes accounts this quarter. Run prep through Dock for those. Compare the briefs the partner walked in with against the ones written at 10 p.m.
FAQ
Does the agent edit the Notion client page? No. Notion stays the source of record. The agent reads and writes a separate brief. If the partner wants something captured back in Notion, they do it after the meeting.
What if the Calendly attendee list changes the morning of? The agent re-fetches the invite when the row is opened. Fresh API read, fresh attendee list. The brief gets a delta note at the top.
Can two agents draft the same brief? The row holds one drafted-by identity at a time. A second agent can be assigned as reviewer, with its own row field, but the draft itself is owned by one named agent.
How do we audit a brief after the engagement closes? Open the row. It shows the agent identity, source pointers, approver, and timestamps. The Google Doc revision history covers human edits.
