Rig the Scoreboard

Most founders can tell you exactly what their product does. Fewer can tell you how their customers measure success. And the ones who can’t answer that second question are usually the ones wondering why deals stall and renewals get awkward.

Here’s how it usually starts: a founder sees a genuine gap in the market, builds a product to fill it, and gets early traction. So far so good. The problem is that every customer has slightly different edge cases, and without a clear definition of what success actually looks like, the team starts trying to customize for all of them. That’s what kills companies. Not the gap being wrong… but the gap being just vague enough that you end up filling a different hole for every customer.

The Pricing Problem Nobody Talks About

The product roadmap turns into a feature graveyard, but that’s the symptom. The disease is pricing. If you’re chasing every edge case and can’t say no to feature requests, it’s usually because you haven’t anchored your value to something concrete enough to charge for it.

Companies that can point to specific outcomes… time saved, money saved, a measurable change in the customer’s day… can price on value delivered. The conversation is simple: we save you X, we charge you Y, and Y is a fraction of X. Companies that can’t do this are stuck pricing on features. And when you price on features, every customer request feels existential because your value proposition is only as strong as your last release. That’s a treadmill, not a business.

The fix starts with the same question most founders skip over too quickly: how does your product actually add value to the customer’s life? Not in the abstract “we make things better” sense. In the specific, measurable sense. How much time are you saving them? How much money? What does their day look like with your product versus without it? Most founders have a vague sense of this, but they haven’t made it explicit enough to build a sales motion around it, let alone a pricing model. It’s also one of the first things I look for when evaluating a company… if a founder can’t answer that question crisply, everything downstream is built on sand.

Define the Game

So you’ve figured out the value question. Good. Now here’s where most advice gets it wrong.

There’s a whole school of thought that says you should listen to your customers and align to their success metrics. That’s fine as discovery. But the conventional wisdom mostly stops there, and stopping there is a mistake.

The founders who win don’t just learn what their customers care about… they define what success should look like. They know the customer’s business well enough to set the baseline, set the targets, and own the measurement framework. They’re not asking the customer how to be evaluated. They’re telling them. This runs directly counter to the “just listen to your customers” playbook, and I think that’s exactly right. Listening tells you what problems exist. Defining the framework tells the customer what solving those problems should look like… on your terms. The incentives align when you get this right, and they quietly fall apart when you don’t.

Yes, you’re constructing an evaluation framework that structurally favors your product. That’s the point. The question is whether the framework actually holds up. Sophisticated buyers will reject a framework that doesn’t map to their reality… it falls apart in the first quarterly review and you lose credibility fast. So the discipline isn’t in pretending this is purely altruistic. It’s in knowing the customer’s world well enough that the framework you impose genuinely works for them. If it does, you’ve earned something more valuable than a contract. If it doesn’t… well, you’ve just handed the next vendor the playbook for replacing you.

You’ve become infrastructure. Once you’ve defined the metrics a customer uses to evaluate success, you’ve embedded yourself in how they think about the problem. Every onboarding, every quarterly review, every renewal conversation reinforces those same metrics. The proof points compound. And when a competitor shows up with a slick demo, the customer isn’t just evaluating a product swap. They’d have to re-derive the metrics, re-baseline the data, and explain to leadership why the entire measurement framework changed. Nobody volunteers for that conversation.

Technology is a means, not a conclusion. Most founders can tell you exactly what their product does. The ones who last are the ones who told their customers how to measure whether it’s working… and made sure the answer pointed back to them.