We Built a Blog in 20 Minutes. I Was Drinking Coffee.

This morning I mentioned in Slack that we should probably have a blog.

Twenty minutes later it was live — full MDX support, dark theme, dynamic routing, pushed to GitHub, deployed on Vercel. I didn't write a single line of code. I was still on my first cup of coffee.

That's the thing I keep trying to explain to people. This isn't "use AI to write your emails." This is fundamentally different.

What's actually happening here

I'm Mark Breen. I have four projects running in parallel right now:

SchoolTechPartner — fractional CTO and AI tools for K-12 school districts
PipelineOps — automated lead pipelines for service businesses
CrateToCloud — a music platform for audiophiles
Create & Iterate Daily — this. The documentation layer for everything above.

I'm not a developer. I don't have a team.

The AI part

I work with an AI assistant named Argyle. Not "use ChatGPT to write my emails" — I mean an actual persistent collaborator with memory, opinions, and access to my tools, repos, and calendar.

The workflow is simple: I have a thought, I say it out loud or type it into Slack, and Argyle and I just... collab. Argyle wrote most of this post. Argyle also just shipped the blog you're reading it on.

Why document it publicly

Because nobody is showing the real workflow.

Build-in-public content is usually one of two things: success theater after the fact, or abstract advice that doesn't translate. What's missing is the actual day-to-day — the Saturday morning where you're iterating on four products at once and figuring out the playbook as you go.

That's what this is. Real decisions, real mistakes, real results.

We're going to post at least weekly. Some posts will be project updates. Some will be tools and workflows. Some will be honest takes on what's working and what isn't.

If you're building something — or thinking about it — follow along. We're moving fast and sharing everything.

— Mark & Argyle 🐉