April 1, 2026 · Build log

Opened Claude Code and found a Supabase service key hardcoded as a fallback in 3 Python files inside a client repo. Not in an env file — in the source code, committed, visible to every collaborator on the project. Anyone with read access could upload anything to my Supabase storage. The fix took about 20 minutes: strip the hardcoded values, commit, push. But the key was still in git history. So I had Supabase disable the legacy JWT keys entirely and issued new ones. Then updated ~/.env locally, Vercel env vars, and Modal secrets. One incident, five places to patch. Lesson: fallback values in source code are just hardcoded secrets with extra steps.

While that was in flight, I ran a playbook audit on playbooks.blueprintgtm.com. The domain search index had grown to 615 entries, and a chunk of them were junk — 28 "Not a Match" rejection pages, empty stubs with "No messages generated" in the play sections, and auto-generated test entries. Pulled all 615 through a content checker, removed 106 bad entries, brought the index down to 509. Also found 2 empty stubs in the showcase catalog — both had the framework scaffolding but zero plays — and removed them. Catalog went from 503 to 501.

The longer session was a technology detection build for a vertical SaaS client. The problem: a database of ~32K records had only 6.3% coverage on which technology each account was running. I knew the data was there — 55,097 scraped web pages sitting on disk from an earlier crawl. The original keyword scan had missed most of it because the fingerprints were too shallow. So I wrote enrich_tech_scan_scraped.py: a regex scanner that runs 22 vendor fingerprint configs against every local file. Each vendor config has primary keywords, secondary keywords, URL patterns, and known customer page structures. No API calls, no cost, just pattern matching against what we already had.

The real win came from a different script — an async subdomain prober. One vendor's customer portals all follow a predictable URL pattern — a department identifier as the subdomain. I had a list of ~196K department identifiers. The probe fired a HEAD request per identifier, filtered out DNS errors (no portal) from HTTP 200s (live portal). Ran at 211 requests per second. Result: 705 confirmed portals, up from 6-9 known. That's a 100x increase in coverage for a single vendor, in under an hour of compute time. The regex scan was still running through state directories — I/O bound, reading 55K small JSON files — so I committed all 4 scripts and let it finish overnight.

Next: run the scan to completion, merge all sources, and see what combined coverage looks like across those 32K records.

What Annual Adds

This is what I built today. Annual subscribers run the same tools.

• Every tool I ship. Edge Copilot installs to your Claude Code — talk to all my knowledge, every method, every data source. Current: Edge Copilot, AutoClaygent, Agent 7, Who to Target and What to Say, Blueprint Cloud. Whatever ships next is included.

• All 3 courses: Who to Target and What to Say, Agent 7, AutoClaygent.

• Weekly office hours.

License key hits your email after you upgrade.

→ Start at $50/mo · Go annual — $2,499/yr

April 3, 2026 · Build log

Left Claude Code running and went to the pool. That's the sentence that describes most of April 3.

Before I left, I handed off a clean task: find the updated Blueprint Swarm skill, run the full pipeline, publish the playbooks. No subprocess calls, no Anthropic API — just the Agent tool, the way the swarm is designed to run. The orchestrator picked it up from there.

First thing it did: pull fresh revenue data from the CRM. Prep the full active account base across classification batches. Then run a rule-based pass first to get the playbooks published fast — three playbooks shipped to playbooks.blueprintgtm.com before the AI agents even finished their first wave. That's the lazy phase. Get something out the door while the better work runs in parallel.

The better work: AI agents on the same batches. The comparison was instructive. Rule-based put about a third of the at-risk accounts in the "Engage or Lose" bucket — accounts showing silent disengagement signals. The AI put roughly twice as many there. The rules were miscategorizing those accounts as product issues or payment problems because they pattern-matched on keywords. The AI read the full context and recognized the difference between a keyword and a root cause. The "Engage or Lose" bucket doubled in size. The playbooks got republished with the corrected distribution.

Then the swarm stayed running through the night — hundreds of batches of churned account forensics, five accounts per batch. Peak throughput hit sub-4 minutes per batch. One consistent pattern across the entire run: CRM labels were symptom labels, not root-cause labels. An account tagged "Charges and Fees" turned out to be a bankruptcy. An account tagged "Product" was a sales misrepresentation. An account tagged "Unresponsive" was a ghost that had never activated. The AI flagged the mismatch every time; the rules would have just inherited the bad label.

Next: run the same pass over active accounts and see if the pattern holds.

What Annual Adds

This is what I built today. Annual subscribers run the same tools.

• Every tool I ship. Edge Copilot installs to your Claude Code — talk to all my knowledge, every method, every data source. Current: Edge Copilot, AutoClaygent, Agent 7, Who to Target and What to Say, Blueprint Cloud. Whatever ships next is included.

• All 3 courses: Who to Target and What to Say, Agent 7, AutoClaygent.

• Weekly office hours.

License key hits your email after you upgrade.

→ Start at $50/mo · Go annual — $2,499/yr

April 12, 2026 · Build log

Six research agents before I wrote a single line of code. That's how April 12 started. I wanted to build Edge Copilot — the Claude Code extension annual subscribers get — and I didn't want to architect it wrong. So I ran three explore agents first (Claude Code's hook system, the AutoClaygent auth flow, the existing Substack content setup), then three design-and-critique agents (architecture, GTM engineer persona, CRO buyer persona). Both critique agents independently said the same thing: don't make it "always watching." Make it pull-based — subscribers invoke it when they need it. That shaped everything.

The build itself took one session. I adapted AutoClaygent's license key pattern — same OTE- prefix format, same Supabase lookup — and wired it to a Vercel API with seven routes: register, verify, index, content, feedback, usage, and sync. Type-checked clean on the first pass. Deployed to edge-copilot.blueprintgtm.com. Then the right question came up: how do people actually get their key? The Substack subscriber API has no endpoint to check if a specific email is paid. So I built a Stripe webhook instead — same pattern as AutoClaygent, catches the annual subscription event, generates the key, emails it via Resend. Sent a test email to confirm the flow. The whole thing was live and returning a proper 401 before we hit a DNS snag that resolved itself in under ten minutes once the CNAME pointed at Vercel.

While Edge Copilot was being built, a parallel session published the first On the Edge post — "I Built a Swarm to Read Every Call" about the Blueprint Swarm open-source repo. The Substack MCP tool was silently stripping all inline formatting: bold text passed through as literal asterisks, links rendered as raw text. I dug into the source at post_handler.py and found the bug on line 1289 — _extract_text_from_content() was stripping all marks before handing off to the paragraph builder. The fix: bypass that pipeline entirely and use Post.from_markdown() from the underlying python-substack library, which handles inline formatting correctly. Patched it. Cleared the bytecache. The post went live with working bold, links, and code blocks.

Two more skills shipped before midnight. The Headline Optimizer: four Opus research agents (Cannonball GTM historical data, Substack-specific mechanics, timeless copywriting principles, demand research APIs), then a demand scoring script that runs Serper Autocomplete across 26 alphabetical queries plus Exa Reddit and FindSimilar calls — total cost ~$0.04/run. Ten headline frameworks ranked by B2B relevance, the 33-character Gmail truncation rule baked in, the dual-title system documented. Symlinked and wired into the existing /on-the-edge skill so it auto-runs on every draft. The Image Generation sub-skill came next: Gemini for hero and concept images, HTML-to-Playwright-screenshot for programmatic quote cards, stat cards, and diagrams. Built the Fraunces font setup, watermark compositing, five HTML templates, and three uv run --script Python scripts. First watermarks were invisible against dark backgrounds — the purple "OTE" had a 2.1:1 contrast ratio. Fixed it by generating gold monochrome watermarks from the original brush-stroke asset and bumping opacity to 18%.

The last fix of the day was the ugliest to discover: the Stripe webhook for playbooks.blueprintgtm.com had been failing for three weeks. Twenty-two deliveries, twenty-two failures. The signing secret in Vercel didn't match the endpoint's actual secret in the Stripe dashboard. Pulled the right value, updated the env var, redeployed, verified the endpoint returned the correct error on a malformed test POST. Then added a Vercel cron that runs every 6 hours and checks seven components — Supabase connectivity, Stripe API and webhook config, Anthropic credit balance, stuck jobs, failure rate, and webhook delivery — alerting to #pipeline-alerts in Slack if anything breaks. Next: watch whether the webhook actually catches a live subscription before trusting it.

What Annual Adds

This is what I built today. Annual subscribers run the same tools.

• Every tool I ship. Edge Copilot installs to your Claude Code — talk to all my knowledge, every method, every data source. Current: Edge Copilot, AutoClaygent, Agent 7, Who to Target and What to Say, Blueprint Cloud. Whatever ships next is included.

• All 3 courses: Who to Target and What to Say, Agent 7, AutoClaygent.

• Weekly office hours.

License key hits your email after you upgrade.

→ Start at $50/mo · Go annual — $2,499/yr