module 14 verify output

You are the quality layer

System Text-to-Speech Ready
Slide: 0:00 / 0:00
Slide 1 of 0Interactive Deck

Full Lesson Reference

Claude Code builds fast. It can produce a report, a campaign, an audit, a landing page in minutes. But it doesn't know if the numbers are right, the brand is correct, or the content makes sense for the client. That's your job.

This module is the discipline that makes you trustworthy - catching Claude's mistakes before a client sees them.

The single most important rule

Every client-facing deliverable gets a human review before it's sent. No exceptions.

Speed is great. Speed without review costs more than it saves when a single mistake destroys trust.

What Claude is reliable at

  • Following explicit written instructions
  • Formatting + structuring content
  • Code + HTML generation when the spec is clear
  • Pulling data from MCPs + databases you've configur ed
  • Applying templates + styles consistently
  • Writing first drafts of most content types
  • Executing multi-step workflows it's done before

What Claude is NOT reliable at

  • Knowing what's true about specific clients - it may assume things that aren't true
  • Verifying numbers it generated - it can't tell fabricated vs real after the fact
  • Judging whether a recommendation is right for the client
  • Spotting its own hallucinations
  • Remembering details from 10 messages ago in a long session
  • Knowing what's currently true vs what was true last year (training cutoff effects)

Your job is focused on the NOT reliable list. Claude handles the reliable stuff.

The review pyramid

Check in this order

  1. Data accuracy (most important)

Every number in the deliverable - is it real? Can it be traced to source?

  1. Client correctness

Is it the right client's name, logo, brand? Any leftover references to other clients?

  1. Content logic

Do the recommendations make sense? Does the narrative flow? Are the conclusions actually supported by the data?

  1. Brand + format

Does it look right? On-brand colours, fonts, layout? Mobile-responsive if applicable?

  1. Mechanical checks

Do all links work? Does the form submit? Does the page load? Spelling + grammar?

Start at 1. If 1 is wrong, nothing else matters.

The fast-review rule

For any deliverable, budget at least 10 minutes of review. Regardless of how quickly Claude produced it.

Fast delivery = fast review required. Not shorter review.

Speed comes from

  • Claude handling the production (fast)
  • You handling the review (always thorough)

Both are needed. Never skip the second.

When review catches something

You'll find mistakes. Every marketer does. When you find one:

  1. Don't panic - caught before client sees = success
  2. Tell Claude what's wrong + why
  3. Have Claude fix + re-check
  4. Update the CLAUDE.md or skill that let the mistake through
  5. Add a rule that catches this category of mistake next time

Every caught mistake makes the system better. Repeat mistakes are the ones you learn from.

When to be most paranoid

  • First time using a new skill or workflow
  • First deliverable to a new client
  • Anything involving sent emails, ad launches, or public posts
  • Any deliverable with financial numbers (revenue, spend, ROAS)
  • Any work done in a session that went over 50% context (degradation territory)
  • Any work done late at night or when you're rushed

Action items

☐ Commit to: every client-facing deliverable gets reviewed, no exceptions

☐ Memorise the review pyramid: data → client → content logic → brand → mechanical

☐ Budget 10 minutes minimum for review, regardless of how fast Claude produced

☐ Be extra paranoid on new skills, new clients, anything with numbers, anything with sends

Next lesson: Tracing numbers to source.

Exercises

  1. Review the concepts covered in this lesson: You are the quality layer.
  2. Write down your key takeaway from this lesson.
  3. Practice running any commands or prompts mentioned above inside your terminal.