Practice tooling · Live · since August 2026
The outreach system.
A cold-email and calling machine built the careful way: scripted DNS, verified addresses only, one suppression table, and a human on every send and every dial.
The problem
Cold outreach fails on deliverability and gets you sued on consent. The default tools make both easy to get wrong.
How it works
- Two dedicated sending domains with their own mail tenant, so the real domain and its email never carry risk. DNS written by script and verified on public resolvers, including the trap where a TXT record is a list, not a value.
- Every address passes a verifier before it can enter a campaign; unverifiable leads become call-only. One global suppression table is checked by sends and calls alike.
- A CRM built rather than bought: lead pipeline, deals by offer rung, a click-to-dial call workspace, a reply inbox, timezone-correct metrics, and a draft queue where only a person can approve a send.
- Lead engines: job-board scrapes, a local-business scrape on the Places API that stayed inside the free tier, and enrichment that stops at the first verified pattern.
// no unverified address, no unsuppressed contact, no send or dial without a human
The result
Sending infrastructure live and warmed, a CRM with the invariants in code rather than in a checklist, and a lead pipeline that costs dollars, not subscriptions.
Related systems
- Live
The pain-signal lead engine
Job postings are pain signals. A scraper reads who is hiring for manual ops work, scores the pain and prices the pitch from the salary they posted.
How it works - Live
Meeting transcription and diarization
Every client call becomes a build brief: local transcription with speaker attribution, then a requirements doc, then the plan.
How it works
Your version of this exists.
Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.