Cloudflare keeps eating my GTM stack

I called Cloudflare “disgustingly goated” on Thursday.

The post has now done 207,703 impressions and at least 2,477 saves.

It was basically a list of things Cloudflare can do. It can host websites and apps, send email, show traffic, store data and run jobs on a schedule.

Cloudflare is easily the most agent-native generalist platform I use.

By agent-native, I mean an agent can run almost all of it through Wrangler, Cloudflare's command-line tool.

Scrape, store, run jobs on a schedule, whatever the fuck. Drop Wrangler into Codex or Claude Code and the agent can do the work instead of asking you where to click.

A subdomain is the extra bit before your main domain, like mail.company.com. We use them for outbound email.

• Scrape data - pull the useful information from a public website automatically
• Make email subdomains look real - keep the email records with Cloudflare and put a branded page on each one
• Build something for the campaign - a proposal page, a calculator, an audit or a small free tool

A lot of these subdomains are nothing more than email records that prove you own the domain and can send from it. Visit one and you either hit a dead page or see absolutely fuck all.

Cloudflare gives each subdomain a proper home. The mail records sit with a provider I trust, and I can throw a branded page on top. Now it looks like a real piece of the company instead of something we threw together on Tuesday.

The outbound stays away from the main site, but anyone who visits the sending subdomain still sees the same company.

We already do a version of this with Legion.

waitlist.joinlegion.io is a real page on its own subdomain. When someone joins, a small Cloudflare program called a Worker handles the form. Its database remembers which page or campaign sent them there, and Resend sends the email.

Resend still sends the emails. Rebuilding mass emails, unsubscribe rules and delivery sounds like a terrible weekend.

I keep the signup rules in the Worker. The agent can change who joins, what gets saved or what happens next. Then it shows me the exact lines it touched.

It can test the Worker, publish it through Wrangler and read the error from the same screen when something breaks.

No screenshot tour. No six-month-old Loom where I mumble through a dashboard and hope the button is still in the same place.

That little waitlist flow gives me four checks for any GTM tool I am thinking about buying:

• The agent can see what came in, what was saved and the actual error
• It can change the real rules and publish the fix from the command line
• I can take the signup data with me
• The tool is doing specialist work that would be stupid to rebuild

A dashboard-only automation gives the agent a worse job. It has to open a browser, find the workflow, click through several screens and guess at whatever the dashboard is hiding.

If a button moves, the agent gets stuck on the dashboard before it can fix the real problem.

It is harder for me to review the change too. The rules are spread across visual steps instead of shown as one clear code change.

I am not trying to jam the entire business into Cloudflare. Resend stays because email delivery is hard. Cloudflare keeps the parts that change every week in code the agent can work on directly.

Take one workflow you already run and follow it from the first input to the final action. Find where the decisions and useful data live, then check what the agent can inspect when it fails.

If the agent needs three dashboards and a support ticket to understand a failure, it will not make the work easier.

Where I can help you:

1. YouTube - see the GTM systems and experiments we're running 2. Legion - join the waitlist for the GTM operating system we're launching soon 3. LeadGrow - apply for a free campaign and let us prove the funnel with you

- Mitch

P.S. Something I've been thinking about: Churchill might be the perfect lazy general. He beat Hitler, wrote roughly eight million words and still found time to paint. He conserved his energy without ducking the duty.