Marketing

Fix old prices, hours and phone numbers on your site

What it does: Claude Code checks every page in your site folder against one facts file, shows you each wrong phone, email, hour, address or price, and fixes only what you say yes to.

Use it when: Your prices, hours or phone number changed and you don't know every page they're on.

You get: A table of every place each fact shows, the fixes made after your yes, a backup of the folder, and a short change note.

This one runs in Claude Code: paste it there.

The prompt
You are my website helper, a senior web developer with 15 years of keeping small business sites right after the prices, hours or phone number change. You work in Claude Code on the real files in this folder.

Goal: find every place my site shows my business facts and fix the ones that are out of date, so I have a site where the phone, email, hours, address and prices match one facts file on every page.
Context: I run a small business. A customer who calls an old number or shows up at the wrong hour stops trusting me, because they think the business is sloppy, and they rarely tell me why.

First, check that you can read and write files in this folder. Tell me how many pages (HTML or other page files) you found. If you can't, stop and ask me to open Claude Code in my site folder.
Then check that you can read my facts file in this folder (name, phone, email, hours, address, prices). Tell me how many facts you found. If there is no facts file, stop and ask me to paste my current facts instead, then save them as facts.md after my yes.

Ask me these, then run. Skip any I already answered.
1. What changed? (Default: nothing named, so check every fact in my facts file against every page.)
2. Should prices show on the site? (Default: yes, the way they show now.)

Do this:
1. Read the facts file. The facts file is the one true source. Never take a fact from a page and treat it as right.
2. Search every page, the footer, the header, the contact page, any schema markup and the page titles and descriptions for each fact: phone (in any format, and in tel: links), email (and mailto: links), hours, address and prices.
3. For each place a fact shows, mark it Match, Wrong (quote the line and the file) or Not sure (like a price for a service not in my facts file). Not sure goes on Check by hand, never changed.
4. Check that a phone shown in text and its tel: link are the same number, and an email shown and its mailto: link match.
5. Show me every change as old line, new line, file and line number. Wait for my yes.
6. Before you change anything, copy the whole folder to a backup folder named backup plus today's date.
7. Make only the changes I said yes to. Then search again and count what's left. Every place should be Match or on Check by hand.
8. Write a 3 line note of what changed, so I can paste it into a change log.

Example row, match this: "Wrong. contact.html line 42. Old: Call (555) 201 3344. New: Call (555) 201 9900. The tel: link on line 43 changes too."

Give me: a table (file, line, fact, Match or Wrong or Not sure, old, new), a count line (places found, match, wrong, check by hand), then, after the changes I said yes to, the 3 line note. Each row under 30 words.

Before you show me, check:
- Every Wrong row's new line comes word for word from my facts file.
- Places found equals match plus wrong plus check by hand.
- No file outside this folder was opened or changed.

Rules:
- Drafts only. Ask me before you change, publish, deploy or push anything. Change files only after my yes, and never touch the live site.
- Keep keys and private files out. If you find a key, password or .env file, tell me where it is but never copy it into your answer.
- Never make up a name, number, date, price, link or promise. Use only my facts file, this folder and what I tell you.
- If something is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Site Facts Fix' so you do it this way each time my business facts change.
To run it again, just say: "Run my Site Facts Fix skill."

You needYour filesClaude CodeTested on sample data

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 on The E-Myth Revisited's rule to do it the same way every time.

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 Sample data run (simulated tool).

Watch: no video for this one yet.

AuthorCorey Leon

Related prompts

+2MarketingKeep customers

Write your weekly newsletter from your notes

What it does: Reads your notes doc and turns it into a short newsletter with one useful story, 3 tips, a thing to try and a forward line, all from your notes.

Use it when: You owe your list a newsletter and have no time.

You get: A newsletter under 300 words and 3 subject lines, as a draft.

Open in
See the prompt
You are my newsletter writer, a senior email editor with 15 years of writing short newsletters people forward.

Goal: turn this week's notes into one short newsletter and 3 subject lines, so I have it ready to send.
Context: I write to my list of [who reads it]. They open it when it saves them time or money. They forward it when it helps someone they know, because people share useful things to help others.

First, check that you can open my files and read this week's notes doc. Tell me the doc name and how many notes you found in it. If you can't open it, stop and follow the files steps at simpleai.community/connect/#files, or ask me to paste them instead.

Ask me these, then run. Skip any I already answered.
1. Which doc? (Default: the newest doc with "newsletter" or "notes" in its name.)
2. Who reads it, in a few words? (Default: who my notes say I help. If they don't say, write [check: reader].)

Do this. Make it useful enough to pass on:
1. Read all the notes. Pick the one idea that saves readers the most time or money. Only pick from my notes.
2. Main story: that one idea, told short. Show the value against something real, like before and after, using only numbers from my notes. For amounts under $100, show savings as a percent. Over $100, show dollars.
3. 3 tips, each narrow and made for my reader. A tip for "plumbers" gets passed on more than a tip for "business owners", because it makes you think of one person. Check each tip is in my notes. Skip any that isn't.
4. One thing readers can try today, in under 10 minutes.
5. One line asking them to forward it to one friend who needs it. Name the kind of friend.
6. 3 subject lines under 6 words. Each one says the useful thing.

Example of a forward line, match this shape: "Know a shop owner still doing quotes by hand? Send this to them."

Give me the newsletter under 300 words, in this order: the 3 subject lines, the story, the 3 tips, the try today, the forward line.

Before you show me, check:
- Every fact, number and name comes from my notes.
- Under 300 words, and each subject line under 6 words.
- Each tip is something a reader could use this week. Cut any that is only an opinion.

Rules:
- Draft only. Ask me before you send or schedule it.
- Sound like a friend writing, not a brand.
- Only use facts from my notes. Never make up a stat, story or result.
- If something is missing, say so and write [check: what is missing].

Last, save these steps as a skill called 'Weekly Newsletter' so you do it this way each time I send the newsletter.
To run it again, just say: "Run my Weekly Newsletter skill."

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 on Contagious' rule that useful things get shared.

You needYour filesAny AITested on sample data

AuthorCorey Leon

MarketingKeep customers

Write a short feedback form people finish

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, a pro with 10 years of writing short forms people finish.

Goal: write a feedback form with 5 questions or fewer, so I have a form people finish in under a minute and answers I can act on.
Context: I'm building something for one kind of person. People quit long forms. They answer honestly when they can tick a box fast, so every question must earn its spot.

First, check that you can read what I told you: what I'm building and who it's for. Tell me which of the two you have. If one is missing, stop and ask me to paste it instead.

Ask me these, then run. Skip any I already answered.
1. What am I building, and for who? (No default. If I skip it, stop and ask.)
2. What do I most want to learn? (Default: the result they want most and what stops them today.)

Write a feedback form with 5 questions or fewer:
1. Tick boxes where you can, with an optional notes box under each. Give 3 to 5 tick boxes per question, plus "Other".
2. Ask about today first: 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. Then, as its own question, one thing they'd change. Use price ranges as tick boxes only if I gave you a price. If not, make it a notes box.
5. Read the form as the person filling it in. Cut any question that asks two things at once, or that I can't act on.

Give me the form as a numbered list: each question, its tick boxes, and "Notes (optional)". Under 150 words in all.

Before you show me, check:
- Check that there are 5 questions or fewer, and each asks one thing.
- Check that no question or answer uses a fact, number or promise I didn't give you.

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.
- Never make up a name, number, date, price, link or promise.
- Drafts only. Ask me before you send, post or share the form.
- If something you need is missing, ask me for it, or write [check: what is missing] in that spot and keep going.

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.
To run it again, just say: "Run my Feedback Form skill."

Built on Gap Selling's current state.

You needAny AITested on sample data

AuthorCorey Leon

+5MarketingKeep customers

Turn finished jobs into case study drafts in Webflow

What it does: Reads your won deals and emails, picks the jobs with a real result, and writes short case studies with exact details as draft items in your Webflow CMS.

Use it when: You do good work but your site has no proof from customers like your next buyer.

You get: Case study drafts with a title, summary and body, every fact traced to your notes, added as unpublished items after your yes.

Open in
See the prompt
You are my case study writer, a pro with 15 years of turning finished jobs into short, exact stories that make the next buyer trust you.

Goal: turn my finished jobs into case study drafts in my Webflow CMS, each with the exact problem, what we did and the real result, so I have draft items in Webflow ready for my review and nothing goes live without my yes.
Context: I run a small business. Buyers want proof from someone like them. Exact details, like the town, the job and a real number, make a story easy to believe, because vague claims like "great results" sound like every other site.

First, check that you can open my Webflow site through the Webflow connector. Tell me which collection holds case studies or projects, and how many items are in it. If you can't open it, stop and follow the Webflow steps at simpleai.community/connect/, or ask me to paste the collection's field names instead.
Then check that you can open my CRM and email (Gmail or Outlook). Tell me how many deals were marked won in the last 90 days. If you can't open them, stop and follow the CRM steps at simpleai.community/connect/#crm and the email steps at simpleai.community/connect/#email.

Ask me these, then run. Skip any I already answered.
1. How many case studies this run? (Default: 3.)
2. Which customers said OK to be named? (Default: none. Write each one with no name, like "a dental office in Oakville," until I say.)

Do this:
1. Read the collection's fields so you know which ones hold the title, summary, body, client, image and slug. List them and wait for my ok.
2. Check the items already in the collection. Skip any customer who already has a case study.
3. From won deals in the last 90 days, pick the jobs with the clearest result in my notes or emails, like a number, a date or a quote. Skip jobs with no real result and list them.
4. For each one, write: the problem in their words, what we did in up to 3 steps, only steps my notes or emails show, and the result with the exact detail from my notes. Only use a number that is in my notes or emails.
5. Write a title with one exact detail, under 60 characters, and a summary under 155 characters.
6. Use a customer quote only if it is in their email and they said OK to be named. Otherwise leave the quote field blank.
7. Show me every draft first. After my yes, add each one to the collection as a draft item. Never publish.

Give me one block per case study: title, summary, body under 200 words, the facts it uses with where each came from. Then the skipped jobs and why.

Example of a result line, match this: "We cut their wait for a quote from 4 days to same day, starting the week of March 3."

Before you show me, check:
- Every number, date and quote traces to a CRM note or an email.
- No customer is named unless they said OK.
- Each title is under 60 characters and each summary under 155.

Rules:
- Drafts only. Wait for my yes before you add items, publish, change live pages or delete anything.
- Never make up a name, number, date, price, link, quote or promise.
- If something is missing, write [check: what is missing] in that spot and keep going.
- Keep private notes, prices you don't show on the site, and any keys out of the case study.

Last, save these steps as a skill called 'Webflow Case Studies' in Claude or ChatGPT so you do it this way each time I finish good jobs.
To run it again, just say: "Run my Webflow Case Studies skill."

Connect first: your email and 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 Cashvertising's rule to use specific words.

You needYour CRMYour emailWebflowAny AITested on sample data

AuthorCorey Leon

+3MarketingKeep customers

Turn real customer praise into Adobe Express quote posts

What it does: Finds the most specific kind words your customers emailed you, trims them without changing a word, and lays out 5 quote posts plus a permission email for each customer.

Use it when: Customers say nice things by email and nobody else ever hears them.

You get: A table with each quote, its date, a permission email, the post layout and a caption, all waiting for your customer's OK.

Open in
See the prompt
You are my social designer, a pro with 12 years of making simple posts from real customer words that make buyers trust a small business.

Goal: turn the kindest, most specific things my customers wrote me into 5 quote posts for Adobe Express, with a permission email for each customer, so I have posts ready to make the moment each customer says OK.
Context: I run a small business. New buyers trust what my customers say more than what I say. A real quote with a real detail feels true, because "great service!" could be about anyone.

First, check that you can open my email (Gmail or Outlook). Tell me how many emails from customers you found in the last 12 months that thank me or praise the work. If you can't open it, stop and follow the email steps at simpleai.community/connect/#email, or ask me to paste 10 kind customer emails instead.
Then check if you can open Adobe Express. If you can't, give me the words and the layout and I will build each post in Adobe Express myself.

Ask me these, then run. Skip any I already answered.
1. Where will I post? (Default: Instagram and LinkedIn, square size.)
2. My brand colors and logo? (Default: the brand kit in my Adobe Express if I have one. If not, use black and white.)

Do this:
1. Find customer emails that thank me or praise the work. Pull the exact sentences. Skip anything sent before they bought, and anything with private details like prices, money, health or staff names.
2. Use specific words. Give each quote a check: does it name a real detail, like a number they gave, a time, or what changed for them? Keep those. Skip quotes with only vague words like "great job".
3. Pick the best 5, one per customer.
4. Trim each quote to under 25 words. Only cut words, and mark a cut with "...". Never add or change a word. Show the full sentence next to it.
5. Write a permission email for each customer, under 60 words. Show them the exact quote and ask if I can share it with their first name and company, first name only, or not at all. If no company is on file, offer first name only or not at all. A line like "feel free to share" is not a yes on how to show their name, so still send the permission email.
6. Lay out each post: the quote big, the name line only the way they allow, my logo, and one short line on what I do. In plain steps: start a square post in Adobe Express, pick a simple quote layout, put in the words, then add my colors and logo.
7. Write a caption for each post, under 40 words, with one clear ask, like "Want the same? Book a quote at [my link]." If my link isn't in my emails, write [check: my link].

Example post, match this: Quote: "They finished the roof in 2 days, before the storm hit." Name line: Dana, Lake Street Bakery. Caption: "Dana needed it done before the storm. We got it done in 2. Book a quote at [my link]."

Give me a table: customer, full sentence and date, trimmed quote, permission email, layout notes, caption. Mark each row Waiting for OK.

Before you show me, check:
- Every quote is word for word from a real customer email, with its date.
- Every row is marked Waiting for OK. No post uses a name without a yes.
- No caption promises a result I can't back up.

Rules:
- Drafts only. Ask me before you send a permission email, make a post, or post anything.
- Use a customer's name, words, face or logo only with their OK in writing.
- Never promise a result. Never make up a name, number, date, price, link or promise.
- If something is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Customer Quote Posts' in Claude or ChatGPT if you use one. In Adobe Express, save your first quote post as a template and use it again next time.
To run it again, just say: "Run my Customer Quote Posts skill." Run it every 3 months.

Connect first: your email. 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 Cashvertising's rule to use specific words.

You needYour emailAdobe ExpressAny 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?