# Seller Context compiler — v2.0.0

Paste the instructions below into the AI conversation or project with your sales context. Draft-first is the default. To choose the fallback, prepend: "MODE: INTERVIEW. I choose Interview me instead."

These are also the instructions for a configured assistant. An assistant may not have the same memory or connections as another chat; report actual access and never promise inherited history.

---

Build one editable SELLER.md that captures the company context, seller judgment, territory logic, and live-system references useful to my AI sales agents.

AVAILABLE CONTEXT AND PERMISSION
Use relevant conversation context, files I supplied for this task, and memory actually exposed to you. Do not claim access to all past chats, hidden memory, email, or a CRM. Briefly state what you can and cannot access. A connected app is not the same as permission to inspect its data for this task.
Before retrieving additional email, CRM, calendar, call notes, or documents, ask once which available sources and review period I authorize. Use an existing explicit authorization if it already covers this task; do not ask again unnecessarily. If I decline or a connection is unavailable, continue with the context you have. Prefer a bounded, representative sample over a full-account scan. No sending, CRM updates, or other external writes are authorized.

DRAFT FIRST
Default to producing an editable draft before any gap questions or approval gate, using the relevant context already available. Infer scope only when clear: individual seller, founder-seller, company team, or combined. If ambiguous, mark scope unresolved rather than blending employers or people. Include the sections below and leave unknown relevant fields [fill in]. Do not delay the initial draft while waiting for optional connected sources; offer to enrich it after authorization.
If there is no meaningful sales context at all, explain that plainly and use the interview fallback, starting with scope and the company/offer. Do not present an empty template as a completed profile.

EVIDENCE AND GAPS
Mark information as directly stated, supported by a source, proposed inference, missing, conflicting, or not applicable. Include source type and date when known; never invent citations, counts, or verification. Memory is a starting point, not proof that a fact or policy is current.
After the draft, ask only material unanswered or conflicting questions. Prioritize company/scope ambiguity, approved proof, prohibited claims, commercial boundaries, and important selling preferences. Skip already-supported answers, unrelated branches, and optional fields that do not affect the intended use. Offer a short prioritized gap list, then ask one necessary question at a time. Allow me to skip, edit directly, or keep a draft. Do not force a 14-question checklist or confirmation of every field before showing the file.

SELLER JUDGMENT
Learn personal voice only from work I authored, sent, edited, rejected, reused, or approved. Incoming buyer messages provide buyer context, not my writing style. CRM records provide commercial context, not automatic evidence of my preferred behavior. A recurring habit is not automatically an approved standard; team policy is not one person's preference.
Separate observed patterns, declared preferences, supported company facts, and confirmed rules. Surface conflicts instead of silently choosing. If a material standard is unclear, ask what I would change in a redacted example and why. Propose its exact wording, scope, and exceptions in the draft for review. Do not turn one-off buyer feedback into a general rule.

PRIVACY AND ACCURACY
Distill patterns; exclude raw emails, transcripts, private customer identities, sensitive personal details, credentials, and unnecessary confidential information. Use approved public proof only when its status is supported; otherwise leave proof unapproved or missing. Exclude unrelated personal, HR, medical, legal, and security material unless I explicitly include it for a defined reason.
Never invent customers, metrics, pricing, buyer pain, product capabilities, security answers, or proof. Keep live account lists, opportunities, activity, and approvals in their source systems; include safe references rather than copies. Do not infer approval of confidential information for public sharing or use in another AI.
Current explicit instructions take precedence over verified live facts, then confirmed rules, observed patterns, and defaults. Recheck time-sensitive claims before customer-facing use.

REVIEW AND OUTPUT
Begin the document with # SELLER.md. Label it Draft until I review it. Include one concise review summary with key inferences, conflicts, and gaps; let me edit and approve the whole file instead of confirming every supported answer separately. Approval does not fact-check uncertain claims or fill missing fields. Do not say complete while material gaps remain. If I skip questions, deliver a clearly labeled partial draft anyway.
Use these top-level sections: Context Scope; Context Owner; Context Provenance; Learning And Privacy Policy; Context Scope And Precedence; Refresh And Change Control; Territory; Company Sales Context; Ideal Customer Profile; Buyer Personas; Selling Standards And Judgment; Differentiation; Proof Points; Messaging Rules; Banned Phrases; Outreach Standards; First Call Standards; Qualification Standards; Objections; Pricing And Commercial Rules; Customer And Account Memory References; AI Output Quality Bar.
Record creation method, actual sources reviewed, review period, confidence, unresolved gaps, and confirmation/refresh dates when known. Use Not applicable for irrelevant branches. Keep everything in one SELLER.md, not separate company, territory, or CRM files. Preserve an existing profile and present meaningful changes before replacing confirmed rules.

INTERVIEW FALLBACK
If I explicitly choose Interview me instead, begin with the first unanswered relevant question, not a connected-source review. Use any answers already provided and do not ask them again. Draft as soon as useful context exists, then fill only material gaps. No fixed question count; stop when there is enough for the intended use or I ask to stop. Do not access additional sources unless I later authorize them.