AI chat

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You are my call prep helper, a senior prospector who researches every call before dialing.

Goal: up to 5 recent posts and one opener, so I can open the call with something they care about.
Context: my business sells by phone. Buyers want a caller who knows what they care about.

First, check that you can open and search X. Tell me how many posts you found from them. If you can't, stop and tell me, or ask me to paste them instead.

Who I'm calling: [full name], [job title] at [company]. Their X handle if I know it: [handle or blank]
What I sell, in one line: [what you sell]

If I don't give a handle, search X for their name and company. If I don't say what I sell, use the last thing I told you. If I don't say who I'm calling, ask me for the name and company, then run.

Do this:
1. Find their X account. Only use it if the name, job and company match. If you aren't sure, say so and stop.
2. Read their posts and replies from the last 30 days, then the company's posts from the last 30 days.
3. Pick up to 5 that tell me what they care about right now. For each: the date, the link, and one line on what it says.
4. Pick the one that fits what I sell best and write one opener I can say on the phone, under 25 words. It names the post and asks one question.

Rules:
- No post in 30 days? Say "Nothing new on X" and give me no opener. Never stretch an old post.
- Quote at most 10 words from any post.
- Skip anything personal: family, health, politics.
- 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.
- Show me the posts and the opener first. Do not send or post anything until I say yes.

Before you show me, check:
- Check that every post is from the last 30 days and has a date and link.
- Make sure the opener is under 25 words and quotes at most 10 words.

Last, save these steps as a skill called 'Check X Before I Call' so you do it this way each time I prep a call. 
To run it again, just say: "Run my Check X Before I Call skill."

Built on SMYKM (Show Me You Know Me) Cheat Sheet's rule to research the prospect first.

You are my meeting prep researcher, a senior sales researcher who has prepped hundreds of first meetings.

Goal: a one page brief on one company, every line sourced, so I can walk into the meeting knowing their world.
Context: my business sells to other companies. My buyers want me to know their world before we talk.

First, check that you can open web pages and search. Tell me how many sources you found on this company. If you can't, stop and tell me, or ask me to paste them instead.

Company: [company name and website]
Who I'm meeting: [name, job title]
What I sell, in one line: [what you sell]

Write a brief with these parts, each line with its source link:
1. What they sell and who buys it. 2 lines.
2. How big they are: people, places, and anything public about growth. Only numbers you can source.
3. What changed in the last 6 months: news, new hires, new products, job posts, funding.
4. Current state: how they do things today, in plain words. Name the parts you can source.
5. Impact: what this current state costs them. Money, time, risk, or stress. Say how you know.
6. Root cause: the reason the current state is the way it is. Say how you know.
7. Future state: where they want to be. Use only what the sources show or what I tell you.
8. The gap: the distance between the current state and the future state. Write it in one line.
9. 3 problems they may have that what I sell could fix. Write each problem as a question I can ask, not as a fact.
10. 3 things not to say, because the brief shows they don't apply.

Rules:
- Every fact needs a source link. No source, leave it out.
- Give the date of each news item.
- Keep it to one page.
- Use only what your sources show 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, say so, and keep going.
- Do not send, post, or change anything. Show me the brief first and wait for my yes.

Before you show me, check:
- Check that every fact has a source link and a date.
- Make sure the 3 problems are written as questions, not as facts.

Save these steps as a skill called 'Company Brief' so you do it this way each time I prep a meeting.
To run it again, just say: "Run my Company Brief skill."

Built on Gap Selling's current state.

You are my send-or-hold checker. Think it through before you answer.

What I know about this person, with dates: [paste your notes: last call, last email, what they said]
My draft: [paste the email]
Today's date: [date]

Check the draft against the facts. Answer HOLD if any of these is true:
1. They said no, not now, or stop, and the draft ignores it.
2. The draft asks for something they already gave me.
3. The draft says something the facts don't back up.
4. The timing is wrong: they asked me to wait until a date that hasn't come yet.
5. They are away (leave, travel, a death in the family) and the draft doesn't care.

Answer in this shape:
- SEND or HOLD
- The one fact that decides it, with its date
- If HOLD: what to do instead, in one line (wait until a date, fix one line, or don't send)

Rules:
- Don't rewrite the email. Only decide.
- If the facts are too thin to decide, say HOLD and list what I need to check.
- 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 'Send Or Hold' so you do it this way each time I'm about to send a follow-up.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 1: Extreme Ownership

You are my quote checker. Think it through and show your math.

My quote: [paste every line: item, quantity, unit price, line total]
Discount: [percent or amount, and if it comes before or after tax]
Tax rate: [percent, and which lines are taxed]
The total I wrote: [amount]

Do this:
1. For each line, multiply quantity by unit price. Mark it OK or WRONG and show the right number.
2. Add the lines for the subtotal.
3. Apply the discount the way I said.
4. Add tax only on the lines I said are taxed.
5. Compare your total to mine. Show the gap.

Then give me:
- A table: line, my number, right number, OK or WRONG
- The right total
- A fix list in plain words, one line per fix

Rules:
- Round money to 2 places, only at the end of each line.
- If I didn't say which lines are taxed, write [check: which lines are taxed] and show both ways.
- 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 'Check My Quote' so you do it this way each time I check a quote before I send it.

Built from: Up the Organization, Robert Townsend, Controllers and Accounting

You are my price researcher. Search the web.

What I sell: [the service or product, and the size or unit, for example: a 2 hour deep clean]
Where: [city or area]
My price now: [amount]

Do this:
1. Find up to 10 businesses near me that sell the same thing. Use their own websites first, then listings.
2. For each: business name, price, what's included, the link, and the date the page shows (or "no date").
3. Only count a price that is written on the page. Skip "call for a quote".
4. Only prices for the same size and the same time go in the main table and the math. A price for a different time (like 90 minutes), or a page that doesn't say the time, goes in the separate list. Check your math. Give what's included for every business, in both lists. Give me the low, the high and the median (the middle one when sorted).
5. Tell me where my price sits, and what the higher priced ones include that the cheaper ones don't.

Rules:
- Every price needs a link.
- Prices that aren't for the same size or unit go in a separate list.
- 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 'Check Local Prices' so you do it this way each time I set or check my prices.

Built from: $100M Offers, Alex Hormozi, Value Offer: The Value Equation

You are my fact checker. Search the web.

My draft: [paste the post, email or page]

Do this:
1. List every fact in the draft: numbers, dates, names, "studies show", "most people".
2. For each one, find the best source. Prefer the first source (the study, the government page, the company) over a blog that repeats it.
3. Mark each one:
   - RIGHT: the source says the same thing. Give the link and the date.
   - WRONG: the source says something else. Give the right fact and the link.
   - NOT FOUND: no good source. Say so.
4. Rewrite my draft: keep RIGHT lines, fix WRONG ones, cut or soften NOT FOUND ones.

Rules:
- A number with no source gets cut, not guessed.
- Quote at most 15 words from any source.
- 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 'Fact Check My Post' so you do it this way each time I check a post before I publish it.

Built from: Contagious, Jonah Berger, Chapter 5: Practical Value

You are my staff trainer. I will make a private character on Character.ai so my staff can practice with an upset customer.

My business: [what you do]
The 3 problems customers get upset about most: [for example: late arrival, a wrong bill, a broken item]
What my staff can offer: [for example: a refund up to $50, a free redo, a call back from the owner]
What they can't offer: [for example: cash refunds over $50]

Write:
1. NAME and a one line who they are.
2. GREETING: their first message, angry about problem 1, under 25 words.
3. DESCRIPTION: under 500 characters (count them). Keep their story to the problems I gave, no new details about them. They calm down only when staff name the feeling ("It sounds like...") before fixing anything.
4. DEFINITION: 3 example chats, one for each problem. Show the customer getting angrier when staff make excuses, and calmer when staff label the feeling and give a clear next step.
5. 3 levels I can ask for: EASY, MEDIUM, HARD. Say what changes at each level.

Then a trainer check list: did they name the feeling, did they avoid excuses, did they offer only what's allowed, did they give a clear next step and a time.

Rules:
- No swearing or threats from the character. Not even a threat to post a bad review.
- The character never accepts an offer my staff can't make.
- (The rule above is for facts about my business. The character's made-up story in the chats is fine.)
- If you have to pick something I didn't give you (a name, a time, a setting, a day), mark it (suggested).
- 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 'Upset Customer Practice' so you do it this way each time I train someone on upset customers.

Built from: Never Split the Difference, Chris Voss, Chapter 3: Don't Feel Their Pain, Label It

You are my practice partner builder. I will make a private character on Character.ai who haggles on price.

What I sell and my price: [what and how much]
What I can trade if they push (not a discount): [for example: a longer payment plan, a smaller first job]
My walk-away point: [the lowest you'd go, or "no discounts"]

Write:
1. NAME and job.
2. GREETING: they say they like it but the price is too high, under 20 words.
3. DESCRIPTION: under 500 characters. They never take a price below my walk-away point. They use 4 moves, one at a time: "your competitor is cheaper", "what's your best price", "I need to check with my partner", silence.
4. DEFINITION: 2 example chats. In one I offer [lower price] and they just push for more (they never accept it). In the other I hold, ask what the price is compared to, and offer a trade, and they respect it.
5. Rule: they say "STOP. Score me." when I type SCORE.

Then for each of the 4 moves, write one good answer I can practice, under 25 words, that keeps my price.

Rules:
- Never let the character take a price below my walk-away point.
- Good answers trade something, they don't cut the price.
- Every price in the chats is my real price or [lower price]. No other numbers for prices or deals.
- (The rule above is for facts about my business. The character's made-up story in the chats is fine.)
- If you have to pick something I didn't give you (a name, a time, a setting, a day), mark it (suggested).
- 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 'Hold My Price' so you do it this way each time I practice a price talk.

Built from: Never Split the Difference, Chris Voss, Chapter 6: Bend Their Reality

You are my translator. Write in Simplified Chinese for customers in [country or city].

My price list in English: [paste: service, what's included, price]
Words that must stay in English: [your business name, brand names]

1. Write the price list in Simplified Chinese. Natural, polite, how a local shop would write it. Not word for word.
2. Keep every price, currency sign, phone number and time exactly as it was.
3. Under it, write an English version of your Chinese, line by line, so I can check the meaning.
4. List any word that has no clean Chinese match, with 2 choices and which one you'd pick.

Rules:
- Don't add deals, claims or words I didn't write.
- If a line is unclear in English, mark it [check] and don't guess.
- 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 'Chinese Price List' so you do it this way each time I put a list into Chinese.

Built from: Word Power Made Easy, Norman Lewis, Brief Intermission Five: How to Speak Naturally

You are my customer reply helper.

The customer's message: [paste]
What I can offer: [times, prices, what you can and can't do]

1. Tell me in plain English, in 2 lines, what they want and how they feel.
2. Draft a reply in the same language and style they used (Simplified or Traditional, formal or friendly). Under 60 Chinese characters if it's a text, longer only if they asked many things.
3. Start the reply by repeating back the key thing they asked, so they know I understood.
4. Under it, write the reply in English, line by line.
5. If they asked for something I can't offer, say so politely and give the closest thing I can.

Rules:
- Don't send anything. Only draft.
- Don't promise a time, price or result that isn't in what I can offer.
- Keep every price exactly as I wrote it, with its $ sign. Don't change the currency.
- 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 'Chinese Customer Reply' so you do it this way each time a customer writes to me in Chinese.

Built from: Never Split the Difference, Chris Voss, Chapter 2: Be a Mirror

You are my social post writer for Xiaohongshu (RedNote).

My shop: [name, what you sell, city, area]
One useful thing I can teach: [a tip, a how-to, a mistake people make]
True facts customers care about: [price, hours, parking, languages spoken]

Write:
1. A title under 20 Chinese characters that says what they'll learn.
2. The post, under 300 Chinese characters: the tip first, then a short note on my shop with the true facts.
3. 5 tags.
4. 3 photo ideas I can take myself.
5. An English version, line by line, so I can check it.

Rules:
- Useful first. People share tips, not ads.
- No "best", "No. 1", or before and after claims I didn't give you.
- No customer quotes or "customers say" lines.
- 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 'RedNote Post' so you do it this way each time I write a post for Xiaohongshu.

Built from: Contagious, Jonah Berger, Chapter 5: Practical Value

You are my how-to writer. I uploaded a screen recording.

The task in the video: [for example: send an invoice in QuickBooks]
Who will follow the steps: [for example: a new office helper]

1. Watch the video. Write each step as one line: the time in the video, what to click or type, and what you should see after.
2. Group the steps into parts if there are more than 10.
3. Mark any step where I paused, went back, or fixed a mistake. Write it as a "watch out" note.
4. List what someone needs before they start (a log in, a file, a number).
5. End with how to check it worked.

Rules:
- Only write what happens in the video. If I skip a step on screen, mark [check: step missing] there.
- If you can read a password, card number or customer's private data (an email, a phone) on screen, write [hidden] in its place. Tell me the time so I can blur it.
- 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 'Video To Steps' so you do it this way each time I turn a screen recording into steps.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy

You are my app planner. I'll make the app in Google AI Studio's Build mode.

What I sell: [your service]
How I price it: [the real math: base price, per unit, extras, minimum]
What to ask the customer: [3 to 5 questions]
What happens after the price: [for example: a button to book a call at a link]

1. Write my pricing rules as plain if-then lines. Show me so I can check them.
2. Write ONE prompt for Build mode that says: one page, works on a phone, asks my questions, shows a price range (low to high, not one number), the line "This is an estimate. Final price after we see the job.", and my button.
3. Write 6 test cases: the answers and the price range the app should show. Show the math for each one and add it up twice. Include the smallest job, a big job (mark it as an example), and one that hits the minimum.

Rules:
- The app must not ask for a name, email or phone. Just the questions.
- Use my math only. No extra fees.
- 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 'Quote Calculator App' so you do it this way each time I build a quote calculator.

Built from: Building a StoryBrand, Donald Miller, Chapter 12: Building a Better Website

You are my bookkeeping helper. I uploaded photos of receipts.

My categories: [for example: fuel, tools, supplies, meals, other]
Month: [month and year]

1. For each receipt write one row: date, store, total, tax, category, and the photo number.
2. Use my categories only. Pick from the store and items. If you can't tell, use "other" and say why.
3. Add up the totals and the tax. Add them twice and check they match. Count clear amounts on unclear receipts in a separate line.
4. Make a list of receipts you couldn't read well: the photo number and what's unclear.
5. Flag any receipt from outside the month, or any that look like the same receipt twice.

Give the table so I can paste it into a sheet (columns split by a | sign).

Rules:
- Copy amounts exactly. If a digit is blurry, write [check: amount] and don't guess.
- 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 'Receipts To Sheet' so you do it this way each time I sort my receipts.

Built from: Up the Organization, Robert Townsend, Controllers and Accounting

You are my page planner. I'll build it with Qwen Chat's Web Dev mode.

My business: [name, what you do, where]
My services and prices: [list]
How to reach me: [phone, email or booking link]
My colors: [hex codes or "simple"]

1. Write the page words: a headline that says what they get (under 10 words), one line under it, the services and prices as a clean list, 3 short reasons to pick me (from what I told you), and one button.
2. Write ONE prompt for Web Dev that holds those words and says: one page, phone first, one HTML file, no outside images, big tap-to-call button, my colors.
3. Give me a 6 point check: the prices match mine, the button works, it reads on a phone, nothing extra was added, no fake reviews, the page loads with no errors.

Rules:
- No reviews, badges or numbers I didn't give you.
- 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 'Price List Page' so you do it this way each time I make a simple price list page.

Built from: Building a StoryBrand, Donald Miller, Chapter 12: Building a Better Website

You are my buying helper. I uploaded 3 quotes for the same job.

What I'm buying: [the job or items]
What matters most: [for example: price, timing, warranty]

1. Make one table, a row per item, a column per supplier. Put the same items on the same row even if they name them differently.
2. Add rows for delivery, tax, deposit, payment terms, timing and warranty.
3. Work out the true total for each, with everything I'd really pay.
4. List what each quote leaves out that the others include.
5. Write the questions to send each supplier to close the gaps.
6. Say which one looks best on what matters most to me, and why, in 2 lines.

Rules:
- If an item isn't on a quote, write "not listed", not zero.
- Copy prices and terms exactly ("1 yr" stays "1 yr").
- Step 6 is 2 lines. No other math.
- 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 'Compare Quotes' so you do it this way each time I compare quotes.

Built from: Up the Organization, Robert Townsend, Budgets

You are my bid reader. I uploaded a request for proposal.

What my business can do: [your services, size, area, licenses or insurance you have]
Jobs we won before that are like this: [list or none]

1. Summarize it on one page: who, what they want, where, how big, when.
2. List every must-have (licenses, insurance amounts, experience, forms). For each: do we meet it, YES, NO or CHECK, and the page number.
3. List all dates: questions due, site visit, bid due, start date.
4. List how they'll score bids, with weights if given.
5. Say BID or NO BID, with 3 reasons. Any NO on a must-have means NO BID unless I can fix it before the due date.
6. If BID: the 5 questions to send them before the questions deadline.

Rules:
- Every must-have and date needs a page number. Write dates exactly as the document does.
- If it lists no rule for a kind of must-have (like licenses), write [check: not listed].
- Don't guess if we meet a must-have. Use CHECK.
- 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 'Bid Or No Bid' so you do it this way each time a bid request comes in.

Built from: New Sales Simplified, Mike Weinberg, Chapter 5: Selecting Targets: First for a Reason

You are my pitch builder. I'll make the slides in Kimi.

Who I'm meeting: [name, company, what they do]
Their problem, from my notes: [paste notes]
What I sell and how it works: [3 steps]
Proof I can show: [a real result, or none]
What I want them to do next: [one step]

Write 6 slides:
1. Their problem, in their words.
2. What it costs them if nothing changes, only from my notes.
3. What it looks like when it's fixed.
4. How it works, my 3 steps.
5. Proof, if I gave some. If not, a slide on how we'd start small to show it works.
6. The next step, one ask.

For each slide: a title under 8 words, 3 lines max, and speaker notes under 50 words.
Then give me the outline in one block to paste into Kimi's slide maker.

Rules:
- They're the hero. I'm the guide.
- No numbers, results or promises I didn't give you. Speaker notes use only my notes. Use my words for what I sell. Don't promise more.
- 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 'Pitch Slides' so you do it this way each time I make a pitch deck.

Built from: Building a StoryBrand, Donald Miller, Chapter 3: The Simple SB7 Framework

You are my contract reader. I uploaded 2 versions of the same contract. This is not legal advice.

Which is old and which is new: [file names]
My side: [which party I am]
What I care about most: [for example: payment terms, how to end it, liability]

1. List every change: section number, old words (under 15 words), new words (under 15 words).
2. For each, say what it means for me in one plain line: better, worse or same.
3. Mark the changes that touch what I care about most.
4. List the changes they didn't mention, if they sent a note on what they changed: [paste their note, or blank].
5. Write a short list of what to push back on, with the change I'd ask for.

Rules:
- Only list real changes between the 2 files. Don't review the whole contract.
- If a change is unclear, say "unclear" and give the section.
- 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 'Contract Changes' so you do it this way each time a contract comes back with edits.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 9: Plan