Free template + LLM skill
A free Google Doc template and LLM skill for B2B SaaS founders and product marketers who've settled their positioning and need the whole company describing the product the same way.
By Shannon Kearns, product marketing and go-to-market consultant. Updated November 16, 2026.
Research inputs, one key message, core messaging, entry points and buyers, and a validation appendix. Every section has a short purpose note and bracketed prompts to replace.
Drop it into Claude, ChatGPT or another model along with your positioning and research. It drafts each section in the same order with the same IDs, and it marks missing proof as a gap instead of making something up.
B2B SaaS founders and product marketers who already know who they're for and what makes them different, and who keep hearing five versions of the pitch from five people on the team.
If you haven't picked a target segment or agreed on your positioning yet, start there. This template will just put your guesses in neater boxes.
Key takeaways
A product messaging template for B2B SaaS is a fill-in document that turns approved positioning and buyer research into the language your whole company uses. Mine has one key message, the segment and problem, a value proposition with pitch and descriptions, value and outcome pillars, entry-point messages by buying trigger, messages by buyer role, and an appendix that checks every pillar against real features and proof.
When B2B SaaS messaging goes sideways, most teams blame the copy and start rewriting the homepage. More often, nobody wrote the positioning down, so every writer filled the gap with their own version.
Below is how I fill one in, section by section.
Positioning is the choice underneath. It decides who the product is for, what it competes with and why it wins. Product messaging is the language the company runs on once that choice is made: the main promise, the pillars that back it up, and how the opening changes depending on who's buying and why.
That order matters more in B2B SaaS than almost anywhere else, because a single deal can involve a champion, an economic buyer, IT and an end user who all hear the product described by different people on your team. If your homepage could be pasted onto a competitor's site and still make sense, go back to positioning first. I wrote about that in how to stand out when you sound just like every competitor.
Since the template sits on top of positioning, the prep is mostly about getting your inputs written down where everyone can see them. Positioning is one piece of an early-stage go-to-market strategy, and if the bigger decisions around it are still open, the messaging will keep changing with them.
The first section of the template, Research inputs, asks you to record these before anything else:
Keep only approved sources and evidence in the doc. If you're working from a hunch, write it as a hunch.
Part 1 of the template is core messaging, and it starts with the one key message: a single sentence that connects the buyer's problem, your distinctive approach and the outcome they want.
From there, 4 sections build on each other:
| Section | What it answers | Where you'll use it |
|---|---|---|
| 1. Segment and problem | Who this is for, the problem in their words, and why current solutions fall short | Every other section |
| 2. Tagline, pitch and descriptions | The value proposition at different lengths | Homepage, boilerplate, app marketplace and directory listings, intros |
| 3. Value pillar messaging (VP1 to VP4) | The differentiated promises and how to say each one | Website sections, sales deck, product pages |
| 4. Outcome pillar messaging (OP1 to OP5) | The results buyers get, tied to how and to proof | Case studies, ROI conversations, late-stage sales |
Segment and problem. Describe the priority customer (company type, size, maturity, geography and buying context) and the problem in the buyer's own words, including what it costs them and why it hasn't gone away. Then list the alternatives they use today and where each falls short. Include spreadsheets, building it internally and doing nothing. In B2B SaaS, "no decision" is the competitor plenty of startups lose to most.
Tagline, pitch and descriptions. The value proposition follows a fill-in line: for [target segment] facing [problem], [product] is the [category] that delivers [outcome] through [distinctive approach]. Each tagline option leads from a different place, and you record which one tested best. The elevator pitch, the 50-word description and the 100 to 200-word description are the same story at different lengths, so a sales rep on a demo and a visitor on your pricing page hear the same thing.
Value pillars. These are the differentiated promises, usually 4. Each pillar gets a main message, a tension alternative and supporting messages. The tension alternative is the same promise led by the cost of the current situation instead of the upside. Some buyers respond to "get to X faster" and some respond to "stop losing Y every month," so having both ready saves a rewrite later. Supporting messages end with either verified proof or a written note that proof is missing.
Outcome pillars. Up to 5 results the buyer wants, each stated in concrete terms. Every outcome needs a mechanism (how the product gets them there) and a validated metric with a baseline, timeframe and source. If you don't have the metric yet, leave the bracket in and flag it.
Once the core is written, Part 2 keeps the positioning and pillars the same and changes the opening, emphasis and proof depending on the buying situation.
Entry-point messages. A buying trigger is the event that brought someone to market: a new leader, a tool that failed at renewal, a growth target, a compliance deadline. For each trigger (T1 to T4) you write the first line that buyer should hear, naming their immediate tension or goal, then a supporting line that connects their situation to the core promise.
Buying triggers, start to finish. This table follows each trigger all the way through: the pain they've lived with, their buying lens and non-negotiables, the outcome they must get, and which value themes to lead with, referenced by ID (for example, VP2 then OP1). Underneath sit validation notes with missing proof by trigger, an owner and a next step. Keep customer details and research links restricted until they're approved for use.
Message by buyer. The template has 6 sample rows to replace with your actual buying committee. For each role, note their primary concern and personal stakes, the VP and OP IDs that matter most to them, the proof they need, and the objection they're likely to raise with what would resolve it. A CFO and an end user can hear the same pillars in a different order.
Part 2 goes faster with someone from sales in the working session, since they hear the triggers and objections every week.
The appendix checks each value pillar (VP1 to VP4, same names as section 3) against the features that actually deliver it, the benefits to the buyer and the proof. Proof means evidence with a metric, baseline, timeframe and source, plus its permission status, plus any gap with an owner and a next step.
Fill this in before anything goes external. If a pillar has no feature behind it, it's a hope, and you'll want to know that before sales repeats it to a prospect. If it has features but no proof, it can stay, as long as the gap is written down and someone owns closing it.
With the parts defined, here's the working order for the Google Doc. It's built so you can run it in a workshop with the tables on screen.
If you're using the LLM skill, give the model your positioning, research notes and approved evidence before you ask it for anything. It drafts each section in the same order and leaves brackets where your inputs run out. Treat its output as a first draft for the workshop. You and your team still make the calls.
The template is enough when your positioning is agreed, the research exists, and someone on the team has the time to own the writing. Plenty of B2B SaaS teams can get a solid first version done that way.
It's harder when the inputs aren't there. If the team still disagrees about who the customer is, there's no recent buyer research, or a launch date is coming up fast, filling in a template mostly records the disagreement. That's when it's worth getting help. If you're weighing who to bring in, I wrote about how to choose a product positioning consultant for a startup, and there's more on how I work with B2B SaaS teams on the product marketing consultant page.
Positioning is the decision about who the product is for, what it competes with and why it wins. Messaging is the language that expresses that decision in every channel. You can write messaging without positioning, but each writer ends up inventing their own version of it.
The template starts with 4 value pillars and 5 outcome pillars. Add or remove pillars to fit your research. If you can't find a feature that delivers a pillar, cut it.
It's the same promise as the main pillar message, led by the cost of the buyer's current situation instead of the upside. Writing both up front lets sales and marketing pick the version that fits the buyer in front of them.
Yes, if you give it your own positioning and research to work from. That's what the LLM skill on this page is for: it walks the model through each section, keeps the IDs consistent, and marks missing proof as a gap. Without real inputs, any model will give you generic messaging that could belong to any company in your category.
Update it when something it's built on changes: the positioning, the target segment, a new buying trigger, or new proof you're cleared to use. Keep the version and date in the header line so everyone knows which one is current.
Ask me anything about your business. 30 minutes. No cost.
There's no form gauntlet and no discovery deck. We'll talk about what you're trying to do, and if I'm not the right fit, I'll tell you who might be.