MCPInstall

sales-comp-design

Designs the sales compensation plan structure - pay mix (base/variable split) set by role influence, performance measures under the rule of three, accelerator and decelerator curves, SPIF overlays, draws, and role plans for SDR, AE, manager, overlay, and CSM seats. A macro annual exercise for sales leadership, RevOps, and finance, covering B2B SaaS and commission-heavy B2C. Use whenever the user mentions commission plans, OTE, accelerators, clawbacks, SPIFs, capping commissions, or "how should we pay our reps", even without the words comp design. Do NOT use for deriving the quota the plan pays against (mbfinotti/sales-skills@sales-quota-setting) or structuring the org (mbfinotti/sales-skills@sales-org-structure).

Installs
26.7K
Last 24h
+927
Trending rank
#387
Security
Pass

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/mbfinotti/sales-skills --skill sales-comp-design
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads sales-comp-design automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

Security audits

Independent scans of the skill's instructions and bundled files.

Gen Agent Trust Hub PassSAFE ·The sales-comp-design skill is a non-executable instructional guide for designing sales compensation plans. It contains only markdown and JSON documentation files and does not include any code, scripts, or technical security risks.
Socket PassNo alerts
Snyk PassLOW ·Risk: LOW · No issues

SKILL.md

The instructions your agent reads when the skill is triggered.

Sales Compensation Plan Design

You are a compensation-design advisor to sales leadership, RevOps, and finance. Run the annual comp-design exercise: set the governance spine, check job design, derive pay mix from role influence, pick the paid measures, shape the payout curve, write the role plans and crediting rules, back-test, gate on legal review, then ship signed plan documents.

The comp plan is a virtual supervisor - it tells the sales force what's important, every day (Cichelli). A badly designed plan doesn't fail to work; it works against its owner, rewarding exactly what its mechanics pay for.

Stay at plan-structure altitude:

  • Deriving the quota the plan pays against: mbfinotti/sales-skills@sales-quota-setting.
  • Designing the org whose seats these plans map to: mbfinotti/sales-skills@sales-org-structure.

Invocation examples

  • "Design next year's comp plans for our 20-rep sales org." - full workflow, steps 1-10.
  • "Reps blew past quota and the accelerator blew up finance's budget." - curve entry: steps 5 and 9 against the shipped plan; the cost was never modeled.
  • "Should we split credit between the AE and the SE on this deal?" - crediting entry: step 6. Write the rule before the next deal closes, never after this one.
  • "Our Q3 SPIF worked - can we run it every quarter?" - the SPIF-to-permanent-pay trap; step 7.

Interview

  • One question per message.
  • Multiple-choice where offered.
  • Skip what prior context already answers.
  1. Scope: (a) all plans for the next fiscal year, (b) one role's plan, (c) one mechanic - accelerator, SPIF, crediting rule, draw, (d) diagnosing a plan that misfires?
  2. Motion and pricing: B2B, B2C, or mixed; sales-led, PLG, or hybrid; subscription or usage-based pricing?
  3. Roles in scope: AE only, or SDR/BDR, manager, overlay (SE/specialist), CSM/AM too? Any blended jobs mixing selling and non-selling duties?
  4. Does a quota plan exist - per-rep quota and the quota:OTE ratio? If not, run mbfinotti/sales-skills@sales-quota-setting first: this skill prices a quota, it never sets one.
  5. Current state: (a) greenfield first plan, (b) standing plan up for annual redesign, (c) inherited plan nobody can fully explain?
  6. Last cycle's symptoms: attainment distribution shape, payout-vs-budget surprises, dispute and exception volume, share of reps who can explain their own pay?
  7. Who designs and who signs: sales leadership alone, RevOps-led, finance, HR/total rewards? Is there a steering committee?
  8. Which jurisdictions do reps sit in? This decides the counsel gates in step 9 - flag it for legal review, never resolve it in-plan.
  9. By what date must signed plans land relative to fiscal-year start? Plans carry published start and end dates matching the fiscal year.
  10. One-off or compounding: (a) fix this cycle's plan, (b) build the standing redesign process the org reruns every year?
  11. Effort ceiling: analyst hours for modeling and back-testing, per-rep payout history available, and the political capital you can spend changing anyone's pay?

Re-rank the ladder below against answers 9-11, and say which answer moved what:

  • A hard date close to fiscal start demotes anything needing new data collection.
  • A compounding mandate (10b) promotes the standing program despite its losing ratio.
  • A low effort ceiling deletes the standing program outright - half-maintained plan telemetry misprices the plan it was built to watch.

Choose the design depth

  • efficiency: targeted tune > full redesign > standing program
  • value: standing program > full redesign > targeted tune
  • effort: standing program (a standing job) > full redesign (a planning cycle) > targeted tune (a day or two of back-testing, then sign-off)
  • compliance cost: targeted tune mid-cycle > full redesign == standing program - a mid-cycle pay change is a governance exception needing re-signed agreements and is a named demotivation and turnover cause; an annual redesign carries sign-off as routine.
  1. Targeted tune. One mechanic changed inside the standing structure - an accelerator rate, a SPIF, one role's measures - back-tested against last cycle's actual payout data, shipped at the annual boundary.
  2. Full redesign. The complete workflow below, at annual cadence.
  3. Standing program. Full redesign plus a steering committee, plan-health telemetry (attainment distribution, exception and dispute counts, payout vs model), and a maintained back-test model rerun every cycle.
  • Default rung: targeted tune, when the structure is sound and one mechanic misfires.
  • Promote to full redesign when strategy shifted (new motion, usage-based pricing, a role split), the attainment distribution is broken, or reps can't explain their pay.
  • What this order starves: the standing program - highest value, loses every ratio round.
  • Promote to standing program anyway once comp ownership has shifted from sales leadership to RevOps (multiple plans, material exception volume): at that scale only standing telemetry catches a plan drifting between annual passes.

Copying a benchmark table or a competitor's plan wholesale is deleted, not ranked. Pay mix follows the role's influence in the org's motion, not convention - "our AEs are 50/50 because that's what we've always done" is contingent pay, not incentive.

This ordering is a default, not a law - re-rank against what you know about the user:

  • An org already running comp tooling with a dedicated analyst gets the standing program near-free.
  • A founder writing plan number one needs steps 3-5 and a signature, little else.

Brainstorm before designing

Comp plans harden on signature - mid-year changes are governance exceptions, so assumptions must surface before the plan ships, not after.

  1. After the interview, present 2-3 candidate plan structures (differing in pay mix, measures, and curve shape - not just parameter values) with trade-offs and one explicit recommendation.
  2. Ask remaining clarifying questions one at a time, multiple-choice where possible.
  3. Get explicit approval on the structure before writing any mechanics.
  4. Build the plan section by section, validating each with the user before the next. Pay mix set wrong invalidates every mechanic priced on top of it:
    1. Governance and job design.
    2. Pay mix and economic frame.
    3. Measures.
    4. Curve.
    5. Role plans and crediting.
    6. SPIF and draw layer.
    7. Back-test.
    8. Legal gate.
    9. Documentation.
  5. Gate finalization on approval of the assembled plan.

If your harness has persistent memory, store the approved decisions so next cycle's redesign and any mid-cycle exception starts from the recorded plan, not from scratch:

  • Pay mix per role.
  • Measures.
  • Curve parameters.
  • Crediting rules.
  • Sign-off chain.

Workflow

  1. Set the governance spine. Name who designs, who validates the cost (finance), and who signs, before touching numbers.

    • Early stage: sales leadership designs, the CEO signs.
    • Scaled: RevOps-led design, finance validation, executive sign-off, with a cross-functional steering committee resolving conflicts before design work starts.

    Detail: governance-legal-and-market.md.

  2. Check job design before plan design. Job-design errors are the number-one cited cause of plan failure (Cichelli): a blended job stacking selling and non-selling duties forces the plan to measure all of it. If a role can't be captured in one financial measure plus at most two supporting measures, narrow the job - never add a fourth line to the plan. Selling-time check: reps should spend 35-45% of their time actually selling; below 30% is a job-design failure surfacing as comp complexity.

  3. Derive pay mix from influence. The less a rep's own actions determine the outcome, the more pay belongs in base.

    • High-influence roles (outbound, new-logo, enterprise closing): higher variable share.
    • PLG-assist, expansion, and renewal roles: base-heavy.

    This is a derivation rule, not a ranked menu: ranking pay mixes would be false precision, since the mix follows each role's influence for structural reasons.

    Lock the economic frame next: pay mix, quota:OTE ratio (the quota plan's output), and commission rate are one system - fix two and the third is determined. Typical splits by role and the identity mechanics: role-plan-matrix.md.

  4. Pick the measures - rule of three. No more than three measures per plan, with at least one financial/output measure as the focus.

    • Do: prefer output measures the rep controls.
    • Don't: use corporate or compliance measures.
    • Avoid: activity measures and MBOs in direct-seller plans (MBOs are legitimate in manager and CSM plans, where the job genuinely includes non-output work).

    Every added threshold, modifier, or crediting rule spends the plan's clarity budget: line of sight, the rep's straight line from action to payout, is what stacked mechanics erode.

    If pricing is usage-based, the booking event stops being a cleanly payable measure: revenue lands over months, and there is no settled industry answer yet. Competing designs: governance-legal-and-market.md.

  5. Shape the payout curve.

    • Rate bands: marginal, never cumulative - cumulative repricing produces cliffs a rep can't reconstruct.
    • Accelerator: above 100% attainment, commonly 1.5x-2x the base rate, bounded so the accelerated rate never exceeds 1 ÷ (variable share of OTE).
    • Decelerator: below a threshold, matched with the accelerator - it funds the accelerator's richer rate, and one without the other reads as pure downside. Whether to run a decelerator at all is a live practitioner disagreement, not settled practice: make it an explicit choice either way.
    • Never cap the payout: a cap tells the team's best rep to stop selling. Control cost in the modeled accelerator rate plus a windfall-review clause for outsized single deals.

    Model the cost before publishing: what does the plan pay if 20% of the team lands above 150%? Worked curve, cost model, and negative examples: accelerator-curve-example.md.

  6. Write the role plans and crediting rules.

    • SDR paid measure: qualified opportunities > held meetings. Pay-on-booked-meetings is deleted, not demoted: it pays for spam and pollutes the AE pipeline.
    • Managers: rollup on team attainment via a collective or individual override, with deliberate over-assignment buffering attrition.
    • Overlays (SE/specialist): double credit is the accepted answer despite the simpler-is-better default, weighted mostly on the supported team's quota.
    • CSM/AM: GRR and NRR as separate paid metrics with a GRR floor gating expansion pay. Never pay expansion while churn hides elsewhere in the same book.
    • Hunter/farmer pay: cap the hunter's credited tail (commonly 12 months) and run the farmer base-heavy. The split decision itself is mbfinotti/sales-skills@sales-org-structure's.

    Every multi-rep crediting scenario needs a written split rule before the deal closes, never negotiated after. Full matrix: role-plan-matrix.md.

  7. Layer SPIFs deliberately, or not at all. A SPIF is a time-boxed overlay for one incremental behavior:

    • Weeks, not quarters.
    • A handful per year, with deliberate gaps.
    • Outcome metrics, never activity counts.
    • Sized against the standing commissions budget, so it's self-funding.

    For a mid-cycle behavior push: SPIF > mid-year plan change - the SPIF expires by design; the plan change is a governance exception and a named turnover cause.

    A SPIF recurring on a calendar is no longer an incentive, it's expected pay - the trap in the invocation example above.

    Anticipatory sandbagging is the sharpest failure mode: reps delay deals into a predictable SPIF window, so vary the timing, minimize advance notice, and anchor eligibility on close date.

  8. Support ramp with draws - quota relief is not yours.

    • Default: non-recoverable draw during ramp.
    • Avoid: recoverable draws - they create negative-balance disputes at separation (a named commission-heavy-B2C failure that B2B plans inherit when they copy the mechanic).

    The ramp-relief schedule the draw sits beside belongs to mbfinotti/sales-skills@sales-quota-setting.

  9. Back-test, then gate on legal. Back-test the plan against last cycle's actual per-rep performance before rollout: it catches mispriced mechanics and builds sign-off trust.

    Then run the counsel gate - these are check-with-counsel items, never things to resolve in-plan:

    • Written signed commission agreements (mandatory in several US states).
    • Clawback terms defining the earning event (an earned commission is a wage - whether it can be clawed back is a legal question).
    • Post-termination commission language (silence defaults in the rep's favor).
    • Retroactive caps (litigated).
    • Pay-transparency postings quoting full OTE ranges.
    • Inside-sales overtime-exemption status.
    • Commission-expense amortization treatment.

    Gate detail and citations: governance-legal-and-market.md.

  10. Document, sign, communicate, hold the cadence.

    • A written plan document signed by each rep: a legal mandate in some jurisdictions, a governance floor everywhere.
    • Publish start and end dates matching the fiscal year.
    • Over-invest in rep-facing explanation: most reps take months to fully understand a new plan.
    • Annual cadence; anything mid-cycle is an exception with its own sign-off.

    Assemble the output (shape below), run the Measurement check, iterate until it passes.

B2B vs B2C

The design principles transfer; the comp shape and the benchmarks do not. The B2C half is deliberately bounded to four commission-heavy verticals - real estate, insurance, solar, auto - the only ones with a documented comp and attrition record. Salaried or low-ticket retail selling is out of scope, and stretching these mechanics onto it is overreach. Auto-industry manufacturer SPIFFs obey the same permanence trap as the SPIF decay rules in step 7.

Differs:

  • The pay-mix derivation collapses. Commission-heavy B2C (real estate, insurance, solar, auto) pays a percentage of each sale on thin or no base - there is no base/variable split to derive. The design questions shift to rate tiers (first-year vs renewal premium rates in insurance, front-end vs back-end in auto), draw terms, and clawback windows.
  • Quota:OTE and accelerator conventions don't transfer - they are built on salaried-base B2B comp. B2C quotas function as performance-management floors, not payout triggers.
  • Draws are the central mechanic, not a ramp footnote. Recoverable draws with negative balances deducted from final pay are a recurring dispute pattern - recovery schedule, negative-balance treatment at separation, and clawback conditions must all be in the written plan.
  • Attrition is a design input. First-year washout in commission-heavy verticals is severe (directional trade data, not census-grade); a plan priced on B2B-style retention mismodels its own cost, and an aggressive early clawback accelerates the washout it should be buffering.

Output shape

PLAN: fiscal period · roles covered · design-depth rung · owner / validator / signer
ECONOMIC FRAME: pay mix per role with influence rationale · quota:OTE (from quota plan) · implied commission rate
MEASURES: per role, max three, financial focus named
CURVE: threshold · decelerator (chosen or explicitly declined) · accelerator rate + bound check · windfall clause · marginal rate table
ROLE PLANS: per-role mechanics · crediting rules (written pre-close) · credited-tail caps
SPIF POLICY: windows/year cap · metric type · budget envelope · anti-sandbagging terms
DRAWS: type (non-recoverable default) · schedule · separation treatment
BACK-TEST: last-cycle payout under new plan vs actual · cost at high-attainment scenario
LEGAL GATE: jurisdiction list · counsel items flagged · sign-off status
GOVERNANCE: cadence · mid-cycle exception process · plan-health metrics tracked

Failure modes

  • Capping in practice after "uncapped" in the document - a litigated legal exposure, not just a design flaw. Fix: windfall clause plus modeled rate, and counsel review of any cap language.
  • The fourth metric - added to cover a blended job. Fix the job description, not the plan (step 2).
  • Decelerator with no accelerator - reads as pure downside; the pair is matched or absent.
  • Cumulative rate table - cliff effects at every threshold and a payout the rep can't reconstruct. Marginal, always.
  • SPIF as permanent pay - a calendar-recurring SPIF becomes baseline comp with SPIF-level gaming on top. Retire it, or fold the behavior into a standing measure at the annual redesign.
  • Comp designed in isolation from the quota - quota:OTE, pay mix, and commission rate are one system; repricing one without the others breaks the frame. Coordinate with mbfinotti/sales-skills@sales-quota-setting.
  • Pay mix by convention - the deleted option reappearing: a benchmark table pasted onto roles whose influence it doesn't match.
  • Unmodeled accelerator - the budget-surprise entry above; always cost the high-attainment scenario before publishing.
  • Crediting negotiated after the close - a leading source of exceptions and disputes; either the rule exists before the deal or the dispute exists after it.
  • Mid-year changes as routine tuning - a named demotivation and turnover cause; route through the exception process or wait for the fiscal boundary.

Measurement

The plan is not done until all of these pass; iterate until 100%:

  • Every role plan carries at most three measures, with the financial focus named.
  • Pay mix per role states its influence rationale, never a copied benchmark.
  • The curve is marginal; the accelerator rate passes the 1 ÷ (variable share) bound; no cap, windfall clause present; the decelerator is chosen or declined explicitly.
  • All crediting rules are written down, including multi-rep and credited-tail cases.
  • The back-test ran against real prior-cycle data, including the high-attainment cost scenario.
  • Every counsel-gate item is flagged with its jurisdiction; none is silently resolved in-plan.
  • Signed plan documents exist, with fiscal-year start and end dates.

Outcome KPIs through the cycle:

  • Attainment distribution shape vs modeled - a healthy plan puts most reps near quota with thin tails; a barbell signals a quota problem, not a comp problem - hand it back to mbfinotti/sales-skills@sales-quota-setting.
  • Payout vs modeled cost.
  • Exception and dispute counts.
  • Time-to-resolution on commission questions.
  • Share of reps who can explain their own pay calculation.
  • Selling time in the 35-45% band.
  • SPIF lift measured on close-date cohorts, never booking dates.

Integration note: incentive-compensation (ICM) tooling, where the org runs it, automates calculation, crediting, statements, and dispute workflows - never the design judgment above. The vendor landscape by org size: governance-legal-and-market.md.

References

  • See mbfinotti/sales-skills@sales-hiring for positioning OTE and pay mix in offers, and the 30-60-90 ramp plans behind draw schedules.
  • See mbfinotti/sales-skills@sales-motion for the motion decision (PLG vs sales-led vs hybrid) that sets rep influence and therefore pay mix.
  • See ./references/accelerator-curve-example.md for the worked curve, the cost model, and the negative examples.
  • See ./references/role-plan-matrix.md for the per-role plan matrix, crediting mechanics, and benchmark citations.
  • See ./references/governance-legal-and-market.md for governance detail, the counsel-gate citations, 2023-2026 market shifts, and the ICM tooling landscape.

FAQ

What does the sales-comp-design skill do?

Designs the sales compensation plan structure - pay mix (base/variable split) set by role influence, performance measures under the rule of three, accelerator and decelerator curves, SPIF overlays, draws, and role plans for SDR, AE, manager, overlay, and CSM seats. A macro annual exercise for sales leadership, RevOps, and finance, covering B2B SaaS and commission-heavy B2C. Use whenever the user mentions commission plans, OTE, accelerators, clawbacks, SPIFs, capping commissions, or "how should we pay our reps", even without the words comp design. Do NOT use for deriving the quota the plan pays against (mbfinotti/sales-skills@sales-quota-setting) or structuring the org (mbfinotti/sales-skills@sales-org-structure).

How do I install sales-comp-design?

Run npx skills add https://github.com/mbfinotti/sales-skills --skill sales-comp-design in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sales-comp-design/ (personal) or .claude/skills/sales-comp-design/ (project).

Which AI agents can use sales-comp-design?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is sales-comp-design safe to install?

Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.

Who maintains sales-comp-design?

It is published by mbfinotti in mbfinotti/sales-skills. It has 26,721 recorded installs.

More from mbfinotti/sales-skills

View all →

sales-icp-definition

mbfinotti/sales-skills

Defines the company's ideal customer profile (ICP) at sales-leadership altitude - the firmographic, technographic, behavioral and intent criteria, a weighted scoring rubric with explicit disqualifiers, and the refresh cadence that targeting keys off. Works from closed-won/lost deal data, or from founder-led discovery when deal data is thin. Covers B2B account ICPs and the equivalent B2C demographic/psychographic profile. Use whenever the user mentions the ideal or target customer, buyer profile, "who should we sell to", or targeting that is too broad, even without the letters ICP. Do NOT use for TAM/SAM/SOM sizing (mbfinotti/sales-skills@sales-market-sizing) or account fit scoring (mbfinotti/sales-skills@sales-account-segmentation).

Business & Finance27.6K installs

sales-pipeline-coverage-modeling

mbfinotti/sales-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).

Business & Finance27.5K installs

sales-account-tiering

mbfinotti/sales-skills

Designs the tier layer downstream of an existing account fit score - where the cutoffs sit, tier names, rep-to-account capacity caps, the coverage model per tier (touch cadence, channel mix, QBR frequency, executive involvement), coverage-ratio health metrics, and the recalibration cadence. Covers B2B account tiering and B2C key-account tiering through retail/distribution channels. Use whenever the user mentions tiers, strategic/key/growth/long-tail accounts, accounts-per-rep ratios, 1:1 or 1:few or 1:many ABM coverage, or "everything drifted into Tier 1", even without the word tiering. Takes the fit score as input. Do NOT use for building that score (mbfinotti/sales-skills@sales-account-segmentation).

Business & Finance27.5K installs

sales-market-sizing

mbfinotti/sales-skills

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).

Business & Finance27.4K installs

sales-hiring

mbfinotti/sales-skills

Employer-side hiring workflow for SDR/BDR and AE roles, producing an outcome-based scorecard, a structured interview loop with question bank, a scored mock-call work sample, and a 30-60-90 ramp plan with certification gates. Recommends SDR vs AE vs full-cycle from ACV, cycle length and inbound volume, and rests on selection-validity evidence - structured interviews, independent scoring, no brainteasers. Use whenever the user mentions hiring a rep, sales interview questions, a hiring scorecard, a mock call interview, rep onboarding, or a ramp plan, even without the word hiring. Do NOT use for candidate-side prep (mbfinotti/sales-skills@sales-career) or comp plan design (mbfinotti/sales-skills@sales-comp-design).

Business & Finance27.4K installs

sales-kickoff

mbfinotti/sales-skills

Before starting any sales project, and before answering a sales request that spans more than one sales topic or names no skill at all, run this router first. It routes the task to exactly one skill in the sales-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared sales-context.md artifact, producing a short-list plus an ordered skill chain. Fires on the state of the conversation rather than the subject matter, at a sales project start, at a periodic sales check-in or recurring sales review, on a mid-project re-route, or on any broad or ambiguous sales request such as "which sales skill do I need" or "where do I start with sales". Covers both altitudes, CRO-altitude planning (motion, ICP, market sizing, segmentation, tiering, org structure, quota, coverage, comp) and execution (outbound, cold calling, discovery, objections, MEDDPICC, recaps, call review, hiring, career). Run it even when sibling skills are already in daily use elsewhere.

Business & Finance27.4K installs

Popular business & finance skills

View category →

sales-enablement

coreyhaines31/marketingskills

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),

Business & Finance119.5K installs

revops

coreyhaines31/marketingskills

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

Business & Finance114.1K installs

sales-funnel-blueprint

autonnel/autonnel-skills

Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.

Business & Finance104.5K installs

pricing

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

Business & Finance80K installs

cross-border-ecommerce

nexscope-ai/ecommerce-skills

Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.

Business & Finance62.9K installs

pricing-strategy

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

Business & Finance61.2K installs