ICP builder
You need to define or sharpen an ideal customer profile (ICP) for B2B sales: starting outbound, the reply rate is low, the pipeline is full of…
You get One-page ICP · Disqualifiers · List-building filters
Use this before the first touch on a Tier 1 account or before any first call. It produces a one-page brief that answers one question: why would this company care about us this quarter?
Use it when you need to research a target company before outreach, a first call or an account plan.
“Research northwind.com before my call on Thursday. We sell warehouse scheduling software.”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Research northwind.com before my call on Thursday. We sell warehouse scheduling software.
account-research-briefReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
Use this before the first touch on a Tier 1 account or before any first call. It produces a one-page brief that answers one question: why would this company care about us this quarter?
Search the CRM before the web. A lost deal from last year, an existing customer in a sister company or an unsubscribed contact changes the whole approach.
Stop when the brief is complete. Thirty minutes of research for a Tier 1 account, five for Tier 2.
A trigger is a change that creates urgency: a new leader, funding, expansion, a hiring wave, a launch, a regulation, a bad quarter. Keep only triggers from the last 6 months and only those that connect to your offer. Read references/trigger-library.md for the trigger list with suggested angles.
Write each as "Because <trigger>, they probably <pain>, which we solve by <outcome>." If you cannot fill all three parts, it is trivia, not an angle.
Economic buyer, likely champion and one alternate. Include title, tenure and anything they have said publicly about the problem.
Account: <name> (<domain>) | Fit: Tier 1/2/3 | CRM history: <one line>
What they do: <one sentence in plain words>
Priorities this year: <2-3 bullets, each with source>
Triggers (last 6 months): <date - event - source>
Likely pains: <2-3, each tied to a trigger or evidence>
People: <name - title - why them>
Angles:
1. <angle> - opener idea - source
2. ...
3. ...
Risks: <reasons this might be a bad fit or bad timing>
Triggers ranked by how reliably they create a buying window. "Window" is how long the urgency usually lasts.
| Trigger | Where to find it | Window | Why it matters | Example angle |
|---|---|---|---|---|
| New leader in the buying role | Leadership posts, company news, profile changes | First 90 days | New leaders audit tools and want early wins | "Most new sales leaders I talk to review the outbound stack in month one…" |
| Funding round | Press releases, funding databases | 3-6 months | Budget plus pressure to grow fast | "With the Series B, the plan likely calls for pipeline to double…" |
| Hiring for a role your product supports | Careers page, job boards | While the listing is open | They are paying to solve the problem; you may be cheaper or faster | "Saw you’re hiring three SDRs. Teams usually…" |
| Expansion: new region, office, product line | Newsroom, leadership posts | 3-6 months | New processes get built from scratch | "Opening in Germany means…" |
| Tool change | Job listings naming tools, review sites | 6 months | Migration projects open the door to adjacent tools | "Since you’re moving to a new CRM…" |
| Regulation or compliance deadline | Industry news | Until the deadline | Fixed date, non-negotiable | "With the deadline in March…" |
| Bad results or layoffs | Earnings, news | 3 months | Efficiency pitches land; growth pitches do not | Lead with cost and time saved, gently |
| Competitor customer churn | Reviews, community threads | 1-3 months | Active pain with a named alternative | "Teams switching from the old way usually ask…" |
| Event participation | Event agendas, speaker lists | 2 weeks around the event | A natural, timely reason to talk | "Saw you’re speaking at…" |
Formula: observation → implication → question. Keep the observation factual and the implication humble.
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“Research northwind.com before my call on Thursday. We sell warehouse scheduling software.”
“Give me an account brief and three angles for Acme Health. Tier 1, VP Operations is the buyer.”
“Research these 10 accounts and rank them by how timely outreach would be.”
Use this before the first touch on a Tier 1 account or before any first call. It produces a one-page brief that answers one question: why would this company care about us this quarter? You get: one-page account brief, trigger events with sources, three outreach angles, contacts to target.
Use it when you need to research a target company before outreach, a first call or an account plan.
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 account-research-brief for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: company name or domain, your offer and icp, crm history if any. 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.