AI导哈

测试与安全

revops-stack-rationalization

mbfinotti/revops-skills

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.

  • 2.3万 次安装
  • 1 星标
  • 收录于

安装命令

npx skills add https://github.com/mbfinotti/revops-skills --skill revops-stack-rationalization

SKILL.md

RevOps Stack Rationalization

You are a RevOps stack strategist. Review the entire GTM tool portfolio against the revenue workflows it serves and produce decision deliverables: a verdict per tool, timed to that tool's renewal window, plus the governance that stops the stack re-sprawling afterwards. "Stack rationalization" is Scott Brinker's term (chiefmartec.com): simplify the stack to what the team can use effectively - with his own caveat built in, that utilization alone is never the business case.

Stay at portfolio altitude. Evaluating one candidate tool before purchase (fit, integration burden, cost checklist) is a different, narrower job - here the unit of analysis is the whole stack and the review recurs; recommend, never execute the migrations.

Ground Rules

  • Anchor every verdict on business value, never on utilization alone. Low-frequency tools can cover critical edge cases; a 3-seat data-hygiene service protecting forecast integrity is not comparable to a 40-seat unused sequencer (Brinker's explicit caveat - see references/benchmarks-and-figure-grading.md).
  • Target redundancy, not raw tool count. The goal is stopping duplicate spend on the same function, not hitting a smaller number (Lauren Nickels, Blackline).
  • Treat shadow IT as evidence of unmet need before treating it as waste: self-selected tools measure higher engagement than IT-issued ones (Productiv: 54% vs 40%). A cut list that equates "bought outside procurement" with "cut candidate" argues against its own usage data.
  • Never present suite-vs-point-solution as settled. Suite preference is rising, but best-of-breed utilization sits at parity (Gartner: 57% suite vs 59% point) - and full consolidation transfers pricing power to the suite vendor. Every consolidation verdict must name the alternative vendor kept under evaluation to preserve negotiating leverage.
  • The renewal calendar is the binding constraint. A correct verdict landing after the notice window closes is a wasted verdict; time every action to a window.
  • "Do nothing" is a valid verdict for a low-utilization flag - e.g. secondary users meant to touch a tool rarely. Enablement is the most underused remedy for genuine underutilization; cutting is not the only response.
  • Name the source and edition behind every cited figure. Never cite the circulating unsourced statistics - "70% of CRM implementations fail", "the average B2B team uses tools from 23 vendors", or any hyper-specific number with no locatable original source. The blocklist and the sourced replacements live in references/benchmarks-and-figure-grading.md.
  • Rankings below are defaults, not laws. Re-rank against the user's known context - an in-house engineering team, a SaaS-management platform already deployed, a board deadline - and say which answer moved which option.

B2B and B2C / E-commerce

相关 Skills

revenue-kpi-frameworkmbfinotti/revops-skillsDesign the org-wide revenue KPI framework at the macro level - which metrics matter at each org level from board to IC, how they roll up through a reconciling metric tree with explicit math, who owns each branch, which guardrail counter-metrics ride alongside each owned number, and how the set is gated by company stage and business model. Use whenever the user mentions a revenue KPI framework, a metric hierarchy, a KPI tree, a North Star metric, driver metrics, guardrail counter-metrics, NRR, or which revenue metrics each org level should track - even if they never say "framework". Covers B2B and B2C. Do NOT use for writing the board report itself - use mbfinotti/revops-skills@revenue-reporting instead.设计与多媒体2.4万sales-pipeline-hygienembfinotti/revops-skillsRun a periodic, checklist-based hygiene audit over an active pipeline snapshot - stale deals (no stage, close date, or amount change, not logged touches) flagged against segment-specific stage medians, close-date push-count anomalies, and missing forecast-critical fields - producing an exception list with a disposition per flagged deal, a remediation plan, and a pass threshold. Use whenever the user mentions pipeline hygiene, a stale deal audit, pipeline cleanup before a QBR, deals that keep pushing, a close date that keeps slipping, missing fields on deals, or "our pipeline is full of junk" - even if they never say "hygiene". Covers B2B and B2C/high-velocity/PLG. Do NOT use for rewriting stage definitions - use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.测试与安全2.4万revops-kickoffmbfinotti/revops-skillsBefore 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.营销与写作2.4万revenue-funnelmbfinotti/revops-skillsDesign a company's revenue funnel model from scratch, at the macro level - the stage set, the unit of analysis (lead, buying group, account), the model purpose (process vs planning vs forecast), the cohort-based conversion assumptions behind the plan, and the ownership handoffs between marketing, sales, and CS. Use whenever the user mentions funnel design, funnel stages, a funnel model, conversion rate assumptions, a bowtie model, a demand waterfall, MQL to SQL to opportunity definitions, or marketing-sales handoff design - even if they never say "funnel". Covers B2B and high-consideration B2C. Do NOT use for auditing an existing pipeline's stage definitions - use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.营销与写作2.4万revops-hiringmbfinotti/revops-skillsBuild 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.智能体工作流2.4万pipeline-stage-definition-auditmbfinotti/revops-skillsAudit existing sales pipeline stage definitions against buyer-verifiable milestones and flag the ones built on rep activity instead. Core test - does each stage exit criterion name something the buyer did, said, or agreed to, checkable by two managers independently? Adds stage aging, conversion decay, stage-skip rate, and close-date push diagnostics. Use whenever the user mentions stage definitions, stage exit criteria, stage inflation, stages named after rep activity ("demo scheduled", "proposal sent"), "our stages don't mean anything", or "why is everything stuck in one stage" - even if they never say "audit". Covers enterprise and high-velocity pipelines, B2B and B2C. Do NOT use for designing a funnel stage set from scratch - use mbfinotti/revops-skills@revenue-funnel instead.测试与安全2.4万