Sales Agent

Discovery Prep

Build the pre-call guide that turns a discovery meeting into a qualified opportunity — hypothesis, question architecture, exit criteria. Use when user has an upcoming discovery or first call, needs discovery questions, or wants meeting prep for an initial prospect conversation. Do not use when account research itself is the ask — use account-research instead.

Meeting Prep

Prep a multi-stakeholder sales meeting (demo, evaluation, or working session) — produces an internal battle-plan pre-read AND a customer-facing agenda, mapped to the account's pains, competitors, and budget. Use when user has a scheduled meeting with a known account and needs both the team brief and the shareable agenda. Do not use for a first discovery call (use discovery-prep), the demo flow itself (use demo-customization), or a written proposal (use proposal-writing).

Account Research

Build account intelligence that reveals how to enter and how to win — company snapshot, stakeholder map, trigger events, entry strategy. Use when user needs to research a target account, understand a prospect's business, or map stakeholders before discovery. Do not use when the need is specific call prep — use discovery-prep instead.

Proposal Writing

Build a stakeholder-tailored proposal — executive summary, situation, solution, outcomes, investment, next steps — that confirms what's been agreed and makes internal approval easy. Use when user needs a sales proposal, quote, or deal-summary document for a prospect. Do not use when the need is an RFP response — that's solutions engineering territory.

Objection Handling

Handle a specific sales objection by diagnosing root cause, acknowledging legitimately, reframing to value, and providing evidence. Use when user faces a specific objection (price, timing, authority, status quo) and needs a strategic response. Do not use when the objection is competitor FUD — use competitor-objection-handling.

Deal Strategy

Diagnose a complex or stuck deal with a MEDDPICC verdict, named risks, and a 7-14 day action plan. Use when user has a stuck/stalled deal, needs strategy for a multi-stakeholder opportunity, or wants a deal-health check. Do not use when the need is discovery prep — use discovery-prep instead.

Demo Customization

Build a stakeholder-tailored demo flow and talk track — opening, core demo, Q&A, next steps — anchored to discovery findings and audience role. Use when user has a demo scheduled and needs persona-tailored flow, industry-specific talk track, or prospect-specific demo script. Do not use when the need is pre-call discovery prep — use discovery-prep instead.

Champion Enablement

Arm an internal champion with the materials and coaching to sell when you're not in the room. Use when user needs to enable a champion for an internal pitch, build an internal-selling toolkit, or coach a champion for a stakeholder meeting. Do not use when the need is an external proposal — use proposal-writing.

Negotiation Strategy

Plan a negotiation — leverage assessment, concession ladder, BATNA, walk-away line — for pricing, terms, or contract structure. Use when user faces pricing pressure, needs negotiation tactics, or wants to plan a concession strategy. Do not use when the need is general objection handling — use objection-handling.

Reference Request

Coordinate a customer reference end-to-end — matching, requesting, preparing both parties, coordinating the call, following up. Use when user needs a customer reference for a competitive deal, has an exec stakeholder skeptical, or needs peer proof to advance a stalled deal. Do not use when the need is a case study for marketing — that's a content task.

Executive Briefing

Prepare for a high-stakes meeting with a C-level executive — research, exec-appropriate content, talk track, exec-level questions and answers, the right ask. Use when user has a meeting with a CFO/CEO/CTO/COO and needs prep. Do not use when the meeting is with manager-level (run discovery-prep) or when enabling a champion for THEIR exec meeting (use champion-enablement).

Follow Up Sequence

Build a post-meeting or re-engagement email sequence that delivers value at every touch — not "just checking in." Use when user needs follow-ups after a meeting, re-engagement for a ghosted prospect, or post-demo/post-proposal cadence. Do not use when the need is a marketing nurture campaign — that's a different motion.

Mutual Action Plan

Build a mutual action plan (MAP) — shared timeline, owners, dates — that creates accountability and surfaces hidden process steps. Use when user needs a MAP, close plan, or joint evaluation timeline to formalize the path to a decision. Do not use when the need is internal-only deal strategy — use deal-strategy instead.

Competitive Battlecard

Build an actionable battlecard against a named competitor — counter-positioning, landmine questions, proof points, objection handlers. Use when user needs a battlecard against a specific competitor, side-by-side comparison, or competitive talk tracks. Do not use when the need is general market landscape — that's market-research or PMM territory.

Landmine Questions

Generate indirect discovery questions that surface a competitor's gaps without ever naming the competitor — questions that make the buyer say "I should ask them about that." Use when user needs competitive discovery questions, trap questions, or gap-finding questions for a known-competitor deal. Do not use when direct feature comparison is needed — use competitive-battlecard instead.

How To Win Playbook

Build a deal-specific competitive strategy playbook — deal context, competitive landscape, positioning, sequenced attack plan — for one named opportunity against one named competitor. Use when user has an active competitive deal and needs a game plan. Do not use when a general battlecard suffices — use competitive-battlecard instead.

Competitor Objection Handling

Build proof-backed responses to competitor FUD using the They-Say / Why-Misleading / Our-Proof / Redirect framework. Use when user faces competitor claims or FUD against your product and needs ready responses with named proof. Do not use when the objection is about pricing or contract terms — use negotiation-strategy.

Customer Persona

Build actionable customer and buyer personas that change targeting, messaging, and sales discovery — not posters for the office wall. Use when user needs ICP definition, named buyer-role persona, persona-based message variations, or segmentation that drives behavior. Do not use when broad market research is the need — use market-research instead.

Launch Planning

Orchestrate a product, feature, or pricing launch across every team — matching effort to market impact, translating capability into buyer value, and driving adoption, gated on product readiness and field enablement. Use when user needs launch strategy, GTM coordination, a launch timeline, go/no-go criteria, tier classification, or a cross-functional launch checklist. Do not use when positioning definition is the need — the launch plan consumes positioning, it doesn't author it.

Pricing Communication

Communicate pricing changes effectively across customers, sales, CSMs, and internal stakeholders — value-first, adequate notice, named escalation paths, no panic. Use when user needs to communicate a pricing change, sales talk tracks for pricing discussions, customer-facing pricing announcements, or pricing FAQ. Do not use when the need is pricing strategy definition or deal-specific negotiation.

Demo Scripting

Build the standard demo script — story arc, click path, talk track, persona/duration variations. Use when user needs the standard demo, a demo flow redesign, or scripted talking points sales can repeat. Do not use when deal-specific customization is the need (route to deal-specific demo prep) or the request is technical POC scoping (route to /solutions).

Win Loss Analysis

Turn deal outcomes into actionable patterns — diagnose whether losses are product, positioning, sales execution, or fit, and what to change. Use when user needs win/loss analysis at the pattern level, competitive intelligence from deal data, or root-cause diagnosis of win-rate trends. Do not use when active deal strategy is needed (use sales/deal skills) or the request is a single deal post-mortem.

Proof Of Value

Design a proof-of-value engagement that proves measurable business impact with a real baseline and a CFO-ready number — not just that the product works. Use when user needs POV planning, ROI validation, value measurement, or CFO-ready value evidence. Do not use when the question is technical ("does it work?") — use @file:poc-planning; when scoping delivery effort — use @file:implementation-scoping.