Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

End of defensibility

Freshness Warning
This blog post is over 16 years old. It's possible that the information you read below isn't current and the links no longer work.

Union Square Ventures' Charlie O'Donnell was having trouble explaining how some of his investments had defensible businesses. It occurred to him that perhaps defensibility is a flawed concept.

What is a defensible business anyway? Last time I checked, we lived in a free country with a government that promotes competition and curbs monopolistic behavior. Any customer of a company can choose to stop being a customer at anytime, right? Now, perhaps switching costs are high, but I would argue that they are capped to the degree that customers would be unwilling to sign up for a product whose switching costs were so high that, in the event of poor performance, they could not afford to leave.

And even if you think you have a good defense, are you defending the business, or the technology?

We saw a lot of late stage VC deals whose "barrier to entry" was that they were the only ones who had a certain technology. However, we started to realize .. that pure technology advantage was a fleeting notion. Maybe you were, in fact, the only ones with a technology, but that doesn’t mean you were the only ones with the solution. In other words, there are always many ways to skin a cat.

A while back I talked to a patent attorney who pointed out that a great many ideas are patentable, but those patents are likely to be useless in a business. You patent the technology, and then someone comes along and solves the same problem in a different way.

Andrew Parker
October 9, 2007 8:09 AM

Charlie wrote that post early in his tenure at Union Square Ventures. After that conversation, this is our new stance on defensibility: http://www.unionsquareventures.com/2006/08/defensibility.html Hope you find that interesting.

This discussion has been closed.

Recently Written

Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.