mbfinotti
出典を確認した実質的な文書を持つ Skill が 108 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
mbfinottinegotiation-concession-planner
Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-them, tiered, each give paired with a required reciprocal get and its approval level, plus a BATNA-based walk-away. Covers B2B (terms, scope, service, risk, price protection) and B2C (bundles, financing, trade allowance). Use whenever the user mentions a discount request, procurement, redlines, give-get trades, walk-away point, or "the buyer wants 20% off", eve
- 24時間の導入数
- 745
- GitHub Stars
- 3
- 更新日
- 10月26日
mbfinotticold-email-deliverability
Reviews a cold email draft and its sending setup for deliverability - SPF/DKIM/DMARC alignment, sender reputation and complaint risk, body mechanics (length, links, images, tracking pixels, HTML vs plain text, opt-out), and legal compliance by region. Covers B2B cold outbound and B2C bulk/lifecycle mail. Use whenever the user mentions the spam folder, blacklisting, domain warmup, inbox placement, bounce rates, DMARC, or "why are my emails not landing", even without the word deliverability. Do NO
- 24時間の導入数
- 739
- GitHub Stars
- 3
- 更新日
- 10月26日
mbfinottideal-red-flags
Reviews one deal's free-text notes - call notes, opportunity fields, CRM activity log, email threads - for qualification red flags such as single-threaded deal, no champion, no compelling event, unverified budget, no agreed next step, or fading engagement, each graded on severity and confidence with the quoted note fragment behind it. Covers B2B and B2C. Use whenever the user mentions deal risk, a stalled or slipping deal, ghosting, forecast inspection, or "is this deal real", even without the w
- 24時間の導入数
- 736
- GitHub Stars
- 3
- 更新日
- 10月26日
mbfinottirevops-career
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 cer
- 24時間の導入数
- 641
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevenue-funnel
Design 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 mar
- 24時間の導入数
- 639
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottipipeline-stage-definition-audit
Audit 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", "proposa
- 24時間の導入数
- 638
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevenue-kpi-framework
Design 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
- 24時間の導入数
- 637
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevenue-data-governance-strategy
Set org-wide revenue data governance policy - which system is source of truth per object class (account, contact, opportunity, subscription, usage event, revenue metrics), how cross-team data contracts bind producers to consumers, where revenue metric definitions live, and who arbitrates disputes. Produces a per-object SOR/SOT designation table, an identity-resolution spine, a data-contract register, and a federated ownership model. Use whenever the user mentions source of truth, "two ARR number
- 24時間の導入数
- 636
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevenue-leakage
Trace where deals and revenue silently exit one specific funnel and size the loss in recoverable (never gross) dollars - untracked steps, unworked leads, manual handoffs, mid-funnel stalls, paper-process drops, billing and renewal misses - separating real leaks from healthy disqualification and data-capture gaps. Use whenever the user mentions revenue leakage, funnel drop-off, a leaky funnel, deals disappearing, unworked leads, handoff gaps, "where are we losing deals", or "why did pipeline vani
- 24時間の導入数
- 636
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevops-hiring
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
- 24時間の導入数
- 635
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevops-radar
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
- 24時間の導入数
- 634
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottisales-pipeline-hygiene
Run 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 pus
- 24時間の導入数
- 634
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottisales-forecast-diagnostic
Diagnose why an existing sales forecast is unreliable and recommend fixes - stage inflation and happy ears, sandbagging, deals without verifiable buyer evidence, stale or mass-pushed close dates, wrong forecast-category assignment, zombie and duplicate opportunities, late-created deals, manager roll-up overrides, and comp incentives that reward bias - separating data-quality from behavioral from genuine demand problems. Use whenever the user mentions forecast accuracy, a forecast miss, reps sand
- 24時間の導入数
- 628
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevops-kickoff
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 ne
- 24時間の導入数
- 624
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevops-stack-rationalization
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, redun
- 24時間の導入数
- 621
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinotticrm-data-governance
Design and operate CRM field-level governance - who owns each CRM field, which system is authoritative for it, how often it must be refreshed, and how the rules are enforced. Produces a field dictionary, per-field ownership, a system-of-record map with write-precedence and conflict rules, freshness SLAs, an enforcement plan, a field lifecycle, and a governance cadence. Use whenever the user mentions field ownership, single source of truth, system of record per field, data dictionary, stale CRM d
- 24時間の導入数
- 619
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottideal-desk-approval
Design the deal desk approval chain and exception-handling process for non-standard B2B SaaS deals - a tiered discount approval matrix and delegation of authority across five concession levers (price, payment terms, services, contract risk, security), margin floor policy, exception intake, two SLA clocks with a sales escalation path, and precedent control. Includes the rules-driven promo/discount-policy equivalent for PLG, self-serve, and B2C. Use whenever the user mentions deal desk, discount a
- 24時間の導入数
- 616
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottilead-scoring
Design, validate, and recalibrate a lead scoring model - fit and engagement signals, weighting, negative scoring and exclusions, decay, MQL/PQL threshold and tier setting, backtesting against closed-won/closed-lost outcomes, and governance; also diagnoses an existing broken model. Use whenever the user mentions lead scoring, an MQL threshold, fit vs engagement scoring, product-qualified leads, score decay, "score my leads", "our lead scores are wrong", "sales rejects our MQLs", or "too many junk
- 24時間の導入数
- 614
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottisales-to-cs-handoff
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 accountab
- 24時間の導入数
- 614
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottilead-routing
Design the assignment logic that routes inbound leads to sales reps - rule precedence and waterfall ordering, lead-to-account matching, territory assignment rules (geography, segment, industry, named accounts), round-robin variants (straight, weighted, capacity-based, availability-aware), fallback catch-all queues, SLA escalation and reassignment, and safe rollout of routing changes. Use whenever the user mentions lead routing, lead assignment, territory assignment, round-robin, lead distributio
- 24時間の導入数
- 611
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinottirevenue-reporting
Define the metric set and narrative structure for an executive or board revenue report so it tells one coherent story - a small stable metric spine, locked definitions, an answer-first narrative around plan vs actual vs forecast, presenting a miss without surprising the board, the reconciliation and sign-off chain, and weekly vs monthly vs quarterly cadences. Use whenever the user mentions a board revenue report, exec deck metrics, the QBR revenue section, a monthly revenue review, an investor u
- 24時間の導入数
- 608
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinotticustomer-health-score
Design, validate, and govern a composite customer health score - product usage and engagement signals combined into one weighted, normalized, decayed, banded account score that flags both churn risk and expansion readiness, backtested against real churn outcomes and recalibrated. Use whenever the user mentions a customer health score, health scoring model, account health, signal weighting, score bands, at-risk account flagging, churn risk score, expansion risk, or says "green accounts keep churn
- 24時間の導入数
- 606
- GitHub Stars
- 1
- 更新日
- 10月26日
mbfinotticac-roas-benchmark
Compute a business's CAC and ROAS family metrics from real spend and outcome data, then judge whether the spend is healthy against three references - the business's own break-even, its own trailing history, and provenance-labelled external benchmarks - returning healthy, watch, unhealthy, or insufficient evidence. Use whenever the user asks whether their CAC is too high, whether a ROAS is good, what ROAS to aim for, whether ads are profitable, or mentions MER, blended CAC, payback period, or a s
- 24時間の導入数
- 604
- GitHub Stars
- 2
- 更新日
- 10月26日
mbfinotticustomer-churn-signals
Assemble, define, validate, and rank leading indicators of customer churn from account activity, product usage, and support data into a ranked churn signal register - each signal carrying event, threshold, window, baseline, lift over base rate, lead time, and coverage. Use whenever the user mentions churn signals, churn indicators, leading indicators of churn, an early warning system for at-risk accounts, champion departure, seat utilisation drops, payment failure, or says "our health score miss
- 24時間の導入数
- 604
- GitHub Stars
- 1
- 更新日
- 10月26日