Founders write fast and review faster. The agent drafts a board update or investor memo in a Google Doc, but the version that ships needs an executive sign-off and a record of who approved which framing. Dock holds the narrative interpretation, the reviewer, and the timestamp. Google Workspace and Notion stay the source of truth for the raw text. This is the founder workflow for shipping high-stakes docs without losing the audit trail.
Google Docs and Notion 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.
Surface: Exec review queue
| Doc | Type | Agent draft | Recommended framing | Exec reviewer | Status | Signed off |
|---|---|---|---|---|---|---|
| Q2 Board Update | Board memo | drive.google.com/d/1aBc | Lead with retention, defer churn root-cause to appendix | gv@ | approved | 2026-05-28 14:02 |
| Series B Teaser | Investor memo | notion.so/series-b-teaser | Anchor on ARR multiple, drop TAM slide | gv@ | revisions | 2026-05-29 09:41 |
| All-hands script | Internal | drive.google.com/d/2dEf | Open with the layoff, then the runway extension | coo@ | approved | 2026-05-30 07:15 |
Every row links back to the Google Doc or Notion page. The agent does not store the draft text. It stores the framing decision, who reviewed, and when the green light landed.
Workflow: Google Doc to narrative draft to exec sign-off
The founder drops a raw data dump into Google Docs (metrics, customer quotes, runway math). The agent reads the doc via the Drive API, proposes a narrative arc as a Dock row, and waits. The exec opens the queue, scans the recommended framing, and either approves or sends back revisions. On approval, the agent writes the polished version back to a new Google Doc and links it. On revision, the exec edits the framing field directly in Dock and the agent redrafts. The decision lives in Dock. The prose lives in Google. The pointer ties them together.
This is the collaboration pattern that lets one founder review six memos in twenty minutes. The framing is the bottleneck, not the typing.
Why it matters
Bain's research on the Founder's Mentality shows that scaling founders lose grip on the front line first. Narrative drift, not bad data, is what makes a board update land wrong. When the agent owns the keyboard and the exec owns the framing, the founder stays close to the message without writing every word. Dock records who chose which angle, which matters six months later when the board asks why a number was framed one way and not another.
The same architecture applies across product, research, and any function where an agent drafts and a human signs off. The platform holds the artifact. Dock holds the judgment.
Set up the founder review queue.
FAQ
Does the agent edit my Google Docs directly? Only when you approve a framing in Dock. The agent reads freely via the Drive API, but writes only after sign-off. Agent identity is scoped per founder.
What if I want to skip Dock and just edit the doc? You can. Dock catches up on the next agent read and logs the unattributed edit as a human override. The audit trail stays intact.
Does this work with Notion pages too? Yes. The pointer field accepts any URL. The agent uses the Notion API for reads and the Google Docs API for writes, or vice versa, depending on where the final artifact lives.
How is this different from Google Docs comments? Comments live inside one doc. Dock holds framing decisions across every doc the agent drafts, with a single queue for the exec to scan. See agent audit and compliance for the full record model. Google Workspace pricing and feature tiers are documented at workspace.google.com.
