B2B SaaS Product Launch PlaybookArchana Panda
Module 4 of 9

Positioning And Messaging

Plenty of buyers leave a first call able to name the category and little else. The website says one thing and the sales deck says another, so the buyer never hears a single reason to choose you. Every rep improvises their own version, and none of them match the launch email that brought the buyer in.

Positioning settles that reason before anyone writes copy. It defines who the product is for, what it replaces and the one difference that matters most to that buyer. A messaging framework then turns the position into words every team uses the same way, from the homepage to the renewal call.

You'll leave with a positioning statement, value pillars backed by proof, a message hierarchy and value propositions tailored to each persona.

Positioning Statement

The statement is for your team, not for customers, so plain wording beats a clever line. The format below is adapted from Geoffrey Moore's in Crossing the Chasm, and every field should trace back to your market research and ICP.

For

The target customer, as defined in your ICP.

Who

The problem they need solved, in their words.

The product is

The category buyers will file it under.

That

The main outcome it delivers.

Unlike

The alternative buyers use today, named or described.

It

The difference that alternative can't match.

Value Pillars

Pillars are the few claims you want every buyer to remember. Two to four is enough, and each one needs proof a buyer can check, or it reads as marketing.

Pillar Buyer outcome What makes it possible Proof

Message Hierarchy

The hierarchy keeps long and short copy consistent. A homepage hero uses the top line alone, and a sales deck works down through every level, but neither should ever contradict the other.

Headline promise

One sentence that states the main outcome for the buyer.

Supporting messages

One sentence for each value pillar.

Proof points

Numbers, customer stories or product facts under each message.

Call to action

The single next step you want the buyer to take.

Value Propositions By Persona

The positioning stays fixed, but each persona needs to hear it through their own concerns. Write one value proposition per persona from your committee map, in the language their pains and goals already use.

Persona What they care about Value proposition

Worked Example

The company and its proof points are fictional and illustrative.

Positioning Statement

For

Sales-led companies with 10 to 200 employees and three to 25 salespeople.

Who

Have outgrown spreadsheets or a free CRM and lose deals to missed follow-ups.

The product is

A CRM with a built-in AI assistant, part of a business-software suite.

That

Runs the path from first call to paid invoice in one system.

Unlike

Free CRM tiers, whose costs climb at higher plans, and enterprise CRMs that need an admin to run.

It

Includes invoicing, help desk and AI on one flat per-seat price.

For sales-led companies with 10 to 200 employees who lose deals to missed follow-ups, the product is a CRM with a built-in AI assistant that runs the path from first call to paid invoice. Unlike free tiers and admin-heavy enterprise CRMs, it includes invoicing, help desk and AI on one flat price.

The positioning statement read as one sentence. Each highlight comes from a field in the table.

Value Pillars

Pillar Buyer outcome What makes it possible Proof
Deal to invoice in one place No re-keying between sales and billing CRM and invoicing share one customer record Setup time from trial accounts, to be measured
An assistant that handles admin Reps spend more time selling AI logs calls and drafts follow-ups Hours saved per rep, from beta users
A price that holds as you grow No surprises at renewal One flat per-seat price on every paid plan Published pricing page

Message Hierarchy

Headline promise

Every deal, from first call to paid invoice, in one CRM your team will use.

Supporting messages

Sales and billing share one record. The assistant logs calls and drafts follow-ups. Your price per seat stays flat as the team grows.

Proof points

Setup time, hours saved per rep and the published price, each to be confirmed in beta.

Call to action

Start a 14-day trial with your own pipeline.

Headline promiseEvery deal, from first call to paid invoice, in one CRM your team will use.
Supporting messagesOne record for sales and billing. An assistant for the admin. A flat price per seat.
Proof pointsSetup time, hours saved per rep and the published price.
Call to actionStart a 14-day trial with your own pipeline.
The message hierarchy from the worked example. Short copy uses the top level, and long copy works down through every level.

Value Propositions By Persona

Persona What they care about Value proposition
Head of Sales Forecast accuracy and rep adoption A pipeline your reps keep current, because the assistant does the logging for them.
Founder or CEO Visibility and predictable cost Your whole pipeline on one screen, at a price that doesn't jump as you hire.
Sales reps Less admin Calls logged and follow-ups drafted, so the end of the day isn't spent on data entry.
Operations or finance lead Clean data and contract terms One customer record from quote to invoice, with no exports between systems.

Mistakes To Avoid

  • A tagline in place of a position - A catchy line with no defined buyer or alternative gives sales nothing to work with.
  • Pillars without proof - A claim nobody can check reads as marketing, and buyers discount it.
  • Messaging that changes by team - If sales, marketing and support each describe the product their own way, the buyer hears three products.
  • One message for every persona - The founder and the rep care about different things, and copy written for one leaves the other unconvinced.

Created by Archana Panda. Licensed under CC BY 4.0.