The Complete Build Guide

Stop using AI as a tool.
Start running it as a team.

The complete playbook for building an AI agent squad that answers your phone, researches overnight, and runs your business while you sleep. No coding required.

Get the Playbook — $79 → See what's inside ↓
The A(I) Team — Build your AI agent squad
14
Chapters
9
Agent types
$60
Monthly running cost
0
Lines of code

Your phone rings while you're working. Someone else's picks up.

These are the people who build an A(I) Team — and what changes when they do.

⚖️
Sarah — Solicitor
Small firm, 3 staff
Misses 30% of inbound calls during client meetings. Potential clients call the next firm on the list.
Her AI answers every call 24/7, takes details, books callbacks. Zero missed enquiries.
🔧
Mick — Electrician
Solo operator, on tools 7am–4pm
Loses 2–3 jobs a week to unanswered calls. At $700 a job, that's real money gone.
Every call answered. Full job details taken. Mick calls back hot leads at lunch. 100% callback rate.
🚗
Chris — Consultant
45-min drive between client sites
Two hours of daily drive time completely wasted. Proposals unwritten. Briefs never prepped.
Calls his AI on the drive, dictates what he needs. Arrives to find it drafted and ready to send.
🍽️
Bella — Restaurant Owner
60 seats, fully booked weekends
Can't answer calls during Friday night service. Regulars book elsewhere by the time she calls back.
AI takes all bookings, answers questions, flags large group enquiries. No missed reservation.
🌿
Ryan — Landscaper
3-person crew, word-of-mouth business
Great at the work, slow on quotes. Jobs go cold before he gets off his knees to write them up.
Dictates job details on the drive home. Quote is structured and ready before he reaches the driveway.
🏥
Dr. Chen — GP
800+ patient panel, solo practice
Phones open at 8am and never stop. After-hours calls go to voicemail. New patients fall through.
AI handles first contact 24/7. Receptionist arrives to a pre-triaged list of overnight contacts.

You've been using AI like a search engine.

You ask it questions. It gives you answers. You copy-paste them into your work. That's not an AI team. That's a very fast intern.

The people actually winning with AI right now aren't using it as a tool. They're running it as infrastructure. They have agents that answer their phone when they can't, research topics overnight and brief them in the morning, draft and edit content without being asked, and monitor their business 24/7.

They built all of it — not by writing code, but by knowing which tools to connect and how. This guide teaches exactly that.

I wanted to use AI properly.
I had no idea how.

I kept reading about founders and executives who had AI working for them — actually working for them. Answering their phone. Briefing them every morning. Handling the stuff that used to take hours.

I'd been using ChatGPT like everyone else. Ask a question, get an answer, copy something useful. That's not a team. That's a very expensive search engine.

Then I found OpenClaw — and it changed everything. In theory. In practice, making it actually work was one of the hardest things I've done. The documentation assumes you're a developer. The tools don't talk to each other out of the box. There are about forty places where something breaks silently and you have no idea why.

I spent weeks on it. Late nights, wrong configurations, agents that answered with the wrong name, voice calls that dropped, phone numbers that connected to nothing. Every time I thought I'd cracked it, something else broke.

But when it finally worked — properly worked — it was unlike anything I'd experienced. I had a chief of staff who answered my phone at midnight. A researcher who had a brief on my desk before I woke up. A full team, always on, that could handle almost anything I threw at it — for about the price of a decent dinner each month.

I built this guide because I didn't want anyone else to spend those weeks figuring it out. Everything I learned, every mistake I made, every configuration that actually works — it's all in here. You skip straight to the part where it works.

— The A(I) Team

14 chapters. Every step explained.

Written for non-developers. If you can follow instructions and copy-paste, you can build this.

00
Real People, Real Problems
Use cases — find yourself in one of these stories
01
The Idea
Why a squad of specialists beats one generalist AI
02
Before You Touch Anything
Terminals, API keys, JSON — explained simply
03
The Stack
Four tools, what they cost, how they connect
04
Your First Agent
Install, configure, first message — done in an afternoon
05
Giving It a Phone Number
Twilio + Vapi: your agent answers real calls
06
Giving It a Voice
ElevenLabs: voices that sound genuinely human
07
The Knowledge Base
What your agent knows and how to control it
08
Building the Squad
9 specialist agents and how they coordinate
09
The Tools Server
Agents that book, send, call, and actually act
10
Security
Passphrases, caller tiers, keeping data safe
11
The 10 Mistakes We Made
Read this before you think you've got it figured out
12
Advanced Setup
Morning briefings, heartbeats, calendar integration
13
Charging Clients
Tiers, the demo that closes, how to price it

Choose your build level

Start with the playbook. Upgrade when you're ready to move fast.

$79
The Playbook
  • 14-chapter complete guide
  • Step-by-step setup instructions
  • All 9 agent archetypes
  • The 10 mistakes chapter
  • Client billing framework
  • Instant PDF download
Get the Playbook →
$2k
Done For You
  • We build it for your business
  • Custom knowledge base
  • Voice agent on your number
  • Full squad (up to 5 agents)
  • 30 days support included
  • Limited availability
Apply Now →

The 10 mistakes we made so you don't have to.

Every single one of these cost us real time. They're in the guide so they don't cost you the same.

01
Wrong Vapi model version string
One character difference. Calls silently stop working. Took a day to find.
02
Quick tunnel URLs in production
The URL changed on restart. Every tool call in every agent broke instantly.
03
Treating session context like persistent memory
The agent promised to send something. Call ended. Session ended. Never sent.
04
Building infrastructure before writing the system prompt
Spent days on the stack. Then discovered the agent was generic and useless.
05
No auto top-up on API billing
Every agent went offline at 4am. Didn't notice until late morning.

+ 5 more in the full guide.

FAQ

Do I need to be technical?
No. The guide is written for non-developers. If you can follow instructions and copy-paste text, you can build this. Chapter 02 explains terminals, API keys, and JSON from scratch.
How long does it take to set up?
A basic voice agent that answers your phone can be live in an afternoon. A full 9-agent squad takes a focused weekend.
What does it cost to run?
Roughly $60–120/month depending on call volume. The guide covers how to start lean and scale up only when needed.
Can I use this to build for clients?
Yes — Chapter 13 covers exactly how to package and sell this as a service, including pricing tiers and the demo that closes deals.
What's included in the Templates bundle?
All 9 agent config files (JSON), the tools server code ready to deploy, system prompt templates for every agent type, and the morning briefing script.
What technology does this use?
OpenClaw (agent orchestration), Vapi (voice AI), Twilio (phone numbers), ElevenLabs (voice quality), and Anthropic Claude as the AI model. All fully documented in the guide.

The team that seemed like science fiction is a weekend of setup away.

Start with one agent. Get it running. Call it. The rest follows.

Get the Playbook — $79 →
Also available: Playbook + Templates $149  ·  Done For You $2,000