Systems Before Campaigns
Most marketing organizations start with campaigns and work backward to infrastructure. I do the opposite. Before launching a single program, I design the lead lifecycle, the scoring model, the measurement framework, and the sales handoff process. This isn’t perfectionism — it’s pragmatism. Without this foundation, every campaign generates activity that can’t be measured, leads that can’t be qualified, and pipeline that can’t be attributed.
The system comes first because the system is what makes campaigns compound rather than exist in isolation. A well-designed lifecycle means every lead that enters the funnel has a defined path forward. A working scoring model means sales trusts the leads marketing sends. Attribution infrastructure means you can make investment decisions based on evidence, not intuition.
Pipeline Is the Organizing Metric
I’m skeptical of marketing organizations that optimize for MQLs, traffic, or engagement as primary metrics. These are leading indicators and they matter, but they’re not the thing. The organizing metric is marketing-sourced and marketing-influenced pipeline tied to revenue.
This isn’t just a measurement preference — it changes how you build programs. When pipeline is the metric, you design campaigns backward from deal creation. You allocate budget based on pipeline contribution by channel, not cost per lead. You build reporting that connects marketing activity to revenue outcomes that sales and finance actually care about. And you earn a fundamentally different kind of credibility with the executive team.
Build to Hand Off
Every system I build is designed so the team can operate it without me. Campaign templates that non-MOps team members can launch independently. Documentation that explains not just what the system does but why it was designed that way. Role frameworks that give people clear ownership and the context they need to make decisions.
This isn’t modesty — it’s a design principle. If a demand generation system requires its architect to run it, the architect failed. The real test of a system isn’t whether it works when you’re in the room. It’s whether it works when you’re not.
MarTech Is Architecture, Not Tooling
Too many organizations evaluate marketing technology as a feature comparison exercise. I treat MarTech decisions as architecture decisions. The question isn’t “which platform has the most capabilities?” — it’s “which platform supports the system this organization needs to run?”
This means evaluating platforms against your specific lifecycle model, your integration requirements, your team’s operational maturity, and your growth trajectory. The right platform for a company building its first demand engine is different from the right platform for a company scaling an existing one. Context determines the answer.
The First 90 Days
When I enter a new organization, the first 90 days follow a consistent pattern. The first month is assessment: understanding what exists, what’s working, what’s broken, and what the business actually needs from marketing. I embed with sales during this phase because pipeline targets are meaningless if you don’t understand how deals actually move.
The second month is architecture: designing the system based on what I’ve learned. Lead lifecycle, scoring, measurement, team structure, budget framework. The third month is launch: standing up the first programs on top of the infrastructure, with clear metrics and a reporting cadence that builds organizational confidence in the approach.
This isn’t a rigid formula — timelines flex based on the situation. But the sequence (assess, architect, launch) is consistent because it works.