I've run revenue orgs. I've built the software. Now I wire GTM systems that actually work.
I'm Trevor, an independent GTM engineer for B2B companies still running revenue out of spreadsheets and gut feel. I audit the CRM, automate the handoffs, and build the reporting that tells you what's actually happening in the pipeline.
Based in Metro Detroit — working with clients locally and remote, expanding nationwide.
Four ways to start
CRM Audit & Data Remediation
A fixed-scope audit of your CRM data model, pipeline stages, and automation — with a prioritized list of what's broken and what it's costing you. Two weeks, one clear report.
Automation & Workflow Build
Lead routing, follow-up sequences, and reporting built directly in your stack — either what the audit found, or what you already know needs fixing.
Fractional GTM Systems
Ongoing systems work. I sit inside your revenue operation part-time, building and maintaining the automation, integrations, and reporting your team runs on.
AI-Assisted Enrichment & Agentic Workflows
Enrichment pipelines and agentic workflows that qualify and route leads before a human touches them — built cost-consciously, tuned against real data, not a demo.
Eight years running revenue, then I started building the software
Before I wrote a line of production code, I spent eight years running revenue organizations — quota-carrying, then managing the team that carried it. I know what a broken CRM costs a forecast meeting, and I know why most "automation" initiatives stall: they're built by people who've never had to defend a number in front of a VP.
I made the switch to engineering because I got tired of asking other people to build the systems I could see needed building. Now I do both sides: I still think like an operator, but I build like an engineer.
- — An operator's read on what a number in a pipeline report actually means
- — An engineer's ability to actually ship the fix, not just diagram it
- — Comfortable naming what isn't working yet, in the CRM and in the build
See the actual work
Architecture decisions made under real constraints, data problems solved against real production data, and honest notes on what's still in progress. The Portfolio page has the details.
See the case studies →Latest notes
Photo resizing as an Automation Component
I found macOS's built-in image tool today and used it to resize 65 photos in under two seconds -- here's what it is, how to use it, and places it (or analogues) could earn a spot in an automated workflow.
What Slow Lead Response Actually Costs You
Slow lead response isn't a motivation problem, it's a systems problem. Here's what the research actually says it costs -- with an interactive calculator to see the number for your own funnel.
When 'No Error' Is the Bug: Forced Tool Choice and a Silently Skipped Web Search
A forced tool_choice call returned an empty result with no error, no exception, nothing. Here's why forcing a tool doesn't mean 'use this eventually' -- and the two-call fix.
Let's talk about your GTM systems
The best next step is a 20-minute call — no pitch deck, just a conversation about what's actually breaking in your pipeline.