Oct 21–22.

Mono, my Telegram bot on Cloudflare Workers, had been live for one day. Before I let it run alone, it got a hardening pass. 9 fixes, each one a real way it could go wrong:

→ Sending the same email twice. Fix: every task is claimed before it runs.

→ Emailing a dead inbox. Fix: check the mail servers first. A hard bounce or a spam complaint (Resend webhook) blocks that address for good.

→ Missing a reply because a co-founder answered, not the owner. Fix: anyone at the business counts. Auto-replies don't.

→ Gemini busy at briefing time. Fix: back off and retry instead of dropping the lead.

Then the part that still feels like cheating: a "Build it" button. A client brief comes in, I tap it on my phone, and a Claude Code cloud session builds the whole site, laptop on or off. Capped at 2 builds a day.

The brief itself became a first call, not a form. "It should be so good that the client doesn't miss the authenticity of an online meeting." Each chapter opens in my words, with a real colour picker (hue strip, eyedropper) and a live sketch of their site that changes as they answer.

I also pulled every price tier off my site that week. A tier column tells people I'd build a worse site for less.

And NEXUS was in its last stretch. The callout arrows pointed at the wrong features again, so I sent the edit back, and pitched the idea that made the film: every technology we mention pops out of our model as a hologram over a blurred city.

Automation isn't the bot. It's the list of ways it can fail, and a fix for each one.

buildinpublic #cloudflare #automation #ai #webdesign

From the build journal of abdulwasaylodhi.com.