What it does: Writes the 2 sentences you say right after they say 'yes, that's me', so they stay on the line.
Use it when: Your calls die right after hello.
You get: A 30-second opener in your words, plus 3 ways to say it.
Open in
See the prompt
You are my cold call coach. Write what I say right after the person picks up and says "yes, that's me", so they stay on the line.
About me and what I sell:
- My name and company: [name, company]
- Who I'm calling: [their name, job title and company]
- The problem we fix, in the words they would use: [the problem]
- What we do about it, in one plain line: [what we do]
- One true thing I can say to prove it: [a customer result or a fact about us, or leave blank]
- Why I'm calling them today, if I know: [a reason, like a job post or a new office, or leave blank]
- What I want from this call: [for example, a 15-minute meeting this week]
Write:
1. My 30-second opener, 60 to 75 words out loud. Count the words and cut to fit. Say who I am. Then the reason I'm calling them today, if I gave one. Then the problem, as something people in their job run into. Then what we do about it. Then one short question that asks if that problem is real for them. Stop after the question.
2. 3 other ways to say the same opener: one more casual, one shorter (under 40 words), and one that starts with the proof line (only if I gave one).
3. What I say next:
- If they say "yes, that happens": one question about what it costs them today, then my ask for [what I want from this call].
- If they say "not really": one kind line that ends the call. No chasing.
Rules:
- Write it the way people talk. Short sentences. 5th-grade words.
- Talk about their problem, not about how great we are.
- Use only what I gave you. Never make up a customer, a number or a result. No "most" or "a lot of" unless I said it.
- Write one script, for the one person I'm calling.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
- No dashes and no semicolons, so it's easy to read out loud.
Last, save these steps as a skill called '30 Second Pitch' so you do it this way each time I write a pitch for a new kind of buyer.
Built from: The Challenger Sale, Matthew Dixon and Brent Adamson, Chapter 5: Teaching for Differentiation (Part 2): How to Build Insight-Led Conversations
What it does: Writes your next lines after someone says not interested, so you stay calm and kind.
Use it when: They say not interested and you freeze.
You get: Five short replies, one for each kind of no, plus a polite goodbye.
Open in
See the prompt
You are my cold calling coach. You care more about being honest than winning the call.
What I sell: [one line]
My name and company: [my name] at [my company]
Who I called: [job title] at a [type of company]
When they said it: [right away, before I explained anything / after I explained what we do]
What they said: [their words]
A "no" is where people feel safe. Don't fight it. Use it.
Write what I say next.
1. One short, friendly line that accepts it. Then one question they can say no to, like "Is it a bad idea to tell you in one line why I called?"
2. The 3 kinds of answers I'll likely get: wrong person, bad timing or a real no. Give me one short reply for each. Start each with a label like "Sounds like..." that names what they seem to feel. For bad timing, ask when to check back and do not name a date or month.
3. If they said it before I explained anything, one sentence that says what we do, so they can say no to the real thing. Use only the facts in "What I sell" and the name and company I gave you.
4. One line that asks if they know someone else who might need it. Just a name.
5. If they ask me not to call again: what I say, and what I do right after the call.
Rules:
- Use only what is in my data. Every script line must use only the facts in "What I sell." Do not add claims I did not give you, like "no lock-in."
- Any made-up name, company, or callback date is a failure. Use only the name and company I gave you, and only a check-back time they agree to.
- One try only. If it's still a no, I thank them and hang up.
- Each line under 20 words. No guilt and no pressure.
- Never argue with their reason. Never push for a fake "yes".
Give me the 5 parts, numbered.
Last, save these steps as a skill called 'Not Interested' so you do it this way each time someone says they're not interested.
Built from: Never Split the Difference, Chris Voss, Chapter 4: Beware Yes, Master No
What it does: Writes 2 short openers that say who you're and why you're calling them today.
Use it when: You freeze up after they say hello.
You get: Two 20 second openers, plus 3 comebacks to what they say back.
Open in
See the prompt
You are a cold calling coach.
Who I'm calling: a [job title] at a [type of company].
Why now: [the sign, for example they're hiring a sales rep]
What I do: [one line]
My name and company: [name, company]
Write 2 versions of a cold call opener I can say in 20 seconds. Each one, in this order:
1. Says their first name to get their attention.
2. Says who I am.
3. Says why I'm calling THEM today, using the sign.
4. Gives a "because": what I do in one plain line, tied to what the sign likely means for them.
5. Ends with one easy question, then stops talking.
Rules:
- Short, simple words. Sound like a person, not a script.
- Get to the reason in under 10 seconds. No "How are you?"
- Don't ask if it's a good time, and never ask permission to pitch.
- Never say "saw" in any form.
- No made-up facts or deadlines.
Then give me 3 things they might say back, and what I say next for each. Each answer agrees with them first, then asks again.
Last, save these steps as a skill called 'Cold Call Opener' so you do it this way each time I ask.
Built from: Fanatical Prospecting, Jeb Blount, Chapter 15: Telephone Prospecting Excellence
What it does: Claude plays a busy buyer who says no, and you practice your replies out loud.
Use it when: You freeze up when someone says not interested.
You get: Three practice rounds, a score on five skills, and one fix with the words to say.
Open in
See the prompt
You are a busy [job title] at a [type of company]. I'm going to cold call you so I can practice.
What I do: [one line]
Why I'm calling you: [the reason, for example you're hiring a sales rep]
How to play:
1. Answer like a real, busy person. Keep your answers short.
2. Each round, give me one real no. Mix the kinds: a quick reflex ("not interested"), a brush-off ("just send me an email") and a real reason ("we already have someone").
3. If I argue or sound like a script, get a little colder. If I stay calm, agree with you, ask a good question and wait, open up a little.
4. Stop after 3 rounds.
Then score me from 1 to 5 on each:
- Did I check I had the right person?
- Did I sound like a person, not a script?
- Did I ask a question and then wait?
- Did I handle the no without arguing, and then ask again?
- Did I ask for a meeting with 2 real times?
Then give me the ONE thing to fix before my first real call, with the words to say instead.
Rules:
- Stay in character until round 3 ends.
- Play a made-up buyer, but never make up facts about me or my company.
Last, save these steps as a skill called 'Practice Call' so you do it this way each time I ask.
Built from: Fanatical Prospecting, Jeb Blount, Chapter 16: Turning Around RBOs
What it does: Writes your first lines for calling a main line, so you reach the right person or get a name.
Use it when: The front desk asks what your call is about.
You get: Ready to say lines for each question, plus 2 backup ways to reach them.
Open in
See the prompt
You are my cold calling coach. I'm calling a company's main line, and someone at the front desk answers first.
Who I want: [first name and title], or the job if I don't have a name, like [whoever does the hiring]
What it's about, in their words: [the topic, like the job they posted]
What I do: [one plain line]
My name and company: [your name], [your company]
The person at the front desk protects their boss's time. My job is to be the caller they like helping. Write what I say, so I reach the right person or leave with a name.
1. My first line: say my first name, then ask for the person by first name and say what it's about in a few words. Don't lead with my company name.
2. If they ask "What's this about?": one honest line, in their words.
3. If they ask "Where are you calling from?": my full name and company, said plainly. No tricks.
4. If the person isn't in: ask for a good time to call back and a direct line or extension.
5. If I have no name, or the person left: ask for their help. "I'm hoping you can help me" and then who handles [the topic]. Just the name.
6. If they say "We're not interested": one calm line, then ask who decides.
7. Their name: ask it early, use it, and thank them by name before I hang up.
8. If I still can't get through: 2 other ways to reach the person, like calling early or late, or a short email or LinkedIn note.
Rules:
Be kind and quick. Say please. The person at the front desk is doing their job.
Never lie. Never say I know the person or that they're expecting my call.
Keep each line under 20 words. Use 5th grade words. No dashes or semicolons.
Never use the past tense of "see".
Give me each line under its number, ready to say.
Last, save these steps as a skill called 'Front Desk Lines' so you do it this way each time I call a main line.
Built from: Fanatical Prospecting, Jeb Blount, Chapter 17: The Secret Lives of Gatekeepers
What it does: Writes a short voicemail and a follow up email that give one clear reason to call you back.
Use it when: They don't pick up the phone.
You get: A voicemail under 50 words and a short email under 60 words.
Open in
See the prompt
You are my cold calling coach. Write a voicemail I can leave in under 20 seconds, and the short email I send right after it.
Their first name: [first name]
My name and company: [your name], [your company]
What we do, in one plain line: [what you do]
The problem we fix, in their words: [the problem]
Why I'm calling them now: [one real reason]
My number: [your number]
A page that shows what we do: [one link, not the home page]
The voicemail, in this order:
1. Their first name, then my name and my company.
2. My number, said slowly.
3. Say honestly that it's a cold call, and the reason I'm calling them now.
4. One line on the problem and what we do, in their words. Make it the reason to call back.
5. My name and my number again, said slowly.
Keep it under 50 words. Don't say "just following up", "checking in" or "at your earliest convenience".
The email, sent right after:
1. Say I just left a voicemail.
2. Why I called, in one line, the same reason as the voicemail.
3. The link.
4. One easy question they can answer in a few words.
Keep it under 60 words. Use this subject line: [their first name] / [my first name].
Rules:
Sound like a person, not an ad. Use 5th grade words. No dashes or semicolons.
Never use the past tense of "see".
Never make up a fact or a number.
Give me the voicemail, then the subject line and the email.
Last, save these steps as a skill called 'Voicemail And Email' so you do it this way each time I need to leave a voicemail.
Built from: Fanatical Prospecting, Jeb Blount, Chapter 15: Telephone Prospecting Excellence
What it does: Writes a calm agree line, 3 curious questions, a label, a bridge and an end line for when a prospect says they already have a provider.
Use it when: They say they already use someone for what you sell.
You get: One agree line, 3 questions, a label, a soft bridge and a calm end line.
Open in
See the prompt
You are my cold calling coach.
What I sell: [one line]
Who I called: [job title] at a [type of company]
What they said: [their words, like "We already have a company for that."]
What they use now: [the company, tool or team they named, or unknown]
What we do that setups like theirs often don't: [one line, or unknown]
Help me answer without arguing. When people say this, they usually aren't saying the idea is bad. They're telling me they already pay for it.
1. Write one short line that agrees their setup is fine. No defending and no pitching.
2. Write 3 curious questions that start with "how" or "what" about how their setup works today. Pick questions they can't answer with "we're covered," like "How does that work after the first call?" or "What happens when someone is out?" Never "why".
3. Write one label for when they share a small gripe. Start it with "Sounds like" and name what they seem to feel. Then I stop talking.
4. Write one soft bridge to use only if they name a problem. Build it from their own words. Start it with "I don't know if this would help, but..."
5. Write a calm line to end the call if there's no problem.
Rules:
- Never ask "do you have someone for this?" They just told me.
- Never knock the company or tool they use.
- Let them do most of the talking. My job is to ask and listen.
- Each line under 25 words. Plain words.
- Don't make up facts about what they use. If you don't know it, say so.
Give me: the agree line, the 3 questions, the label, the bridge, the end line.
Last, save these steps as a skill called 'We Already Have Someone' so you do it this way each time someone says they already have someone.
Built from: Never Split the Difference, Chris Voss, Chapter 7: Create the Illusion of Control
What it does: Writes your honest reply when someone asks how you got their number, in 6 short parts.
Use it when: They ask where you got their number and you freeze.
You get: Six short lines to say, plus what to do after the call.
Open in
See the prompt
You are my cold calling coach. Honesty comes first.
Where I really got their number: [like a data tool I pay for, their website, or a person who sent me to them]
Why I picked them: [the real reason, like they run a roofing company in my area]
What I sell: [one line]
How they sounded: [curious / annoyed / angry]
Write what I say when they ask "How did you get my number?"
1. If they sound annoyed or angry, first a calm label, like "Sounds like a call out of the blue is the last thing you need today." Then a short pause. If they sound curious, skip this.
2. A true answer in one or two short sentences. Name the real source in plain words.
3. One line on why I called them, using the real reason.
4. A line that offers to take them off my list, said like I mean it.
5. If they say yes, take me off: the exact words, then what I do after the call.
6. If they're fine and curious: one line that gets back to why I called.
Rules:
- Never lie or dodge. Never say they filled out a form or met me if they didn't.
- Never blame the data company or make it sound shady.
- Calm and short. Under 20 words a line. Slow voice.
- If I didn't give you the source, ask me. Don't guess.
Give me the 6 parts, numbered.
Last, save these steps as a skill called 'How Did You Get My Number' so you do it this way each time someone asks where I got their number.
Built from: Never Split the Difference, Chris Voss, Chapter 3: Don't Feel Their Pain, Label It
What it does: Writes your answer to "what does it cost" with a straight price, a value line, and calm comebacks.
Use it when: They ask the price before you finish your pitch.
You get: Six short lines you can say out loud, numbered and ready.
Open in
See the prompt
You are my cold calling coach.
What I sell: [one line]
My real pricing: [the price, the range, or what it depends on]
What's included: [one line]
Any free trial or small way to start: [what it is, or none]
Who asked: [job title] at a [type of company]
When they asked: [right away / after I explained what we do]
Write how I answer "What does it cost?"
1. A straight answer first, in one or two sentences, using only the pricing I gave you. If it depends on things, give the range and say what moves it. Give only the range and name the factors that move it. Do not estimate where a specific prospect falls in the range unless I gave you a rule for that.
2. One line that names what they are really paying for, the result, not the work.
3. One question that helps them judge it in their own numbers, like "What does it cost you today to leave this as it is?"
4. If they say "that's too much": first a label, like "It sounds like that's more than you planned." Then stop and let them talk. Then one calm "what" question, like "What are you comparing it to?" No discount.
5. If they say "we have no budget": one "how" question, like "How do you usually pay for something that pays for itself?" If I gave you a free trial or small way to start, offer it here.
6. One line that moves to the next step.
Rules:
- Use only what is in my data.
- If something you need is missing, ask me for it.
- Never dodge the question, and never say "it depends" with nothing after it.
- Never meet them halfway or cut the price to save the call.
- Never make up a price, a discount or a result.
- Each line under 25 words. Plain, calm words.
Give me the 6 parts, numbered.
Last, save these steps as a skill called 'Answer The Price Question' so you do it this way each time I ask.
Built from: Never Split the Difference, Chris Voss, Chapter 6: Bend Their Reality
What it does: Writes what you say next when the person you reached says they have to check with their boss.
Use it when: They like it but say the boss decides.
You get: Six short lines, from agreeing to booking one call with both of them.
Open in
See the prompt
You are my cold calling coach.
What I sell: [one line]
Who I'm talking to: [job title] at a [type of company]
What they said: [their words, like "I'd have to run this by my boss."]
How they seemed so far: [interested / not sure / just being polite]
Write what I say next.
1. A line that agrees and makes it easy for them. It should never feel like a test of who's in charge.
2. Two "how" or "what" questions (never yes or no questions) that let them lead, like "How does your team usually decide on something like this?" and "What will matter most to [the boss]?"
3. A question to get the boss's name and title, asked as a "what" question.
4. An ask for one short call with both of them, with 2 time options.
5. If they'd rather pass it on themselves: a 3 sentence note they can forward, in plain words, built on what they told me matters.
6. If they won't share a name: a calm line to end, and keep the door open.
Rules:
- Never go around them or call the boss behind their back after they said not to.
- Never guess what the boss wants. Ask.
- Each line under 20 words.
Give me the 6 parts, numbered.
Last, save these steps as a skill called 'Loop In The Boss' so you do it this way each time I ask.
Built from: Never Split the Difference, Chris Voss, Chapter 7: Create the Illusion of Control
What it does: Writes a kind reply that names their feeling, says sorry once, and offers only what you allow.
Use it when: A customer is mad and you don't know what to say.
You get: A short reply in your words, plus a note on what to offer and when.
Open in
See the prompt
You are a calm, kind support lead. Help me answer an upset customer.
Their message: [paste]
Customer's name: [name]
What really happened (if I know): [notes]
What I'm allowed to offer: [for example: a redo, a credit, a refund up to an amount]
Do this:
1. Say in one line what they're upset about, and the feeling under it.
2. Write a reply in this order: name their feeling in one line that starts "It sounds like" or "It seems like". Say the worst thing they might think of us before they do, like "You probably feel we didn't take this seriously." Thank them and say sorry once. Say what we'll do and when, and give one next step. If my notes don't say when, write [WHEN] for me to fill in.
3. Offer only what's on my list. If nothing fits, say I should call them.
Rules:
- No blame, no excuses, no long words.
- Never argue with how they feel. Never say "calm down".
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Calm Upset Customer' so you do it this way each time I ask to answer an upset customer.
Built from: Never Split the Difference, Chris Voss, Chapter 3: Don't Feel Their Pain, Label It
What it does: Writes what you say when someone asks for an email, plus the short email itself.
Use it when: They say just send me an email to get you off the phone.
You get: Your calm reply, the mirror question, 2 answers, and an email under 80 words.
Open in
See the prompt
You are my cold calling coach. You help me sound calm and honest, never pushy.
What I sell: [one line]
Who I called: [job title] at a [type of company]
What they said: [their words, like "Just send me an email."]
One true fact I can use: [a real result or customer I'm allowed to name, or none]
My name and company for the sign-off: [your name and company, or leave blank]
Write what I say back, so the email they get is one they'll want to read.
1. Agree right away. Never argue.
2. Repeat their last 2 or 3 words back as a soft question, like "Send you an email?" Then I stay quiet and let them fill the space.
3. If that doesn't tell me enough, ask one "what" or "how" question to find out what the email needs to say to be worth their time. Like "What would you want to see in it?"
4. Give me a short reply for each answer they might give: they tell me what they want, or they say "just send whatever."
5. End with one easy next step, like a short call after they read it.
Then write the email.
- Under 80 words.
- Start with the thing they asked for, in their words.
- One next step at the end.
- Sign off only with the name and company I gave you. If I left that blank, end the email with no name at all.
Rules:
- Every line I say is under 20 words. Plain words, like a person talks. Slow and calm.
- No "why" questions. They sound like blame.
- If they push back twice, I say thanks and just send the email.
- Use only what is in my data. Never make up a number, a result, a customer or a name.
- If something you need is missing, ask me for it. Do not guess or fill it in.
Give me: what I say, the mirror line, the 2 replies, the next step line, then the email.
Last, save these steps as a skill called 'Send Me An Email' so you do it this way each time someone says just send me an email.
Built from: Never Split the Difference, Chris Voss, Chapter 2: Be a Mirror
What it does: Writes a 7 part handoff note for the next team, using only your ticket thread and notes.
Use it when: The next team keeps asking you what happened.
You get: A short handoff note with the goal, the ask, and 2 lines for the customer.
Open in
See the prompt
You are a support agent. Write a handoff note for [team, like billing or tech].
The ticket thread: [paste]
What I tried: [notes]
Write it in 7 short parts, so the next person can act without asking me:
1. The goal: what a good outcome looks like for this customer, in one line.
2. The customer and their account.
3. The problem in one line, and why it matters to them.
4. What I already tried, and what happened.
5. What the customer was told or promised, with dates.
6. What's needed from the next team. One clear ask.
7. How urgent it is, and why.
Then write 2 lines for the customer: who has it now and when they'll hear back. If my notes don't say when, write [WHEN] for me to fill in.
Rules:
- Plain words a new person on that team gets in one read.
- Use only what's in the thread and my notes.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Write Handoff Note' so you do it this way each time I ask to hand off a ticket.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 8: Decentralized Command
What it does: Turns one fixed ticket into a plain how to article any customer can follow alone.
Use it when: You fix the same problem again and again.
You get: A short article with steps, a fallback, and 3 search phrases.
Open in
See the prompt
You are a help center writer at [company].
The solved ticket: [paste, with names and account details taken out]
Write a help article any customer can follow alone:
1. A title in the customer's words, like "How do I..." or "Why can't I...".
2. One line on who this is for, and what they'll have when they're done.
3. Numbered steps to fix it, one action each. Say what they should see after each step.
4. What to do if it still doesn't work.
5. 3 other ways people might ask this, for search.
6. Read the steps as a brand new customer. Fix any step that needs something they might not know.
Rules:
- Plain words. Short steps.
- Leave out names, emails and account details.
- Only steps that are in the ticket. If a step is missing, write "check this step".
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Ticket To Help Article' so you do it this way each time I ask to turn a solved ticket into an article.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy
What it does: Reads your tickets, groups them by the real problem, and shows the biggest groups with counts and examples.
Use it when: You have a pile of tickets and no clear picture of what's wrong.
You get: Up to 5 problem groups with counts, one example each, and the first fix to make.
Open in
See the prompt
You are a support lead. Read this week's tickets.
Tickets: [paste or upload: subject, first message, tag]
Do this:
1. Group the tickets by the real problem, not the tag.
2. Give up to 5 of the biggest groups, with how many tickets each. If two groups tie, say so.
3. For each group: one short example in the customer's words, and which team could fix it at the source.
4. List any ticket that looks urgent or unsafe. These come before everything else.
5. Pick the one problem to fix first this week, and say why in one line.
6. Give one first step and an owner. Then name the next problem in line.
Rules:
- Count only what's in the file. Show your counts.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Find Ticket Patterns' so you do it this way each time I ask to read a week of tickets.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 7: Prioritize and Execute
What it does: Turns your notes into a job post with a must-have list, a weak-spots list, and clear pay and apply steps.
Use it when: Your job posts get few good applicants.
You get: A full job post in plain words, plus the must-haves and weak spots you can live with.
Open in
See the prompt
You are a recruiter. Write a job post.
My notes about the job: [paste]
Company and what we do: [one line]
Pay range: [range]
How to apply: [email, link or steps]
Where they work: [office, remote or both, and the city]
First, from my notes, list the 2 or 3 things this person must be great at here this year, and the weak spots we can live with. Show me both lists.
Then write the post in this order:
1. A plain job title.
2. Two lines on what the job is and why it matters.
3. What you'll do each week: up to 6 lines.
4. Must-haves: up to 5, starting with the strengths above. Nice-to-haves: up to 3.
5. Pay, where you work and how to apply.
Rules:
- Plain words. No buzzwords.
- Never ask for age, photos or anything that isn't needed for the job.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Write A Job Post' so you do it this way each time I ask to write a job post.
Built from: The Hard Thing About Hard Things, Ben Horowitz, Chapter 5, Hiring Executives
What it does: Turns a job post into interview questions, a live task, and a score sheet you can use for every person.
Use it when: You have to interview people and need fair questions fast.
You get: 8 questions with strong answers, a live task, a score sheet, and 2 questions to expect.
Open in
See the prompt
You are an HR manager. Write interview questions for this job.
The job post: [paste]
How long the interview is: [minutes]
Do this:
1. From the post, pick 4 or 5 traits this job needs. For each, one line on what good and great look like.
2. Write 8 questions about real work, tied to a trait. Most should start with "Tell me about a time you...".
3. Under each one: what a strong answer would show, and one follow-up question.
4. One short live task from the job. They try it, I give one piece of feedback, they try again. Say what to look for the second time.
5. Pick what fits in the time I gave, about 5 minutes each, in order.
6. A score sheet: each trait, 1 to 5, so I score everyone the same way.
7. 2 questions they might ask me, with honest answers I can fill in.
Rules:
- Only questions about the job. Never about age, family, health, religion or anything private.
- Plain words.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Interview Questions' so you do it this way each time I ask to plan an interview.
Built from: The Sales Acceleration Formula, Mark Roberge, Chapter 2: Five Traits Great Salespeople Have and How to Interview for Them
What it does: Writes a short email for each candidate based on their stage, in your voice.
Use it when: Candidates sit in silence and start to worry.
You get: One email per candidate, under 80 words each, ready to check.
Open in
See the prompt
You are a recruiter. Write an update email for each candidate.
The job: [title]
My name: [name]
Candidates: [paste: first name, stage, and next step, waiting, or not moving forward]
When waiting candidates will hear back: [date]
My booking link for next steps: [link]
Do this:
1. Next step: a short, warm email. Say what the next talk is about and who they'll meet, so they know what to expect. If a time is already on my calendar for this candidate, tell them that time and do not add the booking link. If no time is set, add the booking link. If the next step is longer or shorter than the time my booking link books, write [check: next step length does not match booking link] and do not add the link.
2. Waiting: a short email that says where they are and when they'll hear back. People worry most when they hear nothing.
3. Not moving forward: a kind, short no. Thank them for their time. Don't give a reason unless I add one.
Rules:
- Under 80 words each.
- Use only the names and dates I gave you.
- Ask me before you send, post, buy or delete anything.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Candidate Updates' so you do it this way each time I ask to update candidates.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 10: Phase 3: Affirm
What it does: Writes a day by day plan for a new hire's first week, with people to meet and a small task to finish.
Use it when: A new hire starts soon and you need a clear plan.
You get: A 5 day plan, a day 3 task, a login list, and 3 day 5 questions.
Open in
See the prompt
You are an HR manager. Plan a new hire's first week.
The job: [title and what they'll do]
Their manager: [name]
The team they'll work with: [names and roles]
Tools and logins they need: [list]
Start date: [date]
Why we do this work: [one line, in your words]
Do this:
1. Start day 1 with the why: what the company is for, how we work and what good work looks like here. Tasks come after that.
2. A plan for days 1 to 5: who they meet, what they learn and what they set up.
3. One small, real task to finish by day 3, with what done looks like.
4. A list of logins and tools to have ready before day 1.
5. 3 questions the manager should ask on day 5.
Rules:
- Short lines.
- Use only the people and tools I listed.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'New Hire First Week' so you do it this way each time I ask to plan a first week.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 16: Your People Strategy
What it does: Groups your notes by real problem, ranks them by how often they show up, and gives a fix for the top 3.
Use it when: The same problems keep coming back and you aren't sure why.
You get: A ranked list of problems, one small fix each, an owner, and a 2 week check.
Open in
See the prompt
You are my operations manager.
What went wrong: [paste your notes for the week or month]
Do this:
1. Group the notes by the real problem.
2. Rank the groups by how often they came up.
3. For the top 3: what part of it we control, one small fix to try, who should own it (a role, or a name from my notes) and how to check in 2 weeks if it worked.
4. If a problem keeps coming back, ask what we didn't make clear: the steps, the training or the tools. No blame on a person.
5. List any problem that could hurt someone or cost a lot, even if it came up once.
Rules:
- Count each note once. Put each note in one group only. If a note fits two groups, say so, but do not add it to both counts.
- If two groups tie for the top 3, list both and say they are tied.
- Count only what's in my notes. Show your counts.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Problem Log' so you do it this way each time I ask to read my problem notes.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 1: Extreme Ownership
What it does: Writes a short one page sheet about your business that you can hand out or email.
Use it when: You need something to leave behind after a visit.
You get: A one page sheet under 200 words with a clear order box and common questions.
Open in
See the prompt
Make a one page sheet about [your company] that I can hand to [who: like an office manager, a shop owner or a home owner].
What we sell: [what you do]
Who it is for: [your customers]
How to order or book: [phone, website, form, hours]
What makes us different: [only true facts]
Questions people ask most: [paste them with your real answers, or leave blank]
Write it so the reader is the hero and we are the guide:
1. A short title that says what they get, not who we are.
2. Their problem, in their words, and how it feels.
3. Why we can help: one line that shows we get it, and one true fact from my list.
4. A 3 step plan: how to start with us.
5. A clear "How to order" box at the bottom.
6. One line on what changes for them after.
Add a short "Questions people ask" section. Use my questions and answers if I gave them. If I left it blank, list the 3 questions buyers will most likely ask, and answer only from my facts. If my facts do not answer one, write [CHECK] so I can fill it in before I print.
Use plain words and short sentences. No jargon. Do not add numbers, awards, reviews or results I did not list. Keep it under 200 words so it fits on one page.
Last, save these steps as a skill called 'One Page Sheet' so you do it this way each time I ask.
Built from: Building a StoryBrand, Donald Miller, Chapter 3: The Simple SB7 Framework
Simple AI
CallsFirst message