I’ve reviewed around 30 @a16z CSS applications across the last few days and wanted to share some key mistakes I’m seeing.

🧵👇

Building @frens | @orangedao | @a16zcrypto CSS

You only get one shot to really help reviewers understand what you’re building, why it matters, and why you’re the right team. This means the most important question is “Describe your project. How will it capture value?”

1 ) Unclear 1-liners 💡 If a reviewer cannot understand what you’re building in the first 1-2 sentence of your answer, they won’t have the right context for everything else. This is where the “Uber for X” or “Stripe for X” model can come in handy.

Damn, and I nearly went with the “Crowdstrike of Crytpo”