How I Run a SaaS Value Proposition Workshop (From A SaaS Copywriter)
Ask five people at a SaaS company what the product does and you'll get totally different answers.
Every team member has their own opinion of the value proposition, their own way of describing it.
But in order to build cohesive, strong messaging across the brand, those diverging opinions need to be:
Heard
Tested
Expanded
Edited
And turned into words
Only then, you can have a value proposition that sticks and works its magic across your brand communications. ie tell your audience what you do, how you do it, and why they should care.
I've run over 50 of these workshops with SaaS teams, from early-stage startups to scale-ups and bigger orgs with a lot of opinions flying all over the place.
This is the exact agenda I use: the pre-work, the timings, the six exercises, the tools, and what to do when the whole thing starts to wobble.
Let's get into it. ⬇️
How to run a SaaS value proposition workshop, in short
Short on time? Here's the whole method in eight steps:
Do the pre-work. Gather customer language, audit competitors' messaging, and collect everyone's one-sentence version of the value proposition, separately.
Build a messaging pyramid. One core message, three pillars, and every pillar has to be provable.
Ladder every feature with "so what?" Keep going until you reach the functional, emotional and strategic value.
Flex the language for each persona, without touching the core message.
Write alone, then rank anonymously. Everyone gets 30 seconds to convince, then votes in Mentimeter before anyone debates.
Map every objection to the fear underneath it, and agree how you'll answer each one.
Finish with a sitemap, so every message has a home on your website.
Test the winning message with real buyers before you rebuild your homepage around it.
What is a SaaS value proposition workshop?
A SaaS value proposition workshop is a facilitated session where founders, product, sales and marketing agree on what their software does, who it's for and why it's worth choosing, then turn that agreement into messaging.
The output is a core message, supporting pillars and words the team can use right away.
But "value proposition workshop" means different things to different people.
A value proposition canvas session is about designing the product. You can map a customer profile (jobs, pains, gains) against a value map (products and services, pain relievers, gain creators) to find the fit between them. This is brilliant for deciding what to build, but it’s less helpful for deciding what goes in your homepage hero.
A positioning exercise decides the context your product sits in: the alternatives, what's unique, who cares most, and which market category makes your value obvious.
A messaging workshop, which is what I run, takes positioning and customer insight and turns them into language. What you say first, what you say next, how you prove it, and where it lives.
In practice, my workshop borrows from all of these. But it always ends in words.
"Customers don't care about your unique features, they care what those features can do for them" (April Dunford)
When do you need a value proposition workshop?
You need one when your team can't give the same answer to "what do we do and why should anyone care?"
A few tell-tale signs:
Your website and your sales team are telling different stories. In a Gartner survey of 632 B2B buyers, 69% said they'd come across inconsistencies between a supplier's website and what its sellers told them.
You sound like everyone else in your category. When Wynter surveyed 100 marketing leaders at B2B SaaS companies with $50M+ in revenue, only 6% described their brand as "very distinctive".
Every team has its own version of the pitch. In the same survey, 44% named cross-team alignment as their biggest barrier to consistent messaging.
Something big has changed. A new product, a new ideal customer, a pivot, a funding round. Positioning isn't a one-and-done job; markets move, and your message has to move with them.
When not to run one: if nobody has spoken to a customer in months, or nobody in the workshop is allowed to make the final call. A workshop can't create customer insight out of thin air, and it can't overrule a founder who wasn't there to experience the workshop.
💡 If your messaging is already fraying at the edges, these 10 fixes for inconsistent messaging are a good place to start.
Who should be in the workshop?
Keep the live group small and cross-functional. The people I want on the call:
The founder or CEO, who owns the final decision
Product, who knows what the thing really does (and what's coming)
Sales, who hears the objections every single day
Marketing, who will use the output first
Customer success or support, who knows why customers stay, and why they leave
Everyone else feeds in through the pre-work. I usually recommend more voices in the questionnaire, fewer in the call.
And agree who has the final say before the workshop. Trust me on this one 🙏
What happens before a value proposition workshop?
The workshop is only as good as what goes into it. Most of the thinking happens before anyone joins the call.
1. A questionnaire for every attendee
I send your team a short questionnaire a week or so before. This can be done on Typeform or, my fave, Google Docs, so everyone can collaboratively iterate on the answers.
The questions pull out language, not opinions:
How would our best customer describe what we do to a colleague?
What do prospects usually compare us to, including spreadsheets and doing nothing?
What's the objection you hear most often?
Finish this sentence: "We're the only ones who…"
2. The one-sentence test
The last question is always the same: write our value proposition in one sentence.
On the day, every answer goes up side by side on the first Miro frame. Without names, ain’t no-one trying to value prop’ shame here!
It's a very useful five minutes. Any misalignment is suddenly visible, without anyone having to argue for it. It really gives everyone permission to say, "Oh. We really don't agree, do we?"
3. Your customers' actual words
This is where a good amount of truth comes to light.
➡️ Customer interviews, sales-call recordings, support tickets, and reviews of your product (and your competitors') on sites like G2, Capterra and Reddit.
I pull out the phrases customers use to describe the problem, the before, the after and their doubts.
💡 I go deeper on how to mine your customers' words in my SaaS homepage guide.
4. A competitor messaging audit
Screenshot the hero sections of your five closest competitors, and a couple of the "do nothing" alternatives too. Then line them up.
If you could swap your logo onto their headline and nobody would notice, you've found the problem the workshop needs to fix.
5. A proof inventory
Every number, customer name, case study, review and award you're allowed to use, all in one list. You'll need it for the pyramid, where every claim has to earn its place.
The full value proposition workshop agenda
Here's the whole thing at a glance. It runs to about five hours of working time, split across two sessions, because nobody does their best thinking in hour four of a video call.
Welcome and ground rules: One goal, one decision-maker, no feature pitches
The current value prop reveal: Where the team agrees, and where it doesn't
Exercise 1 – the messaging pyramid: A draft core message and three pillars
Exercise 2 – SO WHAT laddering: The functional, emotional and strategic value behind each feature
Exercise 3 – persona language-flexing: The same core message, in each buyer's language
☕ A lil break for coffee with cameras off to recharge
Exercise 4 – 30 seconds to convince, and the ranking: A ranked shortlist of core messages
Exercise 5 – objection → fear → handling: An objection map for sales and the website
Exercise 6 – the sitemap: Where every message lives
Exercise 1: The messaging pyramid
The pyramid is the backbone of everything else.
At the top sits one core message: the single idea you want every buyer to leave with.
Underneath it sit three pillars, the reasons that message is true.
And under each pillar sits proof.
The rule I hold everyone to: no proof, no pillar.
If a pillar can't be backed by a number, a customer name, a quote or a demo, it's not a pillar. It's a wish. Wishes get demoted to the parking lot, and that one rule does a surprising amount of the arguing for you.
Why three? Because it's about as many reasons as a buyer will remember after one visit to your site. In my experience, five pillars usually means the team hasn't made a decision yet.
If you want the full anatomy, I've written a whole guide to building a messaging pyramid.
Exercise 2: SO WHAT laddering (functional → emotional → strategic)
This is where features finally get translated into value.
Take one feature. Ask "so what?" Write the answer down. Ask "so what?" again. And once more. There is three levels to this:
Functional benefits: what it lets the customer do
Emotional benefits: how that makes them feel
Strategic benefits: what it means for their business, and for them personally in front of their boss
The thinking behind it is decades old. Consumer researcher Jonathan Gutman's means-end chain model showed that people link a product's attributes to the consequences those attributes produce, and those consequences to their personal values. What something has, what it does, and why that matters.
Here's what it looks like with an invented example:
Feature: Automated Slack alerts for failed payments
So what? Your team hears about a failed payment the moment it happens.
So what? No more finding out from an angry customer.
So what? Less involuntary churn, and a finance lead who looks completely on top of things.
❌ Real-time payment failure alerts
✅ Know about a failed payment before your customer does
Exercise 3: Persona language-flexing
Your core message stays fixed, but the language around it bends.
The finance lead, the ops manager and the end user all need to recognise themselves in your copy, but they won't care about the same things.
Different segments have different priorities, and blending them hides which needs matter most.
So for each persona, the team rewrites the core message and the three pillars in that buyer's words. It’s the same promise in a different accent.
Exercise 4: 30 seconds to convince (and the anonymous ranking)
Everyone writes, alone and in silence, the version of the core message they'd use if they had 30 seconds to convince a prospect.
Thirty seconds is generous, by the way. Jakob Nielsen's analysis of Microsoft Research data found that "the first 10 seconds of the page visit are critical" to whether someone stays or leaves.
Then every version goes into Mentimeter, and the team ranks them anonymously before anyone discusses them.
Why that order? Because when psychologists Michael Diehl and Wolfgang Stroebe studied why brainstorming groups underperform, the main culprit was production blocking: only one person can speak at a time, so everyone else's ideas queue up and fade. Their suggestion was to have people develop ideas separately, then come together to evaluate.
Write alone, rank anonymously, then talk. In that order.
Exercise 5: Objection → underlying fear → how we handle it
This is an exercise you might be tempted to skip. You might think you already have a good idea of customer objections and don’t need this. My recommendation is to do it anyway, because the objection a buyer says out loud is rarely the one that stops them.
The JOLT research from Matthew Dixon and Ted McKenna, based on 2.5 million recorded sales conversations, found that 40–60% of lost deals end in no decision at all. Much of that comes down to indecision: too many options, too much information, or doubt that the promised outcome will really materialise.
So, have the team map three columns:
What they say
What they're worried about
How we handle it
That third column becomes your proof sections, your FAQ and half your sales enablement. Not bad for 40 minutes.
Exercise 6: The sitemap (where every message lives)
The final exercise turns strategy into pages.
Which message leads the homepage?
Which pillar gets its own page?
Where does each objection get answered?
This matters more than ever, because buyers now do most of the homework without you.
In Wynter's 2026 survey of 101 B2B SaaS CMOs, 48% said they arrive at sales calls "very familiar" with the vendor, up from 22% a year earlier.
If a message has nowhere to live, it doesn't exist. And if your proof lives only in the sales deck, most buyers will never see it.
(Here are 12 ways to add social proof to your homepage if you're light on it.)
How do you run a value proposition workshop online?
I run all of mine remotely, with four tools. Each one has a specific job:
Google Meet: Talking, breakout rooms, the moments when we need to see faces
Miro: Silent writing, clustering, the pyramid, the objection map and the sitemap. One frame per exercise, laid out in order
Mentimeter: Anonymous ranking, 100-point voting and quick confidence checks
Google Slides: Framing each exercise, examples, and a single "eyes up here" screen when the Miro board gets busy
A few of my best tips for remote workshops:
Split the day. Two sessions of roughly two and a half hours beat one five-hour marathon. Ideas also have time to settle overnight.
Cameras off during silent work. Stanford's Jeremy Bailenson identified four likely causes of video-call fatigue: intense close-up eye contact, the extra effort of producing and reading nonverbal cues, constantly watching yourself, and being stuck in one spot. His suggestions include hiding self-view and defaulting to audio when faces aren't needed. Silent Miro time is the perfect moment.
Build the board before the day. Every frame labelled, every template ready. Nobody should watch you draw rectangles.
Timebox everything, visibly. A timer on screen does more for focus than any polite reminder.
Put a parking lot on the board. Good ideas that don't belong in this workshop still deserve a home. Otherwise people hang on to them and stop listening.
When does a value proposition workshop go sideways?
Across 50 workshops, it's almost always one of two situations: a big organisation where everyone has competing ideas about what the product is, or a team so technical it can't see the product through its customers' eyes.
Here's what's going on in each, and what fixes it.
1. Big organisations with competing, diverging ideas
The bigger the company, the more versions of the truth there are. Sales has one pitch, product has another, and the founder has a third they wrote at 2am three years ago.
Put all of those people in a call, and one of two things happens. Either the loudest (or most senior) voice wins, or everyone politely agrees on a core message none of them will ever use. There's a name for the first one: the HiPPO, or highest paid person's opinion, a term coined at Intuit in 2006.
What helps:
Decide on the decision-maker before the day. Everyone contributes; one person decides. Say it out loud at the start.
Let one sentence do the arguing. Seeing six anonymous answers side by side depersonalises the disagreement. It's the answers that differ, not the people.
Silent first, senior last. Everyone writes and ranks before anyone speaks, and the most senior person comments last, not first, if everyone is comfortable with this.
Rank anonymously. The Mentimeter vote is the one moment when the founder's opinion carries exactly the same weight as the newest sales rep's.
Check conviction, not just agreement. Before you close, ask everyone to rate one statement in Mentimeter: "I could say this to a customer tomorrow." Polite agreement scores low. Real agreement doesn't.
2. Teams too technical to see things through their customers' eyes
We’ve all seen it before: brilliant engineers and product people who know the product so well they can't un-know it.
Psychologists call it the curse of knowledge. In a classic 1990 Stanford study, Elizabeth Newton asked people to tap out the rhythm of well-known songs and predict how many listeners would recognise them. The tappers guessed 50%; the listeners got 2.5%. The tappers could hear the tune in their heads, but the listeners just heard knocking.
That's exactly what happens when a CTO describes the product through its architecture. To them, the melody is obvious. To a buyer, it's knocking.
What helps:
Open with customer quotes, not the product. Before anyone opens a feature list, the team reads what customers actually said about the problem. It puts the listener's view on the board first.
Ladder one feature at a time. SO WHAT laddering forces the translation from what the product has to why it matters, a feature at a time, no skipping.
Read every line aloud, as if to a prospect. Anything that needs explaining gets flagged. Jargon always sounds like clarity to the people who invented it.
Change the ranking question. Instead of "which line is best?", ask "which of these would a customer repeat to their boss?"
💡 None of this means technical teams don't care about customers. They care enormously. They just know too much to hear the product the way a stranger does. That's why an outside facilitator helps enormously.
For more on this, here's why most startup messaging fails (and how to fix yours).
What do you walk away with?
A workshop that ends in a nice Miro board and nothing else was a very expensive afternoon. Within a few days of the second session, the team gets:
A written insights report: what we learned, what we decided and why
The messaging pyramid: one core message, three pillars and the proof behind each
Persona variations: the core message flexed for each buyer
The objection map: every objection, the fear behind it and how we answer it
The sitemap: where each message lives on the website
Hero-section options: two or three ways to open the homepage, ready to test
That last one is the difference between a strategy session and a messaging workshop. The team leaves with words it could ship.
If the homepage is next on the list, my guide to writing SaaS homepage copy picks up exactly where the workshop leaves off.
How do you test your value proposition after the workshop?
Everyone’s favourite message is still just a hypothesis.
Before you rebuild the homepage around it, put the top two contenders in front of real buyers. You don't need big traffic numbers to do it:
Run a five-second test. Show the hero for five seconds, hide it, then ask what the company does. 5–10 participants is usually enough to spot patterns, and treats more than about 80% getting the main message as a good benchmark.
Use B2B message testing. Tools like Wynter put your copy in front of verified B2B professionals in your target roles, and score clarity, resonance, objections and differentiation, with results in under 48 hours.
Talk to customers. Read both options aloud on your next few customer calls and listen to which one they repeat back to you.
If everyone’s favourite loses the test, it doesn’t mean the workshop has failed, it means it’s working!
Value proposition canvas or messaging workshop: which do you need?
It depends on the question you're trying to answer.
Value proposition canvas workshop
Best for: Designing a new product or feature
Key question: Are we solving the right problem?
Core tool: Customer profile + value map
Typical owner: Product
Output: A tested fit between problem and solution
When: Before you build
Messaging workshop
Best for: Explaining a product that already exists
Key question: How do we say why we're worth choosing?
Core tool: Messaging pyramid + SO WHAT ladder
Typical owner: Marketing, founder, or both
Output: A core message, pillars, proof and page-ready copy
When: Before you launch, rebrand or rebuild the website
If you're still working out what to build, start with the canvas. If you've built it and nobody gets it, you need the messaging workshop.
Can you run a value proposition workshop yourself?
Yes, if you have three things:
Real customer research, not assumptions dressed up as research
A clear decision-maker, agreed before the day
A facilitator with no stake in the outcome
It's very hard to facilitate a debate you have a stake in, and even harder when the person you need to challenge signs off your pay rise. That's usually why teams bring someone in.
An outside facilitator can ask the awkward questions, keep the HiPPO in check and hold everyone to "no proof, no pillar" without it becoming personal.
If you're weighing up outside help, here's how to hire a B2B SaaS copywriter.
Want me to run one with your team?
I've run 50 value proposition and messaging workshops for SaaS teams, and every one ends the same way: with words you can use right away.
If your team has five versions of the pitch and needs one, let's have a chat. Or take a look at how I work on verbal brand strategy.
Value proposition workshop FAQs
What is a value proposition workshop?
A value proposition workshop is a structured session where a company's key people agree on what their product does, who it's for and why it's worth choosing. In SaaS, the best ones end in messaging: a core message, supporting pillars, proof and copy the team can use straight away.
How long does a value proposition workshop take?
Allow four to six hours of working time. I split mine into two sessions of roughly two and a half hours, plus pre-work beforehand and a written report afterwards. Anything much shorter tends to skip the objections and the sitemap, which is where the messaging becomes usable.
What tools do you need to run a value proposition workshop online?
Four is plenty: a video call tool (I use Google Meet), a digital whiteboard (Miro), a live polling tool for anonymous ranking (Mentimeter) and a slide deck for framing each exercise (Google Slides). Set up the whiteboard frames before the day, so the session is spent thinking, not building.
Is there a value proposition workshop template?
Yes. My brand messaging framework template is a good home for the workshop's output. For the agenda itself, use the timed table above as your template and adjust the timings to your team.
Can a small startup team run a value proposition workshop?
Absolutely. A small team often makes it easier. With three or four people, you can compress it into a single half-day, but keep the pre-work, the silent writing and the anonymous ranking. They matter just as much with four people as with twelve.
How often should you revisit your value proposition?
Whenever something material changes: a new product, a new ideal customer, a pivot, new competitors or a sales team that keeps rewriting the pitch. Positioning isn't a one-time exercise, because markets keep shifting. As a rule of thumb, sense-check it once a year even when nothing obvious has changed.
Should you hire a facilitator for a value proposition workshop?
If everyone disagrees, or the most senior person has strong views, yes. An outside facilitator has no stake in which message wins, which makes it far easier to challenge assumptions, keep the discussion balanced and hold every claim to the proof test.
