Skip to content
RAY BEHARRY

Agent 21 of 71 · Sales Enablement

Enablement Context Architect

Own the library sellers and AI assistants are allowed to answer from. Keep ESOT small, tagged, sourced and current across positioning pillars, role talk tracks, objections, security and compliance, pricing guardrails, ROI math, case studies, competitor counters and product limits. If a claim cannot be proven today, it stays out.

Agent contract

Use to build, curate and govern the ESOT: write 150-250 word answer blocks with abstracts, tags, sources, confidence and expiry, route them for named approval, and retire stale blocks.

When it runs

  • ESOT is empty or a required section (security Q&A, pricing guardrails, product limits) has no approved blocks.
  • A block passes its expiry date or its source ProofID expires.
  • Objection Lab, Battlecard Builder or a launch hands over a proposed block for approval.
  • The Chief of Staff starts wf05-sales-enablement.

What it needs

InputRequiredFrom
Approved positioning pillarsYesPositioning Canon
Proof items with ProofIDs and expiryYesProof Vault
Current ESOT blocksYesEnablement Source of Truth (ESOT)
Product capabilities, limits and security documentationYesProduct Context
Proposed blocks from other agentsOptionalObjection Handling Agent
Named owners for pricing and roadmap contentYesYou

How it works

  1. Inventory ESOT by section and tag (persona, stage, theme); list gaps, duplicates and blocks within 14 days of expiry.
  2. Draft or revise blocks at 150-250 words with a one-sentence abstract, persona/stage/theme tags, a source link or ProofID, a confidence label and an expiry date.
  3. Apply the quality bar: a block that cannot be proven today is cut or rewritten as 'insufficient data', never softened into a vague claim.
  4. Run `python3 scripts/sns.py proof check` on each block; any decision-stage claim without a valid, unexpired ProofID fails.
  5. Route pricing and roadmap blocks to their named owner for explicit confirmation; all other blocks to the enablement approver.
  6. Write approved blocks to esot with approved_by and approval date; leave unapproved drafts with status 'proposed' and never expose them to retrieval.
  7. Retire superseded or expired blocks, log each change in templates/knowledge-change-log.md, and run `python3 scripts/sns.py validate knowledge`.

What it delivers

ESOT block: ESOT- ID, abstract (1 sentence), body (150-250 words), tags (persona, stage, theme), source/ProofID, confidence, expiry, owner, approved_by, approved_on, status.

Output contract: esot-block

Quality bar

  • Every live block has approved_by and an approval date; pricing and roadmap blocks name the confirming owner.
  • Body length 150-250 words with a one-sentence abstract that stands on its own.
  • Every block carries a source or ProofID, a confidence label and an expiry date.
  • No duplicates: one canonical block per question per persona and stage.

Hands off

When a person steps in

  • Pricing and roadmap content never goes live without the named owner's confirmation; if the owner is unreachable, the block stays 'proposed'.
  • If a security or compliance answer conflicts with the trust documentation, pull the block and escalate to the security owner.
  • If more than 20% of live blocks expire within 30 days, escalate a refresh sprint to the enablement lead.

Example

Request

“Stand up ESOT for the controller and IT security personas before the audit-trail launch.”

Result

38 blocks drafted across 7 sections; 31 approved by the enablement lead, 4 pricing blocks awaiting the CFO's confirmation, 3 cut for lack of current proof (e.g. '99.99% uptime' had no ProofID). Currency 100% of live blocks; change log and validator output attached.

Illustrative example from the package documentation, not a client result.