Creative Automation / Foundation

3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)

Eric Michaud shares the three systems clients actually pay him to build with Claude Code/Codex skills: a cross-platform intelligence dashboard (most recent sale: over $10K CAD), friction-free field reporting via photo and voice inputs ($3,100), and packaging tools you already built for yourself β€” with the common thread that you make businesses easier to operate, not add more stuff.

Eric Michaud8 minTranscript found

Quick learning frame

Read this before watching.

Creative automation uses agents to accelerate production while keeping human taste in story, pacing, selection, and critique.

New playlist item from Eric Michaud; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Skill you build: The ability to turn AI coding competence into paid work by building what businesses repeatedly ask for: unified data, easier inputs, and productized versions of your own systems.

Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.

Concept diagram

Where this video fits.

01Brief
02Source
03Generation
04Selection
05Edit
06Taste Review

Deep lesson

Turn this video into working knowledge.

1,860 cleaned transcript words reviewed across 536 timed caption segments.

Thesis

3 EXACT Systems I Get Paid $13.1K to Build (COPY ME) teaches a practical creative automation move: Eric Michaud shares the three systems clients actually pay him to build with Claude Code/Codex skills: a cross-platform intelligence dashboard (most recent sale: over $10K CAD), friction-free field reporting via photo and voice inputs ($3,100), and packaging tools you already built for yourself β€” with the common thread that you make businesses easier to operate, not add more stuff.

The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.

0:00

Unify the platforms

β€œIf you don't know what to do with your new found cloud code or code x skills, I'm going to save you some trouble. I've been making full time income in the AI space for the last 2...”

The number-one request is 'make all these platforms make sense to me' β€” leads in HubSpot/Pipedrive, projects in ClickUp, ConvertKit, storefronts, Google Sheets, QuickBooks, each owned by a different person β€” so the build pulls everything into one place focused on answers and correlations ('did this email campaign equate to more leads?'), not just a dashboard of charts. For one business you know, list every platform its operations live in and who owns each, then write three correlation questions the owner can't currently answer without chasing five people.

2:42

The build recipe

β€œserverless functions or something else, but like Claude Code Codex, they can figure that out. The biggest thing is messy, disjointed platforms go in, responsible intelligence comes out. And like I said, this isn't theoretical. The most recent...”

The stack is one source of truth in BigQuery ('like Supabase but on steroids' β€” SQL support, built for huge fast queries, effectively free at this scale, set up via Google OAuth), synced by free GitHub Actions on sensible cadences (project management once a day, CRM hourly), and then Claude Code/Codex builds the front end β€” messy disjointed platforms in, responsible intelligence out. Set up a free BigQuery project and write one GitHub Action that syncs a single data source into it on a schedule, as the seed of a source-of-truth pipeline.

6:21

Remove input friction

β€œyourself and that's the thing. People have bought access to blueprints, workflows, apps, systems from me in the past and the same thing I've been approached by businesses and paid to set up systems for them. These all...”

The second paid pattern makes reporting effortless for field workers β€” photo-in/inventory-out estimates that cut his moving-company site visits from an hour to 10-15 minutes, and voice notes that transcribe 'arrived 8:15, left at 10, routine inspection' straight into forms and spreadsheets β€” and the third is packaging what you already built for yourself (like his Obsidian workspace) and selling it via Gumroad, Skool, or a landing page instead of agonizing over turning it into a SaaS. Identify one report or form that a hands-on worker skips, and prototype a voice-note or photo flow that fills it automatically; separately, list one system you built for yourself that someone else would pay for.

01

Brief

Start with this video's job: Eric Michaud shares the three systems clients actually pay him to build with Claude Code/Codex skills: a cross-platform intelligence dashboard (most recent sale: over $10K CAD), friction-free field reporting via photo and voice inputs ($3,100), and packaging tools you already built for yourself β€” with the common thread that you make businesses easier to operate, not add more stuff. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: β€œIf you don't know what to do with your new found cloud code or code x skills, I'm going to save you some trouble. I've been making full time income in the AI space for the last 2...”

02

Source

Use "Source" to locate the part of the creative automation workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 2:42, where the video says: β€œserverless functions or something else, but like Claude Code Codex, they can figure that out. The biggest thing is messy, disjointed platforms go in, responsible intelligence comes out. And like I said, this isn't theoretical. The most recent...”

03

Generation

Turn "Generation" into the reusable artifact for this lesson: A creative workflow board with critique criteria and review checkpoints. This is where watching becomes something you can inspect and reuse.

04

Selection

Use "Selection" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.

05

Edit

Use "Edit" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.

06

Taste Review

Use "Taste Review" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.

Example

Source-backed work packet

Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a creative workflow board with critique criteria and review checkpoints..

Example

Claim vs. demo brief

Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.

Example

Teach-back module

Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.

Do not learn it wrong
  • Treating the title as the lesson without checking what the transcript actually says.
  • Letting the prompt drift into generic advice that could apply to any video in the playlist.
  • Copying the tool setup without identifying the operating principle that transfers to your own stack.
  • Skipping the artifact, which means the learning never becomes operational or inspectable.

Transcript-derived moments

Use timestamps to study the actual video.

Quality check

Do not count this as learned until these are true.

01

State the transcript-backed claim in your own words: Eric Michaud shares the three systems clients actually pay him to build with Claude Code/Codex skills: a cross-platform intelligence dashboard (most recent sale: over $10K CAD), friction-free field reporting via photo and voice inputs ($3,100), and packaging tools you already built for yourself β€” with the common thread that you make businesses easier to operate, not add more stuff.

02

Explain the practical stakes without hype: New playlist item from Eric Michaud; queued for transcript-backed review, topic mapping, and a practical learning artifact.

03

Map the idea onto the Brief -> Source -> Generation -> Selection -> Edit -> Taste Review sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: A creative workflow board with critique criteria and review checkpoints.

Put it into practice

Give this grounded prompt to Codex or Claude after watching.

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: 3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)
- URL: https://www.youtube.com/watch?v=PiKCyu7WQLo
- Topic: Creative Automation
- My current learning frame: Pick one small business, sync two of its platforms into BigQuery with a scheduled GitHub Action, build a simple correlation dashboard on top, and add one voice-or-photo input flow β€” a miniature version of both systems clients paid $10K and $3.1K for.
- Why this matters: New playlist item from Eric Michaud; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "If you don't know what to do with your new found cloud code or code x skills, I'm going to save you some trouble. I've been making full time income in the AI space for the last 2..."
- 2:42 / Evidence 2: "serverless functions or something else, but like Claude Code Codex, they can figure that out. The biggest thing is messy, disjointed platforms go in, responsible intelligence comes out. And like I said, this isn't theoretical. The most recent..."
- 4:13 / Evidence 3: "my lunch on the road or whatever. I could give you commands, right? Like {slash} invoice. Four movers, seven hours. Boom. Invoice four movers, seven hours. No problem, right? Something else I'm doing really frequently now, too, with..."
- 6:21 / Evidence 4: "yourself and that's the thing. People have bought access to blueprints, workflows, apps, systems from me in the past and the same thing I've been approached by businesses and paid to set up systems for them. These all..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)", not a generic Creative Automation essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.

Misconceptions

What to stop believing.

Creative AI removes the need for taste.

It increases the need for taste because output volume explodes.

The best prompt is enough.

References, critique, iteration, and post-production matter just as much.

Practice studio

Learning only counts when you make something.

01

Transcript evidence map

Separate what the video actually says from what you already believe about the topic.

3 source-backed takeaways with timestamps, confidence, and a transfer note.
02

One useful artifact

Apply the video to a real workflow and produce a creative workflow board with critique criteria and review checkpoints..

A reusable artifact with a done signal and one verification step.
03

Teach-back card

Explain the lesson to someone who has not watched the video yet.

A 90-second explanation, one diagram, one example, and one misconception to avoid.

Recall check

Answer first, then reveal β€” without rewatching.

What is the most common thing clients ask Eric to build, and why is 'dashboard' an incomplete description of it?

Which two free/cheap tools does Eric use to centralize and sync client data, and how does he schedule the syncs?

How did the voice-notes system change reporting for field technicians?

Source shelf

Use the video as a doorway, then verify with primary sources.

ReadingComfyUIwww.comfy.org/ReadingAffinityaffinity.serif.com/