Business & Operations

Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".

Cold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".

Close a specific deal — diagnose why a deal is stalling, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", or "help me get to yes".

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

Audit existing API for breaking change risks and missing compatibility controls. Use when asked to "find breaking change risks in our API", "audit our compatibility controls", or "what could break clients".

Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".

Audit a proposed API change for breaking changes — classification and impact assessment. Use when asked "is this a breaking change", "will this break clients", or "assess the impact of this API change".

Survey existing contracts for common clause patterns and risks. Use when asked "what clause patterns do our contracts use", "survey contract risk", or "find common terms across our contracts".

Generate negotiation playbook for a specific contract type. Use when asked to "build a negotiation playbook", "how do we negotiate this clause", or "what are our fallback positions".

Deep clause-by-clause analysis of a contract with risk scores. Use when asked to "analyze this contract clause by clause", "score the risk in this agreement", or "what is dangerous in this contract".

Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".

Design a dependency scanning program — CVE detection, license checks, and CI gates. Use when asked to "scan our dependencies", "set up CVE detection", or "add a dependency CI gate".

Design an SBOM generation pipeline — format, tooling, and integration into CI/CD. Use when asked to "generate an SBOM", "build an SBOM pipeline", or "add CycloneDX to CI".

Audit existing dependency security — find unscanned packages, license violations, and SBOM gaps. Use when asked to "audit our dependencies", "do we have an SBOM", or "find license violations".

Design cost reduction strategies — model tiering, prompt compression, caching, batch inference. Use when asked to "reduce our AI costs", "set up model tiering", or "cut LLM spend".

Review and redline a contract — flag risk, missing clauses, one-sided terms. Use when asked to "review this contract", "redline this agreement", or "is this contract risky".

Survey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".

Draft a contract or policy document from a description or template. Use when asked to "draft an NDA", "write an MSA", or "we need a vendor contract".

Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".

Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".

Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".