The five growth questions for B2B SaaS

Guide · Frameworks · 6 min read · last verified 2026-07-27

For a B2B SaaS company, a growth plan is the written answer to five questions: where buyers are being lost before they ever reach the website, what to build or publish in response, how to get in front of the people who shortlist software, who ships each piece of work and by when, and whether any of it changed what buyers actually see. The framework itself is laid out in the parent piece on the five questions; this edition is about what the questions become when the product is software sold to businesses — a market where shortlists assemble on category pages and review sites, where the call to action is usually a free trial, and where product-led and sales-led companies have to read entirely different signals.

To keep the discussion concrete, one invented company will run through the whole piece. Call it Relay: a fictional vendor of shift-scheduling software for mid-sized clinics, sales-assisted, with a self-serve trial. Relay does not exist. Every situation it faces does.

How SaaS shortlists form before anyone talks to you

Software buyers rarely begin with vendors. They begin with a category — "scheduling tools for healthcare teams" — and they resolve that category through three surfaces: category pages that group and rank tools, review sites where peers grade them, and, increasingly, AI assistants that summarise both and hand back a small set of names in a sentence. By the time a clinic administrator fills in Relay's demo form, the field has usually been narrowed somewhere Relay could not observe. Larger buyers now run the same pattern formally through procurement; how enterprises discover vendors with AI traces that version of it.

This is the setting for everything that follows. In SaaS, the funnel you can see — traffic, trials, demos — sits downstream of one you cannot, and the five questions are a method for working backwards into it.

Where is Relay losing buyers?

The first question demands named locations of loss, and in SaaS those locations are unusually concrete. Relay's team lists the category pages that cover its market and finds two that omit it entirely. It reads the review-site comparison grids and finds its integrations marked as absent when they exist. It asks AI assistants the questions an administrator would ask — which tools handle credential rules, which connect to the records system the clinic already runs — and finds rivals named, Relay missing, and one answer flatly wrong about how Relay charges.

SaaS adds a loss surface no other business has: the product itself. A free trial is a research channel, and people abandon trials the way they abandon articles — quietly, at a specific step, for a reason nobody recorded. A product-led company loses most of its invisible buyers inside the product; a sales-led company loses them before the first call. Relay, sitting between the two motions, has to map both. The general discipline of finding these losses is covered in the buyers you never see; the SaaS version simply has more named places to look.

What should Relay create?

The second question converts each located loss into an artifact. The unanswered integration question becomes an answer page written in the administrator's vocabulary, not Relay's. The wrong claim about charging becomes a plain page explaining exactly how the pricing model works — not the price list, the model. The absent review-grid data becomes an operational task: correct the listings, and ask happy customers to say in public what they already say in renewal calls.

One creation rule is distinctly SaaS: documentation is marketing. Public docs are read before trials start, quoted in communities, and drawn on by assistants composing answers about what a product can do. A product-led company that hides its docs behind a login is deleting its best answer content. For Relay, opening the integration docs is a bigger visibility move than another quarter of blog posts.

How does Relay reach software buyers?

Reach in SaaS divides by motion. Sales-led Relay needs presence where economic buyers do diligence: the review grids, the category round-ups, the practitioner communities where practice managers compare notes, and the sources assistants lean on when they compose a shortlist. A product-led company would add a different layer entirely — template galleries, integration marketplaces, the surfaces where end users rather than buyers first touch a product and then carry it inward. The two lists barely overlap, which is why copying another company's channel mix fails so reliably. The selection method lives in choosing channels your buyers already use; the SaaS-specific input is knowing which motion each channel actually serves.

Who ships the work?

Here SaaS plans die most often, because the work crosses org lines. The trial-abandonment fix is a product ticket. The docs rewrite belongs to a technical writer. The pricing-model page needs sign-off from whoever owns commercial terms. A growth plan authored inside marketing, listing actions that only product can ship, is a wish list — and wish lists lose to roadmaps every sprint. Relay's version of the fourth question is therefore blunt: for each action, is the named owner inside the team that controls that surface, and have they agreed to a date? If the answer is no, the action is not in the plan; it is in a negotiation.

Did anything move?

The final question splits by motion again. Product-led signals live in the product: did signups from the rewritten page activate, did the trial stop leaking at the step that was fixed. Sales-led signals arrive later and softer: prospects turning up to first calls already citing the integration page, the wrong claim about charging fading out of assistant answers. Both need the same discipline underneath — record what the category pages, review grids and AI answers said about Relay before the work, then re-check the identical set on a scheduled date, so the comparison is honest. This before-and-after loop is what a market growth intelligence platform automates; Magrios, for instance, snapshots that picture at the start and re-runs it against the same benchmark, so a SaaS team can tell a genuine shift from background noise.

Relay's five answers on one page

The questions do not change because the product is software. What changes is how sharply they can be answered: SaaS leaves fingerprints — grids, docs, trials, assistant answers — everywhere buyers pass. A team that reads those fingerprints in order will write a shorter plan than its competitors, and a considerably harder one to argue with.