Build your agentic lead generation system.

Every tool you've ever used waits for you to click. An agent is different: you hand it an outcome — "answer every missed call" — and it works the steps itself: think, act, check, repeat. That loop is the whole trick. The rest of this course is just giving that loop better tools.

Builder's note: start with one agent owning one job end-to-end. "One agent, one job" beats a mega-agent every time — easier to test, easier to trust, easier to fix.

Your CRM, calendar and email each have a socket on the back wall — the API. Any appliance with the right plug can use it, no rewiring. When an agent "connects to your calendar", it's plugging into that socket and asking in the app's own language. The API key is simply the door key that proves it's allowed in.

Builder's note: before buying any software, search "[tool name] API docs". If nothing comes up, your agents can't reach it — a red flag for the whole stack.

Before travel adapters, every country's socket was a small crisis. Tools are the same — every API speaks its own dialect, and hand-wiring agents to each one is slow. MCP (Model Context Protocol) is the universal adapter: a tool publishes one standard port, and any agent can dock with it instantly. Your CRM, inbox, files and browser stop being separate wiring jobs and become sockets on the same ring.

Builder's note: one MCP connection replaces dozens of hand-built integrations. Check for an official MCP server before wiring anything by hand — most major tools ship one now.

The model is the engine — some small and fast, some heavy and clever. The prompt is the blueprint you hand it: what to build, what good looks like, what to avoid. Weak results are almost never the engine's fault — they're a thin blueprint. Builders write blueprints, not wishes.

Builder's note: save every prompt that works. A folder of proven blueprints is a real business asset — it's how one person ships like a team.

You are my [role — e.g. marketing assistant].
Outcome: [one sentence — what done looks like].
Rules: keep my tone; UK English; ask before assuming; show your working.
Good looks like: [paste one real example].
Now do: [the task].

"Should I use Claude or ChatGPT? Claude or Codex?" Wrong question. Models swap places every month — the winners just change engines. What compounds is your system: one central place holding your files, skills, prompts and data. Build that once, and every new model makes it stronger the day it ships.

Builder's note: the moat was never the model. Engines depreciate; your library of skills, prompts and data appreciates. That's the asset you're building in this course.

A chat window answers and forgets — you carry everything in and out by hand. An agent environment is different: it holds your files, uses your tools, runs your skills, and does the work where the work lives. Chat gives advice. Agents give outcomes. The moment you move from asking to delegating, everything else in this course becomes possible.

Builder's note: graduate on purpose — use chat to think, agents to do. Make your first agent task something you already do weekly, then save the method as a skill (1.4). That's your personal AI becoming a foundation for agentic workflows.

A city runs on a grid you never think about. Your stack is the same: one model provider, one automation layer, one place agents live. Pick few, pick boring, wire them well — a builder with three tools ships faster than a hoarder with thirty.

Builder's note: a working example: Claude for the thinking, GoHighLevel for CRM and follow-up, Instantly for cold email, Apollo for lead data. Four tools — that's an entire lead generation system.

An agent reads your folders like a new employee reads the filing hall. If every client has the same folder shape — brief, assets, output — an agent can serve any client without asking. Naming is not admin; it's infrastructure.

Builder's note: the test: could a stranger find any client's proposal in ten seconds? If yes, an agent can too. If no, fix the folders before you build anything else.

Every business repeats one question forever: "where does that live?" Leads in the CRM, content in the drive, money in the ledger. Write it once as a map your agents read, and they stop guessing. The map is one page — and it's the most valuable page you'll write.

Builder's note: when an agent gets something wrong, check the map first. Nine times out of ten it guessed where something lives — because nobody told it.

MAP — where everything lives
Leads      → [CRM name]
Content    → [drive / folder]
Money      → [invoicing tool]
Bookings   → [calendar]
Customers  → [source of truth]
One source of truth per line.
If it's not on the map, agents must ask.

The first time you teach an agent a job, write it down as a skill: the steps, the rules, the examples. Next time it's one line — "run the skill." A library of skills is a workforce that trains itself.

Builder's note: when a skill misfires, fix the instruction — not the output. You're managing a workforce now, and the training manual is the asset.

SKILL: [name — e.g. weekly-report]
WHEN: [trigger — when should this run]
STEPS:
 1) [first step]
 2) [second step]
 3) [third step]
RULES: [what to never do]
EXAMPLE: [paste one good output]
Save this. Next time just say: run [name].

Cold email dies at the door, not in the copy. Fresh domains, warmed inboxes, correct records (SPF, DKIM, DMARC) — that's the postal service learning to trust your envelopes before anyone reads a word. Skip this and every later lesson underperforms.

Builder's note: the maths: 3 domains × 3 inboxes × 30 emails ≈ 270 a day, safely. Want more volume? Add domains — never push one domain harder. That's how you end up in spam. And judge campaigns by replies, not opens: open-tracking pixels are noise (mail apps prefetch them), while Google reads replies as the strongest "this is wanted" signal there is — every genuine reply actively protects your sender reputation.

A CRM is not software you fill in. Done right, agents fill it: every call, reply and booking logged the moment it happens. Pipelines become honest because nobody has to remember to update them.

Builder's note: if a human has to remember to update it, it becomes fiction within a month. Automate the boring writes first — that's what makes the pipeline true.

Most money is lost in the gap after "interested". A follow-up agent works that gap: replies in minutes, nudges at the right hour, books the call at 11pm. Speed isn't politeness — it's revenue.

Builder's note: reply in five minutes and you're talking; reply in five hours and they've bought elsewhere. The agent's edge isn't cleverness — it's being awake.

A list is not names — it's evidence. Source companies that look like your best client, then enrich: size, stack, signals, the person who owns the problem. Agents do the digging; you keep the judgement.

Builder's note: verify before you send — a 5% bounce rate can kill a domain's reputation. List quality is infrastructure, not admin.

LinkedIn is two machines: content that makes strangers trust you, and outreach that starts conversations without smelling like spam. Agents draft both; your voice stays on top. Consistency beats brilliance — the algorithm pays the punctual.

Builder's note: give away the exact playbook publicly. The people who'd do it themselves were never buyers — the ones with budget hire the person who wrote the playbook.

Everything so far assembles into the Machine: infrastructure carries it, lists feed it, agents write 1:1 emails a human would be proud of, replies route straight to booking. You met it on the homepage — here you learn to build your own.

Builder's note: one genuinely personal first line beats every clever template. If the email could have been sent to anyone, it converts like it was sent to no one.

Faceless pages, AI avatars, product clips — content agents can draft, cut and schedule a week of media in an afternoon. The skill isn't making one great post; it's building the pipeline that never skips a day.

Builder's note: batch monthly, post daily. The pipeline that never skips a day beats the genius post that took a week.

A missed call is one event — but it should trigger four hands: text the caller back, log the lead, brief the owner, book the slot. Wiring is deciding which events wake which agents. Draw the wires before you build them.

Builder's note: draw the wires on paper first. If you can't draw it, you can't debug it at 9pm when a client's phone goes quiet.

Voice agents answer instantly, sound human enough, and never sigh on a Friday. They qualify, book, and hand hot calls to you. The craft is the script tree and the handover — knowing when a human must take the wheel.

Builder's note: let it say it's an assistant and offer a human — trust goes up, complaints go down. The goal was never to fool anyone; it's to answer at ring two, every time. We run this exact build on Time Consulting's own line — it's the demo we play to clients.

Invoices chased politely at 9am, reports written in plain English on Monday, anomalies flagged before they hurt. Finance agents don't do accounting — they do attention, relentlessly, on schedule.

Builder's note: the polite chase, sent reliably, collects most invoices before a human ever gets involved. Consistency is the collection strategy.

Every system we install ran on our own businesses first. Do the same. Your business is the show home: when a prospect asks "does this work?", you show them your own dashboard, not a slide.

Builder's note: when a prospect asks "does this work?", the show home answers before you do. Every system you sell should be one you live in.

Nobody buys "automation consulting". They buy "never miss a call again". Package each system with a name, a promise and a price. This is the highest-paid hour in the course.

Builder's note: "never miss a call again" outsells "AI voice automation solution" every day of the week. Nobody buys the plumbing — they buy the hot water.

Two doors: a productised system at a flat monthly (easy yes, compounding), and custom builds at project pricing (bigger, slower, richer). Run both. The product pays rent; the customs pay for the summer.

Builder's note: agents build fast — hourly pricing punishes you for being good. Price the product so yes is easy, and the custom so yes is worth it.

You built the Machine in Level 3 — now point it at your own pipeline. Every email it books proves the product it sells. That's the meta-trick of this whole model: your marketing IS your portfolio.

Builder's note: the audit is the demo. Find money they're losing inside fifteen minutes and the close handles itself.

Growth is unglamorous arithmetic: X clients on the product, Y custom builds a quarter, churn kept low because the systems actually work. Put the whole model on one page so you always know which number to push next.

Builder's note: at any moment exactly one number is the bottleneck. Work on anything else and you're busy, not growing.