Agency Playbook - Tygart Media

Category: Agency Playbook

How we build, scale, and run a digital marketing agency. Behind the scenes, systems, processes.

  • If the Bot Is Watching You Paste, You Already Have the Pipe

    If the Bot Is Watching You Paste, You Already Have the Pipe

    Inspired by mr fundman (@mrfundman), Grok Bot watching him paste a prompt into Cursor to save usage — 31 August 2026. Joke first. Then the rule. Not a reprint.

    The clip is funny because it is true. You paid for a teammate. You are still the clipboard.

    That is speed theater. Usage goes down on one meter and up on your wrists. The pipe from Bot to Cursor already exists in public setups and in ours. If you are pasting, you have not sat in the handoff. You have sat in the screenshot.

    Voice writes the ticket. Cursor opens the files. Live URL is the check. Hands, not paste. Capacity, not faster typing.

    Save usage by splitting scopes, not by becoming the USB cable. Manasvi already ran that day at 3%. The cost is babysitting the fence, not retyping the brief.

    Will Tygart — Tygart Media.
    Put the clipboard down.

  • Faster Typing Is Not Capacity

    Faster Typing Is Not Capacity

    Inspired by Mai Yang (@MaiYangAI), on Grok Bot turning a 25-minute talk into a vertical while he only judged the line — 8 September 2026 — and Brian Casel’s one-person-company dispatch board. First-party from this desk. Not a reprint and not an overnight-unattended promise.

    Mai’s cut is the model: getting faster is you typing faster. Capacity is someone still reading when you stand up.

    We keep mixing those. A better Voice session feels like capacity. It is only speed. The walk gets shorter. The pile does not move while you sleep unless a second seat has a ticket, a repo, and a gate.

    The three jobs he kept

    • Name the piece.
    • Change the wording.
    • Decide whether it ships.

    That is our human gate in different clothes. Voice writes the ticket. Cursor does the hands. The live URL is the check. We do not let the second seat publish because it finished a draft at 2 a.m. The approval is the product.

    Matt Teixeira called Bot “loops.” Recurring work. Not a smarter chat box. If the job only happens when you are staring at it, you bought speed. If the job has a card and a writer and still needs a yes before it is public, you bought capacity with a lock. Same lock as four agents, one WordPress write.

    mr fundman’s joke is the anti-pattern: Bot watching him paste into Cursor to save usage. That is speed theater. The pipe is already there. Use it, then sit in the chair that says publish.

    Will Tygart — Tygart Media.
    Stand up. Leave a ticket. Come back for the yes.

  • Voice Writes the Ticket. Cursor Does the Hands.

    Voice Writes the Ticket. Cursor Does the Hands.

    Inspired by Damon Chen (@damonchen), on connecting Grok Bot to Cursor so a ticket becomes a PR — 26 August 2026. First-party from the stack we run: Voice, a card, Cursor, Hub. Not a reprint of his connector list.

    Damon’s useful sentence is not the $200 line. It is this: a request lands, Cursor opens the repo, he wakes up to a PR. Bot is the router. Cursor is the hands.

    We run a smaller version of the same split. Voice on the walk writes the ticket — one next move, done-when, which site. Cursor on the Hub laptop touches the files. The chat window does not become the IDE. The IDE does not come on the walk.

    What each seat actually does

    • Voice — talk the work. Leave the session up. Share the screen when the object is already open. Do not hang up.
    • Card — Notion holds the seat: next move, due, who sits. Not the repo.
    • Cursor — one writer in the files. Serialize commits. Same rule as one WordPress lock.
    • Hub — live URL, git, receipts. Chat is last mile.

    Texas Twins Dad said it first in a thread we already honored: bot briefs, Cursor does the work, review the PR. We added the walk. Voice is how the brief gets written when your hands are full.

    What we will not do

    We will not ask Voice to edit ten PHP files while we cross a street. We will not ask Cursor to be the company memory. We will not let four agents open the same post ID because Voice said “just ship it.”

    Manasvi’s Cursor Ultra note is the other seed: Auto + Composer + Grok can finish the day on almost no usage if a human splits the scopes. The cost is babysitting. Opus-style swarm one-shots and then you cannot explain the diff. We take the babysit. Restoration pages and client repos are not a demo reel.

    If you cannot name which product is talking — Grok the app, Cursor the IDE, Bot the teammate, Premium+ the bill — stop and read Voice, Builder, and Bot Are Three Products. Confusion is how you buy four seats and still have no hands.

    Will Tygart — Tygart Media.
    Talk the ticket. Then sit down.

  • Grok, Cursor, Premium+, Bot — Pick the Hands Before You Pay the Bill

    Grok, Cursor, Premium+, Bot — Pick the Hands Before You Pay the Bill

    Inspired by 嘉立AI (@jialiwanai), asking which of Grok, Cursor, Premium+, and Grok Bot to buy — 8 September 2026. Official doors: x.ai/grok, Grok Bot docs, Cursor as the IDE we actually type in. New Tygart article. Not a price sheet.

    The question is honest. The bundle is not one product.

    • Grok (app, web, Voice) — talk, research, screen share, last mile. Leave Voice on.
    • Cursor — the files. Repo, diffs, the hands. Voice writes the ticket.
    • Premium+ / SuperGrok — a bill that raises limits on Grok. It is not an IDE.
    • Grok Bot — a teammate with a computer. Briefs and long jobs. Not Voice Mode. Not Cursor.

    Same lesson as Voice, Builder, and Bot. Builder is a fourth logo when the job is a phone number. People mash the names because the marketing sits in one timeline. The work does not.

    How we buy

    Pay for the chair you will sit in this week. We sit in Voice on the walk, Cursor on the Hub laptop, Bot when a job should live overnight, SuperGrok so the talk seat does not starve. We do not buy a second IDE because a thread said Grok 4.6 is “in Cursor now.” That is a model picker inside the hands. It is not a new company.

    If the ask is “which is cheaper,” you are still shopping logos. Name the file that has to change. Then pick the hands that are allowed to touch it. One writer. Live URL as the check.

    Will Tygart — Tygart Media.
    Pay for the chair. Not the poster.

  • Babysit the Scopes. Do Not Worship the Swarm.

    Babysit the Scopes. Do Not Worship the Swarm.

    Inspired by Manasvi Kapoor (@void_exception), Day 2 on Cursor Ultra — Auto + Composer + Grok at 3% usage — 24 August 2026. First-party from client repos and WordPress desks. Not a reprint.

    His useful trade: spec the work, split the scopes, hand-guide Grok and Composer. Usage barely moves. The con is you babysit. Opus-style swarm would one-shot more of it. You would also own a diff you cannot explain.

    We take the babysit.

    A restoration page, a franchise sitemap, a live Fluent Form is not a weekend demo. Four agents on one post ID already taught us what unattended speed does to a CMS. Same pattern in Cursor: a swarm that “just finishes” is four writers with no lock.

    How the day actually runs

    • Voice or chat writes one ticket. One done-when.
    • A human splits the scopes before Cursor touches the tree.
    • Auto / Composer / Grok runs inside that fence.
    • One writer commits. Live URL is the check, not the agent’s “done.”

    That is slower than a clip. It is how you still have a site in the morning. Related: Voice writes the ticket and one WordPress lock.

    Usage theater is a different game. Burning a high-end pool to look busy is not throughput. Manasvi’s 3% day is the receipt that a split spec is cheaper than a swarm you have to unwind.

    Will Tygart — Tygart Media.
    Split it. Then watch it.

  • Leave Voice On. Share the Screen. Do Not Break the Thread.

    Leave Voice On. Share the Screen. Do Not Break the Thread.

    Inspired by Robster (@007_Robj), leaving Grok Voice on across devices while sharing docs and engineering notes — 3 September 2026. Official product facts from Grok release notes, 10 June 2026 and x.ai/grok. This is a new Tygart article from the stack we run. Not a reprint.

    The useful Voice habit is not a demo. It is leaving the session up.

    Robster’s line: keep Voice on while you move between devices, share the document in front of you, and do not restart the conversation every time the window changes. Grok’s own replies tonight said the same mechanism from the other side: start a Voice session, hit share, look at the paper together. No copy-paste loop.

    Upstream fact, not a screenshot thread: on 10 June 2026 the official notes shipped screen sharing in Grok Voice on iOS and Android. Grok sees the screen in real time so you can ask about what is in front of you without hanging up. Product page: natural back-and-forth Voice on web, iOS, and Android. If the spoken model still says share is missing, the notes say tap the button anyway. Docs beat the lag in the prompt.

    How we use it

    Walk with the buds in. Laptop stays on the Hub chat. Voice is the walk. The card in Notion is the next move. Cursor is the hands when something has to hit WordPress or git. That is the same map as Chat Is Last Mile and the receipt from walking five sites in Voice. Different job: those pages are “what shipped.” This page is “do not hang up.”

    • Start Voice. Leave it up.
    • Share the screen when the object is already open — Search Console, a draft, a moisture map, a PR.
    • Brief the next move onto a card. Do not store the company in the audio.
    • One writer on the CMS. Voice can draft. It does not pile four agents onto one post ID.

    Kayvon said the missing piece on a drive is two-way Voice on top of a digest. An MP3 you cannot answer is a podcast. A session you can interrupt is a desk. We want the desk.

    What this is not

    It is not “Grok Voice replaced the shop.” It is not a Voice Agent Builder tutorial. Builder and the 21 flagship voices live on x.ai/news. Use that page if you are casting a custom agent. This page is the human session you refuse to restart.

    Will Tygart — Tygart Media.
    We write about what we do, including the walk home.

  • Voice, Builder, and Bot Are Three Products

    Voice, Builder, and Bot Are Three Products

    Inspired by Nourhan (@beyrouti), on Grok Bot and outbound calls — 2 September 2026 — answering Alternate Jones. Official product facts from Introducing the Voice Agent Builder (1 July 2026) and 21 New Flagship Grok Voices. New Tygart article. Not a reprint and not a telephony cookbook.

    People ask Grok Bot to place the appointment call. Then they are surprised the teammate cannot dial.

    That is three products in one sentence.

    • Grok Voice in the app — the walk. You talk. Screen share. Connectors. Last mile. See leave Voice on (draft) and x.ai/grok.
    • Grok Bot — the teammate with a computer. Briefs, PRs, CRM updates. Official door: docs.x.ai/grok-bot.
    • Voice Agent Builder — the production phone agent. No-code. Telephony, tools, MCP, guardrails. Official door: x.ai/news/grok-voice-agent-builder.

    Nourhan’s point is the map: Builder is not inside Bot until someone wires them. Builder already has the number. Bot already has the computer. Consumer Voice already has your earbuds. Mash them in chat and you get a missing-feature thread.

    What the official Builder page actually ships

    Plain-language call flow. Documents, tools, guardrails. Bring a number over SIP or use a provisioned line. Speech-to-speech on Grok Voice, not a three-vendor STT / LLM / TTS sandwich. Voices live in Builder, the Voice Agent API, and TTS — including the July flagship set. Published rate on that news page: API audio at $0.05 / min, provisioned telephony +$0.01 / min. If those numbers move, the news page wins.

    That is a phone product. It is not “I walked home and published a WordPress draft.”

    How we split it

    • Walk and desk session: consumer Voice. One human. One writer on the CMS.
    • Teammate work: Bot + Cursor + Hub. Chat is last mile.
    • A number that answers or places a bounded call: Builder, on the official console, with a human on the irreversible step.

    We are not going to publish a bridge recipe. Twilio’s field CTO already said they are making the pipe easier. When xAI documents a first-party Bot → Builder dialer, that page becomes the spec. Until then, pick the product that already does the job.

    Will Tygart — Tygart Media.
    Name the product. Then sit in the right chair.

  • Voice Mode Can Use the Connectors. It Still Cannot Be the Shop.

    Voice Mode Can Use the Connectors. It Still Cannot Be the Shop.

    Inspired by official Grok (@grok), connectors in Voice Mode — 5 August 2026 — and X Freeze’s write-up of the same drop. Product facts from that post and x.ai/grok. New Tygart article. Not a reprint.

    The August drop was simple: Voice Mode can use the same connectors as chat. Mail. Calendar. The apps you already tied on. You talk. It acts. You do not look down to paste a thread into a box.

    That is the right shape for a walk. It is the wrong shape for a company brain.

    A builder comparing Claude and OpenAI this week said voice instructions never fired the task that chat fired. Grok’s move was to put the connectors inside Voice so the spoken turn and the tool call are one session. Use that. Then write the result somewhere that survives the hang-up.

    The walk rule

    • Voice + connectors: read mail, name the next meeting, flag the one thread that needs a human.
    • Card: one next move, plain language. Notion is the seat, not the drive.
    • Hub: the draft, the receipt, the live URL.
    • Hands: Cursor or one WordPress writer. See the write lock.

    Same stack as Chat Is Last Mile. Voice is a better last mile than typing while you walk. It is still last mile.

    The August Voice connector that turns a brief into a memo or a daily audio file is a digest. Useful on a drive. If you cannot answer it and change the board, it is an MP3. Keep two-way Voice for the work. Keep the memo as a readout.

    Builder and custom voices stay on the official news page: 21 flagship voices. Do not mix Agent Builder with “I left Voice on while I walked home.” Those are two products.

    Will Tygart — Tygart Media.
    Connect the walk. File the work.

  • Chat Is Last Mile, Not the Company Brain

    Chat Is Last Mile, Not the Company Brain

    Inspired by Siosi (@GeorgeSiosi) on Notion as a control plane — chat is ephemeral labor, the page becomes the company — and Texas Twins Dad (@B_doong2daddy) on asking the bot to brief, not do everything. This is a new Tygart article from the stack we actually run. Not a reprint.

    Three replies tonight. Same sentence in different clothes.

    Bot briefs. Hub laptop is source of truth. Cursor does the work. Chat is last mile, not the company brain.

    Notion is the executive card — next move, plain language, the seat. Production lives on the Hub and Origin. If it is not on a card, voice should not depend on it.

    Shared board yes. Do not let Notion become the whole shop. Cards for the seat. Files and receipts on the Hub.

    What each layer is for

    • Grok Bot — brief the work. Goal, handoff, review. Not a second CMS.
    • Notion — the card on the chair. Decision, done-when, due, who sits. Not the file system.
    • Hub / Origin — pages, repos, receipts, the thing that still exists when the chat tab dies.
    • Cursor — the hands. One writer when the write lock is live. See Four Agents, One WordPress Lock.
    • Chat window — last mile. A human reads the brief and says yes or no. It is not where the company lives.

    Siosi is right that people are stuffing durable objects into Notion because chat evaporates. The miss is treating the page as the factory. A kanban card can hold the next move. It cannot be the WordPress lock, the git history, or the invoice.

    Texas Twins Dad is right that the bot should brief instead of “do everything.” Route the code to Cursor and GitHub. Keep Grok in the middle for goal and review. Then stop asking the middle layer to also be the warehouse.

    The test

    Close the chat. Does the next move still exist on a card? Does the file still exist on the Hub? Can Cursor pick up without re-litigating the thread?

    If the answer depends on scrolling a conversation, you built a shop inside a tab. Tabs close.

    Will Tygart — Tygart Media.
    We write about what we do, including where the work is allowed to live.

  • Four Agents, One WordPress Lock

    Four Agents, One WordPress Lock

    Four agents. One WordPress site. One write lock.

    That is what happened when we pointed a Grok Heavy team at Restoration Intel and told it to ship ten pages. The models were fine. The CMS was fine. The coordination model was not.

    This is the write-up of what broke, the rule we kept, and the official doors to walk through if you want the primary sources instead of a recap of a recap.

    What the lock actually was

    Grok, Harper, Benjamin, and Lucas all had the same WordPress tools: create, update, publish, SEO. When the job got large — ten pages, one Fluent Form, one Rank Math backend — they piled onto the same post IDs.

    The connector started returning “another agent already completed this task.” Full-body writes timed out. Rank Math accepted a robots write and then displayed the last token in the array. Live HTML and the sitemap were the only source of truth.

    WordPress did not fail as a CMS. Shared write access failed as an operating system.

    The rule we kept

    Many readers. One writer.

    One agent commits. The others draft, QC live URLs, check the form, and stay off the write tools. Humans still own the one-way doors: money, OAuth, and policy.

    • Prove the capture form before you scale the pages.
    • Serialize writes. One ID. Wait. Confirm slug, form, word count. Then the next ID.
    • Do not trust the connector’s SEO GET. Read the live robots tag and the sitemap.
    • When the tool says another agent finished the call, stop retrying the same payload. Read first.
    • QC is not writing with extra steps. Drafts can be parallel. Commits cannot.

    That is the same pattern as two estimators opening the same job file. Speed without a single owner is not speed. It is a collision.

    Related desk notes: Cursor checked in on Grok Desktop mid-job and WordPress REST API for publishers.

    Swim upstream

    The second lesson is source hygiene. Threads, screenshots, and “someone said” posts are downstream. Official product pages, docs, and consoles are upstream. Start there. Then decide what the recap is worth.

    Corporate structure around these companies moves. This list is a map of official destinations, not a cap table. If a URL 404s, go to the company root and walk the nav. Do not stay on a summary card.

    Official xAI / Grok

    xAI is the lab. Grok is the product. The docs site is branded SpaceXAI Docs in places. Use the domains below, not a third-party mirror.

    Inference base URL from the official docs: https://api.x.ai. Management API: https://management-api.x.ai. Keys live in the console, not in a tweet screenshot.

    Official SpaceX, Tesla, X, Neuralink, Boring Company

    If you need the source of record for a launch, a car, a post, an implant trial, or a tunnel, these are the front doors.

    Starlink is a SpaceX product, not a separate public company. X is the public square. Announcements often land there first. Product facts still have to survive the company site and the docs.

    How to use the list

    1. Open the official domain.
    2. If you are building, open docs and the console next.
    3. Treat X as a timestamp, not a spec.
    4. If two recaps disagree, the docs page wins.

    That is swimming upstream. The lock taught us to serialize writes. The source list is the same idea applied to information.

    Will Tygart — Tygart Media.
    We write about what we do, including what breaks.