// sales-pipeline

Sales & Pipeline

Prospecting, target accounts, discovery, objections, forecasting, and win-loss.

7 skills

Execute

cold-email-sequence

Cold Email Sequence

Use when the user wants to write a cold outbound email sequence — the multi-touch cadence that opens conversations with target accounts. Also use when the user mentions cold email, outbound sequence, email cadence, prospecting emails, sales outreach, follow-up emails, break-up email, or "emails that get replies." Produces a 4–6 touch cold email sequence with subject lines, send timing, and one clear ask per email, grounded in the prospect's pain.

Sales & Pipeline·Starter#cold-email#outbound
$ npx skills add cold-email-sequence

Execute

discovery-call-framework

Discovery Call Framework

Use when the user wants a discovery call structure or question bank — how to run a first sales call that qualifies and uncovers real pain. Also use when the user mentions discovery call, sales call script, qualifying questions, sales questions, needs analysis, first call, demo call, or "what should I ask on a sales call." Produces a discovery call flow with a prioritized question bank, qualification checks, and next-step language that advances the deal.

Sales & Pipeline·Starter#discovery#sales-call
$ npx skills add discovery-call-framework

Design

objection-handling

Objection Handling

Use when the user wants to handle sales objections or build objection and competitor battlecards — structured responses to the pushback that stalls deals. Also use when the user mentions objections, objection handling, "it's too expensive," competitor comparison, battlecards, rebuttals, deal blockers, status quo, or "how do I respond when they say X." Produces an objection-handling framework and competitor battlecards — the top objections with grounded, non-defensive responses and honest competitive comparisons.

Sales & Pipeline·Starter#objections#battlecards
$ npx skills add objection-handling

Execute

pipeline-and-forecast

engine

Pipeline And Forecast

Use when the user wants to forecast sales or check pipeline health — whether there's enough pipeline to hit the number and what's likely to close. Also use when the user mentions sales forecast, pipeline coverage, weighted pipeline, quota attainment, pipeline gap, commit vs best case, coverage ratio, or "will we hit our number." Produces a weighted forecast (commit vs best case), a pipeline coverage ratio against the target, the gap, and how much new pipeline is needed.

Sales & Pipeline·Intermediate#forecast#pipeline-coverage
$ npx skills add pipeline-and-forecast

Design

sales-process-design

Sales Process Design

Use when the user wants to design or fix their sales process — the stages a deal moves through, what has to be true to advance, and what each side does. Also use when the user mentions sales process, sales stages, pipeline stages, deal stages, exit criteria, sales playbook, qualification, MEDDIC, BANT, or "our pipeline is messy." Produces a defined stage-by-stage sales process with entry triggers, verifiable exit criteria, owner actions, and a fitting qualification framework.

Sales & Pipeline·Intermediate#sales-process#pipeline-stages
$ npx skills add sales-process-design

Design

target-account-list

engine

Target Account List

Use when the user wants to build or prioritize a target account list — which accounts to go after, scored by fit. Also use when the user mentions target accounts, ICP fit scoring, account prioritization, ABM list, named accounts, tiering accounts, lead scoring by firmographics, or "who should we sell to first." Produces a fit-scored, tiered account list (A/B/C) with the scoring rationale and the signals each account matched.

Sales & Pipeline·Intermediate#target-accounts#icp-scoring
$ npx skills add target-account-list

Diagnose

win-loss-analysis

engine

Win Loss Analysis

Use when the user wants to understand why deals are won or lost and turn it into patterns they can act on. Also use when the user mentions win/loss, win-loss analysis, why we lose deals, deal post-mortem, lost-deal reasons, competitive losses, sales feedback, or "why aren't we closing." Produces a structured win-loss summary — top win and loss reasons, patterns by segment and competitor, the no-decision rate, and prioritized fixes for product, pitch, and process.

Sales & Pipeline·Intermediate#win-loss#sales-analysis
$ npx skills add win-loss-analysis

// go deeper

The Sales & Pipeline playbook on aajconsult.com

Interactive tools, methodology, and case studies behind these skills.

// human in the loop

Need a human in the loop?

AAJ builds the strategies, tools, and playbooks these skills are made of — with engagements for growth-stage and enterprise teams.