AI Coach & Strategist · Chief A.I., Oh!
Most teams are paying six figures for what one operator with the right setup can run alone. I'm that operator. I document the builds out loud so other non-technical people can copy what works and skip what doesn't.
Brad Weaver. AI Coach & Strategist under Chief A.I., Oh!
I help non-technical operators run AI like a senior teammate. Coaching, strategy, and the occasional free build that becomes content. The thesis is simple: leverage beats credentials when the scaffolding is right.
I run a commercial insurance book on the side. That book is the proving ground for every system you'll read about here. When something works in the wild on real revenue, it shows up in the writing.
No insurance content lives here. Insurance is the engine, not the brand.
01 · Proof of work
A brand is cheap. The thing it points at is what matters. Below is what's live in the lab right now, with commits and code paths I can show on demand.
First-party Model Context Protocol server. Tool catalog covers prospects, pipeline, enrichment, outreach, niches, campaigns, workflows, and discovery. Chat-driven UI on top, tool-use loop with an audit log behind it.
Source → enrich → synthesize → approve → send → triage → prep → win → renew. End-to-end test prospect passes 22 of 22 assertions. Every stage has a wired contract, not a pitch deck.
Real multifamily operator pulled in. 14-property portfolio enriched across three states. Principals discovered via three sources (team page, Form D, web/press). Draft opened with the right person's first name and the right portfolio specifics.
Shared data brain across the system. ~25 integrations wired in (SEC EDGAR, OSHA, FEMA, USGS, NOAA, Apollo, geocode, podcast indexes, Instantly, and a stack of others). Skills as a goal-directed planner, not a linear workflow.
02 · Open notebooks
These are working notebooks, not products. Each one is a snapshot of a thesis I worked out and wrote down so the next non-technical operator doesn't have to start from scratch.
From "what is AI" to confident with ChatGPT, Claude, and Gemini. Five tiers. No prerequisites. The piece I wish existed when I started.
● LiveBuild, lead, and scale AI agents and agentic teams. The same playbook senior engineers use, written for operators who don't write code.
● LiveA constrained agent that builds Claude Code projects from a curated blueprint library. Paused as a product so I could focus on coaching, but the engine still runs.
◐ Paused, archivedHow this whole thing is supposed to sound. Source palette, typography, voice rules. Useful if you write copy for me or with me.
● Live03 · House rules
If we work together, these are the principles I'll show up with. They're the ones I hold myself to first.
I walk alongside the work. I am not selling certainty. I am selling competence at navigating uncertainty.
Nothing public until the system that's being talked about actually runs. If I'm writing about it, you can look at the code or the result.
Most teams over-tool. Pick the smallest piece that solves the problem. Add complexity only when the simple version breaks for real reasons, not theoretical ones.
Agents stay gated by a human until they earn the gate off. The number is 30+ correct human-reviewed runs in a category before the gate even moves.
If a concept needs three acronyms to explain, the concept is wrong or the explanation is. I rewrite until a non-technical reader gets it on the first pass.
04 · Get in touch
I take on a small number of coaching and strategy engagements with small and mid-sized businesses that want to run AI seriously. I also do the occasional free build for the right problem because the writeup becomes content. Either way, start with a paragraph about what you're trying to do.
Tell me what you're trying to do, what you've already tried, and what would change if it worked. The more concrete, the faster I can tell you whether I can help.