Who Are You Actually Designing For? The Question B2B SaaS Teams Get Wrong

Most SaaS teams answer this quickly: "the user." That answer is incomplete. In B2B, there are always two entities you are designing for, the individual using the product and the organization buying it, and confusing the two is one of the most common reasons websites fail to convert and messaging fails to land.

‍

Why "Designing for the User" Is Not Enough

The logic sounds clean: understand your user, design for their needs, and the product or website performs. In consumer products, this often holds. In B2B SaaS, it breaks down fast.

The person using your product is rarely the person paying for it. A marketing manager logs into your platform daily. A CMO signs the contract. A CFO approves the renewal. Each has different priorities, different vocabularies, and different definitions of success. A website or messaging framework built purely around the end user will resonate with the wrong person at the wrong stage of the buying cycle.

This is not a minor detail. It shapes everything: which problems you lead with on your homepage, how you frame ROI, what you put above the fold, and where you place your CTAs.

‍

User vs Customer: What Is the Real Difference?

In B2B SaaS, these are two distinct groups.

The user is an individual. They interact with your product daily. Their concerns are practical: does it save time, does it fit my workflow, is it intuitive enough to use without training. Their success metrics are personal and task-level.

The customer is the organization or the economic buyer within it. Their concerns are strategic: does this reduce cost, drive revenue, reduce risk, or give us a competitive edge. They are evaluating your product against alternatives and internal priorities, not just usability.

When your website speaks only to usability and features, you win users. When it speaks to outcomes, ROI, and strategic value, you win customers. Most SaaS websites try to do both and end up speaking clearly to neither.

‍

Why Personas Fail in B2B SaaS

Personas are meant to bring users to life, to turn abstract audience segments into relatable, specific people. The problem is that in trying to make them relatable, teams make them fictional.

A persona that says "Sarah, 35, VP of Marketing, values collaboration and hates manual reporting" is technically a user profile. It is practically useless for making hard design or messaging decisions.

Personas collapse complex behavior into a snapshot. They cannot account for Sarah's mental model, the internal politics shaping her decision-making, the approval chain she operates within, or the fact that she uses your product differently depending on whether the company is pre-launch or scaling past Series B.

In B2B SaaS specifically, personas also flatten the buying group. There is rarely one Sarah. There is Sarah the user, her VP of Revenue who has final say, and the IT lead who needs to approve integrations. A persona-first approach often produces websites optimized for the person using the product, not the person approving the purchase.

‍

Why Mental Models Matter More

A mental model is how someone believes a system works based on their past experience. It is not necessarily accurate. It is always influential.

When a B2B buyer arrives at your website, they bring a mental model of your category. They have worked with a competitor, read an analyst report, or heard a description from a colleague. That model shapes how they interpret your homepage in the first few seconds.

If your messaging maps onto their existing mental model, comprehension is instant. If it fights against it, friction builds and attention drops.

This is why category clarity often matters more than feature differentiation on a homepage. Visitors are not processing your full value proposition on first contact. They are pattern-matching against what they already believe. Your job is to confirm the right pattern fast, then challenge it in a way that works in your favor.

For example, if buyers in your category assume your type of tool is complex to implement, your homepage needs to address that belief directly, not by burying a "quick setup" claim in the third section, but by making implementation speed a primary message near the top.

‍

Why Users Ask for Solutions, Not Problems

When users give feedback, they frame it as solutions. "We need a dashboard." "Can you add a CSV export?" "The filter should work differently." These requests feel specific and actionable. They are often misleading.

Users describe what they think will fix their problem because they cannot see everything you can see. They do not have visibility into technical constraints, the needs of other user types, or how their request interacts with the broader product logic. They are solving from their limited vantage point.

The same pattern appears in website feedback and conversion decisions. A team sees low demo conversions and concludes: "We need a better CTA." The actual problem might be that the page fails to establish trust before asking for action, or that the wrong audience is arriving via paid search, or that the value proposition is unclear three scrolls above the CTA.

Treating the surface request as the real problem is expensive. The design or messaging decision that follows will be optimized for the wrong thing.

‍

What This Means for SaaS Websites and Conversion

Getting user vs customer clarity right changes how you build and optimize a website.

It changes your messaging hierarchy. If the economic buyer prioritizes cost reduction and time to value, those signals need to appear early, not buried under product screenshots designed to excite the end user.

It changes how you structure social proof. A testimonial from a power user builds credibility with practitioners. A quote from a CMO or CFO carries weight with the buying group. Most SaaS sites pick one and ignore the other.

It changes your CRO approach. Testing a CTA button color is irrelevant if the section it sits in is speaking to the wrong audience. Conversion optimization that does not start from audience clarity tends to produce marginal gains at best.

It also changes how you handle AEO. When AI engines extract answers from your website, they are looking for clear definitions, structured logic, and direct responses to the questions buyers actually ask. A site optimized for feature storytelling will not rank well in AI answers. A site that clearly explains what you do, who it is for, and what outcome it delivers will.

‍

A practical framework for getting this right:

• Define both entities explicitly:
  Who is the user and who is the economic buyer for each major product or tier
• Map messaging priority to the buying stage:
  Awareness content should address buyer concerns, not just user benefits
• Audit your homepage for who it is actually speaking to in the first three sections
• Validate your assumptions against real customer conversations, not persona documents

‍

These principles are also reflected in how tools themselves are evolving. In our latest video, we break down how Framer is consolidating analytics, personalization, and CRO into a single environment, reducing the time spent stitching together different tools and increasing iteration speed on what actually matters: messaging, clarity, and performance. Watch it here:

‍

‍

Noco's Take

Most SaaS website problems are not design problems. They are clarity problems rooted in a misunderstanding of who the site is actually for. When a team treats user and customer as the same entity, everything downstream gets blurred: the headline, the social proof, the CTA, the feature emphasis.

We start every engagement by mapping the buying group, not just the end user. The gap between the person who uses your product and the person who buys it is where most messaging falls apart. Close that gap first, and the design decisions that follow become sharper and more defensible.

If your website is not converting the way your product deserves, the starting point is usually here.

‍