Assembles one account's story into reusable modules, then pours it into the Pitch Card and its outreach package.
Account Story→Modules→Formats
Digital · live
Pitch Card (PDF + microsite) · Email
Physical · designed
Handwritten note · Print card · Swag
Workflow 01 · The Vault
Five steps, live today
The context engine behind Knowledge. Any raw input, meeting audio, a note, a file, or a link, is captured once and turned into structured, per-account intelligence.
The rule everything hangs on: the raw original, whatever form it came in, is the source of truth. Transcripts, tone reads, and structured facts are all derived, and can be re-made any time as models improve. Nothing important lives only inside a tool the operation doesn't own.
I
Capture
A field mic records meetings and syncs when docked; a note, file, or link drops into the same inbox.
One passive touch
II
Archive
The raw file lands in cloud storage the operation owns, and stays there. Everything downstream can be rebuilt from it.
Automatic
III
Process
Audio gets transcription with speaker separation, plus tone analysis (volume, pitch, pace, pauses per speaker); text and files skip straight to structuring.
Automatic
IV
Structure
The AI layer turns the input into decisions, action items, risks, and quotes, tone read included when there is one, then stores a readable note and a database record on the account.
Automatic
V
Review
A person reviews the structured note and decides what to act on. Nothing auto-sends.
Human decision
What audio adds
Tone & intent
Excited versus just polite, the pause on price: audio keeps what a transcript flattens, and the AI layer can hear it.
Clean speakers
Real speaker separation on good audio beats a notetaker's guess at who said what.
Reprocess forever
Any raw input, recorded or written, can be re-run through better models later, or mined for questions no one asked yet.
Capture, storage, transcription, tone, and structuring are live today. Drafting outreach straight from a meeting or note is planned, not built.
Workflow 02 · Enrichment
A brief becomes a fully written account
Turns one Glean research brief into every enriched field on an account: Sales Intel plus the full pitch-card field set. Nothing invented, blank over guessed.
Two inputs, one merge
The Glean brief is the primary input. The Vault's own meeting notes for the same account (matched by name) are the second. Every fact carries its real source: "(S2)" for the brief, or "(Brain: meeting, date)" for the Vault.
Coverage gate, before anything writes
→
Auto-routed by the brief itself
A filename like GLEAN_[account ID]_city-of-example, or a "UNIQUE ID" header line, lets the brief self-identify. No need to open the right account first.
→
All 9 Glean sections scored
Identity, challenges, security posture, LE relationships, geography, events, budget, Flock relationship, leaders. Each reads as substantive, thin, or not found.
→
Only a real entity mismatch fails closed
If the brief isn't actually about this account, zero fields write and an Action Item is filed. A thin or not-found section on an otherwise-matched account no longer blocks: the same Glean prompt already asked for it, so a follow-up query would just ask again.
Field writes
Sales Intel plus every PC_ pitch-card field, following the real prompt spec: exact character caps, Title Case taglines, the connected-platform story, feature rows. Approved pools are a hard gate. Products come verbatim from the approved 20; quotes and stats are chosen only from the Brand tables, never from model prose.
Writes land in
The account's Accounts row (by field name) and its Joe-Sheet-Mirror row (by field id, created if missing).
Verification
Every capped field is char-counted and trimmed at a word boundary if it runs long. A field-by-field checklist ships as a report, logged in the exceptions ledger. A data sync, a targeted render, and image mining (if the account has none yet) all dispatch automatically.
Live today, manually triggered: Kim drops a brief on an account's drawer, or through the Vault composer. Not on a schedule.
This is a different question from Methodology, which is about categorizing and prioritizing which accounts get researched at all. Enrichment is what happens once a brief already exists for one.
Workflow 03 · Strategy & Pipeline
What runs today
The same account data and knowledge layer also drive territory strategy, deal pipeline, reporting, and follow-up work.
Territory & pipeline
→
Territory plan
A 7-state territory plan: market size, marquee accounts, named champions, and the specific play per account.
Live
→
Deal pipeline
Deal-level opportunities from the CRM (stage, win probability) plus each account's own production stage, from loaded to sent.
Live
→
CRM write-back
The system reads the CRM today; pushing updates back automatically is not built.
Not built
Reporting & follow-ups
→
Reporting
A nightly data-health audit of the account universe and a one-page end-of-day status report, both on the dashboard.
Live
→
Meeting-derived action items
Every processed meeting produces structured decisions, action items, and risks, tied to the account and listed on the Action Items tab.
Live
→
Auto-drafted follow-ups
Turning a meeting's action items into draft emails or a triggered render, queued for review, never auto-sent.
Not built
→
Proposal & meeting-prep documents
A tailored proposal once an opportunity is live, and prep notes before a call, from the same account data.
Not built
Workflow 04 · Outputs
Account Story → Modules → Formats
The system enriches an account once into a single Account Story. It assembles that into reusable Modules (Cover · Products & Capabilities · Trust · Proof · Agencies), then pours it into many Formats. Digital is live today: the Pitch Card generates its PDF and its microsite together from one account record. Physical is designed, not built: the plan is physical shipping first, with digital firing on a delivery signal, so the touch lands with weight instead of arriving all at once.
Digital package
→
Pitch Card
One output, two formats, generated together from the same account record: a 4-page PDF and a browsable HTML microsite with deep-dive product pages, ridership stats, testimonials, and a booking CTA.
Live
→
Email outreach
Bundles the PDF attachment + microsite link. Rep-attributed, agency-type tailored. Would fire on the Delivered signal once physical exists.
Template ready
Physical package
→
Handwritten note
Letterhead with hand-script body + booking QR. Service-printed, signed in ink.
Not built
→
Print card
Production-printed variant of the Pitch Card PDF, trim, bleed, mailer-friendly weight. Sits behind the note.
Not built
→
Swag / goodie
One fixed, non-perishable item, kitted in the same box. Same vendor across all accounts.
Not built
The review, quality before send
Before a card goes out, an automated 10-stage review produces a ranked punch list for human sign-off. Advisory only, a person applies the fixes.
Substance
1Factual / Account-Fit
2Brand
3Stats & Claims
→
Message
4Messaging & Value
5Copy / Grammar
→
Visual
6Typography
7Image Quality
8Layout & Spacing
→
Integrity
9Links & Consistency
⟶
Final pass
A lead-editor pass synthesizes all nine into a single ranked punch list.