UX Research in the Sales Process.

The brief.

Most projects start with a brief.

It lands, gets shared around, maybe discussed for half an hour, and then everyone gets meeting and writing. It looks solid enough on the surface, with objectives, some scope, and occasionally a budget that feels just about workable. It gives you something to react to, something to build around, something to move forward with, and in a busy environment, that sense of momentum is hard to resist. But the brief is rarely the full picture, even when it feels complete.

It’s a version of the problem shaped by whoever wrote it, based on what they know, what they’ve been told, and what they’re trying to achieve internally. It carries assumptions, gaps, and sometimes a bit of internal politics that never quite makes it onto the page. None of that is unusual, but it does mean the brief is only ever a starting point, not the answer.

What usually happens next.

Once the brief is accepted as truth, the process settles into something familiar. You interpret what’s been asked, align it to what you sell, and begin shaping a solution that fits within the perceived constraints. The pitch follows naturally from that, built to persuade, reassure, and show capability in the best possible light.

This is where most agencies are comfortable and business as usual. The whole process depends on one quiet assumption sitting underneath it all, which is that the problem has already been correctly defined. If that assumption is even slightly off, everything that follows begins to drift. The thinking can still be good, the execution can still be strong, but it’s all anchored to something that wasn’t fully understood in the first place.

A different starting point.

UX research introduces a different way into the process, and it’s not as heavy as people tend to imagine. It doesn’t mean slowing everything down or adding layers of complexity before you can respond. It simply creates a moment to ask what’s actually happening, rather than moving straight to what should be built.

Instead of jumping immediately into features, deliverables, and timelines, I take time to understand the situation more clearly. I begin to see the context around the problem, the pressures shaping it, and the gaps between what’s said and what’s not.

Research, but lighter.

This isn’t discovery in the traditional sense. You’re not trying to answer every question or produce something comprehensive enough to hand over as a deliverable. That would slow things down and create more friction than value at this stage of the process.

A few conversations, a look at the current experience, and some structured thinking are usually enough to shift your understanding. Patterns begin to emerge quite quickly when you’re paying attention, and those patterns are often more useful than any single insight on its own. You move from reacting to a brief to seeing the wider context of this brief for the client.

Conversations.

A small number of conversations will almost always reveal more than the brief itself, because people rarely describe the same problem in the same way. Each stakeholder brings their own perspective, shaped by their role, their pressures, and what success looks like to them. Even when everyone is aligned on the surface, those underlying views can pull in different directions and inconsistencies surface quickly.

One person is focused on growth, another on efficiency, another on stability, and another on speed. None of those is wrong, but they don’t always sit comfortably together. That tension is usually where the real complexity lives, and it rarely appears clearly in a written document.

From opinion to something more grounded.

Most pitches are built on informed opinion, often based on experience and best practice. That’s valuable, but it still leaves a gap because it isn’t directly tied to the client’s specific situation. Even strong ideas can feel slightly generic when they aren’t anchored in something relevant to that client specifically.

Research closes that gap. When you can point to what you’ve seen or heard, the conversation becomes more grounded. You’re not just proposing what might work, but reflecting what is happening and what that implies. That changes how your thinking lands, even if the actual recommendations are similar to what you would have said anyway.

What clients are really buying.

Clients will often talk about innovation, creativity, and new thinking when describing what they want. Those things matter, and they do play a role in decision-making. But underneath that, there’s usually something more fundamental driving the choice.

Not just confidence in your ability to deliver, but confidence that you understand their situation properly and won’t take them in the wrong direction. Most agencies try to build that through credentials, case studies, well-crafted presentations and “logo soup” of big brands they've worked with. Those things help, but they don’t replace genuine understanding when it’s visible.

Where this can go wrong.

Even when agencies try to bring research into the sales process, it can become overcomplicated quite quickly. There’s a tendency to treat it as a scaled-down version of delivery, which leads to too much work, too much documentation, and not enough focus on what actually matters at this stage. Clarity can get lost when volume increases.

When it starts to work.

When UX research genuinely informs the sales process, the structure of the conversation shifts noticeably. You don’t begin with who you are or what you do, because that’s not the most relevant starting point. Instead, you begin with what you’ve understood and what you’ve seen.

That changes the dynamic quite quickly. You talk about where things are breaking down, what’s causing friction, and what that means in practical terms. By the time you introduce a solution, it feels like a continuation of the conversation rather than a separate pitch. The client is already aligned with your perspective, which makes the decision feel more straightforward.

A different role.

Stepping back, this isn’t really about adding UX research into sales as another step. It’s about shifting the role you play in the process from someone who responds to requests to someone who helps shape what the request should be. That’s a more involved position, but it’s also a more valuable one.

It requires a bit more upfront thinking and a willingness to sit in uncertainty slightly longer than usual.

In return, you get better conversations, better alignment, and a clearer sense of whether the work is worth pursuing in the first place. Over time, that changes the type of projects you win and the way you’re perceived by clients.

The bottom line.

Most agencies are very good at building things once the direction is clear. Far fewer are good at helping define that direction, especially within the constraints of a sales process. That’s where this approach creates an advantage.

It closes the gap between agency assumption and understanding.

By bringing a small amount of structured thinking into the early stages, you position yourself differently. You’re not just another option responding to a brief, but someone helping to make sense of the situation, and providing the forward vision based on the challenges in the brief, within the context of that client.