For agencies

Orchestrate every platform your clients build on. Get locked into none.

The management layer for AI-powered websites keeps you the partner after handoff: the client’s team approves, the record stays, you stay in the loop.

BYOAbring your own agent

Every platform now wants to be the agentic operating environment for your clients. And each one wants you inside its walls.

Your clients build on Webflow, WordPress, Wix, Squarespace, Framer, HubSpot CMS, and custom code, and they always will. Your value was never one platform. It is knowing which one is right for which client, and running all of them well.

Move a client off the platform when it is holding them back. Keep them where it is not. Govern every code-first site from one place. One layer above them all.

Dispatch · the management layer, above every executor

  • Webflow
  • WordPress
  • Wix
  • Squarespace
  • Framer
  • HubSpot CMS
  • Custom code

Where your clients build today. The judgment about which is right for whom stays yours.

Three jobs, one operating model

Take on the work you used to turn away.

Each of these used to need a developer on retainer or a platform the client did not want. With the governed loop underneath, every one of them is an engagement you can price and run.

01

Migrate a client off the CMS ceiling, governed from day one

When a client has outgrown what their platform exposes, rebuild the site as real code on a modern framework and connect Dispatch before the first agent commit. The repository, the deploy webhook, and a scored baseline of every page are on the record before the migration starts, so the client watches the rebuild happen as governed requests with previews, not as a black box that ends in a cutover.

The Dispatch activity feed on the first day of a client migration: repository connected, deploy webhook armed, pages scored, and the first governed request at preview.

Client site A / Activity

Migration day one. Webflow export in hand, code repository live.

Astro on Netlify
  1. Repository connected

    client-site/www on GitHub, default branch main

    Validated9:02 AM
  2. Deploy webhook armed

    Netlify production and preview deploys now land in this feed

    Armed9:04 AM
  3. Pages synced and scored

    47 routes inventoried from the sitemap, AEO score on each

    Baseline9:11 AM
  4. Preview ready on req-1a4f: rebuild /services as Astro

    Claude Code pushed 3 commits to dispatch/req-1a4f, PR #2 linked

    Awaiting approval11:36 AM

02

Run AI agents on a client's existing code site

Plenty of clients already have a site in a repository and a developer who left. Connect it, sync the pages, and the scheduled crawl starts finding what slipped and drafting the fix. Your team runs the agent; the client's approver reviews the preview. You take on the retainer you used to decline because there was no safe way to touch the site.

An Inbox finding on a client’s existing code site, with the drafted fix and the Draft fix control.

Client site B / Inbox

Next.js on VercelConnected today

Findings with a drafted fix ready

MediumCheck failing

Structured data missing on /pricing

/pricing · seen 40m ago

Add Product and Offer structured data to /pricing as JSON-LD, matching the plans and prices already on the page. Do not change visible content. Keep the existing canonical and meta tags.

Draft fixDismiss
Open page

Draft fix files the request, generates the handoff prompt with the page’s files and the client’s approved context, and waits for whichever agent the team uses.

03

Govern many client sites from one Inbox

Every governed site reports into one Inbox, grouped by client: approvals waiting, findings with a drafted fix, pages that slipped since the last crawl. Risk tiers, approvers, crawl cadence, and auto-approve are set per site, so a cautious client and a fast-moving one run side by side under one operating rhythm.

The Dispatch Inbox for an agency, grouped by client site, with approvals, findings, and slipped pages waiting.

Inbox

4 items need you across 3 sites · 2 in progress

Last crawl: all sites today

Client site A · Astro on Netlify

1
  • Awaiting approvalStandard risk · preview ready 2h ago

    req-1a4f: rebuild /services as Astro

    Review preview

Client site B · Next.js on Vercel

2
  • MediumFinding · drafted fix ready

    Structured data missing on /pricing

    Draft fixDismiss
  • HighHigh risk · 1 of 2 approvals · needs a second approver

    req-9e02: update the fee schedule on /pricing

    Approve

Client site C · Astro on Cloudflare

1
  • 91 to 77Slipped page · crawled 1d ago

    /blog/annual-report slipped since last crawl

    Draft fixDismiss

Turn your playbook into a product.

Onboard, configure, hand off. The same three phases on every client site, written down so the record survives the engagement. The client’s team lands on the Inbox and approves; you stay on as the operator or the advisor, whichever the retainer says.

  1. 01

    Onboard

    Connect the client's repository and host, arm the webhooks, sync the pages for a first score on every route, and add the Slack channel their approvers already read.

    • Repository
    • Host
    • Webhooks
    • Page sync
    • Slack
  2. 02

    Configure

    Write the client's judgment into the system so the agent, the approvals, and the crawl behave the way the client would.

    • Approved context
    • Risk tiers
    • Second approver
    • Crawl cadence
    • Low-risk auto-approve
  3. 03

    Hand off

    Transfer ownership, rotate every token to ones the client owns, confirm the alerts land, walk the Inbox together, and leave the playbook in their context library with the site-specific decisions filled in.

    • Owner role
    • Token rotation
    • Alerts confirmed
    • Inbox walkthrough

The full playbook covers what to collect before you start, the first governed request done together, the handoff checklist, and the fifteen-minute weekly rhythm the client runs afterward.

Read the handoff playbook

Stay the partner after handoff.

Platform vendors would like the relationship to end when the site goes live inside their walls. With the management layer above the site, handoff is where your value becomes visible. Here is what you keep.

  • The record

    Who asked, what context governed it, who approved, what shipped, how long it took. Every client review is a report, not a reconstruction.

  • Restore

    Any owner or admin can put the site back to any prior version in one click, history preserved. Autonomy is safe because it is reversible.

  • Any agent, yours or theirsBYOAbring your own agent

    Dispatch is agent-agnostic. Your team works in the coding agent it is fastest in; the client's team can use a different one; the handoff prompt, the preview, and the approval are the same.

  • Alerts that carry the draft

    Slack and email say what changed, which page, how risky, and the next step. You stay in the loop on every client site without a seat in every meeting.

  • A relationship that outlasts any platform

    Hosts, frameworks, and agents are swappable parts. The governance layer, and the agency that set it up, travel with the site.

A Dispatch approval alert as it appears in Slack.
# website-approvals· today

Dispatch APP 9:14 AM

Preview ready for review on yourcompany.com

req-3f9a12c4: Add a meta description to /about

By Dispatch (drafted from a finding)

Next step: Review the preview and approve or send back

Page: /about  ·  Low risk

The request: Add a meta description to /about (currently missing). Summarize the page in 140 to 160 characters, lead with the primary keyword, and make it a complete sentence. Do not change any other metadata.

Open previewReview in Dispatch

The alert as it lands in the client’s channel. You are in the channel too.

You do not resell hosting, a CMS, or seats. You sell judgment.

The client already owns the tools: the agent, the repository, the host, the framework. You bring the judgment about which platform fits, the migration when it is time, and the governance that lets their team approve AI work without a developer queue. Dispatch is priced by governed websites, and the governed loop is free on the first one, so the safety net is never the line item.

Free

$0

1 governed website

Starter

$29/mo

Up to 3 governed websites

Team

$99/mo

Up to 10 governed websites

Agency plans

Custom

Unlimited governed websites for client portfolios.

Talk to us

Monthly prices; annual billing is lower. See the full pricing page

Agency questions, answered.

Quick answers on running a website that AI agents build and your team governs. More in the Knowledge Center.

  • Not all of them, and not on day one. Dispatch governs websites that live as code in a GitHub repository and deploy through Vercel, Netlify, or Cloudflare. A client whose site fits comfortably inside Webflow, WordPress, Wix, Squarespace, Framer, or HubSpot CMS can stay there; the agency's judgment about which clients have hit the platform ceiling is the point. When a client is ready to move, the migration itself runs as governed work, so the record starts with the first commit rather than after cutover.

Be the AI web partner your clients are asking for.

Every platform. One layer. The client’s team in control, and you still in the loop.

Governed migrations, agents on existing sites, and the multi-site Inbox are all in production today. Read the changelog