SoloClientStack · Proof layer
Building a one-person firm.
With AI. In public.
The central thesis: AI lets one operator perform like a small company. This page tests that in practice — transparently, with real numbers, and without pretending it's simpler than it is.
Current build metrics
What one operator can actually run.
These are real numbers from running SoloClientStack as a one-person operation. Updated as the build evolves.
What these numbers mean: 12 hours of admin per week that would otherwise require a VA or part-time hire is now handled by the AI stack. At $50/hr for a VA, that's ~$2,600/month in avoided labor cost against $340 in software. The efficiency gap is real — but so are the limits below.
What's been tested
Six experiments. Real results.
Each experiment tests a specific claim about AI replacing or augmenting solo operator work.
The honest part
What AI still cannot replace.
This site is not a case for AI replacing operators. It's a case for AI expanding what one operator can do. The distinction matters.
What AI cannot replace
- Judgment — the call only you can make
- Trust — earned over time, not automated in
- Taste — what makes work good, not just done
- Relationships — every referral, connection, and conversation
- Decision authority — accountability for outcomes that matter
Where AI creates real leverage here
- First drafts of anything — content, emails, proposals
- Automation sequences — built once, run forever
- Research synthesis — faster than manual reading
- Formatting and structure — consistent without effort
- Volume — more content, more pages, more coverage
- Speed — ideas to published faster than unassisted
Build stage
Where the build stands now.
✓ Done
Infrastructure layer
Site built, email list connected, lead magnet live, affiliate programs applied and approved, onboarding automation running.
→ In progress
Content layer
Tool reviews, comparisons, and OS pages publishing 2–3x per month. Internal link structure being built. SEO signals accumulating.
○ Next
Playbooks and implementation guides
Detailed implementation playbooks for each OS type. These take real testing time — each one gets built and run before publishing.
○ Later
Operator community
A place for solo operators to share builds, ask questions, and compare stacks. Not launching until content layer is solid.
Follow the build
New experiments publish 2–3 times per month. Subscribe to get them.
- Real experiment results — not theory
- Honest reporting on what didn't work
- Stack updates as tools change
- New OS builds as they launch
- Playbooks when they're ready
Enter your email to follow the build
No spam. Build updates only. Unsubscribe any time.