Anonymous 1:1 · Edition 010 · November 2026

Buyer Perception

I'm not buying what it does today. I'm buying what I can build with it tomorrow

Buyer Persona:
Product Manager
Employer:
Venture-Backed Startup
Company Size:
Under 500

Technologies covered

In-App MessagingDocumentationProduct Analytics

Topics covered

Evaluation criteriaSales processCustomer success

Stage

EvaluationSelectionIn-life

Prepared by

Gordon Smith

Founder, Buyer Perception

Buyer Perception

Most vendors selling to product teams pitch what the tool does today. This buyer evaluates what it becomes. A product manager at a venture-backed startup going through rapid growth, they run the platform side of a business with a lean product team. Their buy decisions are based on development pathway: not the current feature set, but how much the tool's value compounds over time. They replaced an established platform with a startup's product because the switching cost was trivial. They chose a pricier tool over building one, because it could power features inside their own product. And when the solution was niche enough that no vendor could save meaningful build time, they built it themselves without hesitating. The framework is consistent. It is not how most vendors selling to product teams are positioning.

Gordon Smith, Buyer Perception

“The price is the same, but we keep getting more value out of it”

What's the framework when you're deciding whether to buy a tool or build it in-house?

A lot of the time we are buying. We don't have that much bloat in terms of tooling. Everything is kind of serving its worth. But the decision depends on a few things. If it's relatively inexpensive to build and the solution we need is niche enough that generic tools on the market wouldn't save us enough build time, we'll do it ourselves. We built our own notification system because the trigger logic was too complex for any off-the-shelf solution to justify the lock-in. But if a tool can get us from zero to value quickly, and the development pathway is strong, we'll buy.

What do you mean by development pathway?

How much potential is there with the products and services they offer in the future to have compounding value through our interaction with it. It's not just a tool for us. If it can actually help us build features in our own platform, the value we can derive keeps growing even though the price stays the same. That's what tipped one decision recently. The tool wasn't cheap, but it had the technical capability to do something really quite sophisticated. Multiple people could contribute to it without needing to code anything, and we went from zero to having everything we needed in about two weeks.

You also replaced an established platform with a much smaller vendor's product. What drove that?

It was a bit of a no-brainer. Compared to other tools we've invested in, this one is pretty inexpensive. It's a no-code solution, so once you've set up the integration it's very easy to maintain. We worked it out as saving roughly a week of engineering time per year, which has already paid for itself. And the key thing: replacing it in the future isn't going to cost us much effort. If they went bust, building a stopgap ourselves isn't difficult. So the risk exposure was low enough to make the switch.

“The ones who understand how the product works under the hood can talk about it as a true expert. Those who are just seeing it as the thing they're trying to shift will struggle to convey its value.”

Product Manager, Venture-Backed Startup
Buyer Perception

“Vendors assume you're always thinking strategically. I'd love it if I was, but the reality at this stage is different”

What do vendors get wrong when they're selling to product teams?

They often make assumptions about what your focus is. At a startup, the focus is shifting constantly. You've got your north star metric, but that's not in the front of my mind every day. I'm actually thinking about a critical deal that's on fire, where we need a product person in the room to talk about what the product vision looks like. Vendors assume you're always thinking strategically. I'd love it if I was, but the reality at this stage is different.

So they're not segmenting by company stage?

Not really. When I worked at a large enterprise, it was a completely different scale. You're either looking at such a niche problem that the vendor can't relate to, or you're thinking so broadly that their solution is just a tiny part of it. At a startup, it's a different world entirely. Getting that balance right is actually quite hard, and most vendors don't try. I get cold emails where they're talking about capabilities that aren't anywhere near our roadmap. Taking a big gamble, big assumption on focus.

“You need to know what success is for me first”

Can you describe a really good sales experience you've had with a vendor?

One vendor does a really good consultative sell. They take the time to teach you how to get more value from the product, for free. They give tips and advice on how to improve what you're doing, and then they start to paint a really nice picture about premium features, or where usage limits are holding you back. It builds the case really clearly. And it's all tied back to business value or customer value.

So they proved the value before they asked for the money?

Exactly. They helped us design a system that solved one of our biggest internal problems, using their product. That's not something they charged for. But it drove the stickiness, and then the business case for expansion was obvious. That's what most vendors miss. They come in asking for budget before they've understood what success looks like for the buyer. You need to know that first. If you can prove you can deliver it through quicker wins, the trust builds. And once it's there, I'm going to back you when you come to me with something that needs budget behind it. It helps me as a product person build and justify the internal business case.

What about customer success people specifically? What separates the good ones from the rest?

The ones who take the time to understand how the product works under the hood. Who can really talk about it as a true expert to their customers. Those who are just seeing it as the thing they're trying to shift will struggle to convey its value and understand how it can deliver value to different customers in different ways. But if they understand the actual inner workings, what the product was built to solve and how it does it, they can go and talk about it with way more authority. The ones who partner closely with the product team end up doing much better.

Buyer Perception

“We're basically hacking around it”

What's the biggest operational challenge you're dealing with right now?

Data hygiene. Our data is very scattered. Product analytics sits in one system, commercial information in another, marketing comms in a third. Notes from customer interviews and sales discussions sit somewhere else again. We don't have a single identity domain for all of our customers, so it's very difficult to understand the health of a customer holistically.

How does that play out day to day?

It becomes anecdotal. Someone says they spoke to a customer and things are going well, and they'll quote a metric that looks fine. But then you do a discovery interview with that same customer and they tell you they're having a nightmare. Unless you process that properly and put it somewhere visible, it just gets siloed. Our leadership wants to know what's going on across every customer, and it's expected that product knows too, not just sales or account management. But right now that's really difficult and inefficient.

So you've ended up building your own solution?

We're building a single source of truth internally. It runs automatically every day, goes through everyone's notes and messages, and compiles micro-updates rather than big wordy dumps that nobody reads. It goes through a review process to keep the quality high. It's high effort, it's not perfect, but it's the best we've got. The alternative is noise. You either get a wall of text that everyone disregards, or you get the AI summarising its own output and you're getting further and further away from what was actually said.

From this interview

2 weeks

from zero to full deployment on the tool bought for its development pathway, not its current feature set

1 week of engineering time

saved per year by a no-code replacement that already paid for itself

4+ systems

where customer data sits, with no single view connecting them

1 vendor

won the expansion by proving value for free before asking for budget

This edition is part of an ongoing series of anonymous buyer interviews conducted by Buyer Perception. Every participant's identity is protected. No company names, product names, or identifying details are included.

These buyers weren't talking about you. Yours are.

We run the same conversations with your lost prospects and churned customers.

Free 30-minute call. No homework, no commitment.