Use when the user names lead handoff, MQL, SQL, or follow-up speed, or asks why marketing pipeline never closes: the SLA with definitions, handoff rules, time bars, and the joint scorecard.
Instructions your experts follow when using this skill.
Use this when the user names lead handoff, MQL, SQL, or follow-up speed, or asks why marketing pipeline never closes. Start from the lead tiers and definitions on hand, the funnel numbers by stage — HubSpot or an export — and the follow-up reality today.
Lead, MQL, SAL, SQL, opportunity. SAL is where sales accepts or rejects with a reason code — the handoff accountability mechanism. Lifecycle stage is marketing-owned for the first half and sales-owned for the second; lead status is always sales-owned. Each stage gets its entry bar in observable terms — fit score plus behavior, never vibes. One definition per stage, signed by both sides.
Roughly 25 demographic, 25 firmographic, 40 behavioral, 10 negative; MQL at 65–75, SQL at 85. Weight behavior over demographics, decay stale activity, and backtest the bars against the last 100 won and 100 lost before they ship.
What a sales-ready lead carries (tier, source, context, next step), where it routes, and what bounces back with cause. Every bounce gets a reason code; reason codes get reviewed monthly.
First response inside 4 business hours — inbound inside 5 minutes, social inside 15, referral inside 60 — 6 touches over 14 days, and disposition inside 5 business days as Accepted, Rejected, or Disqualified. Speed-to-lead is the one SLA number that never gets negotiated away, and a breached bar escalates to the named owner the same day.
Volume, acceptance rate, conversion by stage, velocity, and the sourced vs influenced pipeline split with named proofs. Starter bars: MQL-to-SAL acceptance above 60%, SQL-to-opportunity above 30%; any published MQL-to-SQL benchmark is direction-only until your own funnel confirms it. One scorecard, reviewed in one forum, monthly at least.
Sales grades lead quality weekly with quotes, marketing tunes scoring and sourcing monthly. Scoring changes need triangulated evidence — quotes plus conversion drift — before they ship.
The SLA doc with definitions, handoff rules, time bars, and the joint scorecard template beside it, shown in chat. Take one round of edits from each side, then save under alignment. You draft the agreement; the approver signs it, and neither side gets to freeload.
No funnel numbers means you draft the SLA on tier math and hold the targets as UNKNOWN. No shared CRM means the SLA ships with a routing log template instead of automation. Never invent a conversion rate, a lead count, or a follow-up time. Label each line FACT, INFERENCE, or UNKNOWN.
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.