aaron

Agree: your “title + DOI” check is the fastest filter. Keep that habit. Now let’s drive hallucinations toward zero with a tight, repeatable system and visible KPIs.

Hook: Make AI work like a junior analyst under audit — every claim has a source, a quote, and a confidence score.

Problem in one line: AI writes fluent prose that blends true studies with plausible fiction. Reviewers notice. You pay for it later.

Why it matters: One fabricated citation can trigger reviewer distrust, delays, and rewrites. A verification-first workflow preserves credibility and speeds acceptance.

Lesson learned: Use “source-locked mode.” Feed the model the abstracts or excerpts you trust, and force it to quote only from those. Treat everything else as hypothesis until verified.

• Do: Require verbatim quotes, DOI, and a confidence reason for every claim.
• Do: Verify two details (title + DOI or title + authors + year) in a database.
• Do: Keep a simple claims register (ID, claim, source, quote, DOI, status).
• Do: Run a second pass where the AI acts as a citation auditor on your draft.
• Don’t: Accept paraphrases as proof; you need the exact sentence from the paper.
• Don’t: Mix preprints and peer-reviewed sources without clearly labeling.
• Don’t: Ask broad questions; specify population, timeframe, outcomes, and study type.

What you’ll need

• AI chat assistant.
• Access to PubMed, Google Scholar, Scopus, or your institutional library.
• A reference manager or a simple spreadsheet for your claims register.
• 10–20 minutes per major claim for verification.

Step-by-step: zero-hallucination workflow

1. Frame tightly. Define the claim scope (population, intervention/exposure, comparator, outcome, timeframe). Note acceptable evidence types.
2. Run strict sourcing. Use the primary prompt below. Extract 2–3 claims you intend to keep. Paste abstracts or key excerpts when you have them and tell the AI to use those only.
3. Verify independently. In PubMed/Google Scholar, confirm at least two details (title + DOI or title + authors + year). If either fails, mark the claim “Unverified.”
4. Quote or cut. Store the exact one-sentence quote and DOI in your claims register. If no verifiable quote exists, remove the claim or label as speculative.
5. Draft from evidence. Write your paragraph using only verified claims. Keep in-text references aligned to your register IDs.
6. Audit pass. Run the auditor prompt on your draft and references. Fix any flagged items before submission.

Copy-paste AI prompt — Strict Verify

“You are my research verifier. Topic: [insert topic]. Produce 3–5 bullet claims. For each claim, return only peer‑reviewed sources. For each source include: full citation (authors, year, journal), article title, DOI (required if available), one verbatim one‑sentence quote that directly supports the claim, and a confidence level (high/medium/low) with a one‑line reason. If you are unsure or cannot find a source, say ‘I don’t know’ and list the exact search queries I should run in PubMed or Google Scholar. Do not invent citations. If I paste abstracts/excerpts, only cite from those and label them [S1], [S2], etc., and map each quote to the claim.”

Auditor prompt — second pass

“Act as a citation auditor. I will provide a draft paragraph and a list of references with DOIs. For each sentence, check whether at least one provided reference contains a verbatim quote that supports it. Flag sentences with no direct support or mismatched claims. Output a list of flagged sentences, the missing evidence, and the exact search terms to verify.”

Worked example (process over content)

1. Claim draft: “Moderate aerobic exercise improves insulin sensitivity in adults over 50 within 12 weeks.”
2. Run Strict Verify on that claim. Get 2–3 studies with DOI and verbatim quotes.
3. Open PubMed/Google Scholar; search the title or DOI. If both title and DOI match, copy the DOI and the exact quote into your claims register.
4. If a source lacks a DOI or the quote doesn’t appear in the paper, mark Unverified and swap in the next candidate source.
5. Write the paragraph using only the verified claim(s); keep the quote in your notes for reviewer queries.
6. Run the Auditor prompt on the paragraph + references; resolve any flags.

Metrics to track (make results visible)

• % of AI-cited claims verified on first pass — target 90%+ after week 2.
• Average verification time per claim — target <15 minutes.
• Title–DOI mismatch rate — target <2%.
• Reviewer reference objections on first submission — target zero.

Common mistakes & fast fixes

• Mistake: Relying on paraphrases. Fix: Store one exact sentence from the paper for each claim.
• Mistake: Over-broad prompts. Fix: Specify population, timeframe, and outcome.
• Mistake: Mixing preprints and peer-reviewed papers. Fix: Label preprints clearly or exclude them.
• Mistake: One-pass drafting. Fix: Always run the auditor pass before submission.

1‑week action plan

1. Day 1: Create a claims register (columns: ID, claim, source, quote, DOI, confidence, status).
2. Day 2: Select one section of your paper. Run Strict Verify for 3–5 claims. Verify title + DOI for each.
3. Day 3: Draft the section using only verified claims; store quotes.
4. Day 4: Run the Auditor prompt on the draft + references. Fix flags.
5. Day 5: Repeat for the next section; track your verification time.
6. Day 6: Normalize references in your manager; ensure DOIs are consistent.
7. Day 7: Quick pre-submission audit: sample 5 claims, re‑verify title + DOI. Update KPIs.

What to expect: Slightly more time up front, major reductions in citation errors, smoother peer review, and confidence you can defend every sentence.

Your move.

Smart addition: Your Naturalness Stack (Reader Mirror + 1–1–1 + Reply Magnet) is the right foundation. I’ll layer on a control system that turns those drafts into measurable results fast.

Try this now (5 minutes): Open your last 10 sent emails or replies from customers. Paste them into AI with the prompt below to extract a Voice Bank. Then regenerate Email 1’s subject/preview using those exact phrases. Expect tighter opens within your next send.

Copy-paste prompt — Voice Bank extractor

From the text below, extract: 1) the 12 most common reader phrases, 2) 5 pains, 3) 5 desired outcomes, 4) 5 words to avoid (sound salesy). Format as four bullet lists. Text: [paste 5–10 short customer emails or replies here]

The problem: Great outlines still underperform without a feedback loop. Most sequences stop at “sounds natural” and never convert because subject lines aren’t tested, reply asks are mistimed, and CTAs don’t ladder toward a single offer.

Why it matters: Small, weekly tweaks move core KPIs — open rate, click/reply rate, and booked calls. A 3–5% lift at each stage compounds into real revenue without rewriting everything.

Field lesson: Sequences that place reply CTAs in Emails 1, 3, and 5, use reader phrases in subjects, and show one small proof by Email 3 consistently beat “polite but generic” flows. Keep the message short; make the next step obvious.

Step-by-step: the Nurture Control System

1. Inputs (10 minutes): Audience line, single goal, 3 micro-proofs (short quote, stat, mini-story), and your Voice Bank phrases (10–12).
2. Generate (20 minutes): Use the assembler prompt below. Ask for 3 variants of Email 1 and Email 3. Pick the clearest.
3. Calibrate (15 minutes): Apply the 1–1–1 rule. Convert half of “we/I” to “you.” End Emails 1, 3, 5 with a one-line question.
4. CTA Ladder (10 minutes): Map actions: E1 reply, E2 read tip, E3 reply, E4 download/checklist, E5 reply, E6 soft book, E7 deadline. One link max per email.
5. Subject/Preview workshop (10 minutes): Create 12 pairs for Email 1 using Voice Bank phrases. Keep subjects 6–9 words, previews 8–12 words.
6. QA + Load (10 minutes): Insert [FirstName]. Mobile check. Plain language. No hype words. Test links. Schedule 2–4 day gaps.
7. Pilot (5 minutes): Send to 100–500 subscribers. Mark baseline KPIs for two weeks.
8. Iterate weekly (15–30 minutes): Change one variable only (subject, CTA wording, or send time). Track trend lines, not single sends.

Copy-paste prompt — 7-email assembler (natural + conversion)

Write a 7-email nurture sequence for [Audience: one line, include one pain]. Goal: [single action, e.g., book a 20-minute consult]. Voice: warm, clear, human, short sentences, no hype. Use these reader phrases: [paste 10–12 from Voice Bank]. Include first-name token [FirstName] where natural. Length: 3–5 short sentences per email (90–120 words max). For each email provide: 1) subject (6–9 words), 2) preview (8–12 words), 3) body, 4) single CTA. Purposes: 1 welcome/expectations + reply question, 2 quick tip with tiny checklist, 3 short proof or 90-word story + reply question, 4 how-to or checklist + one link, 5 address main objection + reply question, 6 soft offer (what happens, how long, zero risk), 7 reminder with real deadline and easy opt-out. Keep paragraphs short for mobile.

What good looks like: Subjects echo reader phrases, bodies stay under 120 words, three emails invite replies, and every email advances one step toward the offer. Expect a friendly, grounded tone you can read aloud in under 20 seconds.

Metrics that matter (with simple targets)

• Open rate: aim 25–40%. If under 25%, fix subject/preview using Voice Bank.
• Primary action rate (click or reply): 3–10% per email. If under 3%, tighten the CTA to one specific next step.
• Reply rate (Emails 1/3/5): 1–4%. If flat, make the question smaller and easier to answer.
• Unsubscribes: keep under 0.5% per send. If higher, increase relevance or widen gaps.
• Booked calls from sequence: track weekly; aim for steady growth, not spikes.

Mistakes that kill performance (and fixes)

• Vague CTAs: replace “learn more” with a precise ask (“Book a 20-minute call”).
• Walls of text: cap to 3–5 short sentences; add a line break after sentence two.
• Proof too late: move a micro-proof into Email 3 (even a one-line outcome).
• No reply friction: ask a one-line question that’s easy to answer (“What’s the one thing blocking you this week?”).
• Mixed goals: one goal only. Remove secondary links and side offers.

1-week action plan

1. Day 1: Build your Voice Bank (5 minutes) and define one goal.
2. Day 2: Run the 7-email assembler. Generate 12 subject/preview pairs for Email 1.
3. Day 3: Edit with 1–1–1. Add reply questions to Emails 1, 3, 5.
4. Day 4: Load, insert [FirstName], mobile test. Fix line length and link placement.
5. Day 5: Pilot to 100–500 subscribers. Note baseline KPIs.
6. Day 6: Review: underperformers get new subject/preview; keep bodies stable.
7. Day 7: Adjust one variable only. Set next week’s test (subject vs CTA).

Bonus prompt — Subject/preview sprint (for Email 1)

Generate 12 subject/preview pairs that use these reader phrases: [paste 6–8]. Constraints: subjects 6–9 words, previews 8–12 words, no hype, plain language, curiosity without clickbait. Output as a numbered list. Mark 3 safest options for an older, professional audience.

Bottom line: Your outline is solid. Add the Voice Bank, a CTA Ladder, and weekly single-variable tests. That’s how you turn “sounds natural” into booked calls and revenue.

Your move.

Quick win (under 5 minutes): Take any generated image and write a one-line critique (“subject is ok, lighting is flat, background cluttered”). Feed that critique as a second prompt: you’ll get an improved result fast.

One polite correction: More words aren’t always better. Long adjective lists often confuse the model. Prompt chaining (short prompt → critique → focused refinement) beats dumping in 30 descriptors.

Why this matters: Prompt chaining turns random results into predictable outcomes. For businesses and creators over 40 who want reliable image output, chaining cuts iteration time and increases usable assets.

My approach — practical, step-by-step

1. What you’ll need: an image generator that accepts text prompts, a baseline image or idea, a simple note with 3 critique points (composition, lighting, subject clarity).
2. Step 1 — Baseline prompt: Create a concise prompt (1–2 short sentences) describing subject, style, and mood. Generate 2 variations.
3. Step 2 — Critique: For each variation, write 1–3 observations: what’s wrong and what needs fixing.
4. Step 3 — Refine: Chain a new prompt that addresses just one critique at a time (lighting, then composition, then color). Generate updated images after each linked prompt.
5. Step 4 — Final polish: Apply a last prompt for brand consistency (palette, logo placement, crop) and export the asset.

Copy-paste prompt (use as a 3-step chain)

1) “Create a high-resolution promotional image of a confident middle-aged entrepreneur standing in a modern office, soft natural light, cinematic framing, neutral color palette.”

2) “Critique the image with 3 bullet points about composition, lighting, and subject focus. Suggest one clear change for each point.”

3) “Apply only these changes: increase key-light contrast by 15%, tighten crop to 3:2 focusing on face and hands, simplify background to a soft gradient. Keep the same style and export at 3000×2000 px.”

Metrics to track

• Iterations to acceptable image (target <= 3)
• Time per iteration (target <= 10 minutes)
• Usability rate (% of images ready-to-use without editing; target >= 60%)
• Stakeholder approval score (1–5)

Common mistakes & fixes

• Mistake: Changing multiple variables at once. Fix: Tackle one critique per chained prompt.
• Mistake: Vague critiques. Fix: Use measurable language (increase contrast, crop to 3:2).
• Mistake: Over-describing style. Fix: Name 1 reference style (e.g., cinematic) and 2 constraints (palette, crop).

1-week action plan

1. Day 1: Run baseline prompt + critique on 3 concepts (30–60 min).
2. Day 2–3: Iterate chains to resolve composition and lighting (20–40 min/day).
3. Day 4–5: Apply brand polish and test stakeholder reactions (30–60 min).
4. Day 6–7: Measure metrics, document best prompts, create a one-page prompt template.

Your move.

Quick confirmation: Good call on verifying two details (title + DOI). That alone eliminates a large share of hallucinations.

Core problem: Large language models mix facts with plausible-sounding errors. For research writing, that damages credibility and slows acceptance.

Why this matters — short version: One bad citation or invented statistic can cost you reviewer trust, require rework, or sink a grant or publication. Fixing this is a process, not a guess.

What I’ve learned: Treat AI outputs as structured hypotheses — fast drafts that must be validated. That changes the workflow from “trust then edit” to “test then publish.”

What you’ll need

• AI chat access (GPT-style or similar).
• Two verification sources (PubMed/Google Scholar/Scopus or institutional library).
• Reference manager or single verification doc (Zotero, EndNote, or a verification spreadsheet).
• 15–30 minutes per major claim for verification.

Step-by-step workflow (do this each time)

1. Run the AI with the strict prompt below asking for citations, quotes, and a confidence level.
2. Extract top 2–3 claims you plan to use — list them separately in your verification doc.
3. Search trusted databases for title, DOI, or author. Verify at least two data points (title + DOI or title + authors + year).
4. If verification fails, label claim as “unverified” in draft and either remove or mark as speculative.
5. When writing, include only verified citations. Use AI text for drafting language only; keep original quotes and methods from sources.

Metrics to track (KPIs)

• % of AI-cited claims verified (target: 95%+).
• Average time to verify a claim (target: <15 minutes for key claims).
• Number of flagged/unverified claims per paper (goal: 0–1).
• Reviewer objections related to references (goal: zero on first submission).

Common mistakes & fixes

• Mistake: Taking AI citations at face value. Fix: Verify two details immediately.
• Mistake: Using paraphrases as factual claims. Fix: Pull direct quotes or methods sections from the primary source.
• Mistake: Vague AI prompts. Fix: Ask for exact citations, quotes, DOI, and confidence level.

1-week action plan (practical)

1. Day 1: Pick one paper or paragraph to revise. Run the strict prompt below.
2. Day 2: Verify top 3 cited claims in databases; record verification results.
3. Day 3: Rewrite paragraph using only verified citations; preserve quotes and methods excerpts.
4. Days 4–5: Repeat for next paragraph or section; monitor verification time.
5. Days 6–7: Consolidate verified references into your reference manager and prepare for submission.

Copy-paste AI prompt — primary (use as-is)

“You are an expert research assistant. Topic: [insert topic]. Provide a 3–5 sentence factual summary. For each key claim, list up to 3 peer-reviewed studies that directly support it. For each study include: full citation (authors, year, journal), article title, DOI (if available), one direct one-sentence quote from the paper that supports the claim, and a confidence level (high/medium/low) with a one-line reason. If you cannot find supporting studies, say ‘I don’t know’ and list how to verify.”

Strict variant (forces transparency)

“Do not invent citations. If unsure, reply ‘I don’t know’. For topic: [insert topic], return only verified peer-reviewed citations with DOI and a verbatim supporting quote. For each citation include a confidence score and the exact search terms you’d use to verify this in PubMed or Google Scholar.”

What to expect: Faster drafting, slightly more time upfront for verification, near-zero citation errors, and improved reviewer confidence.

Your move.

— Aaron Agius

Quick straight answer: You can get a natural-feeling 7-email nurture sequence from AI in under 90 minutes and run it with minimal tech. Do the smallest useful thing and measure the three KPIs that matter.

The problem: Most people ask AI to “write emails” and get long, generic copy that feels robotic. That kills opens, clicks, and trust.

Why it matters: A short, clear sequence that reads like a human will 1) keep subscribers engaged, 2) generate replies (real conversations), and 3) move people toward a single next step — which is where revenue comes from.

What I do and what you’ll learn: I set a single goal, use tight prompts, then edit for voice. The result is repeatable — you can run a new sequence every quarter.

1. What you’ll need
   • a one-sentence audience description (who + one pain),
   • the single goal for the sequence (what you want readers to do),
   • an email tool (any that schedules sequences and supports first-name tokens),
   • 60–90 minutes to create, 15–30 minutes weekly to review.
2. Step-by-step process
   1. Plan: Assign purpose to each of the 7 emails (welcome, tip, story, guide, objection, soft CTA, deadline).
   2. Prompt AI: Use the prompt below (copy-paste) to generate subject, preview, and a 3–5 sentence body for each email.
   3. Edit: Read aloud, shorten, add one personal detail, confirm a single, clear CTA and one link.
   4. Load & test: Insert tokens, schedule 2–4 days between emails, send tests to phone + desktop.
   5. Send to a small segment first (100–500) then ramp up if metrics look good.

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

“Write a 7-email nurture sequence for [Audience: one-line description, include one pain point]. Goal: [single goal, e.g., schedule a 20-minute consult]. Tone: warm, concise, conversational. Length: email body 3–5 short sentences. For each email provide: subject line (5–8 words), preview text (8–12 words), and the body. Email 1: welcome + set expectations. Email 2: quick actionable tip. Email 3: short relatable story or social proof. Email 4: practical how-to or checklist. Email 5: address the main objection. Email 6: soft CTA to next step. Email 7: reminder with deadline and easy opt-out. Include [FirstName] token where relevant.”

Metrics to watch

• Open rate — aim to improve subject lines if under 25%.
• Click rate on your CTA — primary indicator of interest.
• Reply rate — highest-quality signal; replies = opportunities.
• Unsubscribe rate — if it spikes, tighten relevance & cadence.

Common mistakes & fixes

• Too many CTAs: fix by having exactly one action per email.
• Long paragraphs: fix by cutting to 3 sentences and adding a line break.
• Robotic phrasing: fix by adding one short personal line (I did X) and one question to the reader.

1-week action plan

1. Day 1: Write audience + goal. Run AI prompt and generate drafts.
2. Day 2: Edit, humanize, and create subject line variations.
3. Day 3: Load into your email tool, add tokens, set schedule.
4. Day 4: Send tests to yourself and one colleague; fix formatting.
5. Day 5: Launch to a small segment; mark calendar for weekly review.

Your move.

Quick win: In under 5 minutes, paste your project bullet list into the prompt below and get a one-paragraph scope summary you can send to a client to lock expectations.

Good point focusing on scope creep and contracts — that’s where most small businesses lose time and margin. Below is a practical, non-technical workflow to use AI for drafting contracts and managing changes so you get measurable results.

The problem: verbal promises and vague proposals lead to scope creep, unpaid hours and disputes.

Why it matters: a single unmanaged scope change can erase profit on a project and damage client trust. Fixing this increases revenue per project and reduces disputes.

What you need:

• Project brief (deliverables, timeline, price)
• Client name and contact terms
• Access to an AI text tool (copy/paste prompt below)
• A standard change-order template (we’ll create one)
• Final legal review (one-time or periodic)

Step-by-step (what to do):

1. Collect: Write a one-paragraph bullet list of what you will deliver and what you will not (5 min).
2. Generate: Run the AI prompt below to produce a short contract skeleton and a one-click change-order clause (5–10 min).
3. Customize: Edit names, dates, payment terms, and acceptance criteria (10–20 min).
4. Attach: Add the change-order template to every proposal and require signed approval for scope changes.
5. Validate: Send to your lawyer for a quick review (one-time cost) and save as a template.

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

“Create a concise project agreement for a small business. Use these inputs: [paste project bullet list]. Include: deliverables, exclusions, milestones with dates, payment schedule, acceptance criteria, a change-order clause that defines how scope changes are requested, estimated cost and time impacts, and a 3-step approval workflow. Keep language simple for non-technical clients and highlight actions the client must take to avoid extra charges.”

What to expect: AI gives you 70–90% of the draft instantly. You will still need to confirm numbers and run a legal check, but turnaround drops from hours to minutes.

Metrics to track:

• Number of scope change requests per project
• Average revenue lost to unapproved changes
• % of projects with signed scope before work starts
• Time from proposal to signed agreement

Common mistakes and fixes:

• Vague deliverables — Fix: use bullet acceptance criteria tied to deliverables.
• Not enforcing approvals — Fix: require signed change-order and stop work on verbal approvals.
• Blind trust in AI wording — Fix: always review and run a legal check before use.

1-week action plan:

1. Day 1: Draft 3 common project briefs you do most.
2. Day 2: Use the AI prompt to generate contract skeletons for each brief.
3. Day 3: Create a reusable change-order form and attach to proposals.
4. Day 4: Send templates for legal review and finalize language.
5. Day 5: Use new contract on the next proposal and require client sign-off.
6. Day 6: Measure baseline metrics (signed % and change requests).
7. Day 7: Iterate based on what you measured and lock the process.

Your move.

Short version: You’re right — keep it low-tech, repeatable, and QA’d. That’s how you get clean data without extra overhead.

The problem: ad-hoc UTM naming creates fragmented analytics. Small variations (caps, spaces, typos) turn one campaign into dozens in reports — and you lose clarity on what’s driving results.

Why this matters: bad UTMs = bad decisions. If you can’t trust campaign attribution you’ll misallocate budget, under-measure channels, and slow growth.

Quick lesson from the field: a single spreadsheet, a simple naming rule, and one human QA saved a client 40% of time spent reconciling reports and reduced duplicate campaign labels by 85% in three months.

What you need

• Spreadsheet (Google Sheets or Excel)
• Short naming rule (1 sentence, lowercase, hyphens)
• Columns: Base URL | utm_source | utm_medium | utm_campaign | utm_content
• AI assistant for batch naming (optional but fast)

Step-by-step setup

1. Create the naming rule: e.g. product-audience-channel-yyyymm (lowercase, hyphens)
2. Build the sheet with the columns above and add this formula in Final URL: =CONCAT(A2,”?utm_source=”,B2,”&utm_medium=”,C2,”&utm_campaign=”,D2,IF(E2=””,””,”&utm_content=”&E2))
3. Lock the rule: top row or separate tab with exact pattern examples for copy-paste
4. Use AI to batch-create campaign names, paste winners into the sheet, then export final links
5. QA: one person checks 5–10% of rows before launch — catch edge cases fast

Copy-paste AI prompt (use as-is)

Create 10 campaign-name options following this pattern: product-audience-channel-yyyymm. Use lowercase, hyphens only, no spaces or punctuation. Product: “EcoBottle”, Audience: “newsletter”, Channel: “email”, Month: “202511”. Return only the campaign names, then for each return the final URL using base URL https://example.com/product with utm_source=newsletter, utm_medium=email, utm_campaign=[campaignname], utm_content=variantA.

Metrics to track (start with these)

• % of UTM values normalized (target 100%)
• Number of duplicate campaign labels per month (target 0–2)
• Time to generate 100 campaign links (baseline vs after automation)
• Errors found in QA per 100 links (target <2)

Mistakes & fixes

• Mixed case or spaces: =LOWER(SUBSTITUTE(cell,” “,”-“))
• Duplicates: use COUNTIF to detect and append a numeric suffix
• Missing fields: require source/medium/campaign as mandatory in the sheet (data validation)

1-week action plan

1. Day 1: Draft 1-line naming rule and lock it in the sheet.
2. Day 2: Build the sheet with the formula and sample rows.
3. Day 3: Run the AI prompt to batch-generate 20 campaign names and fill the sheet.
4. Day 4: Run QA on 10% of links; fix issues and update rules if needed.
5. Day 5–7: Use the system for actual campaign launches; measure metrics above and adjust.

Your move.

Quick win (3 minutes): Open a keyboard app, play two notes, hum the interval, and name it. Repeat five times. That direct hearing + voice work rewires your ear faster than reading another article.

The problem: Beginners over 40 often flip between apps, rely on automated chord-detection, and skip singing. That slows real progress and kills motivation.

Why this matters: Music skill is pattern recognition — ears, voice, and fingers. Short, consistent habits produce measurable gains; unfocused practice doesn’t.

What I’ve learned: Pick two tools and a simple daily routine. One lesson app for structure, one ear-training app for deliberate listening, and an AI assistant for plain-language explanations and focused practice plans.

1. What you’ll need
   1. Phone/tablet and good headphones.
   2. Optional: basic keyboard or guitar.
   3. 15 minutes/day and a calendar reminder.
2. Daily routine (step-by-step)
   1. 2 minutes: warm-up (hum a comfortable note, sing a simple scale fragment).
   2. 8 minutes: ear drills — intervals first. Play/hear, hum, name. Track correct/attempts.
   3. 5 minutes: guided lesson or focused drill on one concept (major scale, triads, or rhythm).
   4. Optional 5 minutes: slow-down tool to learn one short phrase from a song.
3. Using AI effectively
   1. Ask AI for a 2-week plan that matches your app lesson progress.
   2. Use one-sentence explanations and one playable example when something’s confusing.

Metrics to track (KPIs)

• Minutes practiced per day (target: 15–20).
• Ear-drill accuracy (target: +10% every two weeks).
• Intervals/chords reliably identified (target: 5 new items mastered per week).
• Song fragments learned by ear (target: 1 short phrase/week).

Common mistakes & fixes

• Mistake: Switching apps every week. Fix: Commit to one lesson app and one ear app for 4 weeks.
• Mistake: Not singing. Fix: Hum every interval before naming it — your voice is the fastest feedback loop.
• Mistake: Blindly trusting chord detectors. Fix: Use detectors for hints, then confirm by ear or play on the instrument.

Copy-paste AI prompt (use as-is)

“I’m a beginner learning music theory and ear training. I play (piano/guitar/none). I have 15 minutes/day for 14 days. My goals: reliably identify intervals, tell major vs minor triads by ear, and learn short song phrases by ear. Give me a day-by-day plan with exact drills, one short tip per day, and measurable outcomes to track.”

1-week action plan (exact)

1. Day 1: Do the 3-minute quick win. Install one lesson app + one ear app. Set a 15-minute reminder.
2. Day 2–3: Intervals — focus on minor/major 2nd and minor/major 3rd. Log accuracy.
3. Day 4–5: Major/minor triads — listen, play, label. Practice singing root and 3rd.
4. Day 6: Apply to song fragment — use slow-down tool for a 4-bar phrase.
5. Day 7: Record a 30-sec clip of you humming intervals/chords; compare to Day 1.

Expect clearer recognition in 2–4 weeks and consistent improvement if you hit the KPIs above. Keep it focused: small wins compound.

Your move.