B2B SaaS marketing
Market to a committee, survive procurement, then grow the account
B2B SaaS is narrower than SaaS. The purchase is approved by a group, blocked by security review, negotiated by procurement, and most of the revenue arrives after the first contract through seats you already sold.
Buying behaviour
How your customers actually decide
Strategy follows this, not the other way round. Everything on this page is downstream of how the decision genuinely gets made.
- A group decides and every seat asks something different: the champion needs a case for change, the budget holder cost and risk, the technical owner integration detail, the reviewer controls and evidence. Progress stops wherever there is nothing to read.
- The strongest competitor is doing nothing. Staying with the current tool or the current spreadsheet has no approval cost and no career risk, so material that quantifies the cost of the status quo outperforms material describing your advantages over a named rival.
- Peer evidence outranks vendor claims at every stage. Buyers ask people in similar roles at similar companies, read community threads, and increasingly ask an assistant to summarise what other people have said, which means the view forming about you is assembled from sources you did not write.
- Existing integrations act as a hard filter rather than a preference. If the product does not connect to the systems of record the customer already runs, the evaluation ends there regardless of how much better everything else is.
- Security and compliance posture is checked early by larger buyers and increasingly by mid-market ones. A published certification status and a clear answer on data location can move a company from being reviewed to being shortlisted before a sales conversation happens.
- Renewal is a purchase decision made again with more information. Usage data, support experience and whether the promised roadmap arrived all feed into it, which is why the marketing promise made at acquisition shows up two years later as either expansion or contraction.
Search behaviour
What your customers are typing
Building the internal case
Made by a champion who is not shopping, they are preparing to ask permission.
- how to justify [category] budget to finance
- [category] roi calculation
- business case template for software purchase
- cost of not replacing [legacy process]
- how to run a software evaluation internally
Vendor risk and security review
Searched by a reviewer with a veto and no interest in your product. The searches almost nobody publishes for.
- [vendor] soc 2 type ii status
- [vendor] sub-processors list
- [vendor] data residency options
- [vendor] penetration test summary
- standard security questionnaire responses [category]
Procurement and contracting
The stage where a deal quietly stalls, and the material that removes the stall is rarely public.
- [vendor] terms of service liability cap
- [category] enterprise agreement negotiation
- software vendor onboarding requirements
- annual versus monthly billing software procurement
Fit, integration and rollout
Asked by the person who will own the tool after purchase, and a common source of late objections.
- [product] [system of record] integration
- how long does [category] implementation take
- [product] user provisioning sso
- migrating from [incumbent] to [category]
- [product] admin permissions and roles
These are examples of how customers in this market search, drawn from keyword research and from the questions that come up on sales calls. They are illustrative, not a volume claim — the actual demand in your area is something we size before recommending anything.
Measurement
What we report on, and what we ignore
Sessions are not on this list. These are the numbers that tell you whether the marketing is producing customers.
- Net revenue retention, reported alongside acquisition rather than in a separate deck
- Expansion revenue from existing accounts attributed to marketing activity
- Account coverage: the share of target accounts with more than one engaged stakeholder
- Number of distinct roles engaged per open opportunity, since single-threaded deals stall
- Qualified demonstrations held with the right committee composition, not demonstration count
- Security and procurement review duration, tracked as a cycle time marketing can shorten
- Pipeline and closed-won segmented by contract value band, never blended across motions
- Cost of acquiring recurring revenue, held against contribution rather than against booking value
What usually goes wrong
Where B2B SaaS marketing tends to fail
B2B software is not a smaller version of consumer software with a longer form. The person who wants your product cannot buy it on their own, and the people who can stop them will never visit your homepage.
That is the constraint everything here is written to: a purchase approved by a group, delayed by a review nobody warned you about, negotiated by someone whose job is to reduce what you charge, and then expanded — or not — over the following three years.
- The deal disappears after the champion is convinced.
- A demo goes well, the champion is enthusiastic, and then nothing happens for five weeks. What is happening is an internal process: a business case circulated to a finance approver, a review by whoever owns the systems it touches, and a conversation with somebody responsible for vendor risk. None of them received anything from you. Deals do not stall because the champion lost interest; they stall because the champion ran out of material.
- Security review arrives as a surprise and costs six weeks.
- A questionnaire lands with a hundred and forty questions about access control, encryption, sub-processors, breach notification and business continuity. It is answered by an engineer between other work, returned incomplete, and queried. Companies that publish this information in advance take that entire phase out of the critical path and are found by the reviewers directly, which is faster for everyone including the reviewer.
- Procurement asks for documents marketing has never seen.
- Insurance certificates, financial stability evidence, data processing terms, accessibility conformance statements, supplier codes of conduct and reference customers who are permitted to be named. These requests are routine on the buying side and treated as an interruption on the selling side. Having them ready and consistent is worth more in a competitive process than another feature comparison, because it signals a company that has done this before.
- Growth is reported as new logos while the base leaks.
- Acquisition is visible, well instrumented and celebrated. Contraction — seats removed at renewal, downgrades, quiet non-renewals — is reported elsewhere, later, by a different team. A business adding meaningful new revenue and losing nearly as much from the existing base is described in one report as growing and in another as flat, and marketing is usually working from the first.
- One motion is being stretched across two very different deal sizes.
- A self-serve signup path works for a team buying five seats on a card. It cannot serve a two-hundred-seat purchase that requires legal review, single sign-on, a security assessment and an invoice. Running one motion across both means either loading friction onto small customers who would have converted alone, or presenting large buyers with a process their organisation cannot accept.
Where the money goes
The channels that earn their place here
In priority order for this business, not a menu. Anything not on this list is something we would need a specific reason to recommend.
Ranking for the questions each reviewer asks
Business case searches, integration questions, implementation timelines and vendor risk queries are made by people who never look at a homepage. Publishing properly for them puts your own answer in front of the seats that hold a veto, and it is uncontested ground because almost every competitor is writing for the champion instead.
Coverage across every seat in a named account
When the market is a list of companies rather than an audience, the measure is how many relevant roles inside each target account have engaged with something. Single-threaded opportunities stall when one person changes job. Programmes built around the account rather than the lead are the only structure that matches the way the purchase is genuinely approved.
A trust centre and the proof a committee can cite
A public page carrying certification status, sub-processors, data location, uptime history and a completed standard questionnaire takes a phase out of the sales cycle. Alongside it, original data and named authorship give a champion something with standing to attach to a paper they have to defend internally.
Reaching approvers who never search
Finance, security and operations stakeholders do not research your category and cannot be captured by demand capture. Targeting them by company and role during an evaluation they are part of but not leading is one of the few ways to influence a seat the champion cannot brief on your behalf.
Measurement that reaches retention and expansion
Connecting the marketing systems, the CRM, product usage and billing so revenue can be read as new, expansion and contraction rather than as one growth line. Until that exists, marketing optimises for the half of the business it can see, which in a seat-based model is frequently the smaller half.
The website
What the site has to do for this customer
- A trust centre reachable without a sales conversation: certification status, sub-processors, data residency, uptime history
- A completed standard security questionnaire available on request, and said to be available in public
- Procurement material ready and consistent: processing terms, insurance position, continuity, accessibility conformance
- A page written for each seat on the committee, not one page written for the champion and four for features
- Integration pages with real detail per system of record, since a missing connector ends the evaluation
- Implementation and onboarding described honestly, including what the customer has to supply and how long it takes
- Pricing framed for the way the purchase is approved: contract terms, seat structure, and what moves a customer up a tier
- Named customer references cleared for publication, with the permission recorded rather than presumed
- An existing-customer path that does not route through acquisition content, because expansion starts with people already inside
Constraints
What the rules allow, and what they do not
Security and certification claims have to be exactly accurate, and the distinctions matter commercially. Holding a completed audit report, being mid-audit, and being aligned to a framework without an audit are three different states, and a buyer’s risk team will ask for evidence of whichever one you claimed. Overstating it is the kind of error that ends a deal at the final stage and is remembered afterwards.
Customer naming and logo use are governed by the contract rather than by goodwill. Many agreements restrict public reference to the relationship, some require written approval per use, and buyers in regulated sectors frequently decline entirely. Permissions should be recorded with a date and a scope, not assumed from a friendly conversation.
Material received during a procurement process usually arrives under confidentiality. Questionnaire responses, architecture documents, tender material and pricing benchmarks cannot be reused in marketing even when nothing sensitive is quoted, and the restriction commonly survives the end of the engagement.
Accessibility conformance is becoming a procurement requirement rather than a preference, particularly in public sector and large enterprise buyers, and the applicable standard differs by jurisdiction. Where you sell into those markets, the product and the marketing site both need to meet it and to be able to evidence it.
Claims about automated or model-driven features attract growing scrutiny in several markets, including requirements to disclose how customer data is used. Where a capability is described, it should reflect what the product does today rather than what is planned, and it should be reviewed by your own counsel rather than by us.
Questions
Questions we get from this industry
Our deals stall after the demo. What should marketing be producing?
Material for the people the champion has to convince. In practice that is four things they do not have: a cost and risk summary for the budget holder, an architecture and integration note for the technical owner, a security and controls package for the reviewer, and contract and reference detail for procurement.
Most companies have one of the four. The deal then stops at whichever seat is unserved, and it is recorded as a lost opportunity rather than as a content gap, so it never gets fixed.
Should we publish our security documentation publicly?
Publish the layer that does not need to be gated: certification status and dates, sub-processor list, data residency options, uptime history, and a summary of how you handle access and incidents. Keep the full report and penetration test details behind a request.
The benefit is twofold. Reviewers find the answers without waiting for your team, and the questionnaire phase shortens materially. It also gets found in search by exactly the person who would otherwise be the reason your deal is late.
We are told to focus on expansion but marketing is measured on new business. How does that change?
By changing what gets reported before changing what gets done. Revenue split into new, expansion and contraction, with retention shown next to acquisition, usually reframes the conversation on its own because the net number is often very different from the gross one.
Then the work follows: adoption and onboarding material, content aimed at adjacent teams inside existing customers, and campaigns triggered by usage rather than by the calendar. It is unglamorous and it compounds in a way acquisition does not.
We sell both self-serve and to larger organisations. Should the marketing be split?
The motions should be, and the brand should not. Below a certain contract value a human sales process cannot pay for itself, and above it a self-serve path cannot satisfy the review and contracting requirements the money brings with it.
What works is a genuinely self-serve route that stays self-serve, a clearly separated route for larger buyers, and an honest handover point defined by seat count or contract value rather than by who happens to fill in a form.
Our target market is only a few hundred companies. Is that too small for marketing?
No, but it rules out volume thinking. With a list that size the objective is coverage of the accounts and the roles inside them, not reach, and search volume becomes a poor guide to opportunity because twenty of the right searches a month can be a meaningful channel at enterprise contract values.
It also changes the measurement. Judging that programme on lead count will make it look like a failure, whereas engaged roles per account and inclusion in evaluations describe what is actually happening.
How is this different from your SaaS page?
That page covers software products generally, including self-serve businesses where an individual can buy without asking anyone. This one is about the narrower case where a team is buying, a committee approves and a review process stands in the way.
The practical difference is where the work goes. A self-serve business invests in removing friction between a visitor and first use. A committee sale invests in material for people who will never touch the product, and in the retention and expansion revenue that arrives after the first contract.
Find out what is realistically winnable in your market
A strategy call is a working session on your B2B SaaS business specifically — your area, your competitors, the searches that matter and what it would take to compete for them. If we do not think we can move it, we will tell you.
If we don't deliver the work we agreed to deliver for reasons within our control, you don't pay for the undelivered work. Read our guarantee
Last updated · Reviewed by Zubair Afzal