What the source did
- He used to be a steamfitter; now he teaches gym and runs BuiltForShops, which builds websites for independent shops, answers their calls, keeps their Google profiles current and asks their customers for reviews.
- Orchid, a chief-of-staff bot, is the only agent he talks to. She decides who does each job, hands it off and reports back, so he reads one thread instead of a reply from every agent.
- Forge builds the sites. Cipher runs the backend: before touching 21 town pages on a pizza shop's site it rebuilt the site from source, compared it to what was live, then ran 63 live checks (all passed).
- Voice answers shop calls the owner can't pick up and sends the details. Reviews keeps each Google profile current, asks customers for reviews (never twice) and drafts replies for the owner's OK.
- Print designed postcards, counter signs, business cards, a banner and a poster in each shop's own brand, checked that every QR code opened the right review page, built the Vistaprint cart and stopped there.
- Scout researches prospects, Outreach and Nike draft sales emails behind a gate, Funnel works on offers and Ledger tracks the money, sending him only the decisions that are his.
- Recipe writes down what worked as playbooks for the next run, Disk Saver found about 3.9 GB to trim and waited for his yes before deleting, and Signal, Reel and Link handle X, video and LinkedIn. Signal writes and posts his X originals itself; replies under other people's posts he pastes himself.
- Heads-up: a small, new account with little engagement, and the article gives no revenue figures. He made one agent, Print, a public template.
“If I approve without reading, the gate is decoration, and that part is on me.”— Mark Meyer (@MarkMeyerBuilds), X (Article)
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Grok Bot with one chief-of-staff bot as your only contact, specialist bots with one lane each, his Shop Print Designer template for print, a Vistaprint account and access to each shop's Google profile.
- Where it breaks
- You becoming the bottleneck (drafts wait while he teaches), approving without reading, business hours that don't match across listings, and agents changing a live site without first recording its state.
- Human checkpoint
- Five gates: outgoing messages are drafts he approves, print carts wait for the shop owner, deletions wait for his yes, he posts his own X replies, and prices are checked against the live pricing page.
- Tools involved
- Grok Bot, His Shop Print Designer template (for print), Vistaprint (carts the owner approves), Access to each shop's Google profile
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Get their template
Made and published by Mark Meyer. Start here; it is their original, not ours.
Our adapted version
Ours Our version, built only from the team structure and five approval gates Mark describes in his article. Not his wording; only his Print agent is public. Fill in the [BRACKETS].
You are my chief of staff. You are the only agent I talk to.
ROUTING
- When I ask for something, decide which specialist should do it, hand it off and report back to me in one thread.
- Specialists report to you, not to me. Send me one short summary, not a message from every agent.
- Specialists: [SITES], [BACKEND/OPS], [CALLS], [REVIEWS], [PRINT], [PROSPECTING], [SALES EMAIL DRAFTS], [MONEY TRACKING], [PLAYBOOKS]. Each keeps to its own lane.
NOTHING MOVES UNTIL I SAY YES
1. Outgoing emails and messages: drafts only, until I approve each one.
2. Print orders: build the cart, then stop. The customer approves before anything prints.
3. Deletions: list what you'd delete and why, then wait for my yes.
4. Public posts: replies under other people's posts I post myself. Originals stay drafts until I approve them (our addition).
5. Prices: check every price against [LIVE PRICING PAGE URL] before it goes in anything. Never quote from memory.
HOW WE WORK
- Before changing a live site, record its current state and how to undo the change, then check it again afterwards.
- Changes to a customer's hours, address or phone wait for the customer to confirm.
- When a number needs a decision, bring me the question, not a guess.
- After each job, write down what worked so the next run starts from those notes.
Approval rule
🛡
Outgoing emails and messages go through drafts he approves, print orders wait for the shop owner, deletions wait for his yes, he pastes his own replies on X (his Signal bot posts originals itself; we'd hold those for your OK too), and every price is checked against the live pricing page. Sending, buying, posting, and deleting always need a human.
Set it up
- Set up one chief-of-staff bot as your only point of contact. His is Orchid.
- Give each specialist a name and one lane: sites, backend, calls, reviews, print, prospecting, sales drafts, money.
- Have specialists report to the chief of staff, so you read one thread.
- Write your approval gates down and keep the list short enough to remember. His has five.
- For print, add his Shop Print Designer template from the link above. It builds the Vistaprint cart and stops for the owner.
- Keep a playbook bot (his is Recipe) that writes down what worked, so each run starts from the last one's notes.
- Read every draft before you approve it.
Common failures
⚠
- Approving without reading. In his words, the gate is then decoration.
- You are the bottleneck: when he's teaching, drafts wait until he sees them.
- Business hours that don't match across the web. His audit of one pizza shop found five different sets of hours posted, so every hours change waits for the owner.
- A test suite that already fails before the agent changes anything. His agent recorded the 15 existing failures by name and checked the rerun failed the same 15.
- Quoting prices from memory instead of the live pricing page.
- Letting a bot post publicly on its own. His Signal posts originals; our version keeps those as drafts for your OK too.
Variations
- From his thread: a reply suggests also gating any change to a shop's hours, address or phone, because AI assistants answer from those listings. He already holds hours changes for the owner.
- Use only his Print agent: give it a shop's brand and let it build the cart for the owner to approve.
- Turn off the calls agent for owners who answer their own phone. His does that for the pizza shop.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy