You walked into a PE-backed or growth-stage company with a mandate to build a growth engine. What you inherited was a trade show calendar, a blog nobody reads, and a demand gen “strategy” that’s actually just a list of tactics someone ran last year.
Welcome to the random acts of marketing.
Every VP of Marketing or CMO who’s landed inside a PE portfolio or a growth-stage company scaling past founder-led sales has seen this version of the org. Marketing exists. People are busy. Campaigns ship. But nothing connects to pipeline in a way you can defend in a board meeting. The team measures campaigns launched, leads generated, impressions served. None of those numbers map to the forecast. None of them explain why sales keeps missing and marketing keeps claiming wins.
This is what a support function looks like when it’s been left to operate without a revenue constraint.
The Anatomy of Random Acts
Random acts aren’t lazy. That’s what makes them hard to kill. The team is working. Often working hard. The problem is structural: marketing is running plays that were never reverse engineered from a GTM plan. They were selected by budget remnants, stakeholder requests, or the logic of “we did this last year.”
Here’s how to spot it in your first 30 days:
No shared definitions. Sales calls something an MQL. Marketing calls something else an MQL. Product has a different threshold entirely. There’s no shared playbook for what “demand” means, what “readiness” looks like, or who owns conversion after the handoff.
Tactics without a thesis. The team runs a webinar series, sponsors two events, publishes content on a cadence. Ask why those channels, in that sequence, targeting those segments, and the answer is institutional momentum. Someone chose them once. Nobody re evaluated.
Measurement stops at the top of the funnel. Dashboards track cost per lead, email open rates, campaign engagement. Nothing connects marketing activity to pipeline velocity, win rate, or revenue closed. The CFO asks for marketing’s contribution to bookings and gets a slide full of proxies.
No experimentation infrastructure. Programs run at scale once and get repeated. There’s no hypothesis, no A/B structure, no kill criteria. Decisions come from opinion, seniority, or whatever the agency recommended.
If more than two of those describe your current situation, you don’t have a marketing team with a strategy. You have a marketing team with a task list.
What a Growth Engine Actually Looks Like
The shift requires rebuilding marketing as a revenue-constrained growth system that operates as part of your GTM architecture, not adjacent to it.
Four things change:
Marketing goals start from the revenue plan, not the marketing plan. If your GTM target is $20M in new ARR and your average deal closes at a 22% win rate, you can calculate exactly how much qualified pipeline marketing needs to create. Every program, every channel, every dollar traces back to that number. Marketing stops defending activity metrics and starts owning a share of the pipeline target.
Full-funnel ownership replaces campaign-level thinking. A growth engine treats acquisition, activation, monetization, retention, and expansion as a connected system. One repeatable demand-gen engine with defined plays, segments, sequences, and nurture tracks that can be scaled up or down based on capacity and ROI. The team stops thinking in campaigns and starts thinking in systems.
Experimentation becomes operational, not aspirational. Two to four structured tests per quarter with a hypothesis, a prioritization framework, and clear win/lose thresholds. The team learns at a tempo that compounds. What doesn’t work gets killed. What works gets doubled.
Marketing co-owns the GTM plan with sales and product. ICPs, segment strategies, plays, and motion design are built jointly. Marketing isn’t a service desk filling requests. It’s a partner with shared incentives and shared accountability for what hits and what misses.
The 90-Day Bridge
You have roughly 18 months before the board starts asking harder questions about your hire. Most of that runway gets consumed by inheriting the previous leader’s infrastructure and defending work you didn’t commission. Here’s how to stop that cycle.
Days 1–30: Diagnosis. Map every current marketing activity into three categories. Demand-driving plays that are full-funnel, tested, and ROI-tracked. Random acts that are one-offs with no clear goal or follow-through. Support overhead like brand, PR, enablement, and internal comms. Quantify which 20% of activity drives 80% of pipeline. The rest is your cut list.
Days 30–60: Constraint mapping. Work with sales and product to codify ICPs, define shared conversion definitions, and build a capacity model. If marketing adds 10% more pipeline, what will sales actually close? That answer sets the ceiling for everything you build. Lock the GTM plan before you spend another dollar on expansion-level tactics.
Days 60–90: Minimum viable engine. Pick one or two core plays you can measure rigorously. Account-based nurture into your top segment. A partner-driven co-selling motion. Whatever maps to your strongest ICP with the shortest feedback loop. Define KPIs, experiment cadence, and thresholds for scaling, pivoting, or killing each play. Build basic attribution that sales and marketing agree on. It doesn’t need to be perfect. It needs to be shared.
By day 90, you should be able to walk into a board meeting and say: here is what marketing is responsible for, here is how we’re measuring it, and here is what we’re learning. That sentence is worth more than any campaign report you’ll ever produce.
The Metric That Actually Matters
Attribution models will never be perfect. First-touch, last-touch, multi-touch, revenue-share models all have flaws, and every sales leader will argue with the methodology. Stop trying to win the attribution argument. Win the accountability argument instead.
Build dashboards that show three numbers: pipeline created by marketing, pipeline influenced by marketing, and revenue closed with marketing contribution. When you present those alongside what you tested, what you learned, and what you’re changing next quarter, you stop being the department that makes slides. You become the function that builds pipeline.
That’s the difference between a support function and a growth engine. One defends its existence with activity reports. The other defends its budget with math.