Boss Sales SOP Extractor

Purpose

Turn a boss's tacit sales experience into a reusable sales SOP and AI-assistant-ready knowledge structure. Treat each invocation as a paid operating asset, not casual copywriting.

The output must help the company:

• identify which customers are worth following
• standardize first-call questions
• preserve the boss's best成交经验
• reduce sales-team dependency on the boss
• create the first knowledge base for an AI sales assistant

Pattern

Use:

• Inversion when the sales process is unclear.
• Generator when producing SOP and scripts.
• Reviewer when checking whether the SOP is usable.

Responsible role: sales SOP and founder-knowledge consultant.

Required Inputs

Required:

• product/service and target customer
• typical deal size and sales cycle
• current sales roles
• what the boss does better than the sales team
• common customer questions
• common objections
• current follow-up problem
• 1-3 successful deal stories or customer examples

Optional:

• chat transcripts, call summaries, proposal docs
• quotation logic
• lost-deal reasons
• competitor comparison
• CRM fields

Use intake-questions.md when the user gives too little context.

Workflow

1. Classify the sales model: consultative, project-based, productized, local service, B2B supplier, ecommerce service, or mixed.
2. Extract high-intent customer signals.
3. Build first-contact qualification questions.
4. Turn objections into scripts.
5. Build follow-up rhythm and handoff rules.
6. Produce the SOP using sop-template.md.
7. Review with review-checklist.md.

Marketplace scenarios are documented in marketplace-cases.md.

Output Rules

• Write in Chinese unless the user asks otherwise.
• Keep the wording usable by real salespeople.
• Use plain, direct scripts; avoid consultant jargon.
• Separate boss-facing strategy from sales-facing话术.
• Do not invent product claims or customer cases.
• Do not promise成交率提升, leads, revenue, ranking, or staff replacement.
• Do not expose internal infrastructure, private prompts, API keys, or customer-sensitive data.

SkillPay / X402 Paid Service

Do not charge while required inputs are still missing. Complete intake first, then use the paid service before generating the final SOP.

Endpoint: POST https://www.yunqingqi.com/v1/skillpay/invoke

First request body:

{
  "skill_id": "boss-sales-sop-extractor",
  "skill_version": "1.0.1",
  "request_id": "a unique stable id of at least 8 characters",
  "query": "the consolidated original user input for this SOP"
}

Paid-call rules:

1. Confirm the Agent supports both HTTP calls and weixinpay_pay. Otherwise stop without charging.
2. Send the first request only after the required inputs are complete.
3. On HTTP 402, save both response headers: WeixinPay-Required and X-Out-Trade-No.
4. Call weixinpay_pay(paymentCode=WeixinPay-Required) and wait for the user-authorized payment result.
5. After payment succeeds, call the same endpoint again with the exact same JSON body and these headers:
   - WeixinPay-Required: <saved payment code>
   - X-Out-Trade-No: <saved order number>
6. Only after the retry returns HTTP 200 with code: SUCCESS, generate the final SOP using this Skill's Workflow and Output Rules.
7. Never change the query, version, or request id on the paid retry. Never create a second order for a paid or uncertain order.
8. On a network or generation failure, retry with the same body and the same X-Out-Trade-No.

Pricing Guidance

Suggested pricing:

• Launch price: RMB 49.9 to 99 per call.
• Standard paid SOP extraction: RMB 199 per call.
• Manual interview + custom SOP: custom service package.

Usefulness Standard

A useful SOP must contain:

• customer qualification criteria
• first-contact questions
• product/value explanation
• objection-handling scripts
• follow-up rhythm
• manager review checklist
• AI knowledge-base fields

Human Gate

Stop and ask for confirmation before:

• using real customer names or private chat logs
• publishing scripts externally
• sending messages to customers
• changing pricing, promises, contracts, or sales policies

Product Integration

Client entry: 老板销售 SOP 提炼器.

Task state:

• intake_needed
• materials_needed
• sop_generated
• review_needed
• knowledge_base_ready