Jeff Bullas

Nice point — clear follow-ups are the engine of progress. I like the emphasis on speed: send a tidy follow-up within 10 minutes and you keep momentum.

Here’s a compact, practical way to make that repeatable using AI — quick wins you can do today.

What you’ll need

• Short meeting notes (3–8 bullets).
• Attendee list and roles.
• One follow-up template (subject, 3–6 action bullets, 1 check-in line).
• AI tool or chat window.

1. Capture (0–3 minutes): Immediately after the meeting, list decisions, actions, owner (name), and a target date. Keep each as one line.
2. Draft with AI (1–2 minutes): Paste those bullets into the AI prompt below. Ask for a short subject, 3–6 action bullets (owner + deadline), one calendar/check-in suggestion, and a one-line closing asking for corrections.
3. Review (2–3 minutes): Check names, dates, and links. Fix any ambiguous wording. Keep it under 6 bullets.
4. Send & track (1 minute): Send to attendees, add calendar invites for the check-in, and log actions in your task tracker.

Do / Don’t checklist

• Do: Limit to 3–6 clear actions. Name a person for every item. Include one deadline.
• Don’t: Use vague verbs like “discuss.” Don’t assign work to a department without a named owner. Don’t bury actions in paragraphs.

Worked example (copy-paste ready)

Meeting notes (raw):

• Approve Q3 marketing budget — finance decision
• Create homepage banner — Sarah
• Set launch date — target Sept 15

AI-generated follow-up (example):

Subject: Product Launch — Decisions & Next Steps

• Finance to confirm Q3 marketing budget by Aug 5 — Owner: Finance Lead.
• Design 3 homepage banner concepts by Aug 1 — Owner: Sarah.
• Confirm launch date (target Sept 15); decision due Aug 3 — Owner: Product Manager.

Review meeting: Aug 6, 10:00 AM. Please update the shared doc by Aug 4.

AI prompt (copy-paste)

“You are an assistant that turns raw meeting notes into a concise follow-up email. Produce: 1) a short subject line, 2) 3–6 action bullets with a named owner and a deadline, 3) one calendar/check-in suggestion, and 4) a one-sentence closing asking for corrections. Keep the tone professional, clear, and under 8 short sentences. Meeting notes: [PASTE BULLETS HERE]”

Common mistakes & fixes

• Vague owners — fix: insert a person’s name or escalate to a named role.
• Too many actions — fix: break large tasks into milestones and keep the follow-up to the next immediate steps.
• Trusting AI blindly — fix: always verify facts, dates, and tone before sending.

7-day starter plan

1. Day 1: Make your one-line template and practice the 3-minute capture.
2. Day 2: Use the prompt on your last meeting; send the drafted follow-up.
3. Day 3–5: Send follow-ups for 2–3 meetings and track responses.
4. Day 6: Tweak the template based on replies and confusion points.
5. Day 7: Measure response rate and task completion; adjust deadlines if needed.

Your move: try the prompt on your next meeting notes and send the follow-up within 10 minutes.

You nailed the block lengths. That one tweak (50–60 minutes for heavy problem work, 25–30 minutes for retrieval) keeps your brain fresh and your practice honest. Let’s add two levers that make AI-led planning sing: priority (where the marks are) and pace (time per question). Combine these and your week becomes simple, calm, and effective.

Try this now (under 5 minutes)

• Grab your syllabus and mark the top 2–3 topics by weight.
• Decide your block lengths: 60 minutes for deep work, 25–30 minutes for retrieval.
• Paste the prompt below into your AI tool and get a tailored 7-day plan.

Copy-paste prompt

“I have an exam in 7 days. Topics and weights: [Topic A %], [Topic B %], [Topic C %], [Others]. I can study [X] hours/day. Use 60-minute deep blocks and 25–30-minute retrieval blocks. Create a 7-day plan that prioritizes the top 3 topics, includes a Day 4 half-length timed mock, a Day 7 full mock, nightly 15–20 minute error reviews, and clear micro-goals (e.g., 10-question self-quiz per block). Add: (1) a simple error-log template with error type codes C/P/S (Concept/Procedure/Speed), (2) pacing targets per question for each mock, (3) a daily checklist I can tick in 2 minutes. Keep it concise and practical.”

Why this works

• Priority first: Most marks sit in a few topics. Time follows weight.
• Pace next: Practising under time is what improves exam speed, not rereading.
• Correction compounds: Reviewing mistakes converts effort into marks.

What you’ll need

• Syllabus with topic weights and 2–4 one-page summaries.
• Past papers or a question bank.
• Timer (phone), notebook/error log, calendar.

Step-by-step (the calm, repeatable week)

1. Day 0 (30–60 minutes): List topics and weights. Pick top 2–3. Set block lengths. Collect past papers. Create a blank error log with C/P/S codes.
2. Daily template: Morning Deep (60 min), Midday Retrieval x2 (25–30 min each), Afternoon Problem Set (60 min), Evening Error Review (15–20 min). If energy dips, swap one deep block for two retrieval bursts.
3. Mid-week (Day 4): Half-length timed mock under real conditions. Log every error with C/P/S. Reallocate the next two days toward repeat error types.
4. End-week (Day 7): Full timed paper for your main subject. Spend 60–90 minutes fixing mistakes and making one-page polish notes.

Insider upgrades (small changes, big gains)

• 3–2–1 Practice Mix: In each problem block, do 3 tough, 2 medium, 1 easy question. This keeps confidence up while stretching skill.
• Pacing ladder: Start timed sets at 90 seconds per question, then drop to 80, then 75 across the week. Smoothly builds speed without panic.
• Error heat map: Circle repeat errors in red (C), blue (P), green (S). Fix colours first—visuals nudge the right work.

Worked example (6-hour study day)

1. 08:30–09:30 Deep: Topic A problems (finish with a 10-question self-quiz).
2. 10:00–10:25 Retrieval: flashcards/spaced recall for Topic B.
3. 10:35–11:00 Retrieval: quick past questions on Topic A definitions/steps.
4. 13:00–14:00 Problem Set: mixed past-paper questions across priorities (use 90s per question on Day 1–2; 80s by Day 4).
5. 20:00–20:20 Error Review: log C/P/S, write one-line plan for tomorrow’s first block.

Error-log template (copy this)

• Topic | Question # | Error Type (C/P/S) | Short note on fix | Next action (3 similar questions / re-derive steps / speed drill)

Common mistakes and quick fixes

• Skipping corrections — Fix: make the evening review mandatory. No exception.
• Studying everything equally — Fix: reallocate time by weight and mock errors. Low-weight topics get maintenance, not deep dives.
• Ignoring pace — Fix: set a timer per question. Reduce target time twice this week.
• Learning new topics late — Fix: last 48 hours are for consolidation and speed, not new content.

What to expect

• By Day 2–3: clearer priorities and fewer repeat errors.
• By Day 4: a sharper sense of timing and where marks leak.
• By Day 7: steadier pace and cleaner solutions on priority topics.

Refinement prompts (use after you get the first plan)

“Here are my Day 4 half-mock results: [scores by topic] and top error types: [C/P/S]. Reallocate the remaining days to target these errors. Give me two 25–30 minute retrieval drills and one 60-minute problem set for each weak topic, with a pacing target per drill and a 5-item checklist for my nightly review.”

“Energy dip today. Convert my next 60-minute deep block into two 25–30 minute retrieval bursts and a 10-minute correction sprint. Keep Topic A priority, include 3–2–1 practice mix, and finish with a one-line plan for tomorrow morning.”

Three actions to lock this in today

1. Schedule Day 4 half-mock and Day 7 full mock in your calendar now.
2. Create the error log with C/P/S codes and put it on your desk.
3. Run the copy-paste prompt and print the plan or save it as your phone’s lock screen.

Reminder: Predictable beats heroic. Use the right block for the job, chase the marks that matter, and let the timer teach your pace. AI can draft the week, but your small daily corrections win the exam.

Love your checklist — especially the three-option MCQ and two-track rotation. That’s smart, low-effort data. Let’s add one power move: build a reusable AI prompt that auto-differentiates and self-tunes from yesterday’s results. You’ll get better bell-ringers every day with almost no extra work.

Try this now (under 5 minutes)

• Open your AI chat tool and paste the “Triple‑Track Generator” prompt below. You’ll have today’s bell-ringer (support, on‑level, challenge), answer key, and a teacher note ready in under 60 seconds.

What you’ll need

• Any device with an AI chat tool.
• Today’s topic or standard.
• A way to display text and a visible 3–5 minute timer.
• Your preferred quick evidence check (hands, exit word, or 1‑minute write).

Step-by-step

1. Paste the prompt below and fill in the brackets. Ask for three versions: Support, On‑level, and Challenge.
2. Skim the outputs and pick one track for most students; offer Support or Challenge to a few. Save the text in a “Bell‑ringers” folder.
3. Put it on the board before class. Start the timer as students enter.
4. Collect micro‑data: show of hands for the MCQ + a one‑word confidence (high/low). Note completion rate.
5. After class, use the “Tuner” prompt to auto‑adjust tomorrow’s difficulty based on what you saw today.

Copy‑paste AI prompt: Triple‑Track Generator

Create a 4–5 minute bell‑ringer for [grade level] [subject] on [today’s topic]. Produce three tracks: Support, On‑level, Challenge. For each track include: 1) a 2–3 sentence quick‑write, 2) one multiple‑choice question with 3 options (mark the correct answer and give a 1‑line rationale for each distractor), 3) a 30‑second pair prompt, 4) a one‑sentence fast‑finisher, 5) estimated time for each part, 6) a one‑sentence teacher note with a common misconception and a quick fix. Keep language grade‑appropriate and concise.

Worked example (ready today) — 7th Grade Science, Photosynthesis

• On‑level
  • Quick‑write (2 min): “In your own words, explain how sunlight helps a plant make food. Mention leaves and chloroplasts if you can.”
  • MCQ (30 sec): Plants make glucose mainly in the… A) roots, B) leaves, C) stem. Answer: B. Rationale: A) Roots absorb water, not light. B) Leaves contain chloroplasts for photosynthesis. C) Stems transport, not produce, sugars.
  • Pair (30 sec): Compare photosynthesis to cooking: what’s the ‘energy source’ and what’s the ‘final dish’?
  • Fast‑finisher (30 sec): Write one clue you’d look for to tell if a leaf is doing photosynthesis right now.
  • Teacher note: Misconception — “Plants take in food from soil.” Fix — Emphasize plants make glucose in leaves; soil provides water and minerals.
• Support
  • Quick‑write (2 min): “Sunlight hits the leaf. The leaf uses light to make sugar. Where in the leaf does this happen?” Sentence starter: “It happens in the…”
  • MCQ (30 sec): Photosynthesis needs light from the… A) moon, B) sun, C) candle in the soil. Answer: B. Rationale given for each.
  • Pair (30 sec): Point to where light hits the plant and say why it matters.
  • Fast‑finisher (30 sec): Draw a tiny leaf and label “light in” and “sugar out.”
• Challenge
  • Quick‑write (2 min): “Predict how low light affects glucose output and plant growth. Include chloroplasts and stomata.”
  • MCQ (30 sec): If stomata close, which process drops first? A) CO₂ intake, B) water transport in xylem, C) chlorophyll production. Answer: A.
  • Pair (30 sec): Propose one adaptation for plants in deep shade.
  • Fast‑finisher (30 sec): Design a 1‑sentence investigation to measure photosynthesis rate.

Insider trick: Auto‑tune tomorrow’s warm‑up

After class, paste this into your AI with yesterday’s quick notes:

Yesterday’s bell‑ringer on [topic]: completion [__%], average time‑on‑task [__ min], most‑missed MCQ option [A/B/C], confidence split [__% high / __% low], observed issue [e.g., vocabulary too hard]. Using this data, regenerate a 3–4 minute bell‑ringer for [grade/subject] that: 1) lowers/raises difficulty by one notch, 2) swaps any tricky vocabulary for student‑friendly terms (give a sidebar glossary of up to 3 words), 3) includes one fresh 3‑option MCQ with key + 1‑line distractor rationales, 4) adds a sentence starter for Support and an application twist for Challenge, 5) keeps language at grade level. Keep it concise and classroom‑ready.

Batch your week in one go (optional)

Generate five warm‑ups at once and save prep time:

Create 5 distinct daily bell‑ringers for [grade/subject] covering [unit or standards]. For each day, output Support, On‑level, and Challenge tracks with: quick‑write, 1 MCQ (3 choices + key + distractor rationales), 30‑second pair prompt, fast‑finisher, times, and a teacher note (common misconception + fix). Keep each day under 120 words per track. Number the days clearly for easy copy‑paste.

What to expect

• Consistent 3–5 minute starts that curb transition drift.
• Clear snapshots of understanding via MCQ + confidence check.
• A growing library of proven prompts you can reuse and tweak.

Common mistakes and simple fixes

• Too much text. Fix: Cap each track at ~100 words. Ask AI: “Make it 20% shorter.”
• No answer key. Fix: Always request the correct option and a 1‑line rationale.
• One‑size‑fits‑all. Fix: Offer Support to 3–5 students and Challenge to your fast finishers. Rotate who gets which weekly.
• Forgetting to iterate. Fix: Use the Auto‑tune prompt with yesterday’s quick notes.

1‑week action plan

1. Today (10 minutes): Use the Triple‑Track Generator for tomorrow’s class. Save it as “BR‑[date].”
2. Day 2: Run it. Collect completion rate + confidence split.
3. Day 3: Auto‑tune using the Tuner prompt. Introduce Support and Challenge to a few students.
4. Day 4: Batch‑generate next week’s five warm‑ups. Keep your top two from this week.
5. Day 5: Review which prompts got 85%+ completion in under 5 minutes. Star those for reuse.

Closing thought: Short, specific prompts win. Pair a three‑option question with a confidence check, keep two tracks in rotation, and let yesterday’s data shape tomorrow’s start. That’s how you turn chaos into calm in the first five minutes — every day.

Quick win (5 minutes): Take your highest-traffic post and any lookalike you suspect. Paste both into the prompt below and ask the AI to ignore boilerplate (author bio, newsletter footer) and only compare the main article body. You’ll get a clean similarity call and a recommended action right now.

You’re spot on: AI is great at surfacing risk, not delivering verdicts. Let’s make it work harder for you by cutting noise and speeding decisions — without adding tech complexity.

High-value tip: Compare blocks, not whole pages. Most false positives come from headers, bios, CTAs, and legal text. Have the AI extract the main content first, then compare. This alone makes reviews faster and fairer.

What you’ll need

• Your top 20–50 URLs (export from your CMS is fine)
• One exact-match plagiarism checker
• One semantic/“near-duplicate” checker (or an LLM that can compare text)
• A tracker (spreadsheet) with columns for risk, traffic, canonical, action, owner, due date
• One reviewer for a weekly 60-minute triage

Step-by-step (keep it simple)

1. Extract main content: For each page, copy only the headline and article body. Ignore header, footer, sidebar, author bio, and CTAs.
2. Exact-match scan: Run your pages. Tag results: >80% overlap = high, 50–80% = medium, <50% = low.
3. Semantic scan: Run the same set for paraphrases. Start with a conservative threshold (e.g., 0.75 on a 0–1 scale). Expect noise on generic intros and definitions.
4. Canonical and first-published check: Record whether your page or the other page carries a rel=canonical or a clear syndication notice. Note the earliest publish date you can verify.
5. Triage with a simple rule:
   • Exact duplicate (verbatim sections 3+ sentences): remove, canonicalize, or cite.
   • Near-duplicate/paraphrase (structure and ideas overlap): keep if you add unique value; otherwise, rewrite or consolidate.
   • Unique: keep; consider adding a short citation if you used specific data or quotes.
6. Fix fast: Prioritize by Risk x Traffic. High-risk + high-traffic pages first. Implement top 5 fixes immediately each week.
7. Whitelist boilerplate: Keep a short list of standard snippets (bio, disclaimers, CTAs). Tell your tools and your reviewer to ignore these going forward.

Copy-paste AI prompt (block-first comparison)

“You are an expert content auditor. Step 1: Extract only the main article body from each text (ignore header, footer, sidebar, author bio, legal, and CTAs). Step 2: Compare the two main bodies and provide: 1) an overall similarity score 0–100, 2) sentence-level pairs that match or paraphrase with a 0–100 similarity estimate, 3) a classification: exact duplicate / near-duplicate / paraphrase / unique, 4) a recommended action: keep, add citation, canonicalize, lightly edit, substantially rewrite, or remove, and 5) an evidence list of the top 3 overlapping ideas or phrases. Treat common phrases and definitions as low importance. Explain your reasoning briefly in plain English.”

What to expect from the output

• Cleaner comparisons that focus on the substance of the article, not the template around it.
• Occasional over-flagging on generic openings (“In today’s digital world…”). That’s okay — your reviewer will down-rank these.
• Clear action labels that let you move quickly: cite, canonicalize, rewrite, or keep.

Example

• Post A: “Remote Work Tips” with a unique case study and two original checklists.
• Post B: Similar headings and advice but no case study; two paragraphs are close paraphrases.

• AI classification: Near-duplicate.
• Action: Keep Post A (primary), add a citation for one statistic, and substantially rewrite two paraphrased paragraphs to include your case study insights.

Insider upgrades (optional but powerful)

• Priority scoring: Add a column = Risk (High/Med/Low) x Monthly Sessions to focus on high-impact fixes first.
• Evidence pack: For each flagged item, save a snippet of overlapping text and the first-published date. This saves time if legal questions arise.
• Reviewer calibration: Once a month, review 10 borderline cases together and adjust your similarity threshold and whitelist. Consistency goes up; noise goes down.

Common mistakes and quick fixes

• Mistake: Comparing whole pages including template text. Fix: Block-first comparisons; maintain a boilerplate whitelist.
• Mistake: Labeling quotes or standards as plagiarism. Fix: Ask the AI to treat common definitions and short quotes as low-importance; cite the original where appropriate.
• Mistake: No proof of first publication. Fix: Save a timestamped copy (export or PDF) when you publish.
• Mistake: Action ambiguity. Fix: Use the action set: keep, add citation, canonicalize, lightly edit, substantially rewrite, remove.

One-hour setup for this week

1. Export your top 20 URLs and create a simple tracker with columns: URL, Traffic, Exact %, Semantic Score, Canonical (Y/N), First Published Date, Risk (H/M/L), Action, Owner, Due Date.
2. Run exact-match and semantic scans on the main article bodies only.
3. Create your boilerplate whitelist (bio, disclaimer, newsletter CTA) and note it in the tracker.
4. Reviewer triage (60 minutes): classify the top 10 flags; assign actions and owners.
5. Implement the top 5 fixes today; recheck those pages after edits.

Closing thought: AI won’t hand you a legal verdict — but with block-first comparisons, a boilerplate whitelist, and a tight triage loop, it becomes a fast, reliable radar for duplicate risk. Keep it small, steady, and measurable. That’s how you protect rankings and reputation without drowning in alerts.

Nice point — I like that you’re thinking about both passive and active income together. That mix is the fastest way to build resilience: passive layers grow over time, active income funds new experiments.

Here’s a practical, step‑by‑step plan using AI to build a diversified side‑income portfolio you can start this week.

What you’ll need

• Clear goals: monthly target, time per week, risk tolerance.
• Small capital (even $100–$1,000) for testing.
• Tools: an AI assistant (chat), simple website or newsletter, automation tools (email, scheduling), marketplaces (Upwork, Etsy, Amazon).
• Basic tracking: a spreadsheet for tasks, costs, revenue.

Step‑by‑step (do this in order)

1. Decide your allocation: e.g., 60% passive, 40% active. Write it down.
2. Choose 3–5 income ideas across both buckets. Quick candidates: AI‑assisted niche blog (affiliate), micro‑SaaS or template sales, stock photos/music, freelance AI services, online courses/tutoring.
3. Validate fast: use AI to generate 10 keywords, 5 headlines, and a 1‑page landing page. Spend one week testing interest (ads, social shares, or email signups).
4. Build an MVP: one landing page, one paid or free product, and one service offering. Keep quality high — AI helps speed writing, images, and ads but you must edit.
5. Automate and scale: use email sequences, scheduling, and outsourcing for repetitive work. Reinvest profits into the best performer.
6. Repeat and diversify: once one stream hits consistent revenue, add another and re-balance.

Short example

Week 1–2: Niche blog about ergonomic home offices. Use AI to create 12 posts and an affiliate guide. Week 3: Run a small ad test or post in niche groups. Month 2: Offer paid 1‑hour consulting sessions (active) and sell an eBook or template (passive). Use profits to hire a writer and expand content.

Common mistakes & fixes

• Mistake: Chasing every shiny tool. Fix: Pick one stack and finish one project.
• Mistake: Over‑automating low‑quality content. Fix: Use AI to draft, always human‑edit for value.
• Mistake: No tracking. Fix: Track revenue, hours, conversion per channel weekly.

30/60/90 day action plan

1. Days 1–30: Pick 3 ideas, validate 1, create MVP landing page and lead magnet.
2. Days 31–60: Launch paid test, open first service slot, collect feedback, start automation (email sequence).
3. Days 61–90: Hire/outsourse content, optimize ROI, add a second passive product.

Copy‑paste AI prompt (use it to kickstart planning)

“Act as an experienced side‑income advisor. I am 45, want to earn an extra $1,000–$2,000/month within 6 months, can work 8–12 hours/week, and have $500 to test ideas. Suggest 5 diversified income streams (mix of passive and active). For each stream, list expected startup cost, time to launch, first 10 tasks, and a simple 90‑day plan. Prioritize low technical barriers and explain quick validation tests.”

Closing reminder

Start small, test quickly, and let data guide where to double down. AI speeds creation — you still win by choosing the right niche, delivering value, and tracking results.

Nice point — I like how you highlighted running a few variations and noting which negatives work. That small discipline is the fastest path to consistently cleaner images.

Quick context

Negative prompts are simple but powerful: they tell the model what to avoid so you spend less time editing. Your step-by-step is solid — here are a few practical additions that speed results and reduce guesswork.

What you’ll need

• A generative image tool that accepts negative prompts (Stable Diffusion, Midjourney, etc.).
• A clear positive prompt (subject, style, lighting, mood).
• A short negative list of the top 2–6 recurring problems.
• A simple notes file or spreadsheet to track what words fix what problems.
• Time for 3 quick runs per test — variety beats perfection early on.

Step-by-step — quick practical workflow

1. Run one baseline image using only the positive prompt. Save it and note 2–3 issues (e.g., watermark, extra fingers, text).
2. Create a focused negative prompt naming those specific problems. Keep it short and prioritized.
3. Run 3 variations (different seeds or a slightly different guidance scale). Compare and pick the cleanest.
4. If an issue persists, rephrase that negative (use synonyms or add short clarifiers). Test one change at a time so you know what helped.
5. Save the working pair of positive + negative prompts as a template for similar images.

Copy-paste prompt (use as-is)

Positive prompt: a professional headshot of a smiling middle-aged entrepreneur, natural light, shallow depth of field, neutral background, realistic skin tones. Negative prompt: no text, no watermark, no logo, no signature, no extra fingers, no malformed hands, no missing limbs, no oversaturated colors, no blurred face, no artifacts.

Example — rephrase tricks for stubborn issues

• Watermarks persist: try “no watermark, no stamp, no copyright mark”.
• Text persists: try “no text, no letters, no typography, remove words”.
• Hands are odd: try “hands natural, five fingers, no extra fingers, realistic palms”.

Common mistakes & fixes

• Too vague: “no bad stuff” does nothing — be specific.
• Too many negatives: overload slows the model; prioritize recurring faults.
• Contradictions: don’t tell the model to both include and exclude the same thing.

Action plan — 10 minutes to better images

1. Pick one image type (portrait or product).
2. Run a baseline and note 2 issues.
3. Use the copy-paste prompt above and run 3 variations.
4. Save the best and note which negatives mattered.

Small experiments, clear negatives and a simple tracking sheet will build a prompt library that saves hours. Try this now — three quick runs and you’ll see the difference.

Which tool are you using? I’ll tailor the phrasing for it.

Cheers,

Jeff

Quick win: Paste the prompt below into an AI chat right now and get 3 crisp unique value propositions (UVPs) and 3 short taglines in under 5 minutes.

Why this matters: a clear UVP explains why someone should choose you. A memorable tagline sums that up in a few words. Together they make your marketing simpler and more effective.

What you’ll need

• A short description of your product or service (1–2 sentences).
• Your ideal customer (who, what problem they have).
• Your main benefit (what problem you solve or outcome you deliver).
• One proof point (years, customers, speed, guarantee).
• An AI chat tool (ChatGPT, Bard, Claude or similar).

Step-by-step: how to do it

1. Write one clear sentence: “I help [who] do [what] so they can [benefit].”
2. Open your AI chat and paste the prompt below (copy-paste recommended).
3. Ask for 3 UVPs and 3 taglines, each in different tones (straight, emotional, playful).
4. Pick the best lines, shorten them to plain language, and test with 5 people (friends or customers).
5. Refine based on feedback and pick one UVP + one tagline to publish on your homepage and email signature.

Copy-paste AI prompt (use as-is)

“I run [insert product/service] that helps [insert customer] by [insert main benefit]. We have [insert one proof point]. Write 3 unique value propositions, each one 15–25 words, and 3 short taglines (3–5 words). Provide each UVP and tagline in a different tone: 1) Clear and professional, 2) Warm and emotional, 3) Bold and playful. Keep language simple and avoid jargon. Output: numbered list for UVPs and taglines.”

Example (filled in)

Input: I run a bookkeeping service for small cafes that frees owners 8 hours a week and reduces tax errors. We’ve served 150 cafes.
Output UVP (clear): “Bookkeeping for cafes that saves owners 8 hours a week and cuts tax errors—trusted by 150 cafes.” Tagline (clear): “Books that breathe.”

Common mistakes & fixes

• Vague language — fix: swap fluffy words for measurable benefits (time saved, % improvement).
• Feature-led UVPs — fix: start with the customer outcome, not the feature.
• Long taglines — fix: keep taglines under 5 words and test aloud for memory.
• Jargon — fix: read it to a non-expert and note any confused faces.

7-day action plan

1. Day 1: Run the AI prompt and pick favorites.
2. Day 2: Shortlist 2 UVPs and 4 taglines.
3. Day 3: Test with 5 customers/contacts—ask which they’d remember.
4. Day 4: Finalize one UVP + one tagline and update your homepage headline and email footer.
5. Day 5–6: Share on social and track engagement (clicks, replies).
6. Day 7: Review results and iterate if needed.

What to expect

First pass will be good but not final. You’ll refine wording after real feedback. Aim for clarity and repeatability—if you can explain it in one sentence to a stranger, you’re close.

Small, practical step: run the prompt now and choose one UVP to put on your homepage today.

Quick win (under 5 minutes): Install one reputable coupon/cashback browser extension, add a low-cost item to your cart, go to checkout and let the extension scan. Note the suggested code and whether it applied. That single test tells you if the tool is worth keeping.

Great summary above — I like the realistic success-rate and the do/don’t checklist. Let me add a practical, step-by-step playbook so you can try this with confidence and avoid common traps.

What you’ll need

• A desktop browser (extensions work best there).
• An email account for the cashback tool and a password manager.
• A small test purchase (under $20) to validate behavior and permissions.

Step-by-step: how to set up and test

1. Pick one tool with good reviews and clear privacy terms. Install the extension and open its settings.
2. Inspect permissions. Turn off any setting that asks to read or modify all websites unless necessary for coupons.
3. Create an account with a unique password; do not store credit card numbers in the extension unless you trust it and need that feature.
4. Add a low-cost item to your cart on a site you already use. Proceed to checkout — watch what the extension suggests.
5. Review suggested codes. Apply only those that clearly show savings on the checkout page before you complete payment.
6. Track cashback in the tool’s dashboard. Expect pending status before payout — note the expected timeframe.

What to expect

• Immediate coupon success is common but not guaranteed — expect 20–50% success depending on retailer.
• Cashback appears as pending and clears in days to weeks.
• Small time savings every checkout; larger wins on big purchases.

Common mistakes & fixes

• Granting broad permissions — fix: revoke and test again or pick a different tool.
• Assuming cashback is instant — fix: reconcile pending vs paid and contact support if overdue.
• Relying on one tool for big buys — fix: cross-check manually on expensive purchases.

Copy-paste AI prompt (consumer-friendly)

“You are an assistant that audits my online cart at [RETAILER URL]. Scan for active coupon codes, test each at checkout, report which codes work and the exact dollar savings, check available cashback offers and expected payout timeline, note any region or account restrictions, and give step-by-step instructions to apply the winning code. Also list any privacy/security risks to watch for.”

7-day action plan (quick)

1. Day 1: Install one tool and inspect permissions.
2. Day 2: Run test purchase and document results.
3. Day 3–5: Try two more retailers and compare success rate.
4. Day 6: Adjust or switch tool if needed.
5. Day 7: Tally savings and decide whether to keep automation always on.

Try the quick win now. Small tests build confidence — then scale up for the real savings.