Loading...
Loading...
Found 10 Skills
Design the reward structure of a customer refer-a-friend program - who gets rewarded (referrer, friend, or both), reward type (cash, account credit, discount, product value, status), how much to pay against LTV/CAC and gross margin, when the payout fires, and whether to build a tiered reward ladder. Use whenever the user mentions referral incentives, refer-a-friend rewards, referral bonus amounts, give-X-get-Y offers, double-sided referral rewards, or asks how big a referral reward should be, even if they never say incentive. Covers end-customer rewards only. Do NOT use for commission rates paid to professional affiliates - use mbfinotti/partnerships-skills@affiliate-commission-structure instead.
Use when structuring payouts, tiers, and eligibility for referral programs.
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
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).
Apply contract theory to design incentive-compatible agreements under moral hazard and adverse selection. Use this skill when the user needs to structure principal-agent contracts, evaluate compensation schemes, or analyze incomplete contract problems where parties cannot specify all contingencies ex ante.
Apply Self-Determination Theory to analyze motivation quality along the autonomy continuum and design interventions that satisfy basic psychological needs. Use this skill when the user needs to diagnose why intrinsic motivation is declining, evaluate incentive structures for motivational crowding, design need-supportive environments, or when they ask 'why did rewards backfire', 'how to foster intrinsic motivation', or 'what needs drive engagement'.
Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.
Apply basic game theory concepts including Nash equilibrium, dominant strategies, and the Prisoner's Dilemma to analyze strategic interactions. Use this skill when the user needs to model competitive decisions, predict rival behavior, design incentive mechanisms, or evaluate cooperation vs competition scenarios — even if they say 'what will our competitor do', 'should we cooperate or compete', or 'how do we set up the right incentives'.
When the user wants to design, launch, or optimize a referral or affiliate program. Use when they mention 'referral program,' 'affiliate program,' 'word of mouth,' 'refer a friend,' 'incentive program,' 'customer referrals,' 'brand ambassador,' 'partner program,' 'referral link,' or 'growth through referrals.' Covers program mechanics, incentive design, and optimization — not just the idea of referrals but the actual system.
The essential mental models for building onchain — focused on what LLMs get wrong and what humans need explained. "Nothing is automatic" and "incentives are everything" are the core messages. Use when your human is new to onchain development, when they're designing a system, or when they ask "how does this actually work?" Also use when YOU are designing a system — the state machine + incentive framework catches design mistakes before they become dead code.