afmp94
THE EXPERIMENT LOG

What happens when one person + AI tries to build real companies.

Documenting the wins and the lessons. Building in public, one entry at a time.

FILED · 2026 – May
2026
Ongoing

Brainz Advisory · first external proposal

Six artifacts drafted overnight for a partner pipeline. One-pager, pitch deck, landing, SOW, cover email, index. Going to market via external partners on commission — testing the indirect sales motion before doing it ourselves.

FILED · 2026 – April
2026
Complete

Turnaround as COO · 15 days

Walked into a struggling company as COO. Restructured the org and the burn back toward health, then built an internal product end-to-end with SPARC methodology + Claude. Transitioned to Head of Innovation.

FILED · 2025 – Oct
2025
Complete

Brainz Lab · service backbone deployed

Services live across Mac Studio + DigitalOcean managed databases. The infrastructure everything else inside Brainz now runs on. Internal-first; productized one piece at a time.

FILED · 2025
2025
Complete

LexPro · built 100% with Claude

Shipped a complete legal management product with Claude doing all the code generation. Rails, Hotwire, Tailwind. 16 users on the free tier. The firms themselves priced it 10× our planned price.

FILED · 2025
2025
Complete

Amplifica · live with paying tiers

AI virality scorer + design generator. Daniela runs day-to-day. Nexus (the AI seller) runs outbound. Paying tiers from $150/mo; two pieces free.

FILED · 2025
2025
Ongoing

The holding takes shape

Left full-time employment. Founded Brainz LLC. The hypothesis: one founder + a real team + AI can ship more than a traditional team. Six months in, the answer is leaning yes.

THE NUMBERS · SO FAR
~18 mo
Since founding Brainz
Dec 2024 — present
5
Active products in flight
Amplifica, Lumina, LexPro, Brainz Lab, Advisory
100%
AI-assisted code
Every line read by a human (me)
№ VI · WHAT I'M LEARNING

Four lessons.

  1. № 01

    Claude is a developer, not a copilot.

    Claude doesn't need me to write code. It needs me to make decisions: what to build, how to architect it, which tradeoffs to accept.

  2. № 02

    Code generation was never the bottleneck.

    Everyone can write code. The hard part is deciding what to build and why. Claude takes the former off my plate so I can focus on the latter.

  3. № 03

    Quality matters from day one.

    There's no room for "we'll refactor later." Every generated line needs to be production-ready. Forces better architecture thinking upfront.

  4. № 04

    Shipping is the real skill.

    Building is the easy part now. Getting users, iterating on feedback, handling support — that's where the actual work is.

WHAT'S NEXT

If this works, it changes everything.

Scaling each product. Closing the first Advisory deal. Watching whether the holding model holds up under load.