PEAK 2026

KeyReply workflow — internal

PEAK capture → enrich → push

Snap biz cards by day. Cowork does the rest overnight.
📸
PHASE 1 — ON THE FLOOR

Capture

  • Snap biz card photo (iPhone camera)
  • Hit share → Save to shared iCloud folder PEAK-2026
  • Optional: re-name with tier — A-, B-, C-
  • Takes ~5 seconds per contact
  • You, Callum, Eric all drop into same folder
🌙
PHASE 2 — OVERNIGHT

Cowork processes

  • You tell Cowork: "run PEAK nightly"
  • Reads all new photos in folder
  • Vision model extracts fields
  • Enriches via Apollo (title, LinkedIn)
  • Matches to PEAK target list
  • Drafts personalized follow-ups
🎯
PHASE 3 — MORNING

Everywhere, automatically

  • HubSpot: contact + company + deal
  • Locksmith: record via your API
  • Slack digest to you, Callum, Eric
  • Gmail drafts (one per A-tier)
  • Daily CSV backup in the folder

The pipeline Cowork runs overnight

1. INGESTScan ~/iCloud/PEAK-2026/ for new photos since last run
2. OCRClaude vision extracts: name, title, company, email, phone, booth #
3. MATCHCross-reference with your 25-card flashcard list — pull matching pitch angle, pain, opener
4. ENRICHApollo/Clay lookup — confirm title, add LinkedIn URL, company size, funding
5. WRITEHubSpot create/update (contact + company + deal in "PEAK 2026" pipeline stage)
6. WRITELocksmith POST — your internal tool (API TBD — I'll adapt once you share the schema)
7. NOTIFYSlack digest + personalized follow-up email drafts

What each tool gets

HubSpot
Contact + Company + Deal in "PEAK 2026" pipeline. Notes: tier, pain, pitch, booth #.
Locksmith
Whatever schema it expects — adapter is a stub until you show me the API.
Slack
Morning digest — "yesterday you met 7 contacts, here are top 3 to follow up today."
Gmail drafts
Personalized "great meeting you" drafts, one per A-tier contact. Referenceses pain point discussed.
Shared CSV
Daily roster written to the folder so everyone has offline lookup.

What I need from you before building

Why this wins vs. a SaaS business-card app: everything stays in your toolchain, the follow-up drafts reference the actual conversation (via your notes) instead of generic templates, and it matches captured contacts against the 25-target flashcard roster so high-priority meets don't slip through the cracks.
Minimum viable v1 (buildable tonight): folder → OCR → HubSpot push → Slack digest. That gets you through Tuesday. Locksmith + enrichment + email drafts layer in Wednesday/Thursday.