The 20-Year Customer: The Best Product Advice I Ever Got Came From a Man in an Electric RAV4

From Customer-Led Development: How to Build What Your Customers Want When AI Can Build Anything — the operating manual for building what customers want when AI can build anything. See every chapter.

At 19, I showed up to a lunch with investors wearing a tie, a sweater vest, and glasses I didn't need. I have 20/20 vision. The lenses were for looking older. I had memorized my CAC projections, my marketing channels, and my distribution strategy, and I had a 20-page business plan in my bag.

Nobody ever asked for the business plan. What I walked away with instead was one sentence that I've spent the last decade learning how to actually believe.

Focus on having a 20-year relationship with your customer. If you nail that, everything else follows.

It sounds like a poster in a sales office. It isn't. Taken seriously, it rewires how you prioritize, what you measure, how you handle outages, and even what kind of product person you're allowed to be.

The lunch in the electric RAV4

I'd been selling medical and productivity apps since I was 13. My first one made the cover of Mac Life. Early on I learned two things about myself: I wasn't a great engineer, and I loved talking to customers. My real skill was clarity: hearing a customer's problem, knowing what would solve it, and pulling that solution into existence.

I won a pitch competition at my local city college, the first time a software company had won it. One of the judges, an angel investor, spent a month sharpening my pitch and then introduced me to two investors.

The first, Jacob, was what I expected: nice car, charismatic, sharp questions. His partner, Nick, was the opposite. He had created over $10 billion in enterprise value across his career, and in the early 2010s, when Teslas and Fisker Karmas were the status cars, he pulled up in an electric RAV4. I had no idea who he was.

At the end of lunch, Jacob asked Nick how much they were coming in for. Jacob suggested $25,000. Nick said, "I don't think 25 is going to do much for him. Let's both come in for 50."

Nick made maybe one investment a year. He'd just backed a kid in a sweater vest with no track record, no network, and no product. I went on to raise over $2 million for that company. A decade later, Nick invested in my current company, became one of its largest shareholders, and remains a lifelong mentor.

Context matters here. Nick had worked with Steve Blank and Frank Robinson. Robinson coined "sell-design-build," and Blank built the customer development movement alongside it: market validation before you write a line of code. Nick's whole worldview came from companies that were customer-centric from day one.

The 20-year rule

Nick gave me plenty of tactical advice over the years. Pick a problem people have. Pick a niche. Be essential. Move upmarket. But underneath all of it was a philosophy on retention:

If you can retain customers and deliver a tremendous amount of value, your business will succeed. If you're stuck selling small contracts and never adopt this philosophy, death is knocking at your door. You have a temporary business.

The 20-year frame does something useful: it makes short-term tricks look stupid. Overpromising in a sales call, ignoring a bug because the renewal is 11 months away, routing every support ticket to a bot. All of these optimize this quarter at the expense of the relationship.

Here's the standard I hold myself to now. There are only three acceptable reasons a customer leaves you: death, divorce, or dissolution. The company shuts down, gets acquired, or the champion leaves and the relationship ends with them. Everything else is a choice you made, a consequence of decisions about whether to listen.

Rule of thumb: If a customer churns for any reason other than death, divorce, or dissolution, assume you caused it.

A note on B2B vs. B2C

My first company started B2B and pivoted to consumer. Nick was always against B2C; he called it a lottery ticket. In B2B the deal is clear: make me money, save me money, or save me time. Do those well and there's money to be made. In consumer, doing them well doesn't guarantee anything. Sometimes the winning products waste your time and money. I learned that the hard way.

That's why this idea matters most in B2B. Consumer companies tend to be customer-led by default, because they have to be. B2B companies can grow for years through sales, marketing, and partnerships without ever being customer-led at scale. For them, it's a deliberate shift, not a starting point.

The product purist trap

The 20-year advice was hard for me to take because, at 19, I was a product purist. I was trained in UX research and design. That was my identity. I believed that if you build a great product, people will come.

Then I worked at Procore when it had fewer than 200 employees. I was the youngest person there, running user experience for their mobile products. And Procore violated almost every principle I thought mattered. It served construction workers who had never touched an iPad. It wasn't beautiful. It wasn't especially intuitive. It was wildly successful anyway, because it solved a real problem for people who needed it solved.

Later, at another company where basic things didn't work, I came to a stranger conclusion: most successful companies are successful despite much of what they do, not because of it.

Now, when I see an early-stage product with a gorgeous landing page, perfect animations, and obsessive iconography, polish it hasn't yet earned with customers, I'm fairly confident it won't be around in a year. All that polish is evidence they spent their time on craft instead of customers.

A great product isn't the most polished one. Often it's the one customers are pulling out of your hands so fast you don't have time to finesse it.

Value = Solution / Time

Letting go of purism meant replacing "what's the perfect product?" with a blunter question: what solves the customer's problem, and how fast?

Value = Solution / Time

The same solution delivered in one day is worth ten times more than one delivered in ten days. A perfect solution delivered too late is worth zero.

So every time a customer brings us a problem, I sort the response into three buckets:

1. What solves the problem today?
2. What solves the problem for them going forward?
3. What's the ultimate solution for them and all our other customers?

The first bucket is always the most important. Think about taking a broken laptop to the Apple Store. Of course you want your next laptop not to break. Of course you'd appreciate hearing that a fix is coming for everyone. But what you actually need is your laptop working today. Every product and every business works the same way.

I put it to my teams like this: there's no point shipping burnt toast. But there's also no point waiting for perfectly toasted bread if the customer isn't hungry anymore. Slightly under- or over-toasted beats never getting toast at all.

Rule of thumb: Solve it today first. Solve it for everyone second.

You're only as essential as you act

One of Nick's sharpest lessons: you're only as important to your customers as you let yourself be.

If your service goes down and you post "we're looking into it," then a few hours later post "we're still looking into it," your customers will conclude you're not essential, because you aren't behaving like you are. If you're not panicking about hours of downtime, why should they? They'll quietly start evaluating alternatives.

I've seen this from the customer side. I've used HR and payroll software from companies that market themselves as obsessively customer-led. They advertise a 30-second response time, but the response is a bot, and you can't reach a human to do something critical like pay your employees. The product is mission-critical. The company doesn't treat it that way.

If support is 99% bots and you can't solve a serious problem, your customer learns exactly what you are: sales-led or marketing-led. You cared until they signed.

Why we all want to be the chef

I want to be honest with product people, because I am one. There's a pull toward perfection that never fully goes away. Every product person I know has secretly wanted to be a chef or some other kind of artist. We watch The Bear and think that's who we'd be with enough freedom. I'd be a pastry chef, restarting the same recipe a thousand times in a day until it's right.

But the people we idealize for pursuing perfection have usually already won commercially. Success bought them the resources to focus on artistry instead of commerce. Michelin-starred restaurants are famously hard businesses; many survive on backers, not profits. Dig one or two levels into most celebrated artists and you'll find they were either broke their whole lives or made plenty of work they weren't proud of to pay for the work they were.

Even Apple, with unlimited distribution, has shipped failures that spent too long in the kitchen.

Perfection doesn't exist in B2B. It only exists in unprofitable spaces.

The consolation is real, though. In software you're never done. There's no such thing as a finished business. You die or you innovate. For someone who loves iterating, that's not a compromise. It's the best version of the job.

Measure what you claim to believe

Being customer-led isn't a value statement. It means examining your business model, support structure, OKRs, and incentives. If your incentives reward sales and marketing above everything else, you'll say you're customer-led while your behavior stays the same.

A customer-led organization focuses on four metrics, in this order:

You have to trust that order. If you say retention matters but the number in every board meeting is bottom-line revenue, you're not customer-led. You're revenue-led with customer-led branding.

Why good advice is so hard to take

When Nick first gave me the 20-year advice, I told him: "I know you're right. But until I've experienced why you're right, I'll keep making the same mistake."

That's the problem with good advice. Everything around you pushes the other way: focus on revenue, focus on sales, focus on marketing. And everyone already claims to be customer-obsessed. When you're doing something for the first time on borrowed wisdom, every crack makes you doubt it. Knowing isn't enough. You have to understand, because understanding is what lets you handle the nuance when the situation doesn't match the rule.

There's a reason most success advice doesn't transfer. The moment someone figures out an easy, profitable trick, others copy it and the edge disappears. You can't copy success. You can only avoid other people's failures.

Which is why, after all these years and thousands of conversations with product people, I think the 20-year rule is the only advice worth giving. It isn't a tactic that gets arbitraged away. It's a filter for every decision: does this make the relationship more likely to last two decades, or less?

Answer that honestly, every time, and most of the other questions answer themselves.

If you want the full system for building around 20-year customer relationships, including the prioritization, metrics, and org changes behind it, it's all in Customer-Led Development.

And if this changed how you think about polish, speed, and what your customers actually need from you, subscribe to the Context Limit newsletter for more ideas that fit in your head.