Sales

Use this section to prepare a buyer conversation, find the record behind a claim, or turn what you learned in the field into reviewed, reusable sales knowledge.

The system helps answer three questions before every conversation:

1. Who are we speaking to?
2. Which problem should we test?
3. What are we allowed to say, prove, and ask next?

Start with what you need

I need to…	Start here	You will get
Prepare for a buyer conversation	Audience profiles, then the communication cheat sheet	The relevant problem order, audience framing, and call technique
Qualify an account or choose a motion	Markets, verticals, and personas	The smallest reusable scope for the account and contact
Check whether a claim is usable	Competitors, problems, solutions, and proof	The canonical record, its status, evidence, limits, and prohibited claims
Capture a call note or field observation	Authoring workflows	The right path from raw input to human review
Create or update a sales asset	Authoring workflows	The required source update, validation, approval, and regeneration steps
Understand how the system is governed	Sales introduction	The authority model, authoring rules, and complete document map

How the system works

Market + vertical + persona
          ↓
     Audience binding
          ↓ selects and orders
       Competitors
          +
       Problems → Solutions → Proof
                                  ↓
                         Generated call sheet

Field learning → Inbox → Review → Canonical update → Regenerate

The catalogs define reusable scope. An audience binding selects which problems apply to a precise segment and persona. Problems link to solution mechanisms; solutions link to bounded proof. Generated call sheets render that approved chain for execution, but never become a source of truth.

Before you use any claim

• A match is not proof. Market, vertical, title, and signal data help route an account; they do not establish that the account has a problem.
• Check the record, not just the page. Fenced YAML is authoritative when it disagrees with prose. The weakest source status controls what a generated asset may say.
• Ask before asserting. Treat unverified patterns as hypotheses and render them as questions until account evidence confirms them.
• Change the source, then regenerate. Do not hand-edit an enriched audience profile or generated call sheet. Use the authoring workflows to update the owning record.

New to the sales library?

Read the sales introduction for the full mental model, then open the audience list to see how a target selects canonical problems. If you are contributing content, start with the workflow router; you do not need to choose a schema or workflow ID first.