sales

/sales Command

All-in-one sales command that runs the full suite: config setup, pricing, marketing, and quotation generation.

Usage

/sales
/sales [customer-type]
/sales [customer-type] via [channel]

Workflow

flowchart TD
    A["/sales command"] --> B{product-config.md exists?}
    B -- Yes --> C[Read config]
    B -- No --> D["Run /sales-create-config flow"]
    D --> C
    C --> E[Determine parameters]
    E --> F[Generate Pricing]
    F --> G["Write docs/sales-kit/pricing.md"]
    G --> H[Generate Marketing]
    H --> I["Write docs/sales-kit/marketing.md"]
    I --> J[Generate Quotation]
    J --> K["Write docs/sales-kit/quotation.md"]
    K --> L["Write docs/sales-kit/README.md"]
    L --> M[Display summary confirmation]

Behavior

Step 1 — Ensure Product Config Exists

1. Look for product-config.md in the current project directory.
2. If it exists, read it and proceed to Step 2.
3. If it does NOT exist, run the /sales-create-config flow:
   • Load ~/.claude/product-config-template.md as structural reference
   • Gather product information interactively (same rounds as /sales-create-config)
   • Generate product-config.md in the project root
   • Then proceed to Step 2

Step 2 — Determine Parameters

Parse the user's input to determine:

• Customer type: sme, enterprise, government, or general (default: show all available types from config)
• Channel: referrer, affiliate, reseller, fronting, or direct (default: direct + partner comparison)
• Marketing style: defaults to generating all key types (taglines, elevator pitch, one social post)

If no arguments are provided, use sensible defaults:

• Customer type: generate for the primary/default package in the config
• Channel: direct pricing + partner comparison table
• Marketing: taglines + elevator pitch + one social media post (professional style)

Step 3 — Generate Pricing

Using the logic from /sales-get-pricing, generate: