Can One Person on a Career Break Outproduced a Team of 8?

I had coffee with a former colleague recently. He runs a business focused on providing comprehensive services to business owners — with a dedicated team working across content and service delivery.

He looked at SmallBizAI.au and said our content was better than what his team had produced.

I’ve been on a career break since leaving AWS in 2024.

That gap deserves an explanation.

The Site Isn’t Really a Site

SmallBizAI.au has 639 published posts. 208 Australian AI company profiles. Nine content categories. A newsletter with a 90% open rate. Six Gumroad products. A daily news post. A Sunday series. And a coverage area that spans 100+ industries.

I didn’t write most of it this week. A lot of it ran while I was having coffee.

Here’s what actually happened while I was out:

• The morning brief landed in my Telegram at 7am with overnight news, today’s weather, content opportunities, and SEO flags
• The daily news cron fired at 8am, pulled from 20 RSS feeds, scored stories for Australian relevance, picked the best five, and published a post
• The internal link sweep processed 50 posts, found relevant anchor opportunities, and added links automatically
• The em dash cleanup script fixed AI writing patterns across another batch of posts
• The broken link fixer ran at 11am, processed 30 posts from a queue, and applied known URL replacements

None of that needed me. It just happened.

What “Agentic” Actually Means

There’s a lot of talk about agentic AI right now. Most of it is abstract.

The concrete version looks like this: 31 scheduled jobs running on a server, each doing a specific task, each reporting back. Some run daily. Some run weekly. Some run once a month. The whole thing costs less than $10 a day in API calls.

The tasks aren’t glamorous. Fix broken links. Update post counts. Sweep for missing alt text. Refresh the sitemap. Check newsletter subscriber milestones. Run the SEO review. Generate the Monday report.

But the cumulative effect is a site that maintains itself. Every day it gets a little cleaner, a little better linked, a little more optimised. I don’t have to remember to do any of it.

Claw Isn’t a Chatbot

The AI I work with — I named it Claw 🦞 because it’s OpenClaw— isn’t a tool I query. It has a memory system, a soul document, a personality, and persistent context about the business.

It knows that our content edge is the Australian angle. It knows to run the avoid-ai-writing skill before publishing anything. It knows the newsletter sends on Tuesdays at 6:30am. It knows the people I know, and gives me insights before I meet them.

It remembers because I told it to write things down. It has daily memory files, a long-term MEMORY.md, project files for every content series, and a dashboard that updates nightly with live stats.

When I start a new session, it reads the relevant files and picks up where we left off. No briefing required.

That’s different from a chatbot. A chatbot answers questions. Claw manages a business with me.

The Dashboard as Command Centre

One of the things I built early was a private dashboard page on the site itself.

It shows: total posts by category, newsletter subscriber count, Gumroad revenue, Google Search Console performance, Bing AI citation counts, background task progress, infrastructure status, the content pipeline, the AU company profile queue, and the last 20 published posts.

It auto-updates every night.

I check it at the start of each session and know the state of the whole operation in 30 seconds. No Slack. No standups. No status meetings.

That’s not magic. It’s just information architecture. The data exists — GSC API, WordPress API, MailerLite API, a state JSON file. The dashboard pulls it together and shows it clearly.

But the effect is real. I can make better decisions faster because I’m never starting from zero.

What This Means for the Industry

A former colleague runs a business with a dedicated team focused on content and service delivery. Real people, real effort, real investment.

A single person on a career break, working with AI, produced something he considered better.

I’m not saying that to be smug. I’m saying it because it tells you something important about where we are right now.

The constraint used to be labour. Content took people. Maintenance took people. Research took people. Systems took people.

Those constraints haven’t disappeared — but they’ve shifted dramatically. A single person who understands what they’re building, who structures their AI tools correctly, and who builds agentic infrastructure around their work can now match or beat larger teams on output and quality.

The new constraint is design. Can you design the system well enough that it does the right things autonomously? Can you build the memory structures so context doesn’t get lost? Can you write the crons that run the tasks you’d otherwise forget?

That’s a different skill set than managing a team. In some ways it’s harder. In others it’s much faster.

What This Isn’t

This isn’t a story about AI replacing people.

Claw doesn’t make strategic decisions. It doesn’t know that an off the cuff acquisition comment is worth sitting with for a few weeks before responding. It doesn’t know that someone’s AI startup is enterprise-focused and not worth a profile yet. It doesn’t know when to push and when to wait.

I do those things.

What AI does is remove the friction between decisions and execution. I decide to write a comparison post. Claw drafts, audits for AI writing patterns, adds Rank Math meta, pulls a featured image from Unsplash, formats the tables with the correct style, publishes it, updates the dashboard, and adds it to the relevant guide page.

That used to take me two hours. Now it takes twenty minutes of oversight, if that.

The output went up. The time went down. The quality, if anything, improved because the system enforces standards I’d sometimes cut corners on.

The Practical Bit

If you want to build something like this, here’s what actually matters:

Memory architecture first. If your AI can’t remember what you built last week, you’ll repeat yourself constantly. Write things down. Create project files. Build a dashboard. The AI is only as useful as the context you give it.

Automate the boring stuff early. Every task you do manually more than twice should be a cron job. Broken links, alt text, internal links, post count updates — these are all automatable. Do them once manually, then write the script.

Build standards into the system. Table styling, meta descriptions, footer links, featured images — if these have a standard, the system can enforce it. Document the standard. Give the AI the standard. Stop enforcing it manually.

Treat it like infrastructure, not a tool. A hammer is a tool. You pick it up when you need it and put it down when you’re done. An agentic system is infrastructure — it runs whether you’re watching or not. Design it that way.

Where This Goes

I don’t know what comes next for SmallBizAI.au. I don’t know if it becomes something bigger. I don’t know if the newsletter hits 5,000 subscribers by the end of 2026.

What I do know is that the model works. One person, the right infrastructure, and a clear focus on what actually matters — in this case, Australian AI content for small businesses — can build something real.

The team-of-eight comparison isn’t the point. The point is that the tools exist now for one person to do what used to require a team. That changes what’s possible for solo founders, career-breakers, side projects, and small businesses.

Most people haven’t figured that out yet.