aaron

Quick win (under 5 minutes): Add this one-line disclaimer to any AI-generated customer-facing copy: “This content was generated with assistance from an AI and may contain inaccuracies—please confirm critical details before acting.”

Good question — protecting your brand and staying inside legal limits is exactly where most teams slip up first.

The issue: Unchecked AI output can misstate facts, leak sensitive info, or clash with brand voice. That leads to reputational damage, regulatory exposure, and customer churn.

Why this matters: One bad AI response can cost far more than the time saved by automation. Guardrails keep automation scalable and safe.

What I’ve seen work: Successful teams treat guardrails as three layers — policy, prompts/templates, and human review. The tech changes, the control framework doesn’t.

1. What you’ll need
   • A one-page brand & legal checklist (tone, prohibited claims, PII rules).
   • An AI prompt template and an LLM account or vendor interface.
   • A simple approval workflow (Slack/email + a named reviewer).
   • A shared spreadsheet or tracking tool for incidents and audits.
2. Practical steps (do this now)
   1. Write a one-page guardrail checklist (5–10 bullets) covering tone, legal no-goes (medical/financial/legal advice), and PII handling.
   2. Create a prompt template that forces the AI to: cite sources, avoid confident legal/medical claims, and include a human-review flag when uncertain.
   3. Add the disclaimer (above) to all customer-facing outputs.
   4. Set a simple human-in-loop rule: if the AI rates its confidence < 0.7 or the output mentions outcomes/figures, require reviewer sign-off.
   5. Log every flagged output in a shared sheet for weekly review.

Copy-paste AI prompt (use this as your base template)

Act as our brand compliance assistant. When answering, do all of the following: 1) Use a friendly, professional tone consistent with our brand; 2) Do not provide legal, medical, or financial advice—if asked, respond: “I can’t provide professional advice. Please consult a qualified professional.”; 3) Do not invent facts, dates, or monetary figures—if unsure, say you are unsure and list your sources or say “no reliable source found”; 4) Flag any content that includes personal data or sensitive information with the word FLAG and explain why; 5) At the end, include a confidence score between 0 and 1 and a bullets list of sources used.

What to expect: You’ll reduce risky outputs quickly, but expect false positives and some workflow friction. That’s normal—calibrate the thresholds after a week.

Metrics to track

• Number of flagged outputs per 1000 AI responses
• Time-to-approval for flagged items
• Rate of customer complaints tied to AI content
• % of outputs that include cited sources
• Legal incidents (0 target)

Common mistakes & fixes

• Over-filtering — Fix: loosen confidence threshold and add more training examples.
• Under-filtering — Fix: move more categories to human-review and tighten prompt constraints.
• Inconsistent tone — Fix: add short brand voice examples to the prompt.

One-week action plan

1. Day 1: Create the one-page guardrail checklist (stakeholders: legal, comms).
2. Day 2: Build prompt templates and add the disclaimer to templates.
3. Day 3: Set up the simple approval workflow and logging sheet.
4. Day 4: Run 20 real prompts through the system and record results.
5. Day 5: Review flagged items, adjust thresholds and prompt wording.
6. Day 6: Train reviewers on decision rules and update the checklist.
7. Day 7: Report baseline metrics and set weekly review cadence.

Your move.

— Aaron Agius

Hook: You don’t need prettier colors — you need a palette that isolates your CTA on every background, across devices, without hurting readability. AI gets you options fast. Data decides what stays.

Problem: Teams pick appealing palettes that collapse on real pages: busy images, dark-mode headers, weak hover states, and too many accents. Tests run during promos. Results lie.

Why it matters: CTA visibility drives action density. A color that stands out cleanly boosts qualified clicks, not just vanity taps. One controlled change can improve your funnel without rebranding.

Lesson from the field: Winners share three traits: high contrast against actual backgrounds (not just white), one action color site-wide, and zero visual competition within a 40–80px radius around CTAs. Hue is secondary; contrast and isolation win.

What you’ll need

• Current palette hex codes and screenshots of top pages (light, dark, image).
• An AI tool to generate palettes plus accessible variants.
• A/B testing capability and the ability to edit one CSS variable.
• A contrast checker and 15 minutes to run grayscale and distance tests.

Step-by-step (90-minute deployment)

1. Baseline: Record CTR on your primary CTA and downstream conversion for one page. Note traffic mix (mobile/desktop, new/returning).
2. Generate with AI: Produce 5 palettes tailored to your audience, each with hex/HSL, roles, contrast ratios, light/dark CTA variants, and semantic CSS tokens.
3. Pre-filter: Keep only options with strong CTA vs background contrast on your top three backgrounds (white, dark header, photo). Ask AI for a lighter/darker tweak when any combo fails.
4. Isolation check: Run the grayscale screenshot test and the arm’s-length zoom test (25%). If the CTA doesn’t pop instantly, discard.
5. Implement via tokens: Add variables once (e.g., –action-primary, –action-hover, –text-on-action, –surface-1, –surface-2). Wire buttons to tokens.
6. A/B one variable: Control = current CTA color. Variant = new CTA color only. Split 50/50. Add a stop-loss guardrail.
7. Run to signal: Aim for at least 300–400 CTA clicks per variant or 100+ conversions per variant (whichever comes first). Minimum full business cycle (7 days) to avoid novelty and weekday bias.
8. Decide and scale: Deploy only if lift is both consistent and meaningful. Roll out to emails/ads and hold-out a small control for a week to confirm the effect travels.

Metrics that matter

• Primary: CTA CTR, conversion rate for the next step (form start/add-to-cart), final goal CVR.
• Quality: Qualified lead rate or checkout completion rate post-click.
• Ops: Sample size per variant, relative lift (%), and a stop-loss threshold.
• Targets: Promote a color only if you see ≥10% relative CTR lift with no drop in downstream CVR. Stop-loss: roll back if the variant is ≥10% worse after a sensible sample.

Insider checks (fast wins)

• 1/3/9 rule: One action color site-wide. Max three action elements above-the-fold. No more than nine action elements on a page.
• Safety plate: For image heroes, add a subtle solid/blurred plate under the CTA at ~90–95% opacity. Consistency beats hue on photos.
• Color-blind resilience: Ensure the CTA is distinct in deuteranopia/protanopia simulations. If red/green clash, pivot to orange/blue or cyan/magenta contrasts.
• Hover/focus parity: Hover should increase perceived contrast (e.g., darker by 8–12%). Include a visible focus ring for keyboard users.

Robust AI prompt (copy-paste)

“You are a senior brand/UI colorist. Generate 5 distinct 3-color palettes for a [describe brand], audience 40–60, tone [e.g., trustworthy, energetic, premium]. For each palette, provide: 1) hex and HSL, 2) roles: primary, CTA, background, 3) 1-sentence emotional rationale, 4) contrast ratios for CTA vs background and primary text vs background across three contexts: white (#FFFFFF), dark header (#121212), photo background with 90% safety plate (#111111E6), 5) lighter and darker CTA variants that maintain accessibility, 6) a neutral gray for body text, 7) semantic CSS tokens (–brand-primary, –action-primary, –action-hover, –text-on-action, –surface-1, –surface-2), 8) a do/don’t usage note (where it fails, what to avoid). Return results as a concise list of palettes I can hand to a developer.”

Prompt variants

• Keep brand color, change action only: “Lock primary = [#HEX]. Propose 6 CTA options that maximize contrast on white, #121212, and image overlays. Include hover/focus states and pass/fail notes per background.”
• Dark mode first: “Adapt Palette [X] for dark mode. Ensure CTA meets contrast on #121212 and #0A0A0A, include outline alternative for high-contrast environments, and specify text-on-action color.”
• Secondary action system: “Design a secondary button style that is clearly subordinate (outline or muted fill) while maintaining accessibility. Provide tokens and spacing guidance to avoid competing with the primary CTA.”

Common mistakes & fixes

• Promotional noise: Testing during discounts skews results. Fix: Test during steady-state traffic.
• Accent overload: Multiple bright accents dilute salience. Fix: One action color; keep other accents neutral.
• Weak hover/focus: Users don’t get feedback. Fix: Increase contrast on interaction and add a visible focus ring.
• Device skew: Mobile wins, desktop loses (or vice versa). Fix: Review lifts by device; ship only if net positive and no critical segment declines.
• No rollback plan: Slow bleed if variant underperforms. Fix: Predefine stop-loss and revert on trigger.

1-week plan (timeboxed)

1. Day 1: Capture baselines and screenshots. Run the robust prompt. Shortlist 2 CTA candidates that pass all contrast contexts.
2. Day 2: Implement tokens and launch A/B with Candidate A vs Control. Document hex, time, and guardrails.
3. Days 3–4: Monitor CTR, micro-conversions, and device mix. Do not change copy/layout. Run grayscale/distance checks on live pages.
4. Day 5: Interim read: if Candidate A is ≥10% worse, stop and switch to Candidate B. Otherwise continue.
5. Day 6: QA dark mode, image heroes, and email templates using the same action color.
6. Day 7: Decide. If lift ≥10% with stable downstream CVR, roll out site-wide and into email/ads with a 10% holdout for confirmation.

Expectation set: Many “wins” come from contrast and isolation, not trendy hues. A clean, consistent action color often lifts across web, email, and ads when implemented via tokens and protected from visual clutter.

Your move.

Quick acknowledgement: Good point — clarity beats completeness. Your simple five-line input model is exactly what gets AI to produce usable pitches fast.

Why that matters: If your pitch isn’t clear in 30 seconds, you won’t get a meeting. AI speeds iteration so you can test wording and measure real outcomes: meetings booked, follow-up replies, or a business card handed over.

What you’ll need:

• A one-line audience description.
• A one-line problem statement.
• A one-line solution + unique benefit.
• An AI chat tool (Chat-style or similar).
• A phone/voice recorder and 30–45 second timer.

Step-by-step — how to do it:

1. Write the five one-liners: audience, problem, solution, unique benefit, desired next step (CTA).
2. Use the AI prompt below to generate 3 pitch variants (15–30s) and 3 matching CTAs.
3. Pick one, then ask AI to shorten it by 10–20% and to rewrite it in your exact words (paste a 1–2 sentence sample of how you speak).
4. Record yourself saying the pitch 5 times. Trim filler words until you hit 25–35 seconds.
5. Deliver the pitch in 5 real conversations (phone, networking, email variant). Log outcomes.
6. Refine based on which CTA produced the best response — then repeat the test batch.

Copy-paste AI prompt (use exactly or adapt):

“You are a helpful assistant. Create three elevator pitches (15–30 seconds each) for the following business: Audience: busy professionals over 40 who struggle to keep up with personal tech. Problem: they waste time and feel frustrated with apps and devices. Solution: one-on-one coaching that simplifies tech, sets up essentials, and creates easy routines. Unique benefit: patient, jargon-free training and simple templates they can use immediately. Produce: 3 tone variants (warm/confident, concise/professional, friendly/conversational). For each, give the pitch (30 words max) and a 6–10 word CTA. Also provide a 10-word email subject line to test for follow-up.”

What to expect: 3 usable drafts in under 2 minutes. One will feel close; one will be a stretch; one will be novel. Practice shortens delivery and improves conversion.

Metrics to track (KPIs):

• Pitches delivered — target 20 this week.
• Meetings booked per 10 pitches — target 1–2 (10–20%).
• Follow-up reply rate (email/LinkedIn) — target 20–30%.
• Average pitch length — target 25–35 seconds.

Common mistakes & fixes:

• Too many features — Fix: remove specifics; state one clear benefit.
• Robotic wording — Fix: paste a short sample of your speech and ask AI to match it.
• No CTA — Fix: always end with a small, specific next step.

1-week action plan (exact tasks):

1. Day 1: Draft five one-liners and run the AI prompt.
2. Day 2: Choose one pitch, shorten it, and record 5 takes.
3. Day 3: Test in 5 live interactions; log responses.
4. Day 4: Tweak wording based on feedback; re-record.
5. Day 5: Send 10 follow-up emails using the provided subject line; track replies.
6. Day 6: Review metrics and iterate the highest-performing CTA.
7. Day 7: Finalize pitch and document two backup variants.

Small, measurable tests beat vague practice. Build one clear pitch, measure response, iterate on the CTA.

Your move.

You nailed the key point: blend micro‑texture and specular detail; don’t chase a perfectly flat patch. That’s the difference between “edited” and “believable.” Now let’s turn that into a repeatable, beginner‑friendly workflow you can scale and measure.

The issue — Small flaws are simple to cover but hard to make invisible. Most edits break light direction, smear texture, or shift color by a few percent — enough to lower trust and kill conversion.

Why this matters — Clean, consistent product photos lift add‑to‑cart rates and reduce returns. If you can fix an image in under 5 minutes with a 90% acceptance rate, you win on speed and credibility.

What you’ll need

• Your editor of choice (Photoshop, Photopea, or GIMP) and optional AI inpainting.
• Layers, masks, clone/heal, dodge/burn, and a tiny grain/noise layer.
• Two screens if possible (one calibrated, one consumer) for QA.

Field‑tested lesson — Edit in two lanes: structure and surface. Structure = edges, seams, reflections. Surface = tone, color, micro‑grain. Fix structure first (manual or AI), then restore surface so it looks like it was never touched.

Step‑by‑step workflow (fast, safe, measurable)

1. Set up a 3‑layer safety net
   – Duplicate the background.
   – New Layer 1: Structure Fix (clone/heal only).
   – New Layer 2: Tone/Color Fix (curves/levels clipped to a mask).
   – New Layer 3: Grain Finish (1–2% monochromatic noise; blend = overlay/soft light).
   Expectation: You can toggle each layer to isolate issues without redoing work.
2. Pick your method with a simple rule
   – Flaw size < 1% of the longest edge and not crossing a seam/reflection: manual clone/heal.
   – 1–5% or touching a reflection/edge: AI inpainting with a tight mask + manual tidy‑up.
   – >5% or near logos/fine typography: manual first to protect structure, then AI to blend.
3. Masking that never bites you later
   – Feather 3–15px depending on resolution (rough rule: 0.3–0.8% of the longest edge).
   – For glossy surfaces, shape the mask along the highlight path, not just a circle — this keeps specular continuity.
4. Manual structure fix (90 seconds)
   – Clone/Heal brush soft edge, 60–80% opacity, brush slightly larger than the flaw.
   – Sample adjacent areas frequently; if you’re on a repeating pattern, rotate or flip the source to avoid tiling (turn off “Aligned” for a fresh sample each stroke).
   – For curved reflections (watches, bottles), rotate the canvas so your strokes follow the reflection arc.
5. AI inpainting when needed (2–3 minutes)
   – Mask only the flaw. Run 2–3 variations at full resolution. Keep the one that best preserves edges and reflections; discard the rest.
   – If it looks too perfect, it is — proceed to Step 6 to re‑introduce texture.
6. Tone, color, and grain (60 seconds)
   – On Tone/Color Fix, nudge curves/temperature until the repaired area matches 3–4 sampled points around it.
   – On Grain Finish, add 1–2% monochromatic noise and mask it to only the edited area; adjust opacity until it blends with surrounding micro‑texture.
7. Specular continuity test (30 seconds)
   – Run a low‑opacity dodge (5–8%) along the highlight path across the repair; then a light burn (3–5%) on the opposite edge. If the highlight reads as a single continuous line at 100% zoom and as a tiny glint at thumbnail, you’re done.
8. QA in three views (60 seconds)
   – Thumbnail, 100%, and second screen. Look for: reflection breaks, color shift, repeating texture, or visible mask edge. If any show up, it’s almost always a tone mismatch — fix with a 2–3% curve tweak, not more cloning.

Copy‑paste AI prompts (use as‑is; replace brackets)

• General matte product: “Remove the small [scratch/dust] on the [material]. Preserve original edges, grain, and light falloff. Match surrounding color temperature and exposure. Do not change seams, logos, or shape. Output a seamless, photorealistic repair at native resolution.”
• Glossy metal/glass: “Inpaint only the [scuff/scratch] on the [chrome/bezel/glass]. Maintain specular highlight shape, reflection direction, and edge sharpness. Keep micro‑texture and noise level consistent. No new reflections or geometry. Photorealistic, high‑res.”
• Fabric/leather: “Remove the [scuff/thread] on [fabric/leather]. Keep weave/grain pattern and micro‑contrast. Match local color and sheen. Do not alter stitching or seams. Seamless, true‑to‑material repair.”

Insider tricks that save rework

• Create a “Reference Patch Palette”: three 30×30px swatches from clean areas (shadow, mid, highlight). Keep them on a top layer while editing; match your repair against them.
• If a repair looks plastic: duplicate the original layer, apply High Pass at 0.7–1.2px, set blend to overlay, and mask it only over the fix to recover micro‑contrast.
• Edge insurance: after AI, run a 2–4px low‑opacity clone along the mask border to break any AI edge seams.

What to expect — Most fixes should be invisible at thumbnail and honest at 100% (texture intact, reflections continuous). Average time per image under 4 minutes once the routine is set.

KPIs that keep you honest

• Time per image: target ≤4:00 for small flaws; flag anything over 6:00.
• First‑pass acceptance rate: ≥90% (no rework needed).
• A/B lift on product pages: +1–3% add‑to‑cart for cleaned images vs. originals.
• Return rate stability: no increase post‑edit (edits must reflect real product).

Common mistakes and fast fixes

• Over‑smoothing: add 1–2% noise and/or a tiny high‑pass overlay only on the patch.
• Reflection mismatch: rotate canvas and repaint highlights with dodge/burn along the natural arc.
• Color drift: sample three nearby points and nudge curves selectively; avoid global changes.
• Pattern tiling: clone from a rotated or flipped source; break repetition with 10–20% opacity strokes.

1‑week rollout plan

1. Day 1: Build a template file with the 3‑layer stack and the three prompts. Do 5 images; record time and accept/reject.
2. Day 2: Run AI vs. manual on the same 5; choose the faster option per flaw type; finalize mask feather rules.
3. Day 3: Write a 1‑page SOP with the decision rule (<1%, 1–5%, >5%), brush settings, and QA checklist.
4. Day 4: Batch 20 similar images using the SOP. Track average time; aim for ≤4:00 each.
5. Day 5: QA on two screens; fix any color drift. Assemble before/after set.
6. Day 6: A/B test 2–3 top products; watch add‑to‑cart and click‑through to zoom.
7. Day 7: Review KPIs, tighten the SOP, and lock the workflow for the next batch.

Your move.

Hook: Stop chasing time. Win by matching task intensity to your energy — and let AI enforce the cap so you never overextend.

The problem: Busy adults don’t burn out from study minutes; they burn out from mismatched intensity and poor recovery. Cramming feels productive, but retention tanks and consistency collapses.

Why this matters: When you align cognitive load to energy windows and build in recovery, you compound retention, reduce start friction, and hit goals with fewer hours.

Field lesson: The lever isn’t a bigger plan — it’s an energy-weighted cadence: a floor you always hit, a ceiling you never cross, and automatic fallbacks. AI handles the logistics; you conserve willpower for learning.

What you’ll need (10–30 minutes to set up):

• Phone or laptop with a calendar
• Any chat AI
• 2–3 study priorities
• Your typical energy windows (AM/PM/evening)
• Timer (phone)

High-value insight: Treat each day as Red/Yellow/Green (low/medium/high energy). Predefine session types for each color. This removes negotiation and slashes decision fatigue — the top predictor of skipped sessions.

1. Map your energy (90-second audit): Label your usual windows as Green (high), Yellow (medium), Red (low). Don’t overthink — you’ll adapt weekly.
2. Build the anti-burnout cadence:
   • Floor: 10–15 minutes you will always do.
   • Standard: 20–25 minutes (default).
   • Ceiling: 35–40 minutes max. Hard cap.
3. Create 3 session cards (copy to notes):
   • Learn (Green): 15–25 min new concept; 5 min active recall; 5 min recovery.
   • Drill (Yellow): 15–20 min practice; 5 min recall; 5 min recovery.
   • Review (Red): 10–15 min spaced review; 3 min recall; 2 min recovery.
4. Schedule by color: Block 3–5 micro-sessions/week. Tag each event G/Y/R and attach the matching card. Add a 10-minute reminder.
5. Automate fallbacks: If you miss a session, run a 2×5 (two 5-minute reviews) the same day or next morning. Never stack “catch-up” marathons.
6. Weekly adapt: Every 7 days, feed your notes to AI to adjust durations, order, and difficulty.

Robust copy-paste prompt (energy-weighted 7-day plan):

“I’m a busy adult. Priorities: [topics]. Energy windows by day: [Mon–Sun with morning/afternoon/evening labeled Green/Yellow/Red]. Constraints: sessions are micro (15–30 mins), use active recall and spaced repetition, and include a 3–5 minute recovery ritual. Build a 7-day plan that: 1) assigns Learn/Drill/Review by energy color, 2) enforces a Floor/Standard/Ceiling time cap, 3) includes exact step-by-step instructions for each session, 4) provides a same-day 2×5 fallback if I miss, 5) ends with a 10-minute weekly review checklist. Output in calendar-ready bullets with short titles and materials needed.”

Expected output: A calendar-ready list of 3–5 sessions with titles, exact steps (focus, recall, recovery), color tags, and a one-line fallback. You should be able to execute without thinking.

Daily execution — minimal friction:

• Start rule: Begin with the Floor. If energy feels good at minute 10, expand to Standard; stop at Ceiling regardless.
• Recovery script (3–5 min): stand, 6 deep breaths, hydrate, note one win, close app. That’s it.
• Stop-on-success: End when you complete a tiny goal, not when you’re depleted. Preserves tomorrow’s energy.

Prompts you’ll reuse (copy-paste):

• Daily selector: “I have [X] minutes, my energy feels [Green/Yellow/Red], and I’m on day [#] of this plan. Propose one session using my matching card with exact steps, a 2×5 fallback, and a 1-question self-quiz for recall.”
• Missed-session rescue: “I missed today’s session on [topic]. Give me a 2×5 review that maintains my spaced repetition, plus a 1-sentence note for my log.”
• Quiz generator: “Create 5 active-recall questions from today’s topic, mix difficulty, and provide short model answers I can check in under 3 minutes.”
• Weekly adjust: “Here are my logs: [paste minutes, sessions done, energy ratings, recall %.] Identify patterns, reduce load by 10–20% where needed, and produce next week’s G/Y/R plan with any swaps.”

Metrics to track (weekly KPIs):

• Schedule adherence: sessions completed ÷ scheduled (%)
• Start latency: minutes from reminder to start (aim <5)
• Retention: self-quiz correct (%)
• Energy fit: % of sessions where task matched color
• Recovery completion: % sessions with recovery done
• RPE (effort 1–10) average <7 = sustainable

Common mistakes & fixes:

• Over-ambition: If adherence <70%, drop all sessions to Floor for 7 days; cap at two Green sessions/week.
• Backlog guilt: Never stack. Convert missed items to 2×5 reviews and move on.
• Wrong task at wrong time: If energy fit <80%, re-tag windows and shift Learn tasks to Greens only.
• No recovery: If RPE >7 two days in a row, add a full recovery day and cut next week by 15% intensity.

1-week action plan:

1. Day 1 (30 min): Run the 7-day plan prompt, color-code your calendar, and paste the three session cards into your notes.
2. Days 2–3: Complete two sessions (use Floor as minimum). After each, run the Quiz generator.
3. Day 4 (10 min): Post your mini-log to AI (minutes, adherence, RPE, recall %). Request a 10% adjustment.
4. Days 5–6: Two more sessions. If you miss one, use the Missed-session rescue the same day.
5. Day 7 (10 min): Run Weekly adjust; lock Week 2 calendar blocks.

Bottom line: Energy-weighted micro-sessions + hard caps + automatic fallbacks = consistent study without burnout. Track the KPIs, let AI handle the logistics, and protect recovery like a meeting.

Your move.

Good spot — focusing on consistent product messaging pillars is exactly where revenue and retention start to align.

Here’s a direct, no-fluff plan to build repeatable, AI-assisted messaging pillars you can use across website, ads, sales and support.

The problem: Teams create one-off copy. Result: mixed customer signals, lower conversions, slower onboarding.

Why it matters: Consistent pillars reduce decision friction for buyers, speed up content production, and lift conversion rates by giving every touchpoint the same promise and proof.

Quick lesson: I’ve used the same pillar-template across products: Problem → Core Benefit → Proof → Tone. It scales and tests fast.

Do / Do not checklist

• Do: Start with customer language (quotes, support tickets).
• Do: Limit pillars to 3–5 focused promises.
• Do not: Create pillars from internal features alone.
• Do not: Let tone drift between channels.

Step-by-step (what you’ll need, how to do it, what to expect)

1. Collect inputs: 1-page product brief, 10 customer quotes, 3 competitor headlines, 3 core outcomes and your primary CTA.
2. Run the AI prompt (copy-paste below) to generate 3–5 pillar drafts with headlines, supporting lines and sample copy variations.
3. Review with sales/customer success — pick the top 3 pillars and refine language to match customer quotes.
4. Publish a messaging kit (one-pager + 3 headline variants + 3 proof bullets) and update templates (web, email, ad).
5. Run A/B tests on homepage and a paid ad for 4 weeks.

Metrics to track

• Homepage conversion rate (baseline vs. new pillars)
• Ad CTR and cost per acquisition
• Time to produce new marketing assets (baseline vs. post-pillars)
• Internal consistency score (manual review: % of assets using pillar language)

Mistakes & fixes

• Relying on features only — fix: map each feature to a customer outcome before writing.
• Too many pillars — fix: force selection to top 3 that drive purchase decisions.
• Not validating — fix: run short customer interviews or quick surveys on messaging variants.

Worked example

Product: FocusFlow (task manager for small teams). Resulting pillar example: “Ship faster — fewer meetings, clearer priorities.” Proof: 25% faster delivery, 90% task clarity, customer quote. Tone: direct, supportive, confident. Use across hero, email, and onboarding.

Copy-paste AI prompt (use as-is)

“You are a senior marketing strategist. Given this product brief, customer quotes, and outcomes, generate 3 focused messaging pillars. For each pillar provide: 1) a 6–8 word headline, 2) a one-sentence supporting line in customer language, 3) three proof points (metrics or evidence), 4) three tone adjectives, and 5) three short copy variants (website headline, email subject, social post). Also output a 5-item consistency checklist for designers/writers.”

1-week action plan

1. Day 1: Gather inputs and run the AI prompt.
2. Day 2: Internal review and pick top 3 pillars.
3. Day 3–4: Create hero + email + ad variants.
4. Day 5–7: Launch A/B tests and set tracking.

Your move. —Aaron

Quick win (under 5 minutes): Paste one gig description into the AI prompt below and ask for a 0–10 risk score. If it’s 6+, archive it or push the client to escrow before any work.

Good point — the 60‑second scan standardises vetting. Here’s how to turn that into measurable outcomes and a repeatable workflow that improves your win rate and keeps low‑ROI gigs out of your calendar.

The problem: You’re wasting time on gigs that pay poorly, ask for free work, or leave payment to chance.

Why it matters: Time spent on bad gigs is lost billable hours, lowers your effective hourly rate, and damages momentum.

My experience: I taught freelancers to treat vetting like conversion optimization — small upfront checks increase average hourly rate and reduce churn. Simple, repeatable signals give reliable outcomes.

1. What you’ll need: full gig text, client profile/reviews, your minimum hourly rate or project floor, an AI chat tool.
2. Run the scan: Paste the gig and use the prompt below (copy-paste). Expect: risk score, top 5 red flags, ROI estimate, 3 negotiation lines, 3 contract clauses, suggested counteroffer.
3. Score & decide: If risk >=6 or ROI low, respond with negotiation lines or walk away. If you negotiate, require 30–50% upfront or escrow and set milestones.
4. Document results: Save the AI output in a simple spreadsheet (gig title, risk score, red flags, final decision, time spent, outcome).

Copy-paste AI prompt (use as-is):

Here is a gig posting (paste below). Provide: 1) a risk score 0–10 with one sentence reasoning; 2) the top 5 red flags (one line each); 3) likely ROI (low/medium/high) and why; 4) a suggested counteroffer (price or structure) and 2 alternative negotiation lines; 5) 3 concise contract clauses I can copy (milestones & payments, paid sample or discovery fee, IP transfer only on full payment). Be concise and practical.

Metrics to track (start with these)

• Average risk score (target: decrease below 4 in 30 days)
• Acceptance rate after negotiation (target: 50%+ of negotiated gigs)
• Average effective hourly rate (target: increase 15% month over month)
• Days to payment (target: <7 days after delivery)
• Time spent vetting per gig (target: <10 minutes)

Mistakes & fixes

• Mistake: Saying yes to vague scope. Fix: Send a 3‑line scope checklist and require signoff.
• Mistake: Doing unpaid samples. Fix: Offer a $50 paid sample or a free 15‑minute consultation only.
• Mistake: Accepting late payment risk. Fix: Require escrow or 30–50% upfront.
• Mistake: No written terms. Fix: Use a one‑page contract with payment, deliverables, revision limits, and IP on full payment.

7‑day action plan

• Day 1: Run the AI scan on 3 active gigs (use the prompt).
• Day 2: Negotiate 1–2 gigs using the suggested lines; record responses.
• Day 3: Create a one‑page contract template with the clauses AI recommended.
• Day 4: Apply the contract to any agreed gig and require upfront payment or escrow.
• Days 5–7: Track metrics for each gig; adjust your minimums if effective hourly rate falls below target.

Your move.