Which kind of marketing leader
Six kinds of marketing leader, and where each one is broad rather than deep
Every leader who takes this title at an early stage company is a full stack marketer: broad working knowledge across the six disciplines below, deep on two or three. The one they lead from decides what the company gets in the first year, and the one they go broad on is where the first hire underneath them adds depth. The diagnose path in the builder scores which one your gap needs.
Brand and category
Category definition, the company narrative, analyst standing, and the public voice the market comes to recognize.
Right when: The company is defining a category rather than entering one, an analyst or acquirer conversation is coming, or the CEO answers the category question differently every time.
Broad here, not deep: Pipeline math, attribution and campaign infrastructure. Programs get built to serve the story rather than the number, and the board finds out in the quarter the story is not yet converting.
Where depth gets added: Demand Generation Lead. Someone who owns the pipeline number and the channel mix, so the narrative has a machine underneath it.
Demand and pipeline
Campaign strategy, channel mix, funnel conversion and the marketing sourced pipeline number, with the growth and performance instincts a product led motion needs.
Right when: The story is settled and converting when someone hears it, and the constraint is how many of the right people hear it. Sales trusts the message and is short on pipeline.
Broad here, not deep: Category narrative and positioning depth. The machine runs, and sales keeps rewriting the message because the person running the machine did not stop to fix it.
Where depth gets added: Product Marketing Manager. Someone who owns positioning, the sales narrative and competitive work, so the machine is running the right message.
Product marketing and positioning
Positioning, launches, competitive intelligence and the narrative sales actually uses in the room.
Right when: Prospects hear the pitch and do not understand the difference, sales rewrites every deck, or the company loses evaluations it should win, and the rest of marketing is already covered. When the gaps run wider than positioning, a strategic leader who is deep in positioning is the better hire, with a product marketer underneath.
Broad here, not deep: Program volume and channel execution. The story is strong and the top of the funnel is thin, because building programs is the part this leader finds least interesting.
Where depth gets added: Demand Generation Lead. Someone who turns the positioning into programs and owns the pipeline number.
Content and thought leadership
Research, editorial, evangelism and the material a security buyer comes back to, plus the search and answer engine visibility that makes it findable.
Right when: Practitioners search the problem the company solves and find nothing from it, the company has no research or point of view the market cites, and the buyer is technical enough that product pages do not persuade.
Broad here, not deep: Pipeline accountability and marketing operations. The audience grows and the board asks what it converted to, and the honest answer is that nobody built the measurement.
Where depth gets added: Demand Generation Lead. Someone who turns audience into pipeline and owns the number.
Field, events and partner
Conferences, regional programs, channel and MSSP co-marketing, and the pipeline that comes off the floor and through partners.
Right when: The motion is enterprise or channel led, most pipeline comes from events and partners, and the company needs those programs run as a system rather than a calendar.
Broad here, not deep: Digital, content and the long arc brand. Strong quarters around RSA and Black Hat and quiet in between, because nothing compounds when the booth comes down.
Where depth gets added: Content Marketing Lead. Someone who builds what compounds between events and gives the field programs something to distribute.
Revenue and operations
Attribution, marketing operations, RevOps alignment, intent data and the model behind the pipeline number.
Right when: Marketing and sales report different numbers, nobody trusts attribution, the stack was bolted together by people who left, or the board wants a forecast marketing can defend.
Broad here, not deep: Narrative, positioning and brand. The dashboard is right and nobody can say what the company stands for, because measurement got the attention the message needed.
Where depth gets added: Product Marketing Manager. Someone who owns the message the machine is measuring.
What this checks
Three things a job description template will not tell you
Whether it is actually one job
The builder adds up the functions the description assigns to one person and compares that against the capacity a single hire actually has. A scope that comes back at two or three full time equivalents is not an ambitious job description, it is two or three jobs at one salary, and it will read that way to the candidates worth hiring.
Whether the title matches the work
A description can be well scoped and still carry the wrong title. The builder checks the level against your stage, your team size and the scope you described, and names the adjacent titles this one will get confused with, so the mismatch surfaces before you post rather than in the third interview.
Whether the number is realistic
You get a band with the base and variable split that matches the accountability you described, specific to cybersecurity rather than pulled from a cross industry average. A building role weighted like a closing role signals the wrong thing and filters out the people you want.
The coverage grid
The 20 functions this diagnosis runs on
The bottleneck question earlier in the builder is asking which of these you cover well today, cover thinly, do not cover, or do not need yet. The gaps are what define the role, which is why the tool asks about coverage before it asks about titles.
Strategy and positioning
The work that decides what the company says and who it says it to.
- Positioning and messaging
Value proposition, message hierarchy, proof architecture, and the words the whole company uses. - Category and brand narrative
Long arc market perception, category definition, brand equity, board level story. - ICP definition and market research
Who the buyer is, what triggers a purchase, TAM and segmentation work. - Competitive intelligence
Win and loss patterns, battlecards, displacement plays, pricing pressure tracking.
Demand and awareness
The work that creates and captures interest at the top and middle of the funnel.
- Demand generation and paid
Campaign strategy, paid channels, nurture, pipeline targets and channel mix. - Content and editorial
Thought leadership, research reports, blog, video, and the editorial calendar. - Product marketing and launches
Launch management, pricing and packaging input, sales narrative, competitive positioning. - Website, SEO and answer engine visibility
Site conversion, organic search, schema and structured data, visibility inside AI answers. - Events and field marketing
Conferences, booths, dinners, regional programs, and the pipeline that comes off them. - Analyst relations and PR
Gartner and Forrester engagement, press, awards, customer references and case studies.
Sales and revenue
The work that turns interest into signed contracts and keeps the revenue.
- Pipeline generation and outbound
Prospecting, cold outreach, list building, meeting setting, top of funnel sales activity. - New business closing
Discovery, evaluation management, negotiation, procurement and signature. - Sales team leadership
Hiring reps, quota and territory design, forecast accountability, coaching and performance management. - Sales enablement
Onboarding, certification, playbooks, call coaching, and the content sellers actually use. - Technical pre sales
Demos, proof of concept, technical evaluation, security review support, architecture conversations. - Customer success, renewal and expansion
Onboarding, adoption, retention, upsell and cross sell motion. - Partnerships and channel
Resellers, MSSPs, technology alliances, marketplace listings, co selling motion.
Systems and infrastructure
The connective layer that makes everything above run without a person doing each step.
- Marketing operations
Marketing automation platform, campaign infrastructure, lead flow, attribution reporting. - RevOps, CRM and forecasting
CRM architecture, data hygiene, process definition, forecast models, board reporting. - GTM automation and data engineering
Enrichment pipelines, signal monitoring, routing logic, AI drafted outbound, internal tooling.
Questions
Naming the gap before the title
Why does the builder ask what kind of marketing leader I need after it recommends the role?
Because CMO and VP of Marketing describe the same full stack job below roughly $40 million in ARR, and the title tells you nothing about which discipline the person leads from. A demand leader and a brand leader will both accept the same VP of Marketing description and produce completely different first years. The profile step scores your coverage grid and six situational questions to name the lead discipline your gap actually needs, so the description filters for it instead of hoping.
What is the depth hire and why is it in my job description?
Every marketing leader at this stage is broad across brand, demand, product marketing, content, field and operations, and deep in two or three. Each profile has a discipline where the leader is broad rather than deep, and the depth hire is the first person underneath them who covers it properly. Naming it in the description does two things: it tells strong candidates the company understands the role, and it stops the search from filtering for a person who is deep in all six, who does not exist. Below Series A the tool recommends a fractional or agency engagement instead of a full time hire.
I do not know which role I need. Is that a problem?
It is the reason this path exists. The builder asks about coverage and the bottleneck before it asks about titles, then recommends the role, explains why, and names the titles it will get confused with. Starting from a title you are unsure about tends to produce a description that describes the title rather than the gap.
What does the scope load score actually mean?
The number of full time equivalent people the scope you described would consume, measured against what one hire can realistically carry. Anything meaningfully above one means the description is asking for more than one job. The usual fix is not a better candidate, it is a narrower description or a second hire.
The tool recommended a role I was not considering. Should I trust it?
Treat it as a second opinion rather than an answer. The recommendation comes from the coverage gaps you described, so if it surprises you the useful question is which gap drove it. Companies frequently arrive certain they need marketing leadership and leave realising the bottleneck was execution capacity or an operations problem, which is a different hire at a different band.
Can I use this if I already know the title I want to hire?
Yes. There is a separate path for that which skips the diagnosis and goes straight to scoping the description, still with the scope load check before you post. Use this path when you are less sure the title is right than the gap is real.
Where do the salary bands come from?
Benchmark figures adjusted for stage and geography, with a cybersecurity premium applied on top because general benchmark sources are cross industry and sit below what security go-to-market roles clear. They are directional, for setting a range and structuring the base and variable split rather than for making an offer.
What do I get at the end?
A job description scoped to your stage, team and existing coverage, the scope load reading, a compensation band with the split, the titles the role will be confused with, interview questions mapped to each area of scope, a scorecard, and first ninety day expectations. Export as PDF, Word, an Excel interview kit or plain text.
Is anything I enter stored?
No. Everything runs in your browser. Nothing is sent to a server, nothing is logged and there is no account.