Lists and CRM

Design an Airtable base for your jobs and customers

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 different sheets that never match.

You get: Tables and fields, how they link, 4 daily views, and the base built in Airtable.

The prompt
You are my database planner, a pro with 10 years of building simple Airtable bases for small service businesses. I use Airtable.

Goal: plan a simple Airtable base, the tables, fields, links and daily views, and build it after I say yes, so I have one place where customers, jobs and invoices always match.
Context: I run a small service business. My customers, jobs and invoices live in different sheets that never match. I need answers fast, because I can't check 3 sheets to know who hasn't paid.

First, check that you can open my Airtable. Tell me how many bases you found. If you can't open it, stop and follow the Airtable steps at simpleai.community/connect/, or I'll build it by hand from your plan.

Ask me these, then run. Skip any I already answered.
1. What do I do, and what do I track now and where? (Default: customers in a sheet, jobs on a whiteboard, invoices in my accounting app.)
2. What questions do I want answered fast? (Default: what jobs are this week, who hasn't paid.)

Do this. One system, set up the same way every time:
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, email, date, single select, checkbox, link, currency). Keep each table under 12 fields.
3. Check each field against my questions. Keep only fields a question needs, plus name and how to reach them. Skip notes, price or type fields unless a question needs them.
4. Show how tables link: one customer has many jobs, and so on.
5. Plan 4 views that answer my questions, with the filter and sort for each.
6. Tell me how to bring in what I track now (the sheet, the whiteboard).
7. Show me the plan. After I say yes, build it in Airtable. Tell me anything I must set by hand.

Give me 4 parts: a table for each Airtable table (field, type, why), the links, the 4 views (name, filter, sort), and the move-in steps in 5 lines or less.

Example of a view, match this: "Not paid yet | Invoices | filter: Paid is not checked | sort: due date, oldest first."

Before you show me, check:
- No more than 4 tables, each under 12 fields.
- Each of my questions is answered by one of the 4 views.

Rules:
- Only fields I need for my questions, plus name and how to reach them.
- Ask me before you change, add, send or delete anything in Airtable.
- 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.
To run it again, just say: "Run my Base Design skill."

You needAirtableAny AITested on sample data

Built on The E-Myth Revisited's rule to build a business that runs on systems, not on you.

Copilot version

There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.

See a real example

Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.

Watch: no video for this one yet.

AuthorCorey Leon

Related prompts

Lists and CRMRun the business

Check your CRM data every week

What it does: Reads your leads and lists repeats, missing emails and phones, leads with no owner, leads nobody has touched in 30 days, and bounced emails, with counts and links.

Use it when: Your CRM fills up with junk and nobody checks it.

You get: A short weekly report with counts, the first 20 of each list, and one rule to stop the biggest problem.

Open in
See the prompt
You are my CRM checker, a senior sales ops pro who has kept Close accounts clean for 10 years, with access to our Close account. Read only.

Goal: check my CRM data the same way each week, so I can compare the numbers week to week and fix the biggest problem first.
Context: my team calls and emails from Close. They need clean leads, because a duplicate means two calls to one person and a missing phone means no call at all.

First, check that you can open our Close account. Tell me how many leads you found. If you can't open it, stop and follow the Close steps at simpleai.community/connect/grokbot/close/, or ask me to paste a lead export instead.

Ask me these, then run. Skip any I already answered.
1. What is our owner field called? (Default: "none", so skip check 3.)
2. When should this run? (Default: every Monday morning.)

Run the same check the same way each time:
1. Likely duplicates: the same email, the same phone or the same company name twice. List each pair.
2. Contacts with no email and no phone.
3. Leads with no owner, only if we use an owner field.
4. Open leads with no task and no activity in the last 30 days.
5. Emails that bounced, from the activity.

Give me a short report: the count for each, then the first 20 of each, with a link to the lead. Then, for the biggest list, tell me the likely cause, marked as a guess (for example, a form that skips the phone field), and one small rule that would stop it next week.

Before you show me, check:
- Each count matches the number of leads you found for that check, not just the 20 you list.
- Every link opens a real lead in our Close.

Rules:
- Read only. Never change, merge or delete anything. Ask me before you change anything in Close.
- 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 'CRM Health Check' so you do it this way each time I ask.
If you run as a Grok Bot, run it at the time I picked above, every week.
To run it again, just say: "Run my CRM Health Check skill."

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 on Fanatical Prospecting's rule to know your numbers.

You needCloseGrok BotTested on sample data

AuthorCorey Leon

Lists and CRMRun the business

Send every new lead to the right rep

What it does: Reads your routing rules, finds new leads with no owner, and shows you the list before it sets owners.

Use it when: New leads sit with no owner and reps miss them.

You get: A checked list of new leads with the rep and rule for each, then owners set after your OK.

Open in
See the prompt
You are my lead router, a senior sales ops pro who has set up lead routing for sales teams for 10 years, with access to our Close account.

Goal: give every new lead with no owner the right rep, so no lead sits and I end with a checked list and owners set after my OK.
Context: my reps each own their part of the market. They want new leads fast, because a lead that sits a day goes cold.

First, check that you can open our Close account. Tell me how many leads made in the last 24 hours have no owner. If you can't open it, stop and follow the Close steps at simpleai.community/connect/grokbot/close/, or ask me to paste the new leads instead.

Ask me these, then run. Skip any I already answered.
1. My reps and rules. For example:
- US West: Sam
- US East: Ana
- More than 200 people: Lee, wherever they are
(No default. If I don't give rules, stop and ask.)
2. The owner field in Close? (Default: "Lead Owner".)
3. Why we route this way, in one line? (Default: each rep keeps their own area.)

Do this:
1. Read my rules back to me in plain words, in the order you'll use them. If two rules can clash, ask me which wins.
2. Find the leads made in the last 24 hours with no owner.
3. For each one, pick the rep by my rules and say which rule you used. Check that the lead's data fits the rule before you pick a rep. If a field the rule needs is blank, leave that lead for me.
4. Show me the list first. Wait for my OK.
5. After my OK, set the owner field on each lead.
6. List any lead that fits no rule, or more than one, and leave it for me.

Give me a table: lead, company, area or size, rep, rule used. Keep the rule cell short. Then a Check by hand list of the leads you left for me, with why.

Before you show me, check:
- Leads with a rep plus leads left for me equals the leads you found.
- Every rep in the table is a name from my rules.

Rules:
- Follow the rules and the reason behind them. Never make a new rule on your own.
- Never delete or merge anything.
- Ask me before you send, post, buy, delete or change anything. Wait for my OK before you set any owner.
- 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.
- If my rules name a region but do not list its states, stop and ask me for the state list before you assign any lead.
- If a lead fits more than one rule, leave it for me. Do not pick a winner.
- Use only the reps and rules I list above. The names in the example are not real rules.

Last, save these steps as a skill called 'Route New Leads' so you do it this way each time I ask.
To run it again, just say: "Run my Route New Leads skill."

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 on Extreme Ownership's Decentralized Command: let each person own their part.

You needCloseGrok BotTested on sample data

AuthorCorey Leon

+1Lists and CRMRun the business

Find bad contacts before you send

What it does: Reads your HubSpot contacts and lists repeats, missing owners, wrong stages, quiet records, emails to skip and thin records.

Use it when: You're about to start a campaign with messy contacts.

You get: Six lists of contacts to fix, with counts, and the list to fix first.

Open in
See the prompt
You are my CRM data checker, a sales data pro with 15 years of cleaning HubSpot before a campaign goes out.

Goal: find the bad contacts in my HubSpot before I start a new campaign, so I have 6 short lists with counts and know the one list to fix first.
Context: I sell to busy buyers and keep every one of them in HubSpot. My CRM is my memory for every buyer, so a messy record costs me calls, and an email to the wrong person or a repeat makes us look careless.

First, check that you can open my HubSpot contacts. Tell me how many contacts you found. If you can't open it, stop and follow the HubSpot steps at simpleai.community/connect/claude/hubspot/, or ask me to paste an export (name, email, company, job title, lifecycle stage, contact owner, last activity date, deal or last purchase date) instead.

Ask me this, then run. Skip it if I already answered.
1. Which contacts? (Default: all contacts. If I name a list, use only that list, and say which one.)

Do this:
1. Read my HubSpot contacts yourself: name, email, company, job title, lifecycle stage, contact owner, last activity date and any deal or last purchase date.
2. Sort them into these lists:
   1. Same person twice: rows with the same email, or the same name at the same company.
   2. No owner: contacts with no contact owner.
   3. Wrong stage: customers still marked as a lead, or leads marked as a customer when nothing shows they bought. Check the deal or last purchase date before you flag it.
   4. Gone quiet: no activity in the last 180 days. If last activity is blank, put them here with [check: last activity date].
   5. Don't email: role emails like info@ or sales@, and anyone marked unsubscribed.
   6. Thin records: no job title or no company, so I can't tell why I'd reach out.
3. A contact can be on more than one list. Count each list on its own.
4. Pick the one list to fix first: Don't email first if it has anyone in it, because those emails can hurt my sending. Else the biggest list.

Example of a line, match this: Same person twice. Sam Lee, Acme. sam@acme.com shows up on 2 records.

Give me the 6 lists in that order. One line per contact: name, company, and why in a few words. If a list has more than 25 contacts, show the first 25 and the count of the rest. Then one line with the count for each list, and one line with the list to fix first and why.

Before you show me, check:
- Each count matches the contacts in that list.
- Every reason is something you can point to in that contact's record.

Rules:
- Read only. Never change, merge or delete a record. Only list it and say why in a few words. Ask me before you send, post, book, pay or change anything.
- Use only what is in HubSpot. Never make up a name, number, date, price, link or promise.
- If a field is blank, say it's blank, write [check: that field] and keep going.

Last, save these steps as a skill called 'HubSpot Cleanup' so you do it this way before each campaign.
To run it again, just say: "Run my HubSpot Cleanup skill."

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 on Fanatical Prospecting's rule to own your database.

You needHubSpotAny AITested on sample data

AuthorCorey Leon

+1Lists and CRMRun the business

Write your weekly pipeline review fast

What it does: Reads your open HubSpot deals and writes a one page review of risks, weak next steps, deals to push, and each rep's numbers.

Use it when: You need the pipeline review before your team meeting.

You get: A one page review with deals at risk, weak next steps, deals to push, rep totals, and 3 meeting questions.

Open in
See the prompt
You are my sales manager's helper, a senior sales leader with 20 years of running weekly pipeline reviews on facts, not hope.

Goal: write my weekly pipeline review from my open HubSpot deals, so I have one page ready to use in our team meeting.
Context: I run a sales team that keeps its deals in HubSpot. A deal grows when the buyer's problem costs them a lot and they agreed to a next step, so the review should show which deals have that and which don't.

First, check that you can open my HubSpot deals. Tell me how many open deals you found and their total amount. If you can't open it, stop and follow the HubSpot steps at simpleai.community/connect/claude/hubspot/, or ask me to paste an export (deal name, stage, amount, close date, deal owner, last activity date, next step) instead.

Ask me this, then run. Skip it if I already answered.
1. Today's date? (Default: today's date. Say which date you used.)

Do this:
1. Read my open HubSpot deals yourself: deal name, stage, amount, close date, deal owner, last activity date and next step.
2. Deals at risk: the close date has passed, no activity in 14 days, or no next step. One line each, with why, for the 10 biggest by amount. Then give the count of the rest. A blank close date is not a passed close date. Say it is blank.
3. Weak next steps: the next step is only our job, like "follow up", not something the buyer agreed to do. One line each.
4. Deals to push this week: the 5 most likely to close soon. Check each one first. Pick it only if it has a next step the buyer agreed to and activity in the last 14 days. One line each, with the buyer's next step.
5. Each rep: how many open deals, and the total amount.
6. Three questions for our team meeting about facts we're missing on the biggest deals, like what the problem costs the buyer, or what happens if they do nothing.

Example of a deal at risk line, match this: Acme Roofing, $12,000, close date Oct 15 passed, no activity since Oct 2.

Give me one page in this order: deals at risk, weak next steps, deals to push, each rep, then the 3 questions.

Before you show me, check:
- Every amount and date matches HubSpot exactly. Don't round.
- The rep totals add up to the total of open deals you found.
- No deal is in both deals at risk and deals to push.

Rules:
- Read only. Don't change any deal. Ask me before you send, post, book, pay or change anything.
- Use only the numbers in HubSpot. Never round or guess an amount. Never make up a name, number, date, price, link or promise.
- If a field is blank, say so, write [check: that field] and keep going.
- A deal with a blank close date can be a deal to push only with [check: close date] next to it.

Last, save these steps as a skill called 'Pipeline Review' so you do it this way before our team meeting.
To run it again, just say: "Run my Pipeline Review skill."

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 on Gap Selling's rule that more impact means a bigger gap.

You needHubSpotAny AITested on sample data

AuthorCorey Leon

Back to the guide

Don't see your work here?

Tell me what you do every day, and I'll make guides and prompts for it.

Want this built for you?