I Gave an AI Agent Full Access to My Infrastructure. Here's What Happened in 2 Hours.

How Clawdbot turned my 10-domain email nightmare into a unified system — while I was on a phone call.

---

The Problem Nobody Talks About

I'm building a portfolio of AI-powered micro-businesses. Solo. No team, no freelancers, no VA.

Right now I have 10 products, each with its own domain:

• AImpactScanner.com
• PlebTest.com
• ModelOptix.com
• LLMtxtMastery.com
• SoloMarket.work
• FreeCalcHub.com
• Agent-11.com
• Evolve-7.com
• JamieWatters.work
• AIsearchmastery.com

Here's what nobody tells you about running multiple products solo: the admin work scales linearly, but you don't.

Every domain needs email. Every email needs DNS records — MX, SPF, DKIM, TXT verification. Every domain has a different registrar, different DNS provider, different setup process.

Setting all this up manually? That's an afternoon of clicking through admin panels, copying DNS records, waiting for propagation, troubleshooting typos. Per domain.

I had 10 domains with no professional email. Customers hitting "reply" on support emails would get a bounce. Not exactly the vibe when you're trying to build trust.

Enter Clawdbot

Clawdbot is an open-source AI agent framework that runs on your own infrastructure. Think of it as giving Claude (or any LLM) a body — it can browse the web, run commands, manage files, control APIs, and talk to you through Telegram, WhatsApp, Discord, or Signal.

It's not a chatbot. It's a digital coworker that lives on your server 24/7.

I named mine Marvin. He has access to my:

• AWS server (where he lives)
• Netlify API (where my DNS lives)
• A headless Chrome browser (for admin panels)
• Telegram (how we communicate)

What Actually Happened

I messaged Marvin on Telegram: "I need professional email set up for all my domains through Google Workspace."

Then I got on a phone call.

Here's what Marvin did while I was talking:

1. Audited the DNS landscape

He checked every domain's nameservers, identified which were on Netlify (API-accessible) vs. Namecheap (manual), and formed a plan.

2. Added MX records via API

For each domain on Netlify DNS, he made API calls to add all 5 Google Workspace MX records:

ASPMX.L.GOOGLE.COM (Priority 1)
ALT1.ASPMX.L.GOOGLE.COM (Priority 5)
ALT2.ASPMX.L.GOOGLE.COM (Priority 5)
ALT3.ASPMX.L.GOOGLE.COM (Priority 10)
ALT4.ASPMX.L.GOOGLE.COM (Priority 10)

Plus SPF records for email authentication:

v=spf1 include:_spf.google.com ~all

3. Navigated Google Workspace Admin

Using a headless browser, Marvin logged into Google Workspace Admin Console, added each domain as a user alias, went through the verification flow, grabbed the verification TXT records, added them to DNS via API, and confirmed verification — for each domain, automatically.

4. Handled the curveballs

• Three domains were on Namecheap DNS (not Netlify). Marvin identified the issue, told me to switch nameservers, created the Netlify DNS zones, and noted that each zone gets different nameserver assignments.
• One domain (solomarket.work) was stuck — claimed by an old expired Google account. Marvin found Google's domain recovery tool, walked through the process, and added the DNS verification records for the recovery request.
• The browser session kept expiring. Marvin re-authenticated and picked up where he left off.

5. Set up DKIM and scheduled follow-ups

He started DKIM authentication for email deliverability, and set a reminder to check back in 24 hours (Google requires a waiting period for new domains).

The Results

What	Before	After
Domains with email	1	10
DNS records added	0	70+
Time I spent	~15 min of messages	While on a phone call
Google verifications	0	9 completed
Cost	$0 extra	Already paying for Workspace

9 domains verified and Gmail-active in a single session. DNS records, SPF, verification TXT records — all done.

Why This Matters for Solopreneurs

This isn't about email. Email is just the example.

As a solopreneur, your biggest bottleneck isn't ideas or even building — it's the thousand small tasks that eat your day. DNS records. Deployment configs. Certificate renewals. Monitoring. Documentation updates.

Each one takes 15-30 minutes. Each one requires context-switching. Each one breaks your flow.

An AI agent that lives on your server, has API access, can browse admin panels, and talks to you on Telegram? That's not a fancy chatbot. That's operational leverage.

Here's what Marvin does that a regular AI assistant can't:

• Persists — He's always running, always available
• Acts — He doesn't just suggest, he executes (with my permission for anything external)
• Remembers — He maintains memory files across sessions
• Uses tools — Browser automation, API calls, shell commands, DNS management
• Follows up — He sets his own reminders and checks back

What's Next

This is the first post in a series about building a solopreneur business with an AI agent as your only teammate.

Coming up next: How to Set Up Your Own AI Agent on AWS for Free — step-by-step guide to getting Clawdbot running on the AWS free tier.

After that:

• How we built and deployed a product in a weekend
• The AI agent's daily routine (heartbeats, proactive checks, memory management)
• When AI agents fail (and what to do about it)

If you're a solo founder drowning in operational work, Clawdbot might be the teammate you didn't know you needed.

---

I'm Jamie Watters. I'm building a portfolio of 50+ AI-powered micro-businesses by 2030, solo, in public. Follow along at jamiewatters.work.

Marvin is powered by Clawdbot — open source, self-hosted, and free to use.

---

P.S. In the spirit of full transparency: Marvin drafted this post too. I told him what happened (he already knew — he was there), described the angle I wanted, and he wrote it. I reviewed, tweaked, and hit publish. That's the whole point — this is what working with an AI agent actually looks like. Not perfect, not magic, but genuinely useful. 🧠