B2B SaaS · Positioning and Demand

When a Technical Product
Needed a Business Problem

How positioning, audience segmentation and demand generation helped turn a complex enterprise SaaS offering into a clearer buying journey.

Client
European enterprise SaaS provider
Market
B2B and enterprise software
Role
Strategic marketing and demand generation
Focus
Positioning, ICP strategy, paid acquisition, account-based targeting, funnel design
Confidential engagement
The challenge

The product was strong.
The reason to buy it was unclear.

The company had strong technical expertise and a sophisticated software portfolio designed to automate complex processes within enterprise collaboration environments. The challenge was explaining why someone should buy it.

Existing communication described capabilities, modules and technical functionality, and many messages remained too generic for a product solving highly specific enterprise problems.

Different buyers also experienced very different pain points. A CIO was concerned with governance, security and operational risk. An IT administrator was dealing with duplicated resources, unmanaged users and hours of manual maintenance. A consultant or implementation partner saw an opportunity to standardise governance across multiple customer environments. End users cared about productivity and reducing friction. Explaining the product in one generic message made an already complex solution harder to buy.

The first diagnosis

Features were carrying
too much of the message.

Enterprise SaaS companies often know their product extremely well, which can become a marketing problem. Internal teams naturally describe functionality, integrations, workflows, modules and automation. Prospects usually begin somewhere else. They begin with a problem.

Problems buyers already recognised
Uncontrolled growth of digital workspaces
Unclear external access
Unused resources and manual administration
Inconsistent governance processes
Security and compliance concerns
Expensive specialist time spent on repetitive housekeeping

The strategic shift was to organise communication around recognisable business problems first and explain the technology second.

Before and after comparison replacing a feature-led message with buyer problem, business impact, relevant use case and product.
Technical products become easier to buy when prospects recognise the problem before they need to understand the platform.
One product, several buying realities

The same product needed
different entry points.

The buying ecosystem included CIOs and IT leaders, IT administrators, digital workplace specialists, consultants and implementation partners. These groups could not be treated as one generic IT audience, and the difference became the basis for messaging, paid campaigns and landing-page structure.

The company was also not starting without market access. Its contact base contained hundreds of relevant industry contacts across prospects, customers, demo requests and a substantial partner ecosystem. The opportunity was to make better use of an audience that already had varying degrees of familiarity, intent and relationship with the company.

PartnerCustomerDemo requestEvent leadCold prospect

Each required a different next step. The database needed to be treated as different audience states rather than one contact list.

Four buying roles, CIO or IT leader, IT administrator, digital workplace specialist and consultant or partner, each with different priorities leading to the same enterprise solution.
The same product needed different messages depending on the buyer’s responsibility.
From lead volume to intent

Acquisition was structured
around how prospects searched.

Rather than building one broad campaign around the product, the acquisition architecture separated several forms of intent.

Brand demand
Generic category demand
Specific use-case demand
Problem-based searches
Retargeting

Search messaging was aligned with the problem behind the query. The same principle applied to paid social, where campaigns could speak directly to situations such as unmanaged digital workspaces, unclear external access or specialist IT teams spending too much time on repetitive administration. The problem became understandable before the prospect was asked to understand the technology.

Account-based targeting

Three questions instead of
optimising for clicks.

For a specialised enterprise product, broad reach alone was not enough. The realistically valuable audience consisted of a relatively narrow group of organisations and roles, so large account lists were developed for priority European markets and matched with relevant decision-making roles.

Question 01Which organisations are realistically valuable?
Question 02Who inside those organisations is involved in the problem?
Question 03Which problem is most relevant to that role?

That connects paid acquisition with sales reality rather than treating advertising as a click-generation exercise.

Events and existing audiences

Complex products rarely become
simple purchasing decisions.

Another existing strength was the company's presence within the professional technology ecosystem. Event audiences and existing industry contacts could be used as warm audiences rather than treating every campaign as cold acquisition. Separate audiences were created from event leads and other contact groups for nurturing and paid activation.

Industry exposureRelevant contentProblem recognitionConsiderationDemo or sales conversation

The alternative, moving straight from advertisement to demo, rarely reflects how enterprise software is actually bought.

An operational constraint

Demand should not be scaled
independently of the system receiving it.

The analysis also identified a problem advertising could not solve. Prospects interested enough to request a demo could face a wait of several weeks before an available appointment.

That is not a media-buying problem. It is a conversion-system problem. Generating additional demand into a funnel with avoidable sales friction simply creates more leakage.

The strategic response

Six connected priorities.

01

Translate complexity into buyer problems

Start communication with situations prospects already recognise, then explain how the technology resolves them.

02

Separate audiences by responsibility and intent

Give each buying role its own entry point instead of one generic IT message.

03

Structure paid search around intent

Split brand, category, use-case, problem-led and retargeting demand rather than running one broad campaign.

04

Use account-based targeting

Match priority markets with the organisations and roles that are realistically valuable.

05

Activate existing audience assets

Treat partners, customers, demo requests and event leads as distinct audience states with distinct next steps.

06

Align acquisition with the sales journey

Match demand generation to sales capacity so additional interest does not leak out of the funnel.

The strategic lesson

A marketing problem that
looks like a lead problem.

The company did not primarily suffer from a lack of marketing opportunities. It had strong technical expertise, an established industry network, hundreds of relevant contacts, partner relationships, multiple use cases and an enterprise-grade product. The constraint was turning those assets into a system that was easier for buyers to understand and easier for sales to convert.

Traffic became less important than relevance. Lead volume became less important than intent. Product communication became less about explaining everything the software could do and more about helping buyers recognise why the problem mattered to them.

PositioningICPIntentAcquisitionConversionSales capacity

If one of those elements is disconnected, optimising the others has diminishing value. Before generating more demand, make sure the system knows what valuable demand looks like.

How I work →

Marketing System Audit

If your B2B marketing is generating activity but you are unsure whether positioning, targeting, lead quality and sales conversion work as one system, the Marketing System Audit identifies where the disconnect occurs. Diagnose the constraint before you scale it.