How to Use Customer Interviews to Improve B2B Positioning

Most B2B companies speak to customers regularly. Sales teams conduct discovery calls, account managers discuss delivery and founders hear feedback about their products. Yet these conversations rarely produce a reliable understanding of why customers buy, which alternatives they consider or how they describe the value they receive.

The problem is not a lack of conversation. It is a lack of structured evidence.

A customer interview programme should help a business understand how buyers make decisions and translate that understanding into positioning, messaging, product priorities and commercial execution.

The aim is not to collect positive quotes. It is to discover what actually matters to the people the business wants to serve.

1. Begin with the positioning decision

Before recruiting participants, identify what the interviews need to inform.

A company struggling to differentiate itself from competitors has a different research problem from one attracting enquiries that rarely become customers. The former needs to understand competitive alternatives and selection criteria. The latter may need to revisit its ideal customer profile or the promises its marketing makes.

Useful research questions include:

What situation causes buyers to start looking for a solution?

Which problems are sufficiently important to justify action?

What alternatives do buyers seriously consider?

Which factors determine whether they trust a provider?

What evidence changes their evaluation?

What value do customers describe after implementation?

Avoid beginning with a questionnaire about whether customers like the company's existing positioning. That risks testing the language the business already uses rather than discovering how buyers understand the problem.

The first deliverable is a decision brief: the business question, the relevant buyer population, the evidence needed and the decision that will follow.

2. Recruit for useful differences, not an arbitrary sample size

A fixed requirement to interview 15 or 20 customers is not suitable for every project.

A specialised enterprise service with a handful of major accounts may need a different approach from a SaaS business serving several customer segments. The right interview set depends on the decisions being made, the diversity of buying situations and whether additional interviews continue to reveal materially different patterns.

A useful recruitment framework includes:

Segment the evidence by buying context, not merely by company size or job title. A technical evaluator and an economic buyer from the same account may have very different decision criteria.

Recruitment should also reflect the ideal customer profile, while allowing the interviews to challenge that profile.

3. Ask about real decisions rather than hypothetical preferences

An interview becomes less reliable when the interviewer asks participants to predict behaviour, agree with a proposed benefit or praise an existing idea.

Rob Fitzpatrick's The Mom Test provides a useful methodological principle: investigate real experiences and behaviour rather than relying on compliments or speculative intentions.

For B2B positioning research, questions should help the participant reconstruct a specific buying situation.

The alternative questions do not automatically produce reliable evidence. Interviewers still need to probe for dates, examples, trade-offs and actual decisions.

A participant saying that an integration was essential is a useful starting point. Understanding which integration, what depended on it and how it influenced supplier selection is the evidence the team can act upon.

4. Use a flexible interview guide

Interviews should be comparable enough to analyse but flexible enough to follow unexpected information.

A practical guide can follow six areas.

Buying context. What was happening in the organisation before the search began? Who first recognised the problem? Why did it become important?

Existing approach. How was the problem managed previously? What was working, and what had become unacceptable?

Alternatives. Which suppliers, internal approaches or decisions not to act were considered? What made them credible?

Evaluation. Who participated in the decision? Which questions, risks and proof points mattered?

Decision. What changed the buyer's confidence? What ultimately determined the choice?

Realised value. What happened after implementation? Which benefits were expected, and which were actually observed?

Use follow-up questions such as "Can you give me a specific example?", "What happened next?" and "Who else was involved?"

Interview length should reflect the complexity of the buying decision and participant availability. A shorter, focused conversation may generate better evidence than a long interview filled with hypothetical questions.

5. Conduct interviews in waves

Running every interview before analysing anything can allow a weak research guide to remain weak throughout the project.

Instead, examine early conversations for confusing questions, missing participant types and unexpected themes.

For example, a software provider may initially assume that buyers choose its product for advanced functionality. Early interviews might show that implementation uncertainty dominates the decision. The next interviews can then investigate how buyers assess onboarding capability, migration risk and technical support.

This is a reason to improve the evidence collection, not to steer participants towards a preferred conclusion.

Keep the core questions sufficiently consistent to compare interviews, while documenting when the guide changes.

6. Separate observations from interpretation

Interview analysis often goes wrong because teams immediately convert individual comments into positioning statements.

A participant saying "We needed fewer manual handoffs" is an observation. Concluding that "automation is our primary differentiation" is an interpretation. The latter requires evidence from other interviews and an understanding of competing alternatives.

Create a synthesis table:

Retain specific evidence behind each theme. Do not turn a memorable quote into a universal customer truth.

Look for both repeated patterns and meaningful exceptions. If one segment places greater value on implementation support while another prioritises flexibility, a single generic proposition may be masking distinct buying situations.

7. Translate evidence into positioning decisions

Interview findings should produce explicit choices, not just a collection of attractive quotations.

Customer selection: Which buying situations are best matched to the business's strengths?

Competitive alternatives: What are customers moving away from, including internal processes and doing nothing?

Differentiation: Which capabilities matter to the buying decision and can be demonstrated credibly?

Value: What meaningful change does the customer expect, and what evidence is available?

Messaging: Which explanations are immediately understood, and which create avoidable confusion?

As a complementary lens, Strategyzer's customer jobs, pains and gains framework can help organise interview evidence about buyers' tasks, frustrations and desired outcomes. It is a synthesis aid, not a substitute for validating the underlying observations.

For example, consider an illustrative B2B software company that describes itself as an advanced analytics platform.

Interviews reveal that buyers mostly compare the product with manual spreadsheets, fragmented dashboards and internal reporting work. Their central concern is not the number of visualisations available. It is whether they can trust one consistent view of performance.

A possible positioning hypothesis is therefore a shift from "advanced analytics" to "reliable operational reporting across disconnected systems".

That hypothesis must be checked against product capabilities and further customer evidence. The interviews provide direction, not automatic proof.

8. Validate before rewriting the entire go-to-market system

An interview programme should not trigger an immediate replacement of every headline, sales deck and campaign.

Turn findings into a manageable set of hypotheses. Identify what evidence would support or contradict each proposed change.

Possible validation activities include sales-call observations, message comprehension interviews, controlled landing-page tests where appropriate, and structured feedback on revised proposals.

Judge changes against the intended business decision. A clearer message may help qualified buyers understand the offer without immediately creating more traffic. Conversely, a headline that improves clicks but attracts unsuitable enquiries may weaken the overall growth system.

Interview findings should also inform the wider marketing diagnosis, particularly when the evidence suggests a mismatch between customer expectations and acquisition messaging.

9. Make customer insight a repeatable capability

Customer interviewing should not be treated solely as a large research event before a rebrand.

The business can maintain a lightweight evidence system through sales conversations, onboarding feedback, win/loss reviews and targeted interviews when important decisions arise.

Assign ownership for the interview evidence, keep the underlying observations accessible to relevant teams and record which strategic decisions they influenced.

A useful research output includes:

The decision the research addressed.

The participants and buying contexts represented.

The recurring themes and meaningful exceptions.

Direct evidence supporting each interpretation.

Unresolved questions and limitations.

Proposed changes to positioning or execution.

A validation plan and accountable owner.

Within the NBT Growth Model, customer interviews can inform the Growth Marketing Checkup and Growth Route Formulation before priorities are translated into delivery.

The strongest result is not a polished customer research report. It is a set of better-informed commercial decisions about whom to serve, how to explain the offer and which evidence buyers need before they act.