CoreCMO

Agent directory · Orchestration

Proof Library Agent

The right reference at the right moment. Indexes every customer story, case study, reference contact, testimonial, ROI metric, and public quote by industry, persona, deal size, use case, and objection it disarms.

Who is this agent
Identity card
NameProof Library Agent
RoleCustomer-proof retrieval and curation: the proof-on-demand layer
OwnerHead of Customer Marketing
Reports toVP Marketing (with CRO co-oversight for sales-facing proof)
Versionv0.5 (supervised)
SurfaceClaude Project + Postgres (vectorized proof corpus + structured metadata)
Output target/proof-library/index.json (the corpus) + per-request retrievals to requesting agent / human
Review cadenceWeekly stale-proof sweep; monthly coverage gap analysis; quarterly proof refresh program
Mission
Treat customer proof as a structured corpus, not a folder of PDFs. Index every story, case study, reference, testimonial, ROI metric, and quote by the dimensions that matter (industry, persona, deal size, use case, objection it disarms, contract status). When a deal needs a reference, an AE needs an ROI stat, a PR pitch needs a customer quote, or a board deck needs a case study: the right proof arrives in seconds with consent, contract status, and freshness verified.
Goals & KPIs the agent moves
Leading indicators: the agent controls these
Time-to-proof for an AE request< 60 seconds from query to top-3 matched proof
Reference contact overuse prevention (no contact asked > 4 times/year)100%
Lagging indicators: downstream outcomes with review triggers
Coverage of new closed-won cohorts > $50K added to library within 60 days. Trigger: 2 consecutive months below 60% pages the Head of Customer Marketing for intake-pipeline review.≥ 80%
AE-reported usefulness of returned proofs (quarterly survey). Trigger: usefulness score below 7/10 for a quarter pages the VP Marketing for taxonomy and tagging review.≥ 8/10
What it does
Task list
  1. Real-time Receive retrieval requests from requesting agents (Web Operations, Performance Marketing, ABM Account Researcher, PR Comms Agent, etc.) or humans (AEs, PMM, exec). Return top-3 matched proofs in < 60 sec.
  2. Daily Honor the reference contact ask-rate cap. When an AE requests a reference contact, check the contact’s ask count this year. Block + suggest alternative if over cap.
  3. Daily Watch the closed-won opportunity stream. Flag deals > $50K as reference candidates. Draft the “add to library” intake request to the AE.
  4. Weekly Stale-proof sweep. Mark any proof > 18 months old as stale; pull from active retrieval pool; route to Customer Marketing for refresh or retirement.
  5. Weekly Coverage gap analysis. Which (industry × persona × use case) cells have no proof? Surface gaps to Customer Marketing for active sourcing.
  6. Weekly Permission + contract status check. Verify every active-pool proof still has signed consent + current contract status. Pull anything that’s gone red.
  7. Monthly Retrieval analytics: which proofs were used most? Least? By which agents/humans? Surface underused gems + retire dead weight.
  8. Monthly Compile the proof refresh queue: top 10 candidates for new ROI metrics, updated quotes, or video re-shoots.
  9. Quarterly Proof program review with Head of Customer Marketing + CRO. Adjust the schema, the retrieval-priority weights, the ask-rate cap.
  10. Event When the Win/Loss Agent surfaces a new objection theme, search the library for proof that disarms it; if no match, flag a coverage gap.
  11. Event When PR Comms Agent needs a quote for a press push, retrieve the best-matched + consented quote within 5 minutes.
Schedule grid
TaskFrequencyDurationOutput goes to
Real-time retrievalContinuous (on-demand)< 60 sec per requestRequesting agent / human
Daily ask-rate cap enforcementContinuousInline with each retrievalCustomer Marketing (when cap blocks a request)
Daily closed-won candidate flaggingDaily 09:00~5 minCustomer Marketing + closing AE
Weekly stale-proof sweepWeekly Mon 08:00~30 minCustomer Marketing
Weekly coverage gap analysisWeekly Mon 08:30~20 minCustomer Marketing + PMM
Weekly permission auditWeekly Fri 16:00~15 minCustomer Marketing + Legal if red
Monthly retrieval analyticsMonthly 1st~45 minHead of Customer Marketing + VP Marketing
Quarterly proof program reviewQuarterly Q-1 days~2 hoursHead of Customer Marketing + CRO
Triggers

Scheduled (cron-style):

ScheduleWhat it runs
0 9 * * *Daily closed-won candidate flagging
0 8 * * 1Weekly stale-proof sweep + coverage gap analysis
0 16 * * 5Weekly permission audit
0 9 1 * *Monthly retrieval analytics

Event-driven:

EventWhat it runs
Retrieval request from any sourceReturn top-3 matched proof within 60 sec with consent + freshness verified
Closed-won opportunity > $50KFlag as reference candidate; draft intake request to closing AE within 24 hours
Win/Loss Agent surfaces a new objection themeSearch library; surface matches or flag a coverage gap
Reference contact reaches ask-cap (4 asks/year)Block further requests; alert Customer Marketing to grow the bench
Customer contract status changes (renewal, downgrade, churn)Update proof record; pull from active pool if churned
Who it works with
Inputs
SourceTypeCadenceRequired?
Operator Brief (Sections 1, 2, 3, 6)MarkdownRead on schema updatesRequired: ICP + personas define retrieval dimensions
Case study corpus (existing PDFs / docs / videos)Files + metadataOn ingestion + on refreshRequired: the source corpus
Customer reference intake forms (consent + ask preferences)JSON / AirtableOn addition + quarterly reviewRequired
Closed-won opportunity streamCRM webhookReal-timeRequired: sources new proof candidates
Account Intel Hub recordsJSONLive queryRequired: informs ‘similar customer’ retrieval matching
Customer Success health signals (Gainsight / ChurnZero)APIDailyRequired: ensures references are still happy customers
Win/Loss Agent themesMarkdownPer-interviewRequired: objection coverage analysis
Outputs
OutputFormatTarget pathAudience
Proof retrieval response (top-3 matched)JSON + Markdown bundleReturned inline to requesterAEs + every requesting agent
Closed-won intake requestMarkdown + Slack DMSlack DM to closing AE + /proof-library/intake-queue.mdClosing AE + Customer Marketing
Weekly stale-proof reportMarkdown/proof-library/stale-YYYY-WW.mdCustomer Marketing
Weekly coverage gap mapMarkdown table/proof-library/gaps-YYYY-WW.mdCustomer Marketing + PMM
Weekly permission auditMarkdown/proof-library/permission-audit-YYYY-WW.mdCustomer Marketing + Legal if red
Monthly retrieval analyticsMarkdown + chart bundle/proof-library/analytics/YYYY-MM.mdHead of Customer Marketing + VP Marketing
↑ Upstream: agents/sources that feed this one
  • Customer Marketing Agent. Maintains the customer reference roster + consent records the orchestrator depends on.
  • Account Intel Hub. Provides ‘similar customer’ matching for retrieval queries (industry, ACV, persona overlap).
  • Win/Loss Agent. Surfaces objection themes that need proof coverage.
  • Revenue Attribution Engine. Confirms which customer stories have measurable ROI to cite.
  • Signal Router. Routes closed-won + contract-status-change events to the orchestrator.
↓ Downstream: agents/humans that consume its output
  • AEs (humans). Primary consumer: query the library for references, ROI stats, and customer quotes mid-deal.
  • Web Operations Agent. Pulls case study cards + customer logos for landing pages.
  • Performance Marketing Agent. Pulls customer quotes for ad creative.
  • ABM Account Researcher. Pulls similar-customer references for ABM campaign personalization.
  • PR Comms Agent. Pulls customer quotes + executive quote candidates for press pushes.
  • Field Marketing Agent. Pulls customer-speakers + on-site case study material for events.
  • Executive Comms Agent. Pulls aggregated ROI metrics + customer narratives for board decks.
Human escalation paths
Trigger conditionEscalate toWithin
Reference contact reaches ask-cap; no alternative in the same cellHead of Customer Marketing + CRO< 24 hours (bench gap)
Customer contract status changes to churned with active proof in libraryCustomer Marketing + LegalImmediate (pull from active pool)
Coverage gap on a critical objection theme persists 30+ daysHead of Customer Marketing + PMM + CROSame business day (program-level gap)
Retrieval latency p99 > 60 sec sustained 24hDirector of MarOps + Head of Customer MarketingSame business day
Permission audit flags any proof without signed consentCustomer Marketing + LegalImmediate (pull from active pool)
How to build it
System prompt
You are the Proof Library Agent for [COMPANY]. YOUR JOB Treat customer proof as a structured corpus. Index every story, case study, reference, testimonial, ROI metric, and quote by industry, persona, deal size, use case, and objection it disarms. Return the right proof in seconds with consent, contract status, and freshness verified. INPUTS (always read in this order) 1. /operator-brief.md - ICP + personas inform retrieval dimensions 2. /proof-library/index.json - the structured corpus 3. /proof-library/consent.json - permission + ask-cap status per reference 4. /accounts/<requesting-account-id>.json - context for similarity matching 5. The retrieval request itself (query + filters) OUTPUTS - Inline retrieval response (top-3 matched, ranked) - /proof-library/intake-queue.md (new proof candidates) - /proof-library/stale-YYYY-WW.md (weekly) - /proof-library/gaps-YYYY-WW.md (weekly) RULES 1. Every returned proof shows: source, freshness (date last refreshed), consent status, contract status, ask count this year. 2. Honor the ask-cap (4 asks/contact/year). Block + suggest alternative. 3. Never return a proof from a churned customer in active retrieval. 4. Never invent an ROI stat. Cite source artifact or drop the claim. 5. When no proof matches the request, return "coverage gap" with the specific (industry x persona x use case) cell that's missing. 6. Honor freshness: anything > 18 months is stale; pull from active pool. ESCALATION - Reference at ask-cap with no alternative: Head of Customer Mktg <24h. - Churned customer with active proof: pull immediately, page Legal. - Critical objection coverage gap >30 days: Head + PMM + CRO.
Tools & integrations
Platform / toolUsed forRequired?
Claude Project + Postgres (with pgvector for semantic search)Vectorized corpus + structured metadataRequired
Airtable / Notion (for the structured reference roster)Consent + ask-cap trackingRequired
Salesforce / HubSpot APICustomer contract status + closed-won streamRequired
Gainsight / ChurnZero / Catalyst APICustomer health (don’t reference unhappy customers)Required if CS platform in use
Slack APIAE notifications + intake requestsRequired
DAM (Brandfolder / Bynder / Frontify)Source case study assetsOptional
Video review platform (Wistia / Vimeo) APIVideo testimonial metadata + view trackingOptional
Guardrails: what it must not do
  • Never share a customer quote, name, or logo without signed consent and current contract status.
  • Never exceed the ask-cap on a reference contact. Hard gate.
  • Never return a proof from a churned customer in active retrieval. Quarantine + Legal review.
  • Never invent an ROI metric. Source artifact or no claim.
  • Never share a customer’s identity with a competitor’s prospect: check the ‘do not reference to’ flag on each record.
  • Honor the customer’s preferred reference cadence (some say ‘quarterly max’, others ‘monthly OK’).
  • Never embed customer data into LLM training data via the retrieval cache: consent doesn’t extend to model training.
Evals + hallucination defense

Evals: output quality checks:

  1. Retrieval relevance. Weekly: AE rates 5 retrievals 1–5 for relevance. Target average ≥ 4.0.
  2. Latency p99. p99 retrieval latency. Target < 60 sec.
  3. Coverage breadth. Monthly: count of populated (industry × persona × use case) cells vs. total possible. Target ≥ 70% coverage.
  4. Ask-cap compliance. Monthly audit: was any reference asked > 4 times in trailing 12 months? Target zero violations.

Hallucination defense: specific checkpoints:

  • ROI stats must trace to a specific case study, contract, or customer-provided artifact. No paraphrased numbers.
  • Customer quotes must be verbatim from a signed-consent source (interview transcript, video, written testimonial).
  • Reference contact data must trace to the structured reference roster: never fabricated.
  • Customer logo usage must trace to a current logo-use agreement in the consent record.
  • When the agent isn’t sure a proof is fresh / consented / accurate, it surfaces uncertainty rather than return the proof.
Maturity curve + first-run checklist
v0.1: Manual-assistLibrary is indexed; AEs query manually via search. No automated retrieval. Useful from day 1 to replace the “Slack the team for a customer quote” pattern.
v0.5: SupervisedAutomated retrieval on. Ask-cap enforcement live. Weekly stale + gap reports. Customer Marketing reviews edge cases. Default ship state.
v1.0: Semi-autonomousAfter 90 days of clean evals, the agent can auto-archive stale proof and auto-pull churned-customer proof without manual review. New proof additions still human-approved.

First-run checklist: 5 steps from spec to running agent:

  1. Stand up the vectorized corpus. Ingest existing case studies, testimonials, and customer artifacts. Tag each with the dimensions schema.
  2. Author the structured reference roster in Airtable / Notion. Add every consented customer with ask-cap, preferences, and current consent date.
  3. Wire Salesforce + CS platform for contract-status + health signals. Verify the daily sync.
  4. Run the agent in shadow mode for 2 weeks. AEs query; you compare the agent’s top-3 to what they actually used. Tune retrieval weights.
  5. Turn on live mode. Subscribe Customer Marketing to the weekly stale + gap reports. Log every retrieval in /proof-library/agent-log.md.

Back to the AI Operating Model