Brand positioning for B2B SaaS growth
a practical how-to

Brand positioning for B2B SaaS growth
Written by
Passionate Designer & Founder
Brand positioning for B2B SaaS growth starts before your website, your pitch deck, or your product copy. Here's how to build it from the ground up.

Brand positioning for B2B SaaS growth: a practical how-to
Brand positioning for B2B SaaS growth is not a tagline exercise. It is the upstream decision that determines whether your sales cycle runs 90 days or 9, whether you compete on price or on category, and whether your product design actually converts the buyers you want.
Most SaaS founders get this backwards. They build the product, hire a designer, write some copy, and then ask: how do we position this? By that point they are already locked into execution decisions that conflict with each other, and the positioning work becomes a retrofit that never quite fits. Have a quick question about brand positioning for b2b saas growth? Read our expert answers on brand positioning for b2b saas growth.
Go deeper: Brand strategy as a growth lever · Tech product branding · Developer-first brand identity · Infrastructure SaaS branding · API product brand strategy · Category design for B2B · Brand-led growth · Brand-led acquisition vs performance marketing · Why a brand system needs demand
Before you start: inputs you need in the room
Positioning work without raw material is just opinion. Before running any framework, you need three things on the table: at least 8-10 customer interviews (recorded, not paraphrased by your sales team), a clear view of which deals you lost in the last 6 months and why, and an honest map of the alternatives your buyers actually compare you against. Not the alternatives you think they compare you against.
The mistake I see most often is founders skipping the lost-deal audit. They talk only to happy customers, build positioning around the stories those customers tell, and then wonder why conversion from trial to paid sits at 4% instead of 12%. The signal is in the losses, not the wins.
One more input worth having: your current revenue concentration. If 60% of your ARR comes from one vertical, your positioning should probably reflect that specificity rather than paper over it with broad language about serving any company that has a workflow problem.
Use jobs-to-be-done to understand the real problem
Jobs-to-be-done (JTBD) is the most useful lens for B2B SaaS positioning because it reframes the question from what does our product do to what is the buyer hiring our product to accomplish. Those are not the same question, and the gap between them is where most positioning goes wrong.
The JTBD framework, developed by Clayton Christensen and later operationalised by Bob Moesta, asks you to identify the functional job (ship reports faster), the emotional job (stop feeling exposed in board meetings), and the social job (look competent to my CFO). In B2B SaaS, all three layers exist. Ignore the emotional and social layers and your messaging sounds like every other vendor in your category.
A concrete way to run this: take your best 5 customer interviews and code them against the three layers. Look for the sentence that appears, in some form, across at least 4 of the 5. That sentence is the job. It is probably not on your current homepage.
For a Series B compliance SaaS we worked with, the functional job was obvious: automate audit trails. But the emotional job, which kept surfacing in interviews, was: stop being the person who gets blamed when something breaks. That distinction changed the entire positioning frame, from efficiency tool to risk-transfer product. Those two frames attract different buyers, justify different price points, and require completely different product design approaches. The product design decisions for a SaaS built around risk transfer look nothing like those for an efficiency tool.
Use your JTBD to shape your positioning statement
A positioning statement is an internal document, not a tagline. April Dunford's framework from Obviously Awesome is still the most actionable structure for B2B SaaS: define your best-fit customers, name the category you are competing in, state your differentiated value, and identify the proof points that make that claim credible. Four components, not one sentence. The temptation to collapse them into a single punchy line before the internal work is done kills more positioning projects than anything else.
The structure looks like this in practice. Best-fit customer: mid-market finance teams in regulated industries with 20-100 users. Category: audit automation. Differentiated value: the only tool that generates regulator-ready documentation without a dedicated compliance hire. Proof: SOC 2 Type II certified, used by 3 of the top 10 US regional banks.
Notice what that statement does not contain: the word unique, the phrase best-in-class, or any claim that could apply to a competitor without modification. If your competitor could copy-paste your positioning statement and replace only the company name, it is not positioning. It is category description.
Break up with the word "unique"
This one deserves its own section because it costs real money. Every SaaS positioning document I have reviewed in the last three years contains the word unique at least twice. Every single one. And in almost every case, the claim it attaches to is either unverifiable, temporary, or shared by at least two direct competitors.
Unique is a word that signals the writer stopped thinking. Replace it with a specific, time-bounded, evidence-backed claim. Instead of unique AI-powered recommendations, say: recommendations that improve over 90 days of usage, with a documented 23% reduction in manual review time for customers in the 50-500 seat range. That claim can be tested, referenced, and believed. Unique cannot.
The same applies to industry-leading, cutting-edge, and innovative. If your positioning relies on adjectives rather than mechanisms, the positioning has not been done yet.
Choose a name aligned with your positioning
Naming is a positioning decision, not a branding afterthought. A name that signals your category clearly reduces the cognitive load on buyers and cuts the amount of positioning work your sales team has to do on every first call. A name that is deliberately abstract or clever adds friction unless you have the budget to buy your way into category definition the way Salesforce or HubSpot did.
For early-stage B2B SaaS, the practical rule is: your name should either describe the job (Calendly, Expensify) or be distinctive enough to own a clear search term within 18 months. Abstract names that do neither tend to emerge from naming exercises optimised for domain availability and founder preference rather than buyer clarity, and they cost you 6-12 months of extra content and sales effort to explain what you do.
The tradeoff is real. Descriptive names date faster, can limit category expansion, and are harder to trademark. You are trading long-run flexibility for short-run clarity. For most Series A and B SaaS companies, short-run clarity is the right trade.
Communicate your positioning in a way that connects to customers' emotions
Rational positioning statements need to convert to emotional messaging. The positioning statement lives in your internal brief. What goes on your website, your sales deck, and your onboarding flows is the emotional translation of that statement, targeted at the specific emotional job your JTBD research uncovered.
Emotional does not mean sentimental. In B2B SaaS it means: does your messaging make the buyer feel understood before it explains anything about your product? The fastest test is to read your current homepage headline to a target buyer and ask: does this describe your situation? If they say yes, the positioning is landing. If they say I guess so, it is not.
A well-designed website with weak positioning messaging will produce lower conversion rates than a mediocre design with sharp, emotionally accurate copy. We have run this experiment enough times to be confident in the direction of the effect. The design decisions that make a SaaS website convert are downstream of positioning clarity, not upstream of it.
One structural recommendation: lead with the problem in the buyer's language, then the consequence of that problem remaining unsolved, then your mechanism, then proof. This is not a new formula. It works because it mirrors the structure of how buyers already think when they arrive at your site.
Get testimonials that actually do positioning work
Testimonials are proof points, not decoration. A generic five-star quote from a happy customer does almost nothing for positioning. A quote that names the specific job, the before-state, and the measurable after-state reinforces every claim your positioning makes.
The practical way to get these: during customer interview cycles, ask specifically what were you worried about before you started using this, and what does success look like 6 months from now. Those answers, lightly edited for clarity, produce testimonials that do positioning work rather than social proof theatre.
Brand alignment matters here too. A testimonial from a 5-person startup on a product positioned for 200-seat enterprise teams actively undermines conversion with your target buyer. Audit your current testimonials against your best-fit customer definition and remove or replace the ones that create category confusion. In the SaaS onboarding work we have shipped, misaligned social proof in the first 30 seconds of a user's session is consistently one of the top three friction points in session recordings. The same principle applies on marketing pages. You can go deeper on this in our piece on SaaS onboarding design.
Brand positioning and your product design surface
This is the part most positioning guides skip entirely. Your positioning statement should be a direct input into your product design decisions: what gets foregrounded in your UI, what language appears in empty states and tooltips, what the onboarding sequence covers in the first three sessions. If your positioning is built around risk transfer and your product design leads with speed metrics, you have a misalignment that confuses buyers who arrive knowing your marketing message and then experience something different inside the product.
On a McKinsey workstream we shipped a tool redesign where the product had been built around efficiency language internally but was being sold on compliance outcomes externally. The gap between the two surfaces was costing the sales team 2-3 hours per deal in re-explanation work. Aligning the product language with the positioning statement, which was fundamentally a design and copy decision rather than an engineering one, reduced that to under 30 minutes.
Across 40+ retainer engagements with funded SaaS teams, the pattern holds: the further the product design is from the positioning statement, the higher the support burden, the longer the sales cycle, and the lower the net revenue retention. These are not soft outcomes. They show up in the numbers within two quarters of a positioning realignment.
Which type of positioning fits your stage
Positioning frameworks list four or five types. In B2B SaaS these are the ones you'll actually choose between:
Use-case positioning names the exact situation where you win, like Calendly and the five emails it takes to find a meeting time. It's the only type that works when buyers don't yet know they have the problem, and it shortens sales cycles because buyers recognise themselves before the first call.
User-based positioning owns one audience, which is what vertical SaaS does by definition. Choose it when buyers respond faster the more precisely you name their world.
Value-based positioning owns an outcome, such as cutting churn by 20%. It's the most durable choice, but you need at least five reference customers who actually reached that number before you lead with it.
Attribute positioning claims a product characteristic, like Stripe's developer-first payments. It works in infrastructure and tooling, as long as competitors can't copy the feature within a year.
Competitor-based positioning defines you against an incumbent. It only works when that incumbent is already the default in the buyer's mind, and it ties your story to their roadmap.
Category design names a new category, as Salesforce and HubSpot did. It takes 18 to 36 months of consistent investment, so most growth-stage teams shouldn't start there.
Price and quality positioning rarely hold in software: low prices invite a race to the bottom and make moving up-market harder, and quality is expected rather than a reason to choose you. Your price still sends a signal, though. A tool at $49 a month gets filed differently from one at $2,000, whatever the feature list says. Pick one primary type that matches the proof you have today and how well your buyers understand the category. Mixing two or three types in one statement gives you positioning that is accurate and incoherent.
Map the market before you commit
A positioning map plots 5 to 8 competitors on two axes your buyers actually weigh. Price against quality tells you nothing new. Ask 8 to 12 buyers who compared you with a competitor which factors decided it, and turn the answers that keep coming back into axes, for example setup time against configurability. Place competitors based on evidence (their homepage hero, G2 reviews, what comes up on sales calls) and look for the quadrant with demand and no clear owner. The map gives you a hypothesis, not proof, so only claim an open quadrant if you have the case studies to defend it. We build these maps in our brand strategy sprint before any visual work starts.
Once you've chosen, the classic statement works as a quick internal check next to the structure above: "For [target customer] who [buying trigger], [brand] is the [category] that [key benefit] because [reason to believe]." Push hardest on the "because". Then read the claim to three recent prospects or customers. If fewer than two recognise what they were looking for, the positioning solves your problem, not theirs.
The three positioning mistakes that kill B2B SaaS growth
First: positioning to a category rather than a buyer. Saying you are an AI-powered project management tool describes a market segment, not a specific person with a specific problem. Buyers do not self-identify as members of categories. They identify with their job title, their frustration, and their quarterly target. Position to those, not to the Gartner magic quadrant you want to appear in.
Second: changing positioning before it has had time to work. Positioning takes 6-9 months of consistent execution to produce measurable signal in your pipeline. Most teams abandon it at month 3 when it has not produced a visible spike in inbound. The signal at month 3 is in deal quality and sales cycle length, not volume. Look at the right metrics or you will make the wrong call.
Third: treating positioning as a marketing function when it is a company function. Your positioning should be in your job descriptions, your customer success scripts, your investor updates, and your product roadmap rationale. If it only lives in the marketing team's Notion doc, it is not positioning. It is aspiration.
What to do this week
Pull your last 6 lost deals. Interview one person from each. Ask them what they chose instead and why. Code the answers against the three JTBD layers. If the emotional job that surfaces does not appear anywhere on your current website, you have your first positioning brief. That is a one-week exercise that costs nothing except honesty, and it will tell you more about your positioning gap than any brand workshop. If you want help turning that brief into positioning your whole team uses, that is the work of a brand positioning agency like ours.
If you want a second pair of eyes on the output, book a 20-min intro and bring the interviews.
Core guides

Sunday, May 17, 2026
Written by
Julien Kreuk
Why is my website not converting
12 real reasons (and what to fix first)
Why is your website not converting? Here are 12 specific reasons — with the fix order, tradeoffs, and what most audits miss. From Daasign's senior team.

Sunday, April 12, 2026
Written by
Julien Kreuk
The Ultimate SaaS Design System Guide
Build scalable, accessible UI without chaos
Building a SaaS product is genuinely hard. You're not just shipping features. You're maintaining a living interface that hundreds or thousands of people use every day, and as the product grows, the UI starts to fall apart in slow, painful ways. Buttons drift out of alignment, color usage becomes inconsistent, new pages look nothing like old ones, and every designer or developer who touches the codebase adds their own interpretation of how things should look. A SaaS design system solves this by creating a single, shared source of truth for your product's visual language, component library, and interaction patterns.

Friday, March 13, 2026
Written by
Julien Kreuk
AI-augmented design
the complete guide for SaaS founders and scale-ups
AI-augmented design cuts production time by 30–60% but the strategy gap is where most teams lose. Here's how to actually implement it in 2025.

Saturday, April 12, 2025
Written by
Julien Kreuk
The Ultimate Guide to the UI/UX Design Process
Steps, skills, and best practices for 2025
Whether you're a seasoned product designer, a developer trying to sharpen your design instincts, or a business owner figuring out how good digital products actually get built, the UI/UX design process is what separates products people love from ones they abandon. Mobile apps, enterprise software, e-commerce platforms, SaaS dashboards. the way designers research, prototype, and iterate determines whether a product clicks with its users or quietly collects digital dust.
Brand positioning for B2B SaaS growth
a practical how-to

Brand positioning for B2B SaaS growth
Written by
Passionate Designer & Founder
Brand positioning for B2B SaaS growth starts before your website, your pitch deck, or your product copy. Here's how to build it from the ground up.

Brand positioning for B2B SaaS growth: a practical how-to
Brand positioning for B2B SaaS growth is not a tagline exercise. It is the upstream decision that determines whether your sales cycle runs 90 days or 9, whether you compete on price or on category, and whether your product design actually converts the buyers you want.
Most SaaS founders get this backwards. They build the product, hire a designer, write some copy, and then ask: how do we position this? By that point they are already locked into execution decisions that conflict with each other, and the positioning work becomes a retrofit that never quite fits. Have a quick question about brand positioning for b2b saas growth? Read our expert answers on brand positioning for b2b saas growth.
Go deeper: Brand strategy as a growth lever · Tech product branding · Developer-first brand identity · Infrastructure SaaS branding · API product brand strategy · Category design for B2B · Brand-led growth · Brand-led acquisition vs performance marketing · Why a brand system needs demand
Before you start: inputs you need in the room
Positioning work without raw material is just opinion. Before running any framework, you need three things on the table: at least 8-10 customer interviews (recorded, not paraphrased by your sales team), a clear view of which deals you lost in the last 6 months and why, and an honest map of the alternatives your buyers actually compare you against. Not the alternatives you think they compare you against.
The mistake I see most often is founders skipping the lost-deal audit. They talk only to happy customers, build positioning around the stories those customers tell, and then wonder why conversion from trial to paid sits at 4% instead of 12%. The signal is in the losses, not the wins.
One more input worth having: your current revenue concentration. If 60% of your ARR comes from one vertical, your positioning should probably reflect that specificity rather than paper over it with broad language about serving any company that has a workflow problem.
Use jobs-to-be-done to understand the real problem
Jobs-to-be-done (JTBD) is the most useful lens for B2B SaaS positioning because it reframes the question from what does our product do to what is the buyer hiring our product to accomplish. Those are not the same question, and the gap between them is where most positioning goes wrong.
The JTBD framework, developed by Clayton Christensen and later operationalised by Bob Moesta, asks you to identify the functional job (ship reports faster), the emotional job (stop feeling exposed in board meetings), and the social job (look competent to my CFO). In B2B SaaS, all three layers exist. Ignore the emotional and social layers and your messaging sounds like every other vendor in your category.
A concrete way to run this: take your best 5 customer interviews and code them against the three layers. Look for the sentence that appears, in some form, across at least 4 of the 5. That sentence is the job. It is probably not on your current homepage.
For a Series B compliance SaaS we worked with, the functional job was obvious: automate audit trails. But the emotional job, which kept surfacing in interviews, was: stop being the person who gets blamed when something breaks. That distinction changed the entire positioning frame, from efficiency tool to risk-transfer product. Those two frames attract different buyers, justify different price points, and require completely different product design approaches. The product design decisions for a SaaS built around risk transfer look nothing like those for an efficiency tool.
Use your JTBD to shape your positioning statement
A positioning statement is an internal document, not a tagline. April Dunford's framework from Obviously Awesome is still the most actionable structure for B2B SaaS: define your best-fit customers, name the category you are competing in, state your differentiated value, and identify the proof points that make that claim credible. Four components, not one sentence. The temptation to collapse them into a single punchy line before the internal work is done kills more positioning projects than anything else.
The structure looks like this in practice. Best-fit customer: mid-market finance teams in regulated industries with 20-100 users. Category: audit automation. Differentiated value: the only tool that generates regulator-ready documentation without a dedicated compliance hire. Proof: SOC 2 Type II certified, used by 3 of the top 10 US regional banks.
Notice what that statement does not contain: the word unique, the phrase best-in-class, or any claim that could apply to a competitor without modification. If your competitor could copy-paste your positioning statement and replace only the company name, it is not positioning. It is category description.
Break up with the word "unique"
This one deserves its own section because it costs real money. Every SaaS positioning document I have reviewed in the last three years contains the word unique at least twice. Every single one. And in almost every case, the claim it attaches to is either unverifiable, temporary, or shared by at least two direct competitors.
Unique is a word that signals the writer stopped thinking. Replace it with a specific, time-bounded, evidence-backed claim. Instead of unique AI-powered recommendations, say: recommendations that improve over 90 days of usage, with a documented 23% reduction in manual review time for customers in the 50-500 seat range. That claim can be tested, referenced, and believed. Unique cannot.
The same applies to industry-leading, cutting-edge, and innovative. If your positioning relies on adjectives rather than mechanisms, the positioning has not been done yet.
Choose a name aligned with your positioning
Naming is a positioning decision, not a branding afterthought. A name that signals your category clearly reduces the cognitive load on buyers and cuts the amount of positioning work your sales team has to do on every first call. A name that is deliberately abstract or clever adds friction unless you have the budget to buy your way into category definition the way Salesforce or HubSpot did.
For early-stage B2B SaaS, the practical rule is: your name should either describe the job (Calendly, Expensify) or be distinctive enough to own a clear search term within 18 months. Abstract names that do neither tend to emerge from naming exercises optimised for domain availability and founder preference rather than buyer clarity, and they cost you 6-12 months of extra content and sales effort to explain what you do.
The tradeoff is real. Descriptive names date faster, can limit category expansion, and are harder to trademark. You are trading long-run flexibility for short-run clarity. For most Series A and B SaaS companies, short-run clarity is the right trade.
Communicate your positioning in a way that connects to customers' emotions
Rational positioning statements need to convert to emotional messaging. The positioning statement lives in your internal brief. What goes on your website, your sales deck, and your onboarding flows is the emotional translation of that statement, targeted at the specific emotional job your JTBD research uncovered.
Emotional does not mean sentimental. In B2B SaaS it means: does your messaging make the buyer feel understood before it explains anything about your product? The fastest test is to read your current homepage headline to a target buyer and ask: does this describe your situation? If they say yes, the positioning is landing. If they say I guess so, it is not.
A well-designed website with weak positioning messaging will produce lower conversion rates than a mediocre design with sharp, emotionally accurate copy. We have run this experiment enough times to be confident in the direction of the effect. The design decisions that make a SaaS website convert are downstream of positioning clarity, not upstream of it.
One structural recommendation: lead with the problem in the buyer's language, then the consequence of that problem remaining unsolved, then your mechanism, then proof. This is not a new formula. It works because it mirrors the structure of how buyers already think when they arrive at your site.
Get testimonials that actually do positioning work
Testimonials are proof points, not decoration. A generic five-star quote from a happy customer does almost nothing for positioning. A quote that names the specific job, the before-state, and the measurable after-state reinforces every claim your positioning makes.
The practical way to get these: during customer interview cycles, ask specifically what were you worried about before you started using this, and what does success look like 6 months from now. Those answers, lightly edited for clarity, produce testimonials that do positioning work rather than social proof theatre.
Brand alignment matters here too. A testimonial from a 5-person startup on a product positioned for 200-seat enterprise teams actively undermines conversion with your target buyer. Audit your current testimonials against your best-fit customer definition and remove or replace the ones that create category confusion. In the SaaS onboarding work we have shipped, misaligned social proof in the first 30 seconds of a user's session is consistently one of the top three friction points in session recordings. The same principle applies on marketing pages. You can go deeper on this in our piece on SaaS onboarding design.
Brand positioning and your product design surface
This is the part most positioning guides skip entirely. Your positioning statement should be a direct input into your product design decisions: what gets foregrounded in your UI, what language appears in empty states and tooltips, what the onboarding sequence covers in the first three sessions. If your positioning is built around risk transfer and your product design leads with speed metrics, you have a misalignment that confuses buyers who arrive knowing your marketing message and then experience something different inside the product.
On a McKinsey workstream we shipped a tool redesign where the product had been built around efficiency language internally but was being sold on compliance outcomes externally. The gap between the two surfaces was costing the sales team 2-3 hours per deal in re-explanation work. Aligning the product language with the positioning statement, which was fundamentally a design and copy decision rather than an engineering one, reduced that to under 30 minutes.
Across 40+ retainer engagements with funded SaaS teams, the pattern holds: the further the product design is from the positioning statement, the higher the support burden, the longer the sales cycle, and the lower the net revenue retention. These are not soft outcomes. They show up in the numbers within two quarters of a positioning realignment.
Which type of positioning fits your stage
Positioning frameworks list four or five types. In B2B SaaS these are the ones you'll actually choose between:
Use-case positioning names the exact situation where you win, like Calendly and the five emails it takes to find a meeting time. It's the only type that works when buyers don't yet know they have the problem, and it shortens sales cycles because buyers recognise themselves before the first call.
User-based positioning owns one audience, which is what vertical SaaS does by definition. Choose it when buyers respond faster the more precisely you name their world.
Value-based positioning owns an outcome, such as cutting churn by 20%. It's the most durable choice, but you need at least five reference customers who actually reached that number before you lead with it.
Attribute positioning claims a product characteristic, like Stripe's developer-first payments. It works in infrastructure and tooling, as long as competitors can't copy the feature within a year.
Competitor-based positioning defines you against an incumbent. It only works when that incumbent is already the default in the buyer's mind, and it ties your story to their roadmap.
Category design names a new category, as Salesforce and HubSpot did. It takes 18 to 36 months of consistent investment, so most growth-stage teams shouldn't start there.
Price and quality positioning rarely hold in software: low prices invite a race to the bottom and make moving up-market harder, and quality is expected rather than a reason to choose you. Your price still sends a signal, though. A tool at $49 a month gets filed differently from one at $2,000, whatever the feature list says. Pick one primary type that matches the proof you have today and how well your buyers understand the category. Mixing two or three types in one statement gives you positioning that is accurate and incoherent.
Map the market before you commit
A positioning map plots 5 to 8 competitors on two axes your buyers actually weigh. Price against quality tells you nothing new. Ask 8 to 12 buyers who compared you with a competitor which factors decided it, and turn the answers that keep coming back into axes, for example setup time against configurability. Place competitors based on evidence (their homepage hero, G2 reviews, what comes up on sales calls) and look for the quadrant with demand and no clear owner. The map gives you a hypothesis, not proof, so only claim an open quadrant if you have the case studies to defend it. We build these maps in our brand strategy sprint before any visual work starts.
Once you've chosen, the classic statement works as a quick internal check next to the structure above: "For [target customer] who [buying trigger], [brand] is the [category] that [key benefit] because [reason to believe]." Push hardest on the "because". Then read the claim to three recent prospects or customers. If fewer than two recognise what they were looking for, the positioning solves your problem, not theirs.
The three positioning mistakes that kill B2B SaaS growth
First: positioning to a category rather than a buyer. Saying you are an AI-powered project management tool describes a market segment, not a specific person with a specific problem. Buyers do not self-identify as members of categories. They identify with their job title, their frustration, and their quarterly target. Position to those, not to the Gartner magic quadrant you want to appear in.
Second: changing positioning before it has had time to work. Positioning takes 6-9 months of consistent execution to produce measurable signal in your pipeline. Most teams abandon it at month 3 when it has not produced a visible spike in inbound. The signal at month 3 is in deal quality and sales cycle length, not volume. Look at the right metrics or you will make the wrong call.
Third: treating positioning as a marketing function when it is a company function. Your positioning should be in your job descriptions, your customer success scripts, your investor updates, and your product roadmap rationale. If it only lives in the marketing team's Notion doc, it is not positioning. It is aspiration.
What to do this week
Pull your last 6 lost deals. Interview one person from each. Ask them what they chose instead and why. Code the answers against the three JTBD layers. If the emotional job that surfaces does not appear anywhere on your current website, you have your first positioning brief. That is a one-week exercise that costs nothing except honesty, and it will tell you more about your positioning gap than any brand workshop. If you want help turning that brief into positioning your whole team uses, that is the work of a brand positioning agency like ours.
If you want a second pair of eyes on the output, book a 20-min intro and bring the interviews.
Core guides

Why is my website not converting
12 real reasons (and what to fix first)

The Ultimate SaaS Design System Guide
Build scalable, accessible UI without chaos

AI-augmented design
the complete guide for SaaS founders and scale-ups

The Ultimate Guide to the UI/UX Design Process
Steps, skills, and best practices for 2025
Brand positioning for B2B SaaS growth
a practical how-to

Brand positioning for B2B SaaS growth
Written by
Passionate Designer & Founder
Brand positioning for B2B SaaS growth starts before your website, your pitch deck, or your product copy. Here's how to build it from the ground up.

Brand positioning for B2B SaaS growth: a practical how-to
Brand positioning for B2B SaaS growth is not a tagline exercise. It is the upstream decision that determines whether your sales cycle runs 90 days or 9, whether you compete on price or on category, and whether your product design actually converts the buyers you want.
Most SaaS founders get this backwards. They build the product, hire a designer, write some copy, and then ask: how do we position this? By that point they are already locked into execution decisions that conflict with each other, and the positioning work becomes a retrofit that never quite fits. Have a quick question about brand positioning for b2b saas growth? Read our expert answers on brand positioning for b2b saas growth.
Go deeper: Brand strategy as a growth lever · Tech product branding · Developer-first brand identity · Infrastructure SaaS branding · API product brand strategy · Category design for B2B · Brand-led growth · Brand-led acquisition vs performance marketing · Why a brand system needs demand
Before you start: inputs you need in the room
Positioning work without raw material is just opinion. Before running any framework, you need three things on the table: at least 8-10 customer interviews (recorded, not paraphrased by your sales team), a clear view of which deals you lost in the last 6 months and why, and an honest map of the alternatives your buyers actually compare you against. Not the alternatives you think they compare you against.
The mistake I see most often is founders skipping the lost-deal audit. They talk only to happy customers, build positioning around the stories those customers tell, and then wonder why conversion from trial to paid sits at 4% instead of 12%. The signal is in the losses, not the wins.
One more input worth having: your current revenue concentration. If 60% of your ARR comes from one vertical, your positioning should probably reflect that specificity rather than paper over it with broad language about serving any company that has a workflow problem.
Use jobs-to-be-done to understand the real problem
Jobs-to-be-done (JTBD) is the most useful lens for B2B SaaS positioning because it reframes the question from what does our product do to what is the buyer hiring our product to accomplish. Those are not the same question, and the gap between them is where most positioning goes wrong.
The JTBD framework, developed by Clayton Christensen and later operationalised by Bob Moesta, asks you to identify the functional job (ship reports faster), the emotional job (stop feeling exposed in board meetings), and the social job (look competent to my CFO). In B2B SaaS, all three layers exist. Ignore the emotional and social layers and your messaging sounds like every other vendor in your category.
A concrete way to run this: take your best 5 customer interviews and code them against the three layers. Look for the sentence that appears, in some form, across at least 4 of the 5. That sentence is the job. It is probably not on your current homepage.
For a Series B compliance SaaS we worked with, the functional job was obvious: automate audit trails. But the emotional job, which kept surfacing in interviews, was: stop being the person who gets blamed when something breaks. That distinction changed the entire positioning frame, from efficiency tool to risk-transfer product. Those two frames attract different buyers, justify different price points, and require completely different product design approaches. The product design decisions for a SaaS built around risk transfer look nothing like those for an efficiency tool.
Use your JTBD to shape your positioning statement
A positioning statement is an internal document, not a tagline. April Dunford's framework from Obviously Awesome is still the most actionable structure for B2B SaaS: define your best-fit customers, name the category you are competing in, state your differentiated value, and identify the proof points that make that claim credible. Four components, not one sentence. The temptation to collapse them into a single punchy line before the internal work is done kills more positioning projects than anything else.
The structure looks like this in practice. Best-fit customer: mid-market finance teams in regulated industries with 20-100 users. Category: audit automation. Differentiated value: the only tool that generates regulator-ready documentation without a dedicated compliance hire. Proof: SOC 2 Type II certified, used by 3 of the top 10 US regional banks.
Notice what that statement does not contain: the word unique, the phrase best-in-class, or any claim that could apply to a competitor without modification. If your competitor could copy-paste your positioning statement and replace only the company name, it is not positioning. It is category description.
Break up with the word "unique"
This one deserves its own section because it costs real money. Every SaaS positioning document I have reviewed in the last three years contains the word unique at least twice. Every single one. And in almost every case, the claim it attaches to is either unverifiable, temporary, or shared by at least two direct competitors.
Unique is a word that signals the writer stopped thinking. Replace it with a specific, time-bounded, evidence-backed claim. Instead of unique AI-powered recommendations, say: recommendations that improve over 90 days of usage, with a documented 23% reduction in manual review time for customers in the 50-500 seat range. That claim can be tested, referenced, and believed. Unique cannot.
The same applies to industry-leading, cutting-edge, and innovative. If your positioning relies on adjectives rather than mechanisms, the positioning has not been done yet.
Choose a name aligned with your positioning
Naming is a positioning decision, not a branding afterthought. A name that signals your category clearly reduces the cognitive load on buyers and cuts the amount of positioning work your sales team has to do on every first call. A name that is deliberately abstract or clever adds friction unless you have the budget to buy your way into category definition the way Salesforce or HubSpot did.
For early-stage B2B SaaS, the practical rule is: your name should either describe the job (Calendly, Expensify) or be distinctive enough to own a clear search term within 18 months. Abstract names that do neither tend to emerge from naming exercises optimised for domain availability and founder preference rather than buyer clarity, and they cost you 6-12 months of extra content and sales effort to explain what you do.
The tradeoff is real. Descriptive names date faster, can limit category expansion, and are harder to trademark. You are trading long-run flexibility for short-run clarity. For most Series A and B SaaS companies, short-run clarity is the right trade.
Communicate your positioning in a way that connects to customers' emotions
Rational positioning statements need to convert to emotional messaging. The positioning statement lives in your internal brief. What goes on your website, your sales deck, and your onboarding flows is the emotional translation of that statement, targeted at the specific emotional job your JTBD research uncovered.
Emotional does not mean sentimental. In B2B SaaS it means: does your messaging make the buyer feel understood before it explains anything about your product? The fastest test is to read your current homepage headline to a target buyer and ask: does this describe your situation? If they say yes, the positioning is landing. If they say I guess so, it is not.
A well-designed website with weak positioning messaging will produce lower conversion rates than a mediocre design with sharp, emotionally accurate copy. We have run this experiment enough times to be confident in the direction of the effect. The design decisions that make a SaaS website convert are downstream of positioning clarity, not upstream of it.
One structural recommendation: lead with the problem in the buyer's language, then the consequence of that problem remaining unsolved, then your mechanism, then proof. This is not a new formula. It works because it mirrors the structure of how buyers already think when they arrive at your site.
Get testimonials that actually do positioning work
Testimonials are proof points, not decoration. A generic five-star quote from a happy customer does almost nothing for positioning. A quote that names the specific job, the before-state, and the measurable after-state reinforces every claim your positioning makes.
The practical way to get these: during customer interview cycles, ask specifically what were you worried about before you started using this, and what does success look like 6 months from now. Those answers, lightly edited for clarity, produce testimonials that do positioning work rather than social proof theatre.
Brand alignment matters here too. A testimonial from a 5-person startup on a product positioned for 200-seat enterprise teams actively undermines conversion with your target buyer. Audit your current testimonials against your best-fit customer definition and remove or replace the ones that create category confusion. In the SaaS onboarding work we have shipped, misaligned social proof in the first 30 seconds of a user's session is consistently one of the top three friction points in session recordings. The same principle applies on marketing pages. You can go deeper on this in our piece on SaaS onboarding design.
Brand positioning and your product design surface
This is the part most positioning guides skip entirely. Your positioning statement should be a direct input into your product design decisions: what gets foregrounded in your UI, what language appears in empty states and tooltips, what the onboarding sequence covers in the first three sessions. If your positioning is built around risk transfer and your product design leads with speed metrics, you have a misalignment that confuses buyers who arrive knowing your marketing message and then experience something different inside the product.
On a McKinsey workstream we shipped a tool redesign where the product had been built around efficiency language internally but was being sold on compliance outcomes externally. The gap between the two surfaces was costing the sales team 2-3 hours per deal in re-explanation work. Aligning the product language with the positioning statement, which was fundamentally a design and copy decision rather than an engineering one, reduced that to under 30 minutes.
Across 40+ retainer engagements with funded SaaS teams, the pattern holds: the further the product design is from the positioning statement, the higher the support burden, the longer the sales cycle, and the lower the net revenue retention. These are not soft outcomes. They show up in the numbers within two quarters of a positioning realignment.
Which type of positioning fits your stage
Positioning frameworks list four or five types. In B2B SaaS these are the ones you'll actually choose between:
Use-case positioning names the exact situation where you win, like Calendly and the five emails it takes to find a meeting time. It's the only type that works when buyers don't yet know they have the problem, and it shortens sales cycles because buyers recognise themselves before the first call.
User-based positioning owns one audience, which is what vertical SaaS does by definition. Choose it when buyers respond faster the more precisely you name their world.
Value-based positioning owns an outcome, such as cutting churn by 20%. It's the most durable choice, but you need at least five reference customers who actually reached that number before you lead with it.
Attribute positioning claims a product characteristic, like Stripe's developer-first payments. It works in infrastructure and tooling, as long as competitors can't copy the feature within a year.
Competitor-based positioning defines you against an incumbent. It only works when that incumbent is already the default in the buyer's mind, and it ties your story to their roadmap.
Category design names a new category, as Salesforce and HubSpot did. It takes 18 to 36 months of consistent investment, so most growth-stage teams shouldn't start there.
Price and quality positioning rarely hold in software: low prices invite a race to the bottom and make moving up-market harder, and quality is expected rather than a reason to choose you. Your price still sends a signal, though. A tool at $49 a month gets filed differently from one at $2,000, whatever the feature list says. Pick one primary type that matches the proof you have today and how well your buyers understand the category. Mixing two or three types in one statement gives you positioning that is accurate and incoherent.
Map the market before you commit
A positioning map plots 5 to 8 competitors on two axes your buyers actually weigh. Price against quality tells you nothing new. Ask 8 to 12 buyers who compared you with a competitor which factors decided it, and turn the answers that keep coming back into axes, for example setup time against configurability. Place competitors based on evidence (their homepage hero, G2 reviews, what comes up on sales calls) and look for the quadrant with demand and no clear owner. The map gives you a hypothesis, not proof, so only claim an open quadrant if you have the case studies to defend it. We build these maps in our brand strategy sprint before any visual work starts.
Once you've chosen, the classic statement works as a quick internal check next to the structure above: "For [target customer] who [buying trigger], [brand] is the [category] that [key benefit] because [reason to believe]." Push hardest on the "because". Then read the claim to three recent prospects or customers. If fewer than two recognise what they were looking for, the positioning solves your problem, not theirs.
The three positioning mistakes that kill B2B SaaS growth
First: positioning to a category rather than a buyer. Saying you are an AI-powered project management tool describes a market segment, not a specific person with a specific problem. Buyers do not self-identify as members of categories. They identify with their job title, their frustration, and their quarterly target. Position to those, not to the Gartner magic quadrant you want to appear in.
Second: changing positioning before it has had time to work. Positioning takes 6-9 months of consistent execution to produce measurable signal in your pipeline. Most teams abandon it at month 3 when it has not produced a visible spike in inbound. The signal at month 3 is in deal quality and sales cycle length, not volume. Look at the right metrics or you will make the wrong call.
Third: treating positioning as a marketing function when it is a company function. Your positioning should be in your job descriptions, your customer success scripts, your investor updates, and your product roadmap rationale. If it only lives in the marketing team's Notion doc, it is not positioning. It is aspiration.
What to do this week
Pull your last 6 lost deals. Interview one person from each. Ask them what they chose instead and why. Code the answers against the three JTBD layers. If the emotional job that surfaces does not appear anywhere on your current website, you have your first positioning brief. That is a one-week exercise that costs nothing except honesty, and it will tell you more about your positioning gap than any brand workshop. If you want help turning that brief into positioning your whole team uses, that is the work of a brand positioning agency like ours.
If you want a second pair of eyes on the output, book a 20-min intro and bring the interviews.
Core guides

Why is my website not converting
12 real reasons (and what to fix first)

The Ultimate SaaS Design System Guide
Build scalable, accessible UI without chaos

AI-augmented design
the complete guide for SaaS founders and scale-ups

The Ultimate Guide to the UI/UX Design Process
Steps, skills, and best practices for 2025
Let’s unlock what’s
possible together.
Book a 15-minute call. We’ll diagnose what you need and recommend the right next step for your project.

Let’s unlock what’s
possible together.
Book a 15-minute call. We’ll diagnose what you need and recommend the right next step for your project.

Let’s unlock what’s
possible together.
Book a 15-minute call. We’ll diagnose what you need and recommend the right next step for your project.


Back to top
