An agent on your
morning shift.
Pickle Jar Partners + Duvo. Reads the day's Pro Rata, drafts the emails you'd have written, renders a comprehensive Google Doc brief with public-link sharing, and emails partners the link by 8:31. Four iterations from first ship to live production this week.
Open the live run → See how it worksSix times faster mornings. Eight work-weeks back.
PJP — four partners, one office manager, no IT — runs the morning sweep as a team activity. Today: 90 minutes a day scanning newsletters and cross-referencing the CRM. With the agent: 15 minutes reviewing drafts and skimming the brief.
A short notification. A comprehensive Google Doc.
Partners get a short email at 8:31am with a 2-line summary and a Doc link. The Doc is the canonical artifact: drafts grouped by relationship with full bodies inline, watchlist with thesis-fit scores, full scoring of every mention, and negative-news watch flagged separately. Public link by default; falls back to domain or email-list sharing if workspace policy blocks public. Drafts also sit in Gmail Drafts ready to send. The relationship intelligence is in the details — Brex auto-flagged as competitive to Ramp before any draft gets sent; Linear and Mercury both score perfect 10/10 against the thesis.
The plain-text snapshot below is from an earlier run. Production now renders this content as a Google Doc with full draft bodies embedded — partners can read every proposed email inline before clicking into Gmail Drafts.
Plain-text brief from the live agent run. Drafts wait in Gmail Drafts for review and send.
Same agent. Thirty minutes of skill iteration.
First run had em-dashes everywhere and "Cheering you on" instead of a real CTA. We tightened the skill — no code change, no SOP rewrite, no rebuild — and re-shipped. Same morning. The kind of iteration that takes multiple days on Zapier or n8n.
One orchestrator. Three reusable skills.
Daily 8:30 trigger. Roughly fifteen minutes to set up. The orchestrator skill holds the workflow. Three helper skills handle the deep logic — email tone, thesis scoring, Google Doc rendering. All four are editable by the partner-of-record without touching code; each tightening compounds across every future agent that reuses them.
Three decisions that buy us reliability.
Matching is a rule, not an LLM.
LLMs hallucinate matches — "Notion" matched against the word "notion" in prose. Determinism is worth the brittleness. Better to miss than to misroute.
The skill and thesis are partner-editable.
The thesis lives in pjp_thesis.md. The matching and tone rules live in SKILL.md. A partner edits one file when their thinking shifts; the agent picks it up the next morning. No code, no redeploy.
Drafts only. Always.
Worst case: a partner deletes a draft. Five seconds of friction. We never trade the relationship for the click saved.
From one morning agent to a VC operating system.
Don't miss a deal in your mandate. Evaluate faster. Close faster. Report better. Same Duvo workspace, same skill family, more agents per quarter.
- Newsletter sweep
- Inbound deck triage
- Industry & competitor map
- LinkedIn signal monitor
- Cold-outreach drafter
- Thesis-fit scorer
- Pitch call notes
- Memo augmenter
- Reference-call notes
- Comparable round analysis
- Term sheet drafter
- Round structure modeler
- Side-letter comparison
- Cap table reconciler
- Portfolio weekly digest
- LP quarterly letter drafter
- IR response drafter
- Audit-ready run logs
What we built is a starting point.
PJP signs off on these decisions, not us. None of them require a long answer — just a direction.
Thesis sign-off
The pjp_thesis.md we wrote is our read of how PJP invests, not theirs. Stage range, priority sectors, the avoid list, the scoring rubric — all editable. Whatever you finalize is what the agent reads tomorrow morning.
CRM as Excel or Google Sheet
The brief said you track everything in Sheets. The file we received was an .xlsx. Worth confirming. Google Sheets unlocks something the .xlsx can't: the agent can write back. When a watchlist company scores 9 or 10, the agent can append it to the CRM as a new row with the news as the first note, and store proposed emails in a "drafts" column. Bidirectional CRM.
Who gets the morning brief
Right now the brief goes to a single inbox. All four partners plus the office manager every morning? One partner-of-record who triages and forwards? Different recipients on different days?
Where the drafts land
Default is straight into Gmail Drafts. Alternatives: a Duvo space, a shared Notion or Confluence page, or a Slack DM. Or, if we go with Google Sheets in #2, the drafts could live as a column in the CRM itself. Drafts are saved in the daily run audit log either way.
Cadence and timing
8:30am Prague seems right but happy to shift. Skip weekends? Skip US and Czech holidays, or run anyway? On a quiet day with zero CRM matches, send a "nothing today" note or skip the email entirely?
Newsletter sources on day one
Pro Rata is the obvious starter. The skill handles multiple sources without a redesign, so layering in Strictly VC, Term Sheet, or PitchBook Daily from day one is ten extra minutes of setup if those are already part of the partners' morning.
Source files.
Everything used to ship this — the deck, the skill, the thesis, the test newsletters.