Multichannel cadence
You need an outbound cadence that combines email, LinkedIn, phone and video so each touch builds on the last.
You get Day-by-day cadence · Copy per touch · Capacity plan
Use this before a calling block. It produces a talk track that sounds like a person, not a reading, and that gets to a decision (meeting or no) in under three minutes.
Use it when you need a B2B cold call script or talk track.
“Write a cold call script for IT directors at hospitals. We sell device management.”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Write a cold call script for IT directors at hospitals. We sell device management.
cold-call-scriptReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
Use this before a calling block. It produces a talk track that sounds like a person, not a reading, and that gets to a decision (meeting or no) in under three minutes.
Name yourself, acknowledge the interruption, give the reason in one sentence, ask for 30 seconds.
"Hi Maya, it’s Sam from Acme. This is a cold call, so feel free to hang up, but can I tell you why I called and you decide if it’s worth a minute?"
Permission-based openers convert better than pretending the call is expected.
One or two sentences about a problem people in their role usually have, with a peer reference. End with a question.
"I work with finance leads at companies your size. Most tell me close takes 8 to 10 days because approvals sit in inboxes the last week of the month. Is that true for you, or have you solved it?"
Ask, listen, follow the answer. Good questions are about their current process and its cost: "How long does close take today?", "Where does it get stuck?", "What happens when it runs late?"
If there is a problem: "Contoso was at 9 days and now closes in 4. Worth 20 minutes next week to see if the same thing would work for you? Tuesday or Thursday?" If there is no problem: thank them, ask who else might feel it, and leave.
Read references/call-objections.md for responses to the ten most common brush-offs. The principle: acknowledge, ask one question, then respect the answer.
Opener: <permission line>
Reason: <problem + peer> → "Is that true for you?"
Questions: 1. <current process> 2. <where it breaks> 3. <cost of it>
Proof: <one line>
Ask: <20 minutes, two time options>
If no: "Who else on your team deals with <problem>?"
Pattern: acknowledge → one question → respect the answer.
| Brush-off | Response |
|---|---|
| "Just send me an email." | "Happy to. So I send something useful rather than a brochure, is <problem> actually something you’re dealing with?" |
| "We’re all set." / "We already have something." | "Good to hear. Out of curiosity, how long does <outcome> take with what you have today?" |
| "Not interested." | "Fair enough. Is that because <problem> isn’t an issue, or just not a priority right now?" |
| "I’m busy right now." | "Understood. Is there a better 2 minutes later this week, or should I not call back?" |
| "How did you get my number?" | Answer honestly with the source type (a business contact database, the company website), and offer to remove it. |
| "What’s this about?" (sceptical) | Give the reason in one sentence and ask the problem question. |
| "We don’t have budget." | "Makes sense. When does planning for next year start? I’d rather be useful then than pushy now." |
| "Talk to <someone else>." | "Thanks. What should I know about how <name> thinks about this before I call?" |
| "Call me next quarter." | "Will do. What changes next quarter that makes it a better time?" Then book the callback date. |
| "Is this a sales call?" | "Yes, it is. Can I take 30 seconds to say why, and you decide?" |
Under 20 seconds: name, company, one-line reason tied to the email, "I’ll send you a note too", number said twice slowly. Expect few callbacks; the voicemail’s job is to make the next email familiar.
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“Write a cold call script for IT directors at hospitals. We sell device management.”
“Prep me for 40 calls tomorrow to people who were sent our email last week.”
“Give me responses to 'just send me an email' and 'we're all set'.”
Use this before a calling block. It produces a talk track that sounds like a person, not a reading, and that gets to a decision (meeting or no) in under three minutes. You get: call script, objection responses, one-page call card, practice drill.
Use it when you need a B2B cold call script or talk track.
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 cold-call-script for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: persona and problem, offer and proof, trigger 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.