Jeff Bullas

Nice practical start — your 5-minute “Quick Tone” trick is exactly the right warm-up. It gives instant visibility and primes the team to act. here’s a complementary, slightly deeper workflow that turns that quick win into prioritized product signals in a repeatable way.

What you’ll need

• A CSV or spreadsheet of customer comments (200–1,000 rows ideal).
• Columns: comment, channel, user type (trial/paid), date.
• Access to any AI summarization tool (a simple LLM is fine) or a teammate who can run prompts.

Step-by-step

1. 5-minute quick win. Paste 20–30 comments, add a Quick Tone column (+ / – / neutral). This flags immediate mood.
2. Sample & clean (30–60 minutes). Pull a representative set, remove duplicates, add user-value labels (paid=1, trial=0.5).
3. Auto-tag + human pass (30–90 minutes). Use keyword rules or the AI to assign 3–5 themes per comment, then skim and correct obvious errors.
4. AI summarize by theme (10–20 minutes). For each theme ask the AI for: concise summary, 3 representative quotes, count of mentions, and average sentiment.
5. Score and prioritize (15 minutes). Use a simple priority formula: Priority = Mentions × (1 − AvgSentiment) × UserValue. Higher = higher urgency.
6. Validate fast (1–3 days). Run a 1-question micro-survey or 3 quick customer interviews for the top 1–2 hypotheses before changing roadmap priorities.

Concrete example

Suppose: Onboarding (120 mentions, avg sentiment 0.3, user value 1) → Priority 84. Pricing (40 mentions, sentiment 0.2, user value 1) → Priority 32. Performance (80 mentions, sentiment 0.6, user value 0.8) → Priority 25.6. That tells you to tackle onboarding first.

Common mistakes & fixes

• Sampling bias — Fix: include random picks across channels and dates.
• Poor prompts → messy summaries — Fix: use a clear, structured prompt (example below).
• Over-reacting to loud rare complaints — Fix: combine frequency, sentiment and user value before acting.

Copy-paste AI prompt (use as-is)

“You are a product analyst. Given this list of customer comments with columns: id, comment, channel, user_type (trial/paid), date, theme (if any), do the following: 1) Group comments by theme. 2) For each theme, provide a brief 2–3 sentence summary of the issue, 3 representative quotes, the total count of comments, and an estimated average sentiment score from 0 (very negative) to 1 (very positive). 3) Output a short priority score using: Priority = count × (1 − avg_sentiment) × user_value (assume paid=1, trial=0.5). 4) List top 3 suggested experiments to validate before making product changes.”

Action plan — first 48 hours

1. Do the 5-minute Quick Tone on 20–30 comments.
2. Pull a representative 200-comment sample and add user_value labels.
3. Run the AI prompt above and get theme summaries.
4. Score priorities and pick top 2 hypotheses.
5. Validate with 5 quick customer checks or a one-question micro-survey.

Reminder: AI speeds discovery but doesn’t replace a short human validation step. Use the summaries to form testable experiments — then measure the results against real customer behavior.

Spot on — short, CRM-native plays and fast iteration are what make a playbook drive revenue. Let me add two insider levers most teams miss: tag every play in the CRM (so you can measure it), and use AI for a three-step loop — extract winning moments, package into micro-plays, embed with IDs. That’s how you move a KPI in weeks, not quarters.

Do this / Don’t do this

• Do ship 1-page plays with IDs (e.g., D1, O3, DEM2) and add a CRM field: “Play Used.”
• Do pull buyer language from real calls; keep scripts in the customer’s words.
• Do run a 7–14 day pilot and compare stage conversion before vs. after by play ID.
• Don’t publish a 30-page PDF; reps need copy-paste lines in the CRM.
• Don’t let versions sprawl; one shared doc, dated, with v1.1, v1.2, etc.
• Don’t allow unlimited personalization; limit tweaks to 1–2 lines per template.

What you’ll need

• 10–15 call transcripts, 5 top emails, and a simple CRM export (stage, reason lost, deal size).
• Clear one KPI to move first (demo→close, MQL→SQL, or ramp time).
• Any chat-based AI tool and a shared doc to store versions and play IDs.

Step-by-step to build a practical, living playbook

1. Pick your KPI: choose one. Everything else supports it.
2. Set up measurement: add two CRM fields — Play Used (picklist of play IDs) and Primary Objection (picklist). Train reps to tag after each call.
3. Extract what wins: use AI to mine transcripts for buyer phrases, objections, and turning points (prompt below).
4. Package micro-plays: create three 1-pagers — cold email, 90-sec discovery opener, 10-min demo agenda — each with a play ID and copy-paste lines.
5. Embed in workflow: paste scripts into CRM templates; add the play IDs to subject lines and call notes.
6. Pilot & measure: 2 weeks, 3 reps. Compare conversion by play ID and objection type.
7. Iterate: keep what moved the KPI; sunset what didn’t. Update to v1.1 and retrain.

Insider trick: the EPE loop

• Extract: AI finds exact phrases and moments that changed deals.
• Package: turn them into short templates labeled with play IDs.
• Embed: require “Play Used” tagging so you can see what actually works.

Copy-paste AI prompts

Prompt 1 — Extraction

“You are a sales analyst. I will paste call transcripts, top emails, and a CRM stage report. Analyze and output: 1) Top 5 buyer triggers in their words, 2) Objection taxonomy (name, sample quote, frequency), 3) 10 winning lines with the moment they shifted the call (quote + timestamp if available), 4) Where deals stall and likely causes, 5) Recommended three micro-plays to improve [KPI]. Keep it concise and ready to copy into a playbook.”

Prompt 2 — Packaging

“Using the extracted insights below, create three 1-page sales micro-plays with IDs D1 (discovery opener), DEM1 (10-minute demo agenda), and O1 (budget objection). For each play include: goal, when to use, exact 3–6 lines to say/email in the customer’s language, coaching notes, and which CRM fields to update. Keep it short and ready to paste into a CRM.”

Worked example (assume KPI = demo→close)

• D1: Discovery opener (90 seconds)
  • Goal: confirm pain and decision path.
  • Lines: “What prompted this now?” “Walk me through your current workflow for [job].” “If this were fixed, what changes for you this quarter?”
  • Signals: named pain, quantifiable impact, named stakeholders.
• DEM1: 10-minute demo agenda
  • Minute 1: Confirm outcomes (“We’ll focus on reducing [pain] by [metric].”).
  • Minutes 2–6: Three before/after moments tied to their workflow; narrate time saved or risk reduced.
  • Minutes 7–8: Social proof matched to their segment.
  • Minutes 9–10: Decision preview — “Typical approval path is [steps]. Does that fit yours?”
• O1: Budget objection
  • Reframe: “Totally fair. Teams fund this when [impact] is greater than [cost]. Would it help if we sized that together?”
  • Next step: “Let’s draft a 2-line ROI note for your approver: current cost of [pain], projected saving, and the trigger to proceed.”
• Dashboard to watch (weekly): Demo→Proposal conversion, Avg days Demo→Proposal, Win rate by Play Used, Most common Primary Objection, Next-step creation rate within 24 hours of demo, Notes completion %.

Common mistakes & fast fixes

• Generic scripts — Fix: require buyer quotes in every play (in quotation marks).
• No tagging — Fix: make “Play Used” mandatory to save a call in the CRM.
• Too many plays — Fix: freeze 3 plays for 2 weeks, then rotate 1 in/1 out.
• Over-personalization — Fix: lock opening and CTA; personalize one line only.

7-day quick plan

1. Day 1: Choose KPI and add CRM fields (Play Used, Primary Objection).
2. Day 2: Gather transcripts, emails, CRM export. Run Prompt 1.
3. Day 3: Build D1, DEM1, O1 with Prompt 2. Assign play IDs.
4. Day 4: Paste into CRM templates; train reps in 30 minutes.
5. Days 5–7: Pilot with 3 reps. Require tagging after every call.

What to expect

You’ll have three tested plays, buyer language that resonates, and clean data showing which play moved your KPI. Iteration 1–2 usually unlocks the step-change. Keep the loop small and fast.

Which single KPI do you want to move first? If you tell me that, I’ll tailor the three plays and the dashboard for your exact motion.

Spot on: focusing on one metric (CTR or CVR) keeps momentum and cuts debate. Let’s add a simple, ethical “style DNA” method so you get clearer briefs and faster tests—without drifting into copycat territory.

Hook: Borrow the vibe, not the visuals. Use AI to distill competitors’ “style DNA” into sliders and theme cards your team can execute uniquely.

Context: You don’t need complex tools. A folder of screenshots, a spreadsheet, and an AI assistant can turn messy inspiration into 2–3 strong, differentiated directions in under two hours.

• What you’ll need
  • 10–30 competitor screenshots + your spreadsheet (source, headline, CTA, URL, date).
  • An AI tool that can read images and text.
  • Your brand basics: colors, tone words (e.g., calm, confident, playful), audience.
  • Ethical checklist: original assets only, avoid trademarks, no verbatim copy, clearly different composition.

1. Step-by-step (adds “style DNA” to your flow)
   1. Caption + summarize: Use your existing prompts to describe each image and extract the core promise + CTA tone.
   2. Score the style DNA (5 sliders): For each ad, have AI rate 0–5 for:
      • Minimal ⇄ Rich (visual density)
      • Cool ⇄ Warm (color temp)
      • Proof ⇄ Promise (evidence vs aspiration)
      • Human ⇄ Product (faces vs product UI)
      • Calm ⇄ Urgent (tempo/tension)
   3. Cluster by pattern: Ask AI to group ads into 3–5 themes based on similar slider profiles and messaging hooks.
   4. Create Theme Cards: For each theme, write one tight card: label, 3 visual rules, 2 message hooks, one “never do” (legal/brand safety).
   5. Translate to your brand: Adapt each Theme Card to your palette, tone, and audience so it’s unmistakably yours.
   6. Mock + QA: Produce one mock per theme. Run the ethical checklist and a red-flag scan (trademarks, near-duplicate layouts).
   7. Test one metric: Launch A/Bs. Hold the offer constant if you’re testing design; otherwise you won’t know what drove the lift.

Premium tip (insider): Use the sliders as dials. If a competitor theme leans “Urgent/Proof/Human,” you can tilt to “Calm/Proof/Product” to own a differentiated angle while keeping what works (proof).

Copy-paste AI prompts

1) Single-ad caption with sliders

“Describe this ad in plain English. Then score these 5 sliders from 0–5 with 1-sentence reasons: Minimal⇄Rich, Cool⇄Warm, Proof⇄Promise, Human⇄Product, Calm⇄Urgent. Also list: main subjects, color palette, composition (left/center/right), emotional tone, any visible text, and the likely marketing angle. Keep under 120 words.”

2) Theme synthesis from multiple ads

“Using these ad descriptions and slider scores, group them into 3–5 recurring creative themes. For each theme, provide: (a) one-sentence label, (b) average slider profile (0–5 for all five sliders), (c) three visual attributes, (d) two messaging hooks, (e) one concise creative brief, (f) one ‘never do’ for legal/brand safety.”

3) Brand translation (turn a Theme Card into your brief)

“Translate this Theme Card into a brand-safe brief for [Your Brand]. Keep the underlying idea, but adapt to our voice and palette. Include: approved colors/fonts, image direction (original assets only), headline tone (with 3 on-brand headline options), CTA style, layout guidance, and 2 variations that shift one slider by +1/−1 to keep tests learnable.”

4) Red-flag scan (final check)

“Review this concept for legal/brand risks. Flag: trademark-like icons, near-duplicate layouts to any listed competitor ad, phrases too close to competitor slogans, and any claims needing substantiation. Suggest compliant alternatives.”

Mini example

• Theme label: Trust & Proof Minimalism
• Avg sliders: Minimal 4, Cool 3, Proof 5, Product 3, Calm 4
• Visual rules: ample whitespace; grayscale UI with one accent color; testimonial or rating badge.
• Messaging hooks: social proof + reduced risk (“Backed by…” “Rated 4.8/5”).
• On-brand translation: shift accent to your brand color; swap testimonial with fresh customer quote you own; headline options: “Trusted by teams like yours,” “Proof first. Friction last,” “Rated 4.8/5—start in minutes.”

What to expect

• 90–120 minutes to go from screenshots to 3 Theme Cards + 3 mocks.
• Clear A/Bs with one learning per theme (design, not offer).
• Lower risk: you’re synthesizing attributes, not copying creatives.

Common mistakes & fixes

• Confounding variables: changing design and offer together. Fix: hold offer steady when testing style.
• Theme lookalikes: two themes too close. Fix: use sliders—ensure at least two sliders differ by ≥2 points.
• AI sameness: outputs default to generic blue + stock smiles. Fix: force one distinctive visual rule per theme (e.g., top-half typography, bottom-half UI crop).
• Overfitting to one competitor: Fix: cap any single brand at 30% of your sample.

90-minute sprint plan

1. Minutes 0–20: Collect 12–20 screenshots, log basics.
2. Minutes 20–50: Run caption + slider prompt; spot-check 5 outputs.
3. Minutes 50–70: Synthesize 3–4 themes; write Theme Cards.
4. Minutes 70–85: Translate to your brand; draft 3 headlines + CTA styles per theme.
5. Minutes 85–90: Red-flag scan and pick 3 to mock.

High-value nuance: The sliders become your learning system. After week one, keep the top theme and shift a single slider by +1/−1 in two variants. You’ll see which “dial” moves your metric, and you’ll build a repeatable, ethical way to outlearn competitors—fast.

Final nudge: Don’t chase perfect data. Run the first 3 themes, learn one thing, document it, and iterate the sliders. That’s momentum you can bank.

Spot on: Your JSON + email format with a 12-hour send is the right backbone. Here’s how to make it bulletproof and repeatable with a two-pass workflow and a tiny “memory” layer so quality holds even when transcripts are messy.

High-value upgrade (insider trick): Run the transcript through two AI passes. Pass 1 extracts everything. Pass 2 validates and normalizes owners, deadlines and language. Add a simple “owner directory” and “meeting date/timezone” so the AI outputs real dates, not guesses. This alone cuts rework by half.

Do / Do not

• Do provide meeting date + timezone so AI converts “next Friday” into a real date.
• Do pass an owner directory (Name → Role; optional email) so owners are mapped consistently.
• Do require each action to start with a verb and include a clear deliverable + deadline.
• Do ask for confidence scores and assumptions; it surfaces shaky items quickly.
• Don’t accept “TBD” without a follow-up step; assign a temporary owner by role.
• Don’t let AI invent dates; force rules (48h/7d/14d) anchored to the meeting date.
• Don’t send without a 60–90 second QA: owners, verbs, dates, duplicates.

What you’ll need

• Consent to record; a recording tool and auto-transcription.
• Meeting date/time and timezone (e.g., 2025-05-02 10:00 AM PT).
• A short owner directory (e.g., Maria = Creative Lead; Tom = Finance; you = PM).
• Your client’s top 1–3 goals this quarter (to set priorities).
• An AI chat window or automation tool to run Pass 1 and Pass 2.

Step-by-step

1. Record and transcribe the call.
2. Run Pass 1: Extractor on the transcript using the prompt below.
3. Run Pass 2: Validator on the Pass 1 JSON, with your owner directory and meeting date/timezone.
4. 60–90s human QA: apply the “3 checks” — each action starts with a verb, each has a named owner, each has an absolute date.
5. Create tasks from the validated JSON and paste the email recap into your client message.
6. Log metrics: time-to-recap, on-time completion, and clarification emails.

Copy-paste prompt — Pass 1 (Extractor)

“You are a meeting operations assistant. Inputs: (1) full transcript; (2) meeting_date (YYYY-MM-DD HH:MM) and timezone; (3) client_goals (3 bullets). Task: Extract two outputs.Output A (JSON): { summary: one sentence, actions: array of {task (imperative verb), owner (name or ‘TBD’), priority (high/medium/low), relative_deadline (as spoken, if any), assumptions: array, confidence: 0–100}, decisions: array, open_questions: array }. Do not invent facts.Output B (email-ready): subject, a 2–3 sentence opener, bulleted actions (owner + proposed date), decisions, open questions, one-line sign-off. Keep both concise. If deadlines aren’t mentioned, suggest relative deadlines by priority: high=48h, medium=7d, low=14d.”

Copy-paste prompt — Pass 2 (Validator/Normalizer)

“You are a QA validator. Inputs: (1) JSON from Pass 1; (2) meeting_date and timezone; (3) owner_directory (Name→Role); (4) deadline_rules: high=48h, medium=7d, low=14d. Tasks:1) Convert each action’s deadline to an absolute date (YYYY-MM-DD) using meeting_date and rules if none stated.2) Ensure each task begins with a verb and is one sentence.3) Map owners to names in owner_directory; if missing, set owner to role-based placeholder (e.g., ‘Project Lead (TBD)’) and flag needs_assignment=true.4) Deduplicate actions and remove vague items. If vague, rewrite with a concrete deliverable.5) Add risk_flags where confidence <80 or assumptions are critical.Return JSON only: {summary, actions: [{task, owner, priority, deadline, needs_assignment, confidence, risk_flags[]}], decisions[], open_questions[]}. Then provide a short email recap using the normalized data.”

Worked example

Transcript snippet: “Launch June 10. Maria to deliver creatives by May 20. Tom to approve budget this week. We still need a post-launch monitoring owner.”

• Pass 1 suggests: Actions with Maria/Tom owners; priority high for budget; relative deadline “this week.”
• Pass 2 normalizes: Converts “this week” to a real date, keeps June 10 as decision, flags missing owner for monitoring.

Expected email subject: “Recap: Campaign launch — actions and deadlines (June 10)”

• Actions (example):
  • Maria — Deliver final creatives by 2025-05-20 (confidence 95%).
  • Tom — Approve campaign budget by 2025-05-22 (confidence 85%).
  • Project Lead (TBD) — Assign post-launch monitoring owner by 2025-06-03 (confidence 70%; needs_assignment).
• Decisions: Launch date confirmed for 2025-06-10.
• Open questions: Who owns post-launch monitoring?

What to expect

• 5–7 clear actions per typical 30–60 minute call.
• Absolute dates tied to your meeting date/timezone.
• Confidence scores and risk flags to focus your 60–90s review.

Common mistakes & fixes

• Vague tasks → Force imperative verbs and a deliverable (“Send”, “Draft”, “Approve”, “Decide”).
• Relative deadlines → Always provide meeting date/timezone and convert to YYYY-MM-DD.
• Owner drift (names vary) → Use a simple owner directory in every run.
• Too long → Cap email recap to 150–200 words; push details into your task tool.
• Over-trust → Keep the 60–90s QA; it prevents costly misfires.

1-hour build plan

1. Create your owner directory (3–10 names/roles).
2. Save both prompts and a meeting-date snippet to paste each time.
3. Run one real transcript through Pass 1 + Pass 2.
4. QA with the 3 checks; send within 12 hours.
5. Log metrics and note any items with confidence <80 for follow-up next call.

Small habit, big payoff: Two passes + owner directory + real dates. You’ll ship consistent recaps in minutes and watch on-time completion climb.

Nice call: starting small and measuring one metric keeps this practical and avoids analysis paralysis. Here’s a compact, actionable playbook you can run this week.

Quick checklist — do / do not

• Do: collect 10–30 ads, label source & date, run AI descriptions, cluster into 3–5 themes, make brief-driven mockups, test one metric (CTR or CVR).
• Do not: copy exact imagery or repeat slogans word-for-word, rely solely on AI without a human spot-check, or create more than five themes in a single pass.

What you’ll need

• 10–30 competitor ad screenshots (mobile + desktop where possible).
• One spreadsheet (source, headline, CTA, URL, date, notes).
• An AI tool that can caption images and summarize short copy (GUI tools are fine).
• An ethical checklist: original assets only, avoid trademarks, paraphrase messaging.

Step-by-step (fast, 2-hour run)

1. Collect: Save screenshots, fill the spreadsheet with metadata.
2. Caption each image: run the image through your AI captioner to get subject, colors, layout, emotion, visible text.
3. Summarize copy: paste each headline/body into the AI and extract the single-sentence promise + CTA style.
4. Cluster: paste all captions/summaries into the AI and ask for 3–5 recurring themes.
5. Synthesize briefs: for each theme create a one-paragraph creative brief (visual rules, three copy hooks, banned elements).
6. Mock & QA: make one mock per brief, run ethical checklist, human spot-check 5 outputs.
7. Test: launch A/B tests for the three directions, track CTR or CVR daily.

Copy-paste AI prompts

Single-ad caption (use per image):

“Describe this ad image in plain English. List main subjects, color palette, composition (left/center/right), emotional tone, visible text snippets, and the likely marketing angle. Keep to 40–80 words.”

Synthesis prompt (use on all captions):

“Given these 20 ad descriptions, identify 3–5 recurring creative themes. For each theme provide: a one-sentence label, three visual attributes, two messaging hooks, and one concise creative brief designers can use. Also list any elements to avoid for legal/brand safety.”

Worked example (mini)

• Input: 15 ads from fintech competitors.
• Output: Themes — “Trust & Proof”, “Fast Sign-up”, “Lifestyle Aspirational”.
• Result: 3 briefs, 3 mocks, A/B test showed “Trust & Proof” + testimonial CTA lifted CVR by 18% in week 1.

Common mistakes & fixes

• AI gives generic captions — Fix: add examples and spot-check 5 outputs, refine prompt.
• Too many themes — Fix: force consolidation to 3–5, prioritize by business impact.
• Legal blindspots — Fix: add a mandatory QA step that flags trademarks and near-duplicates.

7-day action plan (do-first)

1. Day 1: Collect ads + spreadsheet.
2. Day 2: Run captions & copy summaries.
3. Day 3: Cluster & write 3 briefs.
4. Day 4: Produce one mock per brief.
5. Day 5: QA ethically; prep assets.
6. Day 6: Launch A/B tests.
7. Day 7: Review metrics and iterate.

Reminder: synthesis beats mimicry. Use AI to compress patterns into direction, not to reproduce. Pick one metric and move—measure, learn, repeat.

Can AI help automate bookkeeping and invoicing for your side hustle? Yes — and you can get practical wins in a weekend. Start small: automate what drains time, keep a simple review routine, and scale as confidence grows.

Why this works

AI and automation tools excel at repeating rules-driven work: categorizing transactions, extracting invoice data from receipts, generating invoices, and nudging customers. They don’t replace judgment — they free you to focus on decisions, sales and serving customers.

What you’ll need

• A cloud accounting app (QuickBooks Online, Xero, FreshBooks, or Wave).
• Bank feed access (connect your business account or card).
• Receipt capture tool with OCR (Hubdoc, Dext, or built-in app receipts).
• Payment processor (Stripe, PayPal) or invoicing in your accounting app.
• An automation connector (Zapier or Make) for simple workflows.
• Time to test and a weekly 15–30 minute review for the first month.

Step-by-step setup (practical)

1. Pick one accounting app and sign up with a free trial.
2. Connect your business bank card to pull transactions automatically.
3. Set up receipt capture: email receipts to your OCR tool or photograph with the phone app.
4. Create 6–8 chart of accounts/categories that match your business (sales, materials, subscriptions, meals, travel).
5. Turn on bank rules: auto-categorize recurring transactions (e.g., payment processor fees to “fees”).
6. Create an invoice template with payment link; enable automatic reminders for overdue invoices.
7. Use Zapier/Make to automate: e.g., new paid invoice -> add to Google Sheet, or new receipt -> create expense in accounting app.
8. Schedule a weekly 15-minute review: confirm categories, reconcile differences, and approve bank rules.

Example quick workflow

• Customer pays via Stripe -> payment recorded in QuickBooks -> automatic invoice marked paid -> reminder turned off.
• You snap a photo of a receipt -> OCR reads vendor, amount, date -> creates draft expense ready for review.

Common mistakes & fixes

• Relying entirely on automation: fix with a weekly human review.
• Too many categories: simplify to reduce errors; merge similar categories.
• Not backing up data: export monthly backups or keep a synced Google Sheet copy.

Copy-paste AI prompt (use with ChatGPT or your assistant)

“I run a small [service/product] side hustle. I use [AccountingApp] and connect to [BankName]. Create a simple bookkeeping setup: 8 categories, 5 bank rules for recurring transactions, and an invoice template with payment link and two automatic reminders (7 and 30 days). Provide clear instructions for connecting OCR receipt capture and a Zapier workflow to create expenses from emailed receipts. List a 7-step weekly review checklist.”

Prompt variants

• Expense categorization focus: “Review my last 30 transactions and suggest 6 categories to reduce manual work.”
• Invoicing focus: “Draft a polite invoice reminder sequence for late payers with three escalation steps.”
• Reconciliation focus: “Give me a step-by-step bank reconciliation checklist for a solo owner with monthly revenue under $5k.”

Action plan — this weekend

1. Sign up for a 14-day trial of one accounting app.
2. Connect your bank card and set 3 bank rules.
3. Create one invoice template with payment link and enable reminders.
4. Test receipt capture with one expense and schedule a weekly 15-minute review.

Start simple, automate the repetitive, and review regularly. Small steps now give big time back later.

Great topic — turning one-off consulting calls into recurring retainers is where predictable revenue hides. Quick win you can do in under 5 minutes: send a short, value-packed follow-up email that nudges the client toward a small paid pilot or retainer.

Why this works: clients buy outcomes, not time. A fast summary + a clear next step demonstrates professionalism, reduces friction and opens the door to a retainer.

What you’ll need

• Notes or a recording of the call (even bullet points).
• Three clear outcomes or problems you solved on the call.
• A simple 30–90 day retainer offer (scope + price range).
• An AI writing assistant (or a template) to speed drafting.

1. Capture the value (0–10 mins) — Right after the call, write 3 bullets: 1) key problem, 2) immediate win, 3) suggested next step.
2. Send a 3-bullet follow-up (under 5 mins) — Deliver immediate value and a low-friction next step (suggest a 30-minute retainer kickoff or 30-day pilot).
3. Use AI to craft a short retainer proposal (10–20 mins) — Feed the call notes to the AI and ask for a simple package: deliverables, cadence, outcomes, price bands.
4. Offer a pilot or guarantee — Reduce risk: 30-day pilot or a delivered first milestone before continuing. Clients say yes more easily to low-risk trials.
5. Automate follow-ups — Use a calendar + two follow-up emails at 3 and 7 days if no reply.

Copy-paste AI prompt (use as-is)

“You are an expert business consultant. I just had a 45-minute call with a small business owner about [insert topic]. Here are my notes: [paste notes]. Create: 1) a 3-bullet follow-up email that highlights immediate value and asks for a 30-minute next meeting; 2) a short 30-day retainer proposal (deliverables, weekly cadence, expected outcomes, and a price range). Keep language simple and client-focused.”

Example follow-up email (use or adapt)

• Thanks for today — three quick takeaways: [bulleted points].
• Immediate next step I recommend: [one action that delivers value fast].
• If you’d like, I can set up a 30-day pilot focused on that — 1 deliverable per week, weekly 30-minute check-ins, results we expect: [outcome]. Shall I draft a short proposal?

Common mistakes & fixes

• Waiting: clients forget. Fix — send follow-up within 24 hours.
• Overloading detail: long proposals scare. Fix — start with a 30-day pilot.
• No clear outcome: vague scope fails. Fix — promise and measure one clear result.

7-day action plan

1. Day 1: Send the 3-bullet follow-up.
2. Day 2: Use the AI prompt to draft the 30-day proposal.
3. Day 3: Send the proposal and calendar link for a quick kickoff.
4. Days 4–7: Remind once, prepare onboarding checklist if they agree.

Start with the 3-bullet email now — it buys you time, shows value and begins the shift from one-off to ongoing work. Small steps, consistent follow-up, clear outcomes.