Loading...
Loading...
Found 42 Skills
Models how much pipeline a team needs relative to quota - coverage ratios derived from win rates (raw multiplier, stage-weighted, conversion-inversion), segment-level coverage targets, in-quarter timing and the point of no return, seasonality indexing, and pipeline-gap math that turns a ratio into new-pipeline-required. A macro modeling exercise for sales leadership and RevOps, covering B2B and high-velocity/B2C motions. Use whenever the user mentions pipeline coverage, 3x pipeline, a pipeline gap, forecast shortfall, or "we missed quota with 4x coverage", even without the word coverage. Do NOT use for deriving the quota itself (mbfinotti/sales-skills@sales-quota-setting) or inspecting one deal (mbfinotti/sales-skills@deal-red-flags).
Before starting any RevOps or Sales Ops task, and at the start of every session on an ongoing RevOps project, run this first - it routes the task to exactly one skill of the revops-skills collection or says plainly that none fits, and bootstraps or resumes the project's shared, versioned context artifact so the next session starts warm instead of cold, ending in a short-list plus an ordered skill chain. Run it even when the collection's other skills are already used daily - a new project is a new context. Also use whenever the user mentions a revops kickoff, a new RevOps project, a revops project start, revops or crm skill routing, a periodic RevOps check-in, a recurring RevOps review, "which revops skill do I need", or "where do I start with RevOps" - even if they never name a skill, and even if the request looks like it already belongs to one specific skill. Do NOT use for routing quota-carrying sales tasks - use mbfinotti/sales-skills@sales-kickoff instead.
Build the complete hiring packet for a RevOps or Sales Ops role - archetype and level decision, outcome scorecard, interview stage map with a competency question bank and anchored rating scales, a work-sample exercise with rubric and debrief, and a 30-60-90 ramp plan branched on seniority and archetype. For the hiring manager or founder recruiting the hire. Use whenever the user mentions hiring a RevOps manager, sales ops interview questions, a RevOps take-home exercise, a scorecard for a first ops hire, or a 30-60-90 for a new ops hire - even if they never say "hiring packet". Does not source candidates or post jobs. Do NOT use for a candidate's own interview prep - use mbfinotti/revops-skills@revops-career instead.
Build a personalised, time-budgeted watch list of RevOps / Sales Ops information sources - revops podcasts, revops newsletters, revops communities, industry events, and revops people to follow - every source verified still active, with a periodic refresh routine that keeps the list fresh. Use whenever the user mentions a revops radar, staying current in revenue operations, which revops newsletters or podcasts to subscribe to, which revops communities or conferences deserve their time, or who to follow in the field - even if they never say "radar". Tool-agnostic; B2B-SaaS-centric with explicit B2C guidance. Do NOT use for sales-specific sources - use mbfinotti/sales-skills@sales-radar instead.
Build and advance a RevOps or Sales Ops career from the candidate's side - place the candidate on the ladder by scope rather than title, close competency gaps, build defensible evidence of structurally invisible work, and prepare the four exercises RevOps interview loops actually run. Produces a career plan with a gap roadmap, an evidence ledger, interview readiness, and a compensation ask. Use whenever the user mentions a RevOps career, a sales ops career path, RevOps interview prep, RevOps certifications, "how do I break into RevOps", "am I ready for a RevOps manager role", or proving impact when nobody notices ops working - even if they never say "career". Candidate side only - for the hiring manager's side, use mbfinotti/revops-skills@revops-hiring instead.
Run a macro, periodic review of the full RevOps/GTM tool stack against the revenue workflows it serves and decide, tool by tool, what to keep, consolidate, replace, or cut - four-channel inventory, function-level overlap map, TIME scoring, a renewal-triggered action calendar, and re-sprawl governance. Use whenever the user mentions stack rationalization, GTM tool consolidation, a revops stack audit, a GTM stack review, SaaS sprawl, too many sales and marketing tools, cutting tooling spend, redundant GTM tools, or platform vs point solutions - even if they never say "rationalization". Covers B2B sales-led and B2C/e-commerce GTM stacks. Portfolio-level and periodic - not a pre-purchase checklist for one candidate tool, and not contract or legal negotiation.
Design the sales-to-CS handoff process after a deal closes - what data transfers, when, in what artifact, and who is accountable - producing a handoff spec with a gated closed-won trigger, a required handoff packet, timing SLAs, a kickoff meeting pattern, and a CS acceptance/rejection step. For RevOps and Sales Ops designing and enforcing the process, not a CSM running one handoff. Use whenever the user mentions sales to CS handoff, post-close transition, closed-won to kickoff, handoff accountability, "the CSM starts from zero", or "customers repeat themselves after signing" - even if they never say "handoff". Covers B2B high-touch through PLG/self-serve and B2C subscription. Do NOT use for account health scoring - use mbfinotti/revops-skills@customer-health-score instead.
Эксперт RevOps. Используй для GTM стратегий, процессов продаж, CRM систем и revenue метрик.
Rank outreach campaigns by real revenue impact — which campaigns actually generated deals, pipeline, or meetings — by cross-referencing the user's La Growth Machine campaign data with their CRM deal data (HubSpot today). Use whenever the user wants to know which campaigns drove pipeline, compare campaign ROI, see which campaigns to continue / stop / adapt, audit campaign impact, review attribution, asks 'which of my campaigns is actually working', or wants a campaign performance ranking by deals or revenue. Triggers on: 'which campaigns drove pipeline', 'rank my campaigns by deals', 'campaign ROI', 'campaign impact', 'which campaigns to stop', 'which to scale', 'attribution review', 'pipeline by campaign'. Pulls live data from the La Growth Machine MCP and the HubSpot MCP when connected; works from pasted exports otherwise. For RevOps, Heads of Sales/Marketing, founders and growth leads doing campaign performance reviews. Maintained by La Growth Machine.
Expert sales operations and analytics guidance for revenue teams. Use when designing CRM workflows, building sales dashboards, optimizing pipeline analytics, creating lead routing rules, designing territories, calculating commissions, managing data quality, building forecasting models, or integrating sales tech stack. Covers Salesforce, HubSpot, Outreach, Gong, and RevOps best practices.
Use when designing or revising a company's commercial policy — the rules of engagement governing discounts off list price, approver thresholds, exception flows, and the deal framework that Deal Desk and AEs operate under. Covers discount matrix design (ARR band x term length x payment terms x strategic value), commercial policy design, exception policy, discount governance, approval thresholds, deal framework structure, and policy linting (contradictions, gaps, cliff edges, gaming surfaces). For Head of Commercial, Head of Deal Desk, VP Sales, or RevOps at the policy-design moment — NOT per-deal application (that is deal-desk) and NOT pricing model selection (that is pricing-strategist).
Estimates TAM, SAM, and SOM for a market or sub-segment to ground sales capacity, territory, and quota planning - top-down, bottom-up on named accounts or population math, value theory, triangulation, a capacity-based SOM ceiling, and a per-layer refresh cadence. A macro planning exercise for sales leadership and RevOps, covering B2B and B2C. Use whenever the user mentions TAM, SAM, SOM, market size, addressable market, "how big is this market", or the number behind next year's quota, even without those acronyms. Sizes for planning, not pitching. Do NOT use for defining the ICP (mbfinotti/sales-skills@sales-icp-definition) or turning SOM into quotas (mbfinotti/sales-skills@sales-quota-setting).