Posts from Fred Wilson

USV’s current thesis is:

Enabling trusted brands that broaden access to knowledge, capital, and well-being by leveraging networks, platforms, and protocols.

https://www.usv.com/#thesis-3-0

That last word is powerful but unfortunately less understood than the other words in that sentence.

Protocols have been around forever and are well-understood codes of conduct between people.

In computer science, protocols are the same thing, codes of conduct.

I like this definition of computer protocols from the Cloudflare website:

Standardized protocols are like a common language that computers can use, similar to how two people from different parts of the world may not understand each other’s native languages, but they can communicate using a shared third language. If one computer uses the Internet Protocol (IP) and a second computer does as well, they will be able to communicate — just as the United Nations relies on its 6 official languages to communicate amongst representatives from all over the globe. But if one computer uses IP and the other does not know this protocol, they will be unable to communicate.

https://www.cloudflare.com/learning/network-layer/what-is-a-protocol/

Protocols have been around for as long as computers, but we are at the beginning of a golden era of protocols that I like to call “web3.”

Until recently protocols were mostly free and unmonetized. We all use the HTTP protocol every day to access web pages. We all use the SMTP protocol every day to send email. But these protocols are free to use and don’t make money for any company or project or individual.

With the arrival of Bitcoin back in January 2009, we got a protocol that had monetization built in.

And since then, computer scientists have been creating web3 protocols for all sorts of things, most of which have a token that monetizes the protocol.

The monetization is not just about enriching the creator(s) of the protocol. It is also used to incentive usage of the protocol and operation of the protocol. In the Bitcoin protocol, that is operating mining computers that secure the Bitcoin network. In the Helium protocol, that is operating hotspots that connect the network. In the Ethereum protocol, that is staking to secure the network. In the Filecoin protocol, that is operating storage systems that provide decentralized storage.

It is the monetization that sustains these protocols and makes them reliable for others to use and build on them.

And with sustainable and reliable protocols, we will get a new architecture of services that will be much more interoperable.

Let’s look at mobile messaging. Most of my friends and family are on iPhones. I use an Android. Messaging does not work very well between iPhones and Android phones. Many people in the world use Whatsapp for mobile messaging. But Whatsapp doesn’t speak to iPhone’s messaging app. Nor does Signal. And Signal doesn’t talk to Whatsapp. And so on and so forth.

If every mobile messaging app was built on a monetizable protocol, that was sustainably reliable because operating it made people and companies money, and if developers were incentivized to build on it so they could also make money, we would have a different situation. All of our mobile messengers would interoperate with each other.

The same situation will play out in every computing sector over the next few decades as these web3 protocols are designed, built, shipped, and built on. We are in the early days of this golden era of protocols, but we already have many working extremely well in the decentralized infrastructure and decentralized finance sectors.

It upsets me that protocols are both so powerful and also so poorly understood by the media, the mainstream, and the government.

The White House recently put out a document that said “crypto assets currently do not offer widespread economic benefits” suggesting that web3 was not economically important to the US. While the economic benefits of web3 are not widespread today, they are quite powerful and will eventually impact every economy and every market. And pouring cold water on them will not make them go away. Thankfully.

Six months ago, I wrote about Direct Air Carbon Capture and ended with this:

I remember hearing that “we’ve spent hundreds of years taking carbon out of the ground and putting it into our atmosphere and we are going to spend hundreds of years taking carbon out of the atmosphere and putting it back into the ground”. I believe DAC will be a big part of how we do that.

I used that quote again on a blog post I wrote yesterday on the USV blog about Noya, a Direct Air Capture company that USV recently invested in.

Sometimes when I write about something here at AVC, it is a sign that it will end up on USV.com. This was one of those times.

I have watched so many leaders over the years in my various roles as lead investor, board member, board chair, investor, and advisor.

And one thing I have learned from this front-row seat is that leading from the heart is very powerful.

A leader can be the most brilliant product person, strategist, entrepreneur, and business builder, but if they cannot get people to follow them, trust them, and care for them, they will not be an effective leader.

This is a hard lesson to learn. It is a fairly natural tendency to hold your emotions in check when you are in front of a large group of people. We are taught to project strength in moments like this.

And it is also a natural tendency to hold back the most difficult-to-process information, like a fundraising process that is not going well, or conflicts in the board room, or a co-founder relationship that is fraying, or the loss of the biggest customer, or a key supplier relationship that is at risk.

And yet, it is these exact moments where leaders develop that followership, trust, and care from the team.

I am not suggesting that leaders should become deeply emotional every time they talk to the team. I am not suggesting that leaders share every little detail about the business with the team. I understand that some details about the business need to stay confidential until the appropriate time to communicate them. There is a balance to all of this.

I am suggesting that more transparency, more vulnerability, and more honesty is the winning formula and when you are choosing between the two, choose these things.

One of my favorite stories about this comes from a particularly difficult moment in my career where I had to transition a founder out of the company they started. It was the night before the all-hands where the CEO transition was going to be announced. I asked the founder if they were going to attend the all-hands and the founder said no. I then asked the founder what I should tell the team. The founder said, “tell them you fired me because that is what happened”.

The next day I stood up in front of the entire company and told the team the Board had asked the founder to leave the company they started and that the Board had asked a member of the team to step into the CEO role.

After the all-hands ended, there was a line of about twenty or thirty people long to talk to me. And every single one of them waited in line to tell me the same thing which was “thank you for telling us the truth.”

It was a powerful lesson for me. And like most of the lessons I’ve learned in business, I learned it from a founder and their team.

If you are struggling to build the level of trust you want with the team in your company, try a little more transparency, vulnerability, and honesty in your communication style. It will pay dividends.

The first project launched this week on our portfolio company Blackbird‘s platform.

It is a friends and family program at a restaurant in Williamsburg Brooklyn called Gertie.

Blackbird wrote about it today on their excellent Supersonic blog:

Throughout, when you tap Gertie’s Blackbird-powered NFC chip (shown above), wonder awaits. On the first tap, a free cookie sourced from a nearby bakery comes your way. On the second, coffee is on the house. Over time, one-size-fits-many freebies give way to the kinds of perks you’d expect as a regular, like a personalized coffee mug that is always at the shop awaiting your arrival.

I also really love how Blackbird’s founder Ben Leventhal describes the company’s mission:

Blackbird is here to create meaningful connectivity between restaurants and their customers. By connectivity, we mean direct connectivity, where guests know that the more they show up, the better their experience is going to be. We hope to help restaurants think about benefits as a line of business, not just a bunch of random comps. If we can, restaurants will begin to deliver magic at scale, and get more profitable in the process. We’ll turn good restaurants into bonafide thrill rides — spontaneous, consistent, and compulsively enjoyable.

The Blackbird platform is a great example of what can be built on a web3 stack when most of the web3 stuff is under the hood, invisible to the users but powering things that can’t happen on a web2 stack. Some people call this “web 2.5” but I just call it awesome.

Blackbird will continue to introduce capabilities and develop its platform much further. So in the weeks, months, and years ahead, when you see this on the host stand when you walk into an establishment, you will be in for some of that awesomeness.

USV is an investor in Bolster, a marketplace for fractional and full-time executive talent for startups and growth companies.

This week Bolster launched a daily short (5min) podcast and email with actionable insights and advice from founders, operators, and investors. It is called The Daily Bolster.

I did a Daily Bolster episode and it is featured today. I’ve embedded it below and you can watch it here if you are reading AVC via email.

The daily email contains a short pull quote from the daily podcast which in and of itself is quite useful but is also a prompt to spend five minutes and watch or listen to the daily podcast.

I strongly recommend founders and operators in the startup and growth sectors subscribe to the daily email and podcast. You can do that here:

Subscribe to The Daily Bolster Email

Podcast:

Subscribe on Apple Podcasts

Subscribe on Spotify

Subscribe on YouTube

Mike Zamansky is the person who got me interested in K12 Computer Science Education in NYC, a cause I have now contributed almost fifteen years of my life to.

Our family’s public charity, Gotham Gives, has been funding the work we do in K12 Computer Science Education in NYC for the last decade and a month or so ago, the Gotham Gal recorded a podcast with Mike talking about the early days of our journey into K12 Computer Science, how we met, and what transpired.

That podcast is up on YouTube and I’ve embedded it here. It’s about ten minutes long.

Last Thursday, three new blog posts hit USV.com announcing our three new analysts:

This is our tradition at USV. When someone starts at USV, we ask them to write a post on the USV blog introducing themselves. This helps founders who come to talk to us about their companies understand the folks they will be talking to.

Grace joins us from Silver Lake where she was working on their ESG strategy.

Nikhil joins us from Daffy where he was helping to build charitable giving software.

Matt joins us from Aerofarms where he was working on vertical farming.

At USV, they will work with all of us areas helping us find, invest in, and support founders working in our thesis areas. I am excited to work with them for the next two years.

I saw Dan Primack assert that the venture capitalist’s customer is their limited partners in this tweet about the Citizen app, the recap, and their VCs:

Regular reminder that, ultimately, VC funds works for their limited partners, not for their portfolio companies. https://t.co/0uGuk8KUZo

— Dan Primack (@danprimack) February 25, 2023

I DM’d Dan to let him know that is not the right way to think about the venture capital business.

Back in 2005, in the early days of this blog, I wrote this post on the topic.

The entrepreneur is the customer and the LP is the shareholder. That’s the only way to think about the venture capital business that makes sense to me.

https://avc.com/2005/11/the_vcs_custome/

I encourage everyone to read that post. It is one of the most important things I’ve written about the VC/founder relationship and I would not change a single word in it almost twenty years later.

When a new technology comes to market, we often look for “native” applications of that technology.

What is a “native” AI application?

What is a “native” Web3 application?

I have not seen a better articulation of “native” than my partner Albert’s post from 2009 on native mobile applications.

He started out by laying out the new primitives that mobile smartphones made available to developers. In the case of mobile, he cited:

• Location
• Proximity
• Touch
• Audio Input
• Video Input

He then went on to say that it would be the combination of these primitives, more than any individual one, that would make for native mobile applications.

And then he went on to lay out some of the applications he was seeing that were native.

If you want to figure out what the native AI applications or the native Web3 applications will be, or the native AI/Web3 applications, start by laying out the new primitives and going from there.