Enterprise SaaS Marketing Playbook

At 200,000 dollars a year, nobody fills in a form and books a demo. A committee of eleven spends nine months deciding whether your company will still exist in five years, whether your security posture survives their audit, and whether the person championing you is staking their reputation on something defensible.

That’s a different job. Almost nothing from the standard SaaS playbook survives the move, and the parts that look familiar (content, events, email) are doing entirely different work here. This playbook rebuilds the programme from the constraints.

Account selection: you need fewer accounts than you think

Enterprise marketing starts with arithmetic that shocks teams arriving from mid-market.

Say you need 15 million dollars of new pipeline. At a 150,000 dollar average deal, that’s 100 opportunities. If roughly a quarter of properly engaged target accounts produce an opportunity within the year, you need about 400 accounts under real coverage. Four hundred. You can put them in a spreadsheet and read every name.

That changes the economics of everything. Spending 400 dollars per account on research, custom content and events is 160,000 dollars total, which is defensible. The same per-account spend at 20,000 accounts is not a budget, it’s a fantasy.

Build the list from three signals, in this priority order:

• Structural fit: employee count, revenue, regulatory environment, existing tech stack
• Triggers: a new executive in the buying role, a funding or acquisition event, a compliance deadline, a publicly announced initiative your product serves
• Relationship surface: existing customers who moved there, investors in common, mutual advisors

Tier them. Roughly 50 accounts get one-to-one treatment, 150 get one-to-few, and the remaining 200 sit in a programmatic tier. The tiering mechanics are worked through in Account Based Marketing for SaaS, and the coverage discipline matters more than the tooling.

Analyst relations: what it costs and when it pays

For categories Gartner and Forrester cover, analysts sit inside your buyer’s decision process whether you engage or not. Procurement teams at large enterprises frequently require a shortlist supported by analyst research, and an uncovered vendor has to fight to get on the list at all.

The realistic numbers: a vendor programme with briefing rights and inquiry access commonly runs 40,000 to 150,000 dollars a year. Add a dedicated AR person, or a fractional consultant at 5,000 to 12,000 a month, because an unattended programme is money burned. Then add the clock. Briefings feed research cycles, research cycles publish on annual calendars, and the first report that mentions you may be three or four quarters out.

Investment	Annual cost	Time to influence a deal	What it buys	Skip it if
Gartner or Forrester vendor programme	40K to 150K	2 to 4 quarters	Inquiry access, briefings, shortlist presence	Your category has no analyst coverage
Fractional AR consultant	60K to 145K	1 to 2 quarters	Briefing quality and analyst relationships	You have an in-house AR lead
Independent analysts and practitioners	10K to 50K	1 quarter	Credible commentary without the wait	Your buyers only cite the majors
Peer review platforms	20K to 80K	1 to 2 quarters	Verified reviews procurement will accept	Nothing, most teams should do this

My position: for a company under 10 million ARR, a fractional AR consultant plus peer review presence beats a full analyst programme. Buy the relationship, not the seat, until you’re genuinely competing in a covered category. Snowflake and ServiceNow both invested heavily in analyst positioning, and both did it when they had the product maturity to survive the scrutiny.

The trust stack as a conversion asset

At enterprise scale, security documentation is marketing collateral. It’s read earlier, by more people, and with more consequence than anything on your blog.

The stack, in build order:

Vanta and Drata both publish trust centres, which is a useful signal given that removing security friction is literally their product. The pattern works because it converts a blocking, human-mediated step into a self-serve download, and every week you remove from a nine month cycle is a week your champion is still in their job.

Pair the trust stack with the document your champion needs on the same timeline, which the Champion Business Case Template covers. Security clears the objection, the business case creates the reason to keep going.

Marketing should own the trust centre page even though security owns its contents. It’s a conversion surface, it needs a content owner, and left to engineering it becomes a stale PDF link.

Field marketing: dinners, roadshows and what they cost per opportunity

Enterprise buyers meet people. That isn’t nostalgia, it’s how risk gets underwritten on a purchase that will outlive several org changes.

Format	Cost per run	Attendees	Realistic opportunity yield	Best used for
Executive dinner	8K to 25K	12 to 20	3 to 8 opportunities created or advanced	Multi-threading open deals
City roadshow, half day	25K to 60K	40 to 80	6 to 15 opportunities	Entering a new region
Industry conference booth	60K to 250K	Highly variable	Often poor unless meetings are pre-booked	Meeting existing pipeline efficiently
Private customer advisory board	30K to 70K	8 to 15	Expansion and referenceability, not new logos	Retention and product direction
Small vertical roundtable	5K to 12K	8 to 12	2 to 5 opportunities	Category education in a niche

The dinner is the most reliable format and the most commonly wasted. Build the guest list from open opportunities and named target accounts, invite the economic buyer rather than the practitioner, and accept 14 of the right people over 30 of the wrong ones. A dinner filled to capacity with whoever accepted is a catering expense.

Conference booths deserve more scepticism than they get. A 150,000 dollar booth that produces badge scans is a lead gen tactic in an environment where lead gen doesn’t apply. The same money spent on twelve dinners across four cities, targeted at your account list, will almost always produce more pipeline. If you do the conference, go for the pre-booked meetings and treat the booth as a meeting room.

Pipeline math and reporting on a 12 month lag

The reporting problem is structural. Money spent in Q1 shows up as booked revenue in Q4 or later, and CAC payback at this ACV runs 18 to 24 months. A board reviewing enterprise marketing on a quarterly demand report is reading a number that cannot yet contain the answer.

Publish the lag model before you spend, and get the CFO to sign off on the shape of it. Then report the same chart every quarter without redesigning it.

The sales side of this, including quota math and the assets each stage needs, sits in B2B SaaS Sales Strategy. A deal walked end to end, with the actual sequence of touches, is in the Enterprise SaaS Deal Teardown.

What fails at this level

Volume tactics. A webinar that fills with 400 practitioners from companies of 30 people is a good webinar and irrelevant pipeline. Judge enterprise programmes by who attended, never how many.

Gated ebooks aimed at a committee. The security architect is not filling in a form to read your whitepaper, and the CFO certainly isn’t. Ungate everything a committee needs to evaluate you, then instrument account-level engagement instead of contact-level form fills.

Treating awareness as optional. Only a small slice of your 400 accounts is buyable this year, which is what The 95-5 Rule in B2B Marketing describes, so a programme that only touches in-market accounts leaves the other 380 to a competitor who showed up earlier.

Aggressive nurture. A 200,000 dollar buyer receiving a four-email drip about your feature release is being told you don’t understand the purchase. Reduce frequency and raise the quality of each touch.

And the expensive one: hiring a field marketer before the trust stack exists. Dinners generate interest that then dies in a security review you weren’t ready for.

Where vertical focus changes the math

If your enterprise motion is vertical, reference customers matter more than everything above combined. In a market of 600 hospital systems or 300 regional banks, the buyer will call two of your customers before they call you, and one bad reference ends the deal. Budget for customer marketing at the same level as demand generation, which is covered in Vertical SaaS Marketing.

The rest of the go-to-market plan, including how this programme fits alongside mid-market and self-serve motions running in parallel, belongs in the B2B SaaS Go to Market Plan Template. The broader context is in B2B SaaS Marketing.

Start here

Three moves in the first 90 days. Lock a 400 account list with sales and stop changing it. Ship the trust centre with whatever compliance you currently hold, and put a dated roadmap for the rest on the page. Then run two executive dinners built from open opportunities, and measure the meetings with economic buyers that follow.

Everything else, including analysts, waits until those three are real.

Coordinate the decision before increasing account activity

Enterprise is not defined by one universal contract value or sales-cycle duration. The useful distinction is often the complexity of approval, implementation and organizational change. Map that complexity for the actual account instead of assuming that a large company needs every element of a traditional enterprise campaign.

Build an evidence path for each requirement

The user needs to understand the workflow, the commercial owner needs a defensible offer, and relevant technical or risk teams need verified scope. One contact may coordinate the process without having authority to resolve every requirement. Give the champion a shareable decision brief that preserves assumptions and limits.

Keep evaluation and implementation connected

A proof exercise should include the system access, sample data and customer participation required to establish the result. Record unresolved dependencies in the handoff. A successful sales presentation does not prove that the account can implement, and a signed agreement does not remove those dependencies.

Use the late security-review diagnostic and pilot decision-date diagnostic when the account has activity but no clear route to a decision.