Founders close candidates on the slowest part of the funnel: the personal pitch. A Dock candidate-pitch workflow lets an attributed agent read the candidate in Lever, pull the role brief from Notion, and assemble a draft deck in Pitch. The hiring manager reviews, and the founder sends. Every draft carries the agent identity, the reviewer, and pointers back to the source. See the Dock for founders pillar for the cluster.
Lever, Notion, and Pitch 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 architecture mirrors what we describe in Cloud 2.0 for product teams.
The Dock surface: candidate pitch queue
| Candidate | Role | Lever pointer | Notion brief | Pitch draft | Agent | Hiring manager | Status |
|---|---|---|---|---|---|---|---|
| Priya R. | Founding PM | lever://opp/8821 | notion://page/role-pm-001 | pitch://deck/pm-priya-v2 | hiring-pitch-agent-v3 | govind | Approved, sent 2026-05-29 |
| Marcus T. | Staff eng | lever://opp/8847 | notion://page/role-eng-014 | pitch://deck/eng-marcus-v1 | hiring-pitch-agent-v3 | flint | Revise: tighten comp story |
| Aisha K. | Head of design | lever://opp/8902 | notion://page/role-design-002 | pitch://deck/design-aisha-v1 | hiring-pitch-agent-v3 | sarah | Pending review |
Each row is a decision the agent made and a human signed. The pointer columns let any reviewer re-fetch the Lever opportunity or Notion brief. The agent identity column lets an audit trace which version produced which draft, per the agent collaboration primer.
The workflow
- New Lever opportunity moves to stage "founder pitch." A webhook lands in Dock.
- The pitch agent re-fetches the candidate from Lever and the role brief from Notion.
- The agent drafts a four-slide deck in Pitch: why this candidate, why this role, first 90 days, comp and equity.
- Dock writes a row with the Pitch pointer, the agent identity, and the assigned hiring manager.
- The hiring manager opens the draft and either approves, requests a revision, or rejects.
- On approval, the founder gets a Slack ping with the deck link, sends, and marks sent in Dock.
The agent never sends. The founder sends. The hiring manager reviews. Three attributed actors, three rows of provenance. Same shape as the screening workflow in how to do hiring with AI in 2026.
Why this matters
First Round Review reminds founders that "the first 100 people you hire will define the next 200," which is why personalized pitch quality compounds. (First Round Review, "Give Away Your Legos") LinkedIn's talent solutions resource library makes the same point about personalized outreach versus templated blasts. (LinkedIn Talent Solutions)
A pitch agent that hallucinates a candidate's prior role is worse than no agent. Dock's row-per-decision pattern means every claim maps to a Lever or Notion record the reviewer can open. When a draft goes wrong, the team knows which agent version produced it. That is the agent identity discipline applied to founder hiring.
CTA
Stand up the candidate-pitch queue in your Dock workspace today. Wire the Lever webhook, point the agent at your Notion role brief, and route to your hiring manager.
FAQ
Q: Does the agent send the pitch directly to the candidate? A: No. The agent drafts. The hiring manager reviews. The founder sends from their own account. Dock records the chain.
Q: What if the role brief in Notion changes mid-draft? A: The agent re-fetches on every draft cycle. Notion is the source of truth for the brief. Dock stores the interpretation and the pointer.
Q: Can multiple agents draft for the same role? A: Yes. Each draft row carries its own agent identity. The hiring manager picks the strongest draft and rejects the others. See agent identity.
Q: What audit trail does a row carry? A: Lever pointer, Notion pointer, Pitch deck pointer, agent identity and version, hiring manager who approved, founder who sent, and a timestamp on each step.
