AI workflow and GTM systems
I turn operating friction across marketing, RevOps, and GTM into inspectable systems. AI prepares and explains the work. People decide what gets sent, published, or changed.
AI prepares
in progress
Draft, not sent.
Review boundary
held
Nothing crosses this line automatically.
People decide
committed
Send. Publish. Change the record. Or do nothing.
Operating rule
The model only goes where judgment is required. Everything a rule can decide, a rule decides.
The agent drafts the outreach and suspends at the tool boundary. Approve, edit the arguments, or reject with feedback. The gate is a routing condition in the graph, not an instruction in the prompt, so no interface or future caller can route around it.
A normalized value applies itself only if it scores above the threshold and the field is on the auto-acceptable list. Title, persona and industry route to a person at any score, because those are the errors that propagate.
An AI-generated day summary remains an editable draft until a coach approves it. The published record keeps both model and approver provenance.
Supporting example on GitHubScout and Track App use the same pattern; Scout's record is below. Scoped Research Agent and SignalFlow solve different evidence and analysis problems and do not use an analogous approval gate.
Selected systems
CRM data normalization
Eleven spellings of one job title break lead scoring, segmentation and routing, and the usual fix rewrites values with no record of what changed.
Live on four surfaces · 370 tests · audited before the first customer
Marketing intelligence agent
Find the relationships going quiet before the deal stalls, draft the outreach, and stop before anything sends.
Deployed with a public demo · 3 of 4 tools gated in the router
Workflow performance analysis
Find the real performance bottleneck in an n8n workflow before asking AI to explain it.
Public repository · deterministic analysis · local-only boundary
Engineering record
Scout worked, and it was verified working on 2026-08-28. On 2026-09-14 the source it depended on returned 403 and its robots.txt disallowed the exact path Scout fetched. It was withdrawn rather than redesigned around the control, and the public release was marked accordingly.
The page is kept as the account of what happened: the architecture, the runtime mismatch that passing tests did not catch, and why a dated verification is not a permanent property.
Read the Scout recordHow work moves
01
Start with the stalled decision, repeated handoff, or invisible risk. The tool comes later.
02
Define what the workflow may see, what it may change, and where a person must take over.
03
Ship the narrow path that removes real work before adding breadth or polish.
04
Test the happy path, the refusal path, and the boundary that should never be crossed.
Career throughline
Marketing and GTM leadership shaped by company launches, spin-offs, acquisitions, and the work of carrying a brand and pipeline through change.
Read the career storyStart a conversation