2,211 karma · joined October 27, 2010
I just did a podcast on it if you’re curious: https://theboostvcpodcast.simplecast.com/episodes/ep98-the-e...
My biggest advice is get a coach/mentor/consultant who you talk with once per week to get feedback. This is how professional sales people learn in practice (eg from a sales manager). This will accelerate you learning by a factor of 10 versus doing it yourself. They will help you read each situation and push you to focus on the right places. Otherwise it’s easy to flounder on the wrong ones.
RE metrics- closed business is the only one that matters! Do whatever gets you that as fast as possible.
I wasted a year when I first founded Amplitude trying to brute force it myself and closed a grand total of two contracts for $36k. After that I ended up working with a guy named Mitch Morando and got from $36k to $1M in ARR in less than a year. He cost me $5k a month and increased our market cap by $20M, it was well worth the investment. I’m happy to make an intro if you’d like.
Good luck on the journey ahead and I’m excited for you!
That said, this is a post-hoc justification of why having real-time analytics is bad. Delaying the data by 24 hours doesn't automatically make significance testing better or force people to incorporate more context when interpreting their data. If that's the issue, fix that problem, don't blame the tools.
There's a ton of positive value to having real time data. Just off the top of my head: 1) If you've instrumented something incorrectly you can see that and fix it right away 2) Even worse, if you've accidentally messed up a feature with a release you can know about it right away. This happened to one of our customers recently and without a real-time analytics system they wouldn't have caught it quickly (and this is a tech startup that's well regarded for their engineering that everyone here would know the name of). 3) You can observe significant changes to your user base right away, eg during a launch or if you're getting a lot of new users from a specific channel. 4) It allows you to have more confidence in deploying multiple times a day. It's a little crazy to me that the deployment of a product is faster than our ability to measure it.
I think the real issue is that we're in the early days of analytics and people don't have a great understanding of how to leverage their tools properly. It's like web search before Google or file sync before Dropbox. People will look at single data points and conclude totally crazy things. They won't have an understanding of basic things like the amount of fluctuation on a week to week basis. The largest analytics provider in the world (Google) gives away their product as an ancillary service to drive you to purchase more ads, not to have a better understanding of how your customers are using your product. I'm hopeful this will change over the next 5 years though (and for us to be a part of that!)
What this protocol does is make it so each individual failure mode is much more likely to overlap with each other failure mode. Correlating the performance of individuals when you have a one fail all fail scenario is a common solution to this type of problem.
However, equity is a significant form of compensation, not just at startups, but at large companies as well. You're missing out if you don't take some time to understand it in early stage startups.
If you were to derive how to think about employee ownership of a company as a form of compensation from first principles, you'd never come up with options and you'd never come up with a 90-day exercise window on top of that. Those are both artifacts from tax law yet it's become the standard form of compensation!
You really think the 90 day exercise window is fair? It means an employee who just left a company has a huge burden with their vested options- either come up with a lot of cash and take a massive risk or have your equity compensation be worth nothing.