Hey Prompt Warrior,

I built an AI sales coach last week that records my calls, analyzes them, and writes me a detailed coaching report. The whole thing took under 10 minutes to set up.

Every morning it pulls yesterday's call transcripts, scores them against sales frameworks I uploaded, and drops a full breakdown into Notion. Talk ratio, key moments, a scorecard, action items. I just read it with my coffee.

In this post, I'll walk you through the exact three steps to build it yourself.

If you prefer watching over reading, here's the YouTube video.

Here's what we'll cover:

Read time: 5 minutes

If you're an operator who knows AI matters but has no time to figure it out yourself, this is what I do with clients.

I help you build an army of AI agents that run the workload of an entire team, so you grow without growing payroll.

What you get:

Spots are limited. If that sounds like you, apply for a call here.

Now, back to the tutorial.

A year ago, an automation like this meant wiring up a sprawling n8n canvas. You remember the videos: 40 nodes to do something simple, and it broke every other week.

Now you describe what you want in plain English and Claude Code builds it. The flow is three steps:

That's the whole shape. Here's each piece.

Fathom is the call recorder. It sits on your Google Meet or Zoom calls and gives you clean transcripts after.

Best for: any call you want analyzed later, sales calls, discovery calls, client check-ins.

Plenty of recorders exist. The one you want is the one that exposes an API, an MCP, or a CLI, so Claude Code can actually reach the data. Fathom has an API, which is why I picked it.

Then open a Claude Code session in that folder and say: "I saved the Fathom API key in my env file, check it works and fetch some data." It pulled my latest meeting on the first try.

Pro tip: while you're there, tell it to save a compressed copy of the Fathom API docs into your tools folder and add Fathom to your TOOLS.md. That way every future session already knows the tool exists and how to call it. I do this for every tool I connect.

The skill is the brain. It's a plain text file that describes exactly what the automation should do, written in natural language.

Best for: any repeatable job you'd otherwise do by hand every day or week.

I wrote this straight into the chat and let it build:

That folder I pointed it at holds the sales frameworks I'd saved over time (mine lean on Alex Hormozi's stuff). The skill reads those, scores the call against them, and writes the report.

The best part: that text file replaces the entire n8n canvas. One readable document does the job 40 nodes used to do.

A routine is just the timer. It wakes the skill up on a schedule so you never touch it again.

Best for: anything that should run daily or weekly without you remembering to press a button.

One thing I caught: the first draft of the routine was bloated with the full instructions. You don't need that. The skill already holds the logic, so the routine just points at it and fires.

After that it runs on its own. You watch the runs land and check Notion to confirm the reports showed up.

And here’s a snippet from the report that was generated (see the full thing in the youtube video):

✅ An AI sales coach records, scores, and writes up your calls automatically
✅ Step 1: connect a call recorder with an API (Fathom)
✅ Step 2: write a skill, a plain text file describing the job
✅ Step 3: add a routine to run it on a schedule
✅ The skill file replaces the whole n8n canvas

Thanks for reading!

If you enjoyed this, consider forwarding this newsletter to a friend or colleague.

What would you like me to write about in the next post? Reply to this email and let me know.

Moritz

P.S. The sales coach is one skill. The real win is the foundation underneath it, the ClaudeOS setup where every tool, framework, and routine lives in one folder that compounds over time. If you want help installing that in your business, apply for a strategy call.