FIG. 01 — DIAGNOSIS
I install the operating infrastructure that survives the next stage. Twenty years. Two acquisitions. From the inside.
// or do it the normal way: start a conversation →
FIG. 02 — DEPLOYMENT RECORD
GTM Integration
Led the five-month migration from HubSpot to Salesforce across a six hundred million dollar revenue organization. Rebuilt the GTM data model so revenue, marketing, and finance worked from one source of truth.
Post-Acquisition Integration
Integrated Lumi into Narvar after acquisition. Stood up a Metabase business intelligence layer used by more than one hundred operators daily. Aligned two operating systems without breaking either.
Series A → Acquisition
Built and ran the operating function from Series A through acquisition. Grew a vendor network of more than three hundred partners and drove error rates from over six percent to under one percent at scale.
FIG. 03 — OPERATING METHOD
#1 DIAGNOSE
First week is listening. Customers, team, data, vendors. The real problem is rarely the one in the brief.
#2 BUILD
Systems that depend on heroes break. I design process and tooling for the operators who will run it after I leave.
#3 EXIT
Documented. Hired. Handed off. Success is the day no one needs to call me.
PLATE 01 — THE OPERATOR
Two decades running operations at companies on the line between scrappy and serious. Sometimes the line moves under your feet. That is usually when I get the call.
Migrations. Integrations. Vendor networks. Forecasting. The plumbing that decides whether a Series B becomes a Series C or quietly stalls.
FIG. 04 — INITIATE
RESPONSE <24H // ONE CONVERSATION, NO DECKS