I built the site that names the exact agent stack I run.
agenticworkforcecompany.com carries the AI-era side of my story — a portfolio, a CV, and a positioning piece at once. Built end-to-end with Claude Code on Next.js, Vercel, and Cloudflare, it names the real infrastructure I operate on and frames the agentic-workforce offer without hand-waving.
Two stories a generic agency site couldn't hold.
One is the SEO agency. The other is the AI-era operator story.
Holistic SEO (now niched to wellness clinics) is the local-business offer. The second story is multi-agent workflows, an agent fleet across Mac minis, and the infrastructure built during the Dr. Berg engagement.
I needed a dedicated property for that second story — one that could serve as my personal portfolio and CV for senior SEO and AI-operator roles, and as the public face of the agent-systems positioning.
It had to be credible to technical readers — name the actual stack, don’t fake it — and fast to build and update. Building it into WordPress made no sense; I wanted the same modern stack I chose for the agency rebuild.
The positioning was the real work.
I built AWC as a Next.js site and shipped it the same way as the agency rebuild — Claude Code as the build partner, me making every positioning, structure, and design call. Vercel for hosting, Cloudflare for DNS.
The content is deliberately structured as portfolio + CV: a hero with headline proof points, an About that frames the agentic-workflow approach, a projects section (Dr. Berg, HyperWolf, Celebrity Plastic Surgeons), a full reverse-chronological experience section, a skills/certifications block, and an explicit tech-stack section that names the tools I actually deploy on.
AWC presents as “AI operators that own complete workflows,” spun off from the delivery infrastructure built at Holistic SEO, with clear ways to engage — and everything routes to a single Calendly entry.
Credible to technical readers means naming the real stack — OpenClaw, Hermes, Claude Code, Supabase, Vercel — not faking it.
— Positioning principle · stack-honest by designOne shared stack, two properties.
The same JAMstack build — Next.js on Vercel, Cloudflare DNS, directed through Claude Code — produced two coordinated properties: holisticseo.co as the local-business offer, and agenticworkforcecompany.com as the agent-systems offer. AWC adds a portfolio/CV structure and a /cv PDF export.
One shared JAMstack build — Claude Code → Next.js on Vercel, Cloudflare DNS — produced two coordinated properties: holisticseo.co as the local-business offer and agenticworkforcecompany.com as the agent-systems offer. AWC layers on a portfolio/CV structure, a public tech-stack section naming 15+ tools, four headline proof points, and a downloadable /cv PDF. Both route to a single Calendly entry.
Framework & Hosting
Build Tooling
SEO / AEO & Export
Named Agent Runtime
Named Data / Infra
Named Comms
One page, one coherent story.
Verified from the live site and the Apr 2026 Slack rebuild record.
The four proof points that lead the hero: 10+ years SEO, 20 active AI/SEO certifications, $8.86M attributed organic revenue, and +217% organic traffic (Dr. Berg) — surfaced up top, grounded in the flagship engagement.
What shipped — and how it's framed.
The left is what exists and works. The right is the honest boundary, including the career-context caveat that governs reuse for job applications.
A credible, stack-honest portfolio property built solo.
- agenticworkforcecompany.com is live and is Mike’s public portfolio and CV.
- Holds the AI-operator positioning in one coherent place, built on Next.js/Vercel/Cloudflare via Claude Code.
- Names the real agent stack — no faked infrastructure.
- Logged into durable memory on Apr 20 2026 as “the agent-systems offer,” alongside the agency site as “the local-business offer.”
- The team adopted the new stack as canonical.
A positioning property — not a product, with a framing rule.
- This is a positioning and portfolio site, not a product; it’s actively iterated (an “AI OS” control plane is noted as in-progress).
- The verifiable win is that Mike conceived, built, and shipped a credible, stack-honest property himself by directing an AI build tool.
- Client-acquisition results from the site are not claimed.
- Career-context caveat: the live “About” says “I run two ventures.” For full-time job applications, apply the vault framing rules — AWC is framed as a small side project that keeps AI-era skills sharp, and Holistic SEO as founded/ran (past tense). Flag this tension before reusing site copy verbatim.
Next.js, Vercel, Cloudflare, and Claude Code are third-party tools. The work is the site, the positioning, and the direction.
Two offers, cleanly split.
I decided the story and built it.
I owned the concept, the positioning, the structure, the copy, and the stack decision — and directed Claude Code to build it.
I decided what the AWC story was (agentic workflows that own end-to-end operations, spun off from Dr. Berg infrastructure), which proof points led, and how the CV/portfolio was organized. I’m the operator who built and ships it.