Clients & Work
Most of my work is long-term and deep. I tend to enter narrow, absorb the parts of the revenue system nobody owns, and leave the team able to run it without me. Each one shows the stack I built and where the data lands in the CRM.
Who I work with
Prefab home manufacturing
The foundation of the practice. A five-year engagement that started in 2016, rebuilding the website and then absorbing marketing ops, sales ops, and IT until I was co-running the department. Rebuilt Salesforce sales-first and led the full migration to Microsoft 365.
Life sciences / biopreservation
Anchor client. Connected sales, marketing, and customer service end to end, migrated off legacy Salesforce add-ons, and made the CRM agree with the ERP. Rebuilt email deliverability from the DNS up.
Life sciences / cold-chain logistics
The full connected GTM build. Default routing, de-anonymization, scoring, and Slack alerts wired around Clay and Unify GTM, with custom research and outreach agents that are checked before they send. The data lands clean in the CRM, not in a spreadsheet.
Ultra-low temperature equipment
Project-based work inside a larger group. Built Salesforce CPQ and quote configuration into production, and ran a focused data audit during a corporate transition.
Education technology
The most cross-functional engagement: IT, customer success, sales, and marketing. Led the data-hygiene push, retired hundreds of thousands of junk contacts, fixed hosting and deliverability, and pulled them off a blacklist they did not know they were on. A Common Room signal play turned community and product signals into a prioritized prospecting motion.
Education technology
A focused Marketing Cloud spin-up. Stood up MCAE / Pardot, imported and cleaned the prospect database, retired legacy campaigns, and modernized the website onto Gravity Forms.
Revenue operations / my own pipeline
Clay as one layer of a connected stack. Custom agents classify, enrich, and score every account on arrival, so the target list never goes stale. The build I run on my own pipeline.
What an engagement looks like
Usually one system, one problem someone can name. A website, a CRM nobody owns, an email program that stopped landing.
Because the systems are connected, the work is too. I become the connective tissue across sales, marketing, ops, and IT.
Tools talk to each other. The CRM matches the ERP. Deliverability gets fixed at the DNS level. The numbers finally reconcile.
I build for the people who run it, not for me. Capability transfers in. Consultant dependency breaks.
A good engagement ends because you no longer need me in it daily. The system runs without me, and the relationship stays warm.
“He has been hired to set up a system for us to have it work.”
Doug West