Working with a Head of Customer Marketing

What this role actually does

The Head of Customer Marketing owns the marketing motion targeted at the installed base. The seat sits inside the marketing organization but the constituency is customer success, sales expansion, and the customers themselves. The mandate is expansion revenue, retention influence, and advocacy at scale. In a subscription business this seat is where marketing earns its right to talk about net revenue retention.

A working Head of Customer Marketing spends real hours with customer success leaders on the accounts up for renewal and expansion, real hours with product marketing on feature adoption campaigns, real hours with the events team on user conference programming, and real hours with the reference program manager on advocate recruitment. The seat carries a lifecycle marketing manager, a reference or advocacy manager, an events lead focused on customer programming, and a customer content producer. Team size ranges from three in a mid market org to twelve in a public company.

The Head owns adoption campaigns, expansion enablement, the customer reference and advocacy program, the user conference or customer community, and often the customer newsletter. They also own the account based marketing motion when it is aimed at expansion inside the current base. The seat carries a real number: expansion pipeline sourced or influenced by customer marketing.

What a functioning Head of Customer Marketing does not do: own the churn number end to end, run the customer success team, or draft every case study personally. They do not own the renewal forecast and they do not own product decisions. They own the marketing programs that make retention and expansion cheaper. A Head who is writing case studies at ten at night has an editorial problem below them and a resourcing problem above them.

The Head also owns the political discipline that keeps customer marketing from becoming a favor economy for CS. Every CSM wants a custom campaign for their favorite account. The Head who does not tier programs by segment ends up with a calendar full of bespoke work that does not scale. Segmented programs are the operating discipline the seat lives on.

How to brief them well

You brief a Head of Customer Marketing on the expansion outcome and the retention support you want. Here is the expansion pipeline target. Here is the segment split between low touch and high touch. Here is the reference program commitment for sales. Here is the events budget. Here is the constraint on headcount. The Head comes back inside three weeks with a customer marketing plan, a program calendar, and a resource plan.

Bad briefs at this level look like a campaign or event wish list. Please launch a user conference. Please run a webinar series. Please write more case studies. Every ask without a segment plan produces content that never gets used in the right sales cycle. The Head who executes a campaign brief either builds the wrong thing well or spends the year defending activity to a CFO who wants outcomes.

Context the Head needs on arrival includes the actual state of the reference program, the current adoption rate on core features, which customers are advocates and which are quiet, and the political relationship between customer success and sales on expansion motions. A Head who does not know which CSMs are hoarding references is going to miss the expansion pipeline number the first quarter.

The strongest brief pairs an expansion target with a hard boundary. Source ten million in expansion pipeline. Do not launch a user conference in year one. Do not run adoption campaigns that require product engineering time. Named nos protect the plan from every sales leader who wants a custom program for their favorite account.

The strong brief also names the customer segment the Head will not serve with scaled programs. Not every account needs a high touch invitation to the executive dinner. A written tier document that names low touch, mid touch, and high touch coverage is what saves the team from serving the whole base with the same play.

Review cadence + operating rhythm

Weekly rhythm

Weekly at the Head of Customer Marketing level is a program review and a leader standup. A Monday of about an hour covering active campaigns, upcoming customer moments, and any escalation from CS or sales. A Wednesday sync with customer success leadership on expansion pipeline and at risk accounts. A Friday one on one with the CMO or VP of Marketing. Numbers reviewed weekly are program pace, expansion pipeline sourced, and any adoption campaign in flight.

Monthly and quarterly reviews

Monthly is the operating review. Expansion pipeline sourced and influenced, adoption rate movement, reference program capacity against sales demand, and event yield tied to pipeline. The Head walks in with a proposed reallocation and defends it in front of the CMO. Monthly is also when the Head reviews the case study backlog and prunes anything that is not being used in the field.

Quarterly is where the honest conversation happens. The Head presents expansion pipeline attainment, program yield, advocate roster health, and the plan for the next quarter. This is where entire programs get retired and new ones get greenlit. Sales leadership attends this QBR. If sales cannot name three programs the Head shipped that helped them win, the Head is running programs the field does not use.

Annual planning

Annual planning at the Head level is a segmented customer marketing plan, a reference program capacity commitment, and an events calendar. A Head who arrives at January without a written expansion pipeline forecast is going to lose budget to the VP of Demand.

Between the standing cadences the Head also runs a monthly reference program review with sales. When sales demand for references outpaces the roster, the Head is at risk of losing sales trust. When the roster outpaces demand, the Head is over investing in advocacy. The monthly forum keeps the ratio honest.

Measurement (real KPIs, not vanity)

Four numbers matter at the Head of Customer Marketing level.

First, expansion pipeline sourced and influenced. Dollars of upsell or cross sell pipeline where customer marketing programs originated or contributed to the opportunity. The number that ties the seat to revenue. A Head who cannot pull this from the CRM in a week is not close enough to the operations.

Second, adoption rate on core features tied to retention. The percentage of the active base using the features that predict renewal. When adoption on a critical feature is below fifty percent, the Head has a campaign to run and a product problem to escalate.

Third, reference program capacity against sales demand. The number of active advocates, the coverage across industries and use cases, and the utilization rate. When sales asks for a reference and CS cannot supply one, deals slow down. The Head owns the ratio.

Fourth, event yield. Pipeline sourced from user conferences, webinars, and roundtables cut by cost per attendee. The number that lets the Head defend the events budget in a year when the CFO is cutting.

Vanity metrics that mislead include gross attendee count at customer events, case study count, and community member volume. A Head who reports how many case studies shipped is measuring effort. A Head who reports which case studies were sent by sales in the last quarter is measuring outcomes.

The diagnostic layer under expansion pipeline is the product usage signal on the accounts CS is running expansion plays on. When usage decays on an account the CSM is expanding, the play is going to fail. The Head who wires usage signals into the customer marketing motion catches the failing plays before they burn sales cycles.

Compensation + career path (honest ranges)

Head of Customer Marketing comp splits into three market bands.

Compensation bands by market

Mid market. Series B to C, ten to fifty million ARR. Base 155 to 210 thousand. Bonus 10 to 20 percent. Equity 0.05 to 0.20 percent. Total cash 175 to 250 thousand. Team size two to five. Often the seat carries the events function double duty.

Tech metro. Series C onward, fifty to two hundred million ARR. Base 200 to 275 thousand. Bonus 15 to 25 percent. Equity 0.04 to 0.15 percent. Total cash 235 to 340 thousand. Team size four to nine. Formal handshakes with customer success on expansion pipeline are expected weekly.

Coastal enterprise. Public or late private. Base 250 to 335 thousand. Bonus 20 to 35 percent. Equity or RSUs 175 thousand to 600 thousand a year. Total comp 475 thousand to 1.0 million. Team size seven to fourteen. This band often owns the entire user conference production budget.

The typical next step is VP of Marketing at a smaller company, Chief Customer Officer at a customer led company, or head of lifecycle marketing at a larger org. Some Heads move sideways into product marketing when the seat opens.

Common departures. The two year exit when expansion pipeline stays flat. The eighteen month exit when the Chief Customer Officer changes and the incoming leader restructures marketing coverage. The clean four year run when the Head builds a compounding advocate program and moves to a bigger seat. A healthy tenure is three to five years.

The negotiation moment for a Head of Customer Marketing is whether the seat carries a piece of the NRR number or only the marketing sourced expansion pipeline. If the seat carries NRR, comp reflects it. If the seat carries only expansion pipeline, comp reflects that scope. The offer that pretends the accountability question does not matter produces a Head who spends the year fighting for credit.

Common ways this seat fails

The Head who confuses hospitality with pipeline. The user conference is beautiful, the case studies are polished, and expansion pipeline is flat. Every program the team runs is well produced and none of them show up in the sales cycle. Two quarters of that pattern and the CFO decides the seat is a cost center. The Head who does not tie every program to a pipeline outcome loses budget every planning cycle.

The Head who cannot align with customer success. CS hoards references. CSMs skip adoption campaigns because they see them as marketing noise. The Head who does not build a joint operating plan with the head of CS in the first ninety days is going to fight the same battle every quarter for the tenure.

The Head who over invests in the community. A branded community is expensive to run. When engagement plateaus, moderation costs stay high and the ROI stops being defensible. A Head who does not audit community ROI quarterly is going to be forced to shut the community down in a bad budget cycle.

The Head who cannot say no to sales. Every sales leader wants a custom program for their favorite account. The calendar collapses into bespoke work. Scaled programs stop shipping. The Head who cannot filter for the team is running a favor economy, not a marketing function.

The Head who ignores adoption analytics. Feature adoption is a leading indicator of churn. When the Head cannot tell the CS team which customers are quietly declining, the retention motion is reactive. The Head who does not partner with product analytics in month one is missing the most important input the seat has.

The seat also fails when the Head cannot make the case that a customer program deserves a full time producer. User conferences, communities, and reference programs each require dedicated ops capacity to run at scale. The Head who tries to run all three with the same generalist team burns out the generalist and produces mediocre versions of each.