What it does: Reads your help docs, then writes a short reply that only uses what the docs say.
Use it when: You need to reply to a ticket but the answer is buried in docs.
You get: A ready to check reply, the steps, and the doc each fact came from.
Open in
See the prompt
You are a support agent at [company]. Answer this ticket.
Where our help docs and rules live: [the Google Drive or OneDrive folder]
The ticket: [paste]
Customer's name: [name]
Do this:
1. Read our help docs and rules in that folder before you write anything.
2. Say in one line what the customer needs.
3. Write a short, warm reply that fixes it, using only our docs. Assume they don't know how we work. Say what to do, what happens next and why.
4. If the fix has more than one step, number the steps and say which one they're on.
5. If our docs don't cover it, or cover only part of it, answer the part they cover. For the rest, write "Needs a person" and say why. Don't guess.
6. End with who to reach if it doesn't work.
7. List which doc each fact came from.
Rules:
- Short. Plain words. No blame.
- Never promise a refund, a date or a fix our docs don't allow.
- 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 'Answer Support Tickets' so you do it this way each time I ask to answer a ticket.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 12: Phase 5: Acclimate
What it does: Reads your kickoff call and writes a 4-week plan with a day 30 goal in the client's own words.
Use it when: You hang up and the plan is still in your head.
You get: A one-page plan by week, a quoted goal, and a list of what you still need.
Open in
See the prompt
You are my client success lead.
The kickoff call: read the transcript called [file name] in my files.
No file? Paste the transcript: [transcript]
Do this:
1. Pull out: who they sell to, what they sell, the words their buyers use, the top 3 objections, and the 3 things they want in 30 days.
2. Write the goal for day 30 in the client's own words, quoted from the call.
3. Write a one-page plan in plain words: what we'll do each week for 4 weeks. Make week 1 a fast, visible win.
4. List anything I still need, and how WE can find it ourselves.
Rules:
- Don't ask the client to do homework I can do myself.
- 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 'Kickoff Plan' so you do it this way each time I have a kickoff call.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 11: Phase 4: Activate
What it does: Reads your client talks in Close and adds them to their Notion page, newest first.
Use it when: Clients keep asking where things stand.
You get: A fresh client page with a new top line and a count of rows added.
Open in
See the prompt
You are my client success lead. Use the pasted Close and Notion data below as the source of truth.
Client: [client name]
Their Smart View in Close: [Smart View name]
Their Notion page: [link]
Do this:
1. Find today's real conversations in Close, only for the leads in that Smart View.
2. Update only [client name]'s page from that client's conversations, not every lead in the Smart View.
3. Add each one as a row on their Notion page: date, person, company, what they said in one line, next step.
4. Newest at the top.
5. Keep the line at the top of the page current: where we are in the plan this week and what happens next, so they always know what's going on without asking.
Rules:
- Plain words.
- Never put anything about my other clients on this page.
- Add rows only. Never move or delete a page.
- 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.
In your final answer, state that the rows were added. Give the final row and the top-line text.
Last, save these steps as a skill called 'Update Client Page' so you do it this way each time I update a client's page.
Connect first: your CRM. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 12: Phase 5: Acclimate
What it does: Turns your month end list into one ordered checklist with owners, due days, and clear done marks.
Use it when: Month end is near and your steps are scattered.
You get: One checklist in order, plus what to do today and what to fix next month.
Open in
See the prompt
You are my controller. Help me close the month.
Month we're closing: [month]
Today's date: [date]
What we do at month end, and who does it: read my doc called [doc name] in my files. No doc? Paste the rough list: [list]
When the books must be closed: [for example, the 5th business day]
Where things are now (optional): [paste notes, like "bank match done, 3 bills missing"]
Do this:
1. Turn my list into one checklist in the right order. Put steps that others wait on first.
2. For each step: who does it, the day it's due, and what "done" means, in words anyone on the team could check.
3. Add any common step I missed, marked "you may need this".
4. If I gave you where things are, mark each step done, open or late, and list what to do today.
5. End with one line: what to change in the checklist next month, so it runs the same way with less help from me.
Rules:
- Short lines.
- Never mark a step done unless my notes say so.
- 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 'Month End Close' so you do it this way each time I close a month.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 8: The Franchise Prototype
What it does: Reads this week's call reviews and writes one fix for each rep, with a quote, new words, and a drill.
Use it when: You have call scores but no time to coach each rep.
You get: One fix per rep, a quote, words to say, a 10 minute drill, and a short summary list.
Open in
See the prompt
You are my sales coach.
This week's call reviews for my team: [the folder or doc where I save the daily pages]. Read every page from this week.
For each rep:
1. Find the one thing that cost them the most this week, like talking over the buyer or not asking for the meeting. Count how many calls it showed up in.
2. Quote one moment from their calls that shows it.
3. Give them the words to say instead, in one or two lines.
4. Give a 10 minute practice drill for it, done first in a safe role play, not on a big call.
5. Set the bar for next week: use the new words on at least 3 real calls before we judge it.
6. Name one thing they did well, with a quote.
Then give me a short list: each rep, their one fix and how many calls it showed up in.
Rules:
- One fix per rep. Never a list of 10.
- Only use what's in the reviews. Quote them.
- 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 'Weekly Coaching Fix' so you do it this way each time I ask.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: SPIN Selling, Neil Rackham, Chapter 11: Turning theory into practice
What it does: Reads each resume and makes a table showing who meets your must-haves and where it says so.
Use it when: You have a pile of resumes and need to sort them fast.
You get: A sorted table with proof lines and one call question per person.
Open in
See the prompt
You are helping me screen applicants. A person makes every decision.
The job's must-haves: [paste, up to 5]
Where the resumes are: [the Google Drive or OneDrive folder, or upload them]
Do this:
1. Read every resume in that folder. Make a table: applicant number, each must-have (yes, no or not clear) and the line in the resume that shows it.
2. Sort the table by how many must-haves are a clear yes. Look for real strength on the must-haves. Don't push someone down for small gaps that aren't on my list.
3. For each applicant, write one question to ask on a first call, about a must-have marked no or not clear. Make it ask for a real example, like "Walk me through a time you...".
Rules:
- Judge only on my must-haves. Ignore name, age, gender, photos, address and anything else not on the list.
- Never say to reject anyone. Write "not clear" when you can't tell.
- 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 'Screen Applicants' so you do it this way each time I ask to screen applicants.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: The Hard Thing About Hard Things, Ben Horowitz, Chapter 5, Hiring Executives
What it does: Reads your handbook and answers a staff question in plain words, quoting the exact section it came from.
Use it when: Staff keep asking you the same handbook questions.
You get: A short answer, the handbook quote and section, and when to send them to HR.
Open in
See the prompt
You are an HR manager. Answer a staff question using only our handbook.
Where our handbook lives: [the Google Drive or OneDrive file]
The question: [paste]
Do this:
1. Read the handbook first. Then answer in 3 short lines or less, in words the newest person on the team would get.
2. Quote the part of the handbook it came from, with its section name.
3. If the handbook gives the reason for the rule, add it in one line.
4. If the handbook doesn't answer it, say so and write "Ask HR". Don't guess.
5. If it's about pay, health, leave or a complaint, add: "Talk to HR about this one."
6. End with: "Not clear? Ask me again in your own words."
Rules:
- 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 'Answer From Handbook' so you do it this way each time I ask to answer a staff question.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 6: Simple
What it does: Writes 5 short ads, each with a different reason to click, in plain words.
Use it when: You need ads but don't know which angle works.
You get: 5 ads with short headlines and one line each.
Open in
See the prompt
You are my ad writer.
What I sell: [what you sell]
Who it's for: [who]
What I want them to do: [click, book, buy]
Write 5 ads. Each has a headline under 30 characters and one line under 90 characters.
1. Call out who it's for, so the wrong people scroll past.
2. Each ad tries a different reason to click: save time, save money, a result, a question, a story.
3. End with the one thing I want them to do.
4. Tell me how to pick the winner: run all 5 with the same small budget, then keep the ad with the most [booked calls, sales] and stop the rest.
Rules:
- Plain words. No hype.
- No claims I can't prove.
Last, save these steps as a skill called 'Five Ad Tests' so you do it this way each time I need new ads.
Built from: $100M Leads, Alex Hormozi, Section III: Get Leads, Run Paid Ads Part I: Making An Ad
What it does: Writes a feedback form with 5 or fewer simple questions, mostly tick boxes, so people finish it fast.
Use it when: Your feedback form is long and people quit it.
You get: A short form with 5 questions or fewer.
Open in
See the prompt
You are my product researcher.
I'm building: [what]
For: [who]
Write a feedback form with 5 questions or fewer:
1. Tick boxes where you can, with an optional notes box under each.
2. Ask the result they want most, and what stops them today.
3. Ask what would make it faster or less work.
4. Ask what they'd pay, and one thing they'd change.
Rules:
- Simple words. Takes under a minute.
- Use only what is in my data. Do not add facts, numbers, response times or promises I did not give you.
- If something you need is missing, ask me for it.
Last, save these steps as a skill called 'Feedback Form' so you do it this way each time I ask to write a feedback form.
Built from: $100M Offers, Alex Hormozi, Value Offer: The Value Equation
What it does: Writes a short Tally form for new leads: 4 to 6 questions, the right answer types, a yes to texts box, and a thank you page.
Use it when: Your contact form asks too much, or too little to call back well.
You get: The form questions in order with answer types, the permission line, the thank you words, and the hidden fields to add.
Open in
See the prompt
You are my form helper, a sales ops pro who builds short forms that get filled in.
Goal: a full Tally form draft, so I can build it in 10 minutes.
Context: my business gets leads from a form. They want a short form, and I need enough to call back well.
First, check that you can read my answers below. Tell me which ones I gave. If one is missing, use its default, or ask me to paste my current form instead.
What the form is for: [for example: people who want a quote]
What I need to call them back well: [list. If I don't say, use name, phone, email and what they need]
How fast I really call back: [for example: same day. If I don't say, write [check: callback time]]
My booking link for the thank you page: [link or blank]
Write the form:
1. A title and one line under it that says what happens after they send it.
2. 4 to 6 questions, in order. For each: the words, the answer type (short text, multiple choice, phone, email), and required or not. Easy ones first.
3. One question that tells me how soon they need help, with choices.
4. A checkbox: "Yes, you can text me about my request." Not ticked by default.
5. The thank you page words, with the booking link if I gave one.
6. Hidden fields to add so I know where they came from (for example: utm_source).
Rules:
- Every question must help me call them back. Cut the rest.
- 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, say so, and keep going.
- Do not publish or change anything in Tally. Show me the draft and wait for my yes.
- Draft only. Never send, post, book, pay or change anything until I say yes.
Before you show me, check:
- Check that every question helps me call them back.
- Make sure the text checkbox is not ticked by default.
Last, save these steps as a skill called 'Lead Form' so you do it this way each time I build a lead form.
To run it again, just say: "Run my Lead Form skill."
Built on Never Lose a Customer Again's Assess phase: the buyer is still deciding.
What it does: Reads your Tally form answers and scores each lead on fit and how soon they need you, so you call the hottest first.
Use it when: Form answers pile up and you call them in the order they came.
You get: A ranked call list with a score, the reason in a few words, and the bad fits set aside.
Open in
See the prompt
You are my lead sorter, a sales manager who has ranked inbound leads for years. You are a pro at this.
Goal: every form answer scored and ranked, so I can call the best fits first today.
Context: my business gets form leads. The best ones want a call first, and they need it fast.
First, check that you can open my Tally answers. Tell me how many answers you found. If you can't open it, stop and tell me to connect it (Claude: Customize, then Connectors, then add a custom connector), or ask me to paste it instead.
A good fit is: [for example: offices over 2,000 square feet in my city]
A bad fit is: [for example: outside my area, students, vendors]
1. Score each answer:
Fit: 0 to 3. 0 = matches none of my good fit. 1 = matches one part. 2 = matches most. 3 = matches all of my good fit.
Soon: 0 to 3. 0 = no timing given. 1 = sometime this year. 2 = next few months. 3 = needs it now or has a date.
Total = Fit + Soon.
2. For each lead, write the gap in plain words: where they are now, where they want to be, and what waiting costs them. Use only what they wrote.
3. Sort by total, then by newest.
4. Give me a table: rank, name, phone, total, why in under 10 words, and whether they ticked yes to texts.
5. List bad fits at the end with the reason. Don't delete them.
Rules:
- If an answer is empty, score that part 0 and say so.
- Only text people who ticked yes. Call the rest.
- 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.
- Do not send texts, make calls, or change anything without my yes.
Before you show me, check:
- Check that each total equals Fit plus Soon.
- Make sure ties are sorted newest first.
Last, save these steps as a skill called 'Sort My Form Leads' so you do it this way each time I sort new form answers.
To run it again, just say: "Run my Sort My Form Leads skill."
Built on Gap Selling's rule that more impact means a bigger gap.
What it does: Reads your Asana projects, finds late and stuck tasks, and drafts a short, kind nudge for each person.
Use it when: Tasks slip and you only find out when a customer asks.
You get: Late tasks by person, what's blocking the rest of the work, and a draft nudge for each person.
Open in
See the prompt
You are my project helper, with access to Asana.
Today's date: [date]
Projects to check: [project names]
1. Find tasks that are past due, and tasks with no due date or no owner.
2. Group late tasks by person. For each: task, project, due date, days late.
3. Find the late tasks that block other tasks, and put them first.
4. Pick the one task that matters most this week, and why, in one line.
5. For each person, draft a short nudge under 50 words: name the tasks, ask what's in the way, and ask for a new date. Kind, not blaming. Don't promise anything for me.
6. Show me everything. Don't change tasks or post comments unless I say yes.
Rules:
- Use only task data. Don't guess why something is late.
- 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 'Late Tasks' so you do it this way each time I check on late work.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 7: Prioritize and Execute
What it does: Reads your meeting notes, pulls out every to-do with an owner and a date, and adds them to Asana after you OK the list.
Use it when: Meetings end with 'great, let's do that' and nothing gets done.
You get: A task list with owners and dates, the open questions, and the tasks added to Asana once you say yes.
Open in
See the prompt
You are my meeting helper, with access to Asana.
My notes: [paste your notes or the transcript]
The Asana project for these tasks: [project name]
Team names: [who's on the team]
1. Pull out every to-do. For each: what, who, by when.
2. If no one owns it, mark [check: owner]. If there's no date, mark [check: date]. Don't guess either.
3. Write each task name as a verb and a thing, under 10 words.
4. List decisions made and open questions, separate from tasks.
5. Show me the list. After I say yes, add the tasks to the Asana project with owner, date and a one line note from the meeting.
Rules:
- Only things said in the notes. No extra tasks.
- 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 'Notes To Tasks' so you do it this way each time I finish a meeting.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Up the Organization, Robert Townsend, Meetings
What it does: Turns how you start with a new client into an Asana project with steps, owners and days, so every client gets the same good start.
Use it when: Every new client starts a little differently, and things get missed in week one.
You get: A project plan with sections, tasks, owners, days after start, and a welcome step, built in Asana after you say yes.
Open in
See the prompt
You are my process builder, with access to Asana.
What I sell: [your service]
How I start with a new client now: [rough steps, in any order]
Who does what: [team names and roles]
What clients should feel in the first 2 weeks: [for example: looked after, clear on what happens next]
1. Put my steps in order and group them into sections: Before day 1, Week 1 (day 1 to 7), Week 2.
2. Add any step that's missing for a good start, and mark it NEW so I can check it: a welcome message, a "what happens next" note, a check-in at day 7.
3. For each task: name, owner role (a role, not a name), day after start (mark days I didn't give as suggested), what done looks like. Mark every task I didn't list as NEW.
4. Show me the plan. After I say yes, make it as a project in Asana. Tell me how to save it as a template so I can use it each time.
Rules:
- Keep it under 20 tasks.
- 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 'Client Onboarding Plan' so you do it this way each time I set up how we start with clients.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 11: Phase 4: Activate
What it does: Reads your ClickUp tasks each morning and writes a short update: what got done, what's due today, and what's stuck.
Use it when: You spend the first hour of the day asking everyone where things are.
You get: A short update under 120 words: done yesterday, due today, stuck, and one question for each stuck task.
Open in
See the prompt
You are my team update writer, with access to ClickUp.
Today's date: [date]
Which spaces or lists: [names]
1. Find tasks closed yesterday, tasks due today, and tasks past due.
2. Count days late from the due date to today, and check the count. Find stuck tasks: in the same status for over [number] days, or with a comment asking for help.
3. Write the update, under 120 words:
- Done yesterday: who and what, one line each
- Due today: who and what
- Stuck: the task, how long, and one question to unstick it
4. End with the one thing that matters most today.
5. Show me. Don't post it or change anything unless I say yes.
Rules:
- Use names and task names exactly as they are in ClickUp.
- Write dates as dates, no weekday names.
- Only tasks from the lists I named.
- 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 'Daily Team Update' so you do it this way each time I start the work day.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 10: Leading Up and Down the Chain of Command
What it does: Turns the way you do a job into a clean ClickUp task with a checklist, so anyone on the team can do it the same way.
Use it when: The how-to for a job lives in your head and new people do it differently.
You get: A task with a checklist in order, the why for the tricky steps, and how to save it as a template.
Open in
See the prompt
You are my process writer, with access to ClickUp.
The job: [for example: closing up a job site]
How I do it, rough: [type it out, in any order]
Who does it: [role]
1. Put the steps in order. Each step starts with a verb and is under 12 words.
2. Mark the steps that are easy to skip but matter, and add why in under 10 words.
3. Add the check at the end: how they know it's done right.
4. Show me. After I say yes, make a ClickUp task named "[job] checklist" in the list I name: [list name], with the steps as a checklist.
5. Tell me how to save it as a template in ClickUp so we can reuse it.
Rules:
- Only my steps. If one seems missing, ask, don't add it.
- Under 20 steps.
- 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 'Checklist From Steps' so you do it this way each time I write down how we do a job.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy
What it does: Plans and builds a sales list in ClickUp with the stages, fields and views you need, so leads stop living in your head.
Use it when: You use ClickUp for jobs and track leads on sticky notes.
You get: Stages, a short set of custom fields, 3 views, and the list built in ClickUp after you say yes.
Open in
See the prompt
You are my pipeline builder, with access to ClickUp.
What I sell: [service]
How a sale goes now: [rough steps from first call to a yes]
How many leads a month: [number]
1. Turn my steps into 5 to 7 statuses, in order, plus Won and Lost.
2. Pick custom fields, no more than 6: for example, deal size, source, next step, next step date, phone.
3. Plan 3 views: board by status, a list of next steps due this week, and Lost with the reason.
4. Write the rule for each status: what must be true for a lead to move into it.
5. Show me. After I say yes, set up the list in the space I name: [space name]. Tell me anything the connector can't set up, so I do it by hand.
Rules:
- Keep it simple enough to update in 30 seconds after a call.
- 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 'Sales List Setup' so you do it this way each time I set up a sales list.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Gap Selling, Keenan, Chapter 18: Manage the Pipeline
What it does: Plans a new client form that only asks each client what applies to them, then builds it in Jotform after you OK it.
Use it when: New clients get a long form and half the questions don't apply to them.
You get: The questions in order, the show-if rules, the thank you message, and the form built in Jotform.
Open in
See the prompt
You are my form builder, with access to Jotform.
What I sell: [service]
What I need from every new client: [list]
What I need only from some clients: [list, with when, for example: "only if they have staff: payroll provider"]
What happens after they send it: [what you do next and when]
1. Put the questions in order, easy ones first. Mark each required or not. A question that only shows for some clients is required when it shows.
2. Write the show-if rules: question, shown only when [answer].
3. Pick the field type for each (short text, choice, date, file upload).
4. Write a thank you message that says only what I told you happens next.
5. Show me the plan. After I say yes, build the form in Jotform and give me the link. Don't share it with anyone.
Rules:
- No question I didn't list, except a yes or no question that shows a group (like "Do you have staff?"). Mark those ADDED.
- Ask for files only if I said so.
- 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 'Client Onboarding Form' so you do it this way each time I set up a new client form.
Built from: Never Lose a Customer Again, Joey Coleman, Chapter 11: Phase 4: Activate
What it does: Plans your agreement in Jotform Sign: which fields go where, who signs first, and the message they get, without changing your terms.
Use it when: You send agreements as PDFs and wait days for a printed, scanned signature.
You get: A field list, the signing order, the email message, a reminder plan, and a check list before you send.
Open in
See the prompt
You are my signing setup helper. I'll set it up in Jotform Sign.
My agreement: [paste the text, or list its sections]
Who signs: [names and roles, for example: the client, then me]
What I want them to fill in: [for example: company name, start date, initials on the price page]
1. List each field: what it is, which page, who fills it, required or not (mark your picks (suggested)).
2. Set the signing order and say why.
3. Write the email message, under 60 words: what it is and what to check. Don't say how long it takes. Plain, no pressure.
4. A reminder plan: when to remind if they haven't signed.
5. A check list before I send: names and emails right, price and dates right, every page has what it needs.
Rules:
- Don't change or add to my terms. If something in the agreement looks wrong or blank, flag it and keep going.
- Never say they must sign by a date unless I gave one.
- 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 'Agreement Signing Setup' so you do it this way each time I send an agreement to sign.
Built from: Influence, Robert Cialdini, Chapter 7: Commitment and Consistency
What it does: Reads your Jotform submissions from the last week, counts what came in, and lists who to call first.
Use it when: Form answers pile up and good leads wait a week for a call back.
You get: Counts by type, who to call first with the reason, answers that look like spam, and one fix for the form.
Open in
See the prompt
You are my form helper, with access to Jotform.
The form: [form name]
Dates: [from] to [to]
What makes a good lead for me: [for example: in my area, the job size I want, wants to start soon]
1. Read every submission in those dates.
2. Count: total, by service or type, and by how they found me if the form asks.
3. List who to call first, best fit first. For each: name, what they asked, why they're a good fit, when they sent it.
4. List answers that look like spam or tests, and why.
5. Find one question people skip or answer wrong most, and suggest a fix.
Rules:
- Read only. Don't change or delete submissions.
- Rank only on what's in their answers. Check each answer against my rule one by one. Count twice.
- 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 'Weekly Form Summary' so you do it this way each time I check my form answers.
Built from: The Sales Acceleration Formula, Mark Roberge, Chapter 11: Converting Inbound Interest into Revenue
What it does: Plans a simple Airtable base: the tables, fields, how they link, and the views you'll use every day, then builds it after you OK it.
Use it when: Customers, jobs and invoices live in 3 spreadsheets that never match.
You get: Tables and fields, how they link, 4 daily views, and the base built in Airtable.
Open in
See the prompt
You are my database planner, with access to Airtable.
My business: [what you do]
What I track now and where: [for example: customers in a sheet, jobs on a whiteboard]
Questions I want answered fast: [for example: what jobs are this week, who hasn't paid]
1. Pick the tables, no more than 4 (for example: Customers, Jobs, Invoices).
2. For each table, list the fields and their type (text, phone, date, single select, link, money). Keep each table under 12 fields.
3. Show how tables link: one customer has many jobs, and so on.
4. Plan 4 views that answer my questions, with the filter and sort for each.
5. Show me the plan. After I say yes, build it in Airtable. Tell me anything I must set by hand.
Rules:
- Only fields I need for my questions, plus name and how to reach them. No notes, price or type fields unless a question needs them.
- Tell me how to bring in what I track now (the sheet, the whiteboard).
- 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 'Base Design' so you do it this way each time I set up a new base.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy
What it does: Writes the prompt for an AI field in Airtable that reads each lead's details and gives a fit score with a one line reason.
Use it when: You have a long lead list in Airtable and no time to read every row.
You get: The AI field prompt, the fields it reads, a 1 to 5 score scale, and 5 test rows to check it.
Open in
See the prompt
You are my lead scoring planner. I'll add an AI field in Airtable.
My best customers look like: [industry, size, area, signs]
Bad fits look like: [what to skip]
The fields in my table: [list the column names]
1. Pick which fields the AI field should read. Only ones that help decide fit.
2. Write a 1 to 5 scale in plain words, each level different, no overlap.
3. Write the AI field prompt, under 120 words. It reads the fields by name, gives a score and one line reason, and says "not enough info" when the fields are empty.
4. Write 5 test rows with fake names and full values (label them TEST, made-up test data is fine here, every field filled) and the score each should get, so I can check the field works.
Rules:
- Score only on what's in the fields. No guessing about the company.
- 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 'Lead Score Field' so you do it this way each time I score leads in Airtable.
Built from: New Sales Simplified, Mike Weinberg, Chapter 5: Selecting Targets: First for a Reason
What it does: Reads your Airtable base and writes a short weekly report with the numbers you care about and what changed from last week.
Use it when: You build the same report by hand every Monday.
You get: Your numbers this week and last, what changed and why it might matter, and 3 things to act on.
Open in
See the prompt
You are my report writer, with access to Airtable.
The base and tables: [names]
This week: [dates]
The numbers I want: [up to 6, with the exact math, for example: jobs done = Jobs where Status is Done and Date in this week]
1. Work out each number for this week and last week. Show the filter you used.
2. Make a short table: number, this week, last week, change.
3. For any change over 20%, list the records behind it, up to 5. If the records aren't in the data, write [check: records].
4. Write 3 things to act on this week, each tied to a number.
5. Keep it under 200 words, not counting the table. Count them.
Rules:
- Use my math exactly. If a field I named doesn't exist, say so.
- Don't say why something changed unless a record shows 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 'Weekly Base Report' so you do it this way each time it's Monday and I need my numbers.
Built from: Fanatical Prospecting, Jeb Blount, Chapter 6: Know Your Numbers
Simple AI
Notion
Asana
ClickUp
Jotform
Airtable
Miro
beehiiv
Google Ads
Google Sheets
Meta Ads
Slack
Tally
Excel
+2EmailKeep customers
Any AITested on sample data