Use when a large deal needs procurement, legal, security, and pricing orchestration: mutual close plans, deal-desk runs, and signature.
Instructions your experts follow when using this skill.
Use this when a large deal needs procurement, legal, security, and pricing orchestration. Start from the deal with value and term, the buyer-side owners for procurement, legal, and security, the commercial asks on the table, the approval bands, and the target signature date.
Write the buyer-visible mutual close plan first: the buyer outcome and go-live anchor, then dated steps with single owners on each side. Procurement, legal, security, and commercial terms each get their own track. A step with no date is blocked until it has one.
Map the paper process in full before any proposal: procurement steps and cycle, legal redline rounds with liability, data-processing-agreement, and SLA flags, security review artifacts, and vendor onboarding in their purchasing or finance system. Ship the readiness packet with the plan, not after the questionnaire lands: a public trust page plus first-tier evidence (a SOC 2 Type II security audit report, single sign-on, audit logging, encryption). Work the veto coalition as a coalition: any one stakeholder can kill the deal, but none can approve it alone. A verbal yes is not signed; redlines kill enterprise deals as surely as feature gaps.
Run bespoke terms through the deal desk: every commercial ask names the paired give, ranked easy to hard, with the walk-away set first. Nothing prices or discounts without your explicit yes. Log every concession with date and owner.
For multi-subsidiary and global mechanics, name the contracting entity per region, the currency and tax treatment, and which subsidiary signs what and when. One master track with dated sub-tracks per entity; a region with no owner is blocked.
Orchestrate redlines to signature: collect buyer marks in one round, resolve internally against the approval bands, and return one clean draft per round.
Gate every commit on full MEDDPICC: Metrics, Economic Buyer with confirmed budget, tested Decision Criteria, Decision Process, Paper Process, identified Pain, a Champion who sells internally, and Competition including the status quo. Hold stage advancement on required CRM fields — no Contract Sent without the Paper Process field filled. A blank field stays blank until verified.
The mutual close plan with dated tracks, the paper-process map, the readiness packet, the deal-desk concession log inside approval bands, the global contracting track, the MEDDPICC gate, and the signature orchestration read.
No buyer owners named means you draft the plan with UNKNOWN owners and ask for the intro path. No approval bands means you draft inside the last approved deal's terms and flag every line as INFERENCE. Nothing goes to the buyer and no pricing, terms, or concessions are promised without your explicit yes.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.