Account tiering
You need to decide which accounts get the most effort.
You get Tiered account list · Score breakdown · Effort rules per tier
Use this when the question is "which leads should sales call first?". It produces a scoring model with point tables, a threshold and a validation test, documented well enough that anyone can configure it.
Use it when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first.
“Build a lead scoring model from this export of 4,000 leads with outcomes.”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Build a lead scoring model from this export of 4,000 leads with outcomes.
lead-scoring-modelReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
Use this when the question is "which leads should sales call first?". It produces a scoring model with point tables, a threshold and a validation test, documented well enough that anyone can configure it.
A single blended number lets a student who downloads ten ebooks outrank a VP who visited pricing once.
For each attribute and action, compare the opportunity rate of leads that have it with the base rate. Points roughly follow the lift: an action with 4x the base opportunity rate earns about twice the points of one with 2x. Read references/scoring-tables.md for starter tables and the lift method.
Subtract for students, competitors, personal emails, job seekers and unsubscribes. Halve engagement points every 30 days so old activity does not keep a lead hot.
Choose the fit and engagement cut-offs that send sales roughly the number of leads they can work within the SLA. A threshold that produces 300 leads a week for a team that can work 80 trains reps to ignore scores.
High-intent actions such as a demo request or pricing contact bypass scoring entirely.
Backtest on last quarter: the top 20% of scored leads should hold at least 50% of the opportunities. Then review monthly.
Only trust lifts computed on 30+ leads with that attribute.
| Attribute | Points |
|---|---|
| Title in buyer persona | +25 |
| Title in champion persona | +20 |
| Company size in sweet spot | +20 |
| Target industry | +15 |
| Target region | +10 |
| Uses an integrated technology | +10 |
| Personal email domain | -20 |
| Student, intern, job seeker | -50 |
| Competitor domain | -100 |
| Action | Points | Notes |
|---|---|---|
| Pricing page visit | +20 | Count once per 7 days |
| Comparison or alternatives page visit | +15 | |
| Case study view | +10 | |
| Product sign-up or trial start | +30 | |
| Replied to an email | +25 | Any reply, triaged separately |
| Webinar attended live | +15 | Registered only: +5 |
| Content download | +5 | Diminishing: cap at +15 total |
| Email opened | 0 | Unreliable signal; ignore |
| Unsubscribed | -30 | |
| Demo request | Route directly | Bypasses scoring |
Decay: engagement points halve every 30 days.
Start with fit ≥ 60 and engagement ≥ 40 for sales handoff, then tune weekly in the first month until the volume matches capacity.
| Score band | Leads | Opportunities | Rate | Lift vs base |
|---|---|---|---|---|
| Top 10% | target 3x+ | |||
| 10-30% | ||||
| 30-100% |
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“Build a lead scoring model from this export of 4,000 leads with outcomes.”
“Our MQLs convert at 3%. Redesign the scoring so sales trusts it.”
“Set a threshold that sends my 5 reps about 60 leads a week.”
Use this when the question is "which leads should sales call first?". It produces a scoring model with point tables, a threshold and a validation test, documented well enough that anyone can configure it. You get: fit and engagement scoring tables, handoff threshold, sla, validation report.
Use it when you need a lead scoring model that sales trusts: inbound leads pile up unworked, marketing and sales argue about MQL quality, or reps chase the wrong leads first.
Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill lead-scoring-model for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: won and lost leads with attributes, engagement data, sales capacity. If something is missing, the skill tells the agent to ask for it rather than guess.
Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.
No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.
Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.
Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.
Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.