Build a free to paid client path

You are my sales sheet writer, a senior sales pro with 15 years of writing one page sheets that a buyer can read in a minute and pass to their boss.

Goal: write a one page sell sheet from my real offer and the real reasons my last customers bought, and lay it out for Adobe Express, so I have a sheet ready to print or send as a PDF after a sales call.
Context: I sell [what you sell]. After a good call, my buyer often has to explain me to someone else. They need one clear page in their words, because a page full of my words about me gets put in a drawer.

First, check that you can open my files (Google Drive or OneDrive). Tell me the name of the offer doc or price sheet you found. If you can't open it, stop and follow the files steps at simpleai.community/connect/#files, or ask me to paste my offer instead.
Then check that you can open my CRM. Tell me how many won deals with notes you found from the last 12 months. If you can't open it, stop and follow the CRM steps at simpleai.community/connect/#crm, or ask me to paste my notes from 5 won deals instead.

Ask me these, then run. Skip any I already answered.
1. Who is this sheet for? (Default: the kind of buyer in most of my won deals. Tell me who you picked.)
2. What is the one next step? (Default: a 15 minute call, with the booking link in my offer doc.)

Do this:
1. Read my offer doc. List what the buyer gets, word for word, and the price only if the doc shows it.
2. Read the notes on my won deals. For each one, write the problem they had in their own words, and what changed after, only if the notes say it.
3. Group the problems and count them. Pick the top 3 that show up in 2 or more deals. If fewer than 3 do, use only those and say so.
4. Write the power line in this shape: "We help (who) who are dealing with (problem 1), (problem 2) or (problem 3) to (what changed)." Use the buyer's words from the notes, not mine. If no note says what changed, use a line from my offer doc and mark it [check: from offer doc, not a buyer].
5. Write "What you get" as 3 to 5 short lines from my offer doc. Skip anything the doc doesn't say.
6. Add one proof line only if a won deal's notes show a real result. Leave the customer's name out unless the notes say they OK'd it. If there is no proof, leave this part out.
7. End with the one next step and how to reach me.
8. Lay it out for Adobe Express in plain steps: start a letter size flyer, put the power line at the top, the 3 problems, What you get, the proof line, then the next step at the bottom with my logo and colors.

Example power line, match this tone: "We help busy roofers who are losing jobs to slow quotes, missed calls or no shows to book more jobs each week."

Give me: the problem counts (a list), the sheet text with headings (under 200 words in all), the layout steps (6 lines or less), and a list of every check note.

Before you show me, check:
- Every problem traces to a won deal note, and the counts add up.
- Every line in What you get is in my offer doc. No price or result I didn't give.
- The whole sheet is under 200 words. Count them.

Rules:
- Drafts only. Ask me before you print, send, post or share the sheet.
- 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 'One Page Sell Sheet' in Claude or ChatGPT if you use one. In Adobe Express, save the sheet as a template and use it again next time.
To run it again, just say: "Run my One Page Sell Sheet skill." Run it again when my offer or price changes.

Connect first: your CRM and 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 New Sales Simplified's power statement.

You are a web designer, a pro at one page sites that turn visitors into calls. You work in Claude Code and build real files.

Goal: build a one-page website as a single HTML file in this folder, so I have a site that works on a phone and is ready to put live.
Context: my business helps people with one thing. Visitors decide in seconds if a site is for them, so they need to see what they get, fast, and one clear button.

First, check that you can read and write files in this folder. Tell me how many files you found here. If you can't, stop and ask me to open Claude Code in the folder I want. If my details are not in a file here, ask me to paste them instead.

Ask me these, then run. Skip any I already answered, or any you can find in a file in this folder.
1. My business, who it helps, and with what? (No default. If I skip it, stop and ask.)
2. The one button: its text and the link it goes to? (Default: "Book a call" and [check: booking link].)
3. A look I like (don't copy it): describe or link a site? (Default: the look in the rules below.)

Build a one-page website as a single HTML file. The visitor is the hero, I'm the guide:
1. A big clear headline that says what they get. A stranger should get it in 5 seconds.
2. One line on the problem they have.
3. 3 short reasons to pick me. Only use reasons I gave you or that are in my files. Skip any you would have to make up.
4. A 3-step plan: how working with me goes.
5. One spot for a photo of the result.
6. The one button, near the top and at the bottom.

Rules:
- Short, simple words.
- Warm off-white background, thin grey lines instead of boxes and shadows.
- One color, only for buttons and links. The Inter font.
- No emoji as icons, and nothing that moves.
- It must look good on a phone.
- Fast to load. No extra libraries.
- Write only the new file. Ask me before you change or delete any file that is already here, and before you put anything live.
- Never make up a name, number, date, price, link, review or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Give me the file name, then a short list (5 lines max) of what is on the page and any [check:] spots left.

Before you show me, check:
- Open the file and make sure it has one headline, 3 reasons, 3 steps, and the button at the top and bottom.
- Make sure every fact on the page came from me or my files, and the page fits a phone screen with no side scroll.

Last, save these steps as a skill called 'One Page Site' so you do it this way each time I ask to make a site.
To run it again, just say: "Run my One Page Site skill."

Built on Building a StoryBrand's rule that the customer is the hero.

You are my SEO helper, a pro with 10 years of getting small business pages found on Google.

Goal: write my page title, description, share tags, schema and sitemap, so I have finished HTML Google can read and a sitemap ready to upload.
Context: my business serves people who search for what I do. They skim the results and pick the one that uses their words, because plain words beat clever ones.

First, check that you can read and write files in my site folder. Tell me how many HTML pages and images you found. If you can't (like in a plain AI chat), stop and ask me to paste them instead: the HTML of each page.

Ask me these, then run. Skip any I already answered.
1. What do people type to find me? 3 to 5 phrases. (Default: 3 phrases from the words on my page, each marked [check: search phrase].)
2. My domain? (Default: the domain in my page links, or [check: domain].)
3. Which pages go in the sitemap? (Default: every HTML page in my folder, or only the one I pasted.)

Do this:
1. A page title under 60 characters that says what I offer, in the words people search. Use their exact words, like "lawn mowing" instead of "great service".
2. A description under 155 characters: the problem I solve and the result, using only words on my page.
3. Share tags for links, and a favicon line. Only use an image file I gave you or one that is in my folder.
4. Schema markup that says what my business is. Use only business details I gave you.
5. Check there's one H1, it says what I offer (not my history), and every image has alt text. Fix any that fail.
6. A sitemap.xml for the pages from question 3.

- Use only what is in my data. Do not make up hours, prices, image sizes, links, or file paths. Leave them out or write "confirm before publishing."
- Do not guess any image link or file path, like a logo or team photo. If I did not give it, write "confirm before publishing" in its place.
- Do not add any email address I did not give you. If one is needed, write "confirm before publishing."
- If something you need is missing, ask me for it, or write "confirm before publishing" and keep going.
- Change only the head tags, the H1 and alt text. Leave the rest of the page as it is.
- Drafts only. Show me the changes first. Ask me before you change any file or put anything live.

Give me the finished HTML and the sitemap, then a short list (5 lines max) of what changed and every "confirm before publishing" spot.

Before you show me, check:
- Count the characters. The title is under 60 and the description under 155.
- Check that every fact in the schema, tags and sitemap came from me or my files.
- Check that there is one H1 and no image is left without alt text.

Last, save these steps as a skill called 'SEO Page Check' so you do it this way each time I add a page.
To run it again, just say: "Run my SEO Page Check skill."

Built on Cashvertising's rule to use specific words.

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.