Building AIM in Public: Why a Solo Operator Is the Point, Not the Apology
Every agency website has a team page. Stock photos, invented job titles, a "we" that means one stressed person and a Fiverr account. This is the post where AIM commits, publicly, to never doing that.
Solo is the model, not the limitation
Ten years ago, one person genuinely couldn't deliver ads, content, automation and analytics well. The tooling didn't exist. In 2026 it does, the same AI leverage AIM sells to clients is what lets one operator run builds that used to need five people.
That's the pitch in a sentence: I don't sell what I haven't installed in my own business first. The automations answering your enquiry, the structured data on this site, the tracking behind the case numbers, all the product, running in production, on the company that sells it.
What solo means for clients, practically
- You talk to the builder. No account manager translating your needs into a Slack channel you'll never see.
- Honest capacity. "Limited slots" on the coaching page isn't scarcity theatre. It's a diary.
- Honest boundaries. Enterprise RAG compliance builds, thousand-SKU e-commerce, crisis PR, not my lane, and you'll be told so with a referral, not a learning-on-your-invoice experiment.
The rules this business runs on
- Numbers over adjectives, and every number gets its "results vary" caveat.
- Clients own everything: accounts, code, workflows, data. Leaving must be easy.
- No invented team, no invented testimonials, no dark patterns. Ever.
- Share the playbooks. The guides give away the method; the paid work is the build.
What gets shared here
Real wins with real numbers (anonymised), experiments that failed and why, revenue milestones when they're interesting, and the occasional unpopular opinion about this industry. The Journey category is the build-log.
If watching someone build a systems company in the open sounds useful, the guides are where the actual playbooks live. And if you want the systems without the DIY. You know where the audit is.