Skills RevOps
Support-led growth
Someone has noticed support talks to more customers than any other team and asked what it could be doing commercially. The question is reasonable and the usual answers are bad.
npx rulebase-skills install cx-support-led-growthWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “can support drive growth”
- “support-led growth programme”
- “should agents mention other features”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
The mechanisms, best first
1. Removing adoption blockers. A customer who cannot get a capability working will not expand into it. Fixing that is unambiguously support's job, it requires no change of posture, and it is the largest of these effects in most businesses. This is where to start, and it is mostly an onboarding-friction and knowledge problem rather than a new programme.
The line, stated plainly
Support may help the customer do more of what they already bought. Anything that requires the customer to spend more is a commercial conversation and belongs to whoever owns the account.
Design the safe motions properly
Request loop-closing. Needs a record of who asked for what, a trigger when it ships, and a message that is a genuine notification rather than a pitch. Send it from support, reference their original conversation, and do not attach an upsell. Measure adoption of the shipped capability among those told versus comparable customers not told.
Measure it as an experiment, with a guardrail
Every one of these is testable and almost none are tested.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
