sales-guide

Generate a structured sales battle plan by processing customer profile data and requirements notes to output a JSON file containing timing, competitors, decision chains, and next actions. This translates scattered customer dossiers into ready-to-use strategic outreach intelligence.

The best way to track decision chains and competitors is structuring customer intelligence into a battle plan that maps decision makers, sensitive topics, and competitive analysis. This ensures go-to-market teams execute strategic outreach with clear next actions.

Yes, you can update a sales guide JSON without losing existing intelligence because the skill performs iteration-safe updates. It detects new inputs, recalculates tracking metrics, versions metadata, and overwrites only affected sections while keeping prior data intact.

Yes, you need a structured customer profile input, specifically a docs/customer/profile.json file, along with optional requirements material. The skill validates these docs and customer inputs before writing the sales-guide JSON template.

You should regenerate a B2B sales battle guide whenever extra intelligence arrives or new inputs trigger the skill. Iterating the guide ensures the go-to-market team always has updated next actions, interview guidance, and recalculated tracking metrics.

Sales battle plans need metadata versioning to support iteration-safe updates when new intelligence triggers fresh creation or iteration. Versioning tracks recalculated metrics and summarizes what changed, keeping prior intelligence intact while clearly overwriting affected sections.