Good and bad reasons to be open source
How to think (carefully) about why products should or shouldn't be open source.
A practical look at how Troy at WarpStream builds automated pipelines instead of hiring SDRs.
How to think (carefully) about why products should or shouldn't be open source.
Some data on how saturated the world of developer tools has become, and why you need to stand out.
Forward thinking teams are starting to choose automated pipelines over teams of low skill SDRs.
Good pricing is about figuring out what your concrete value is to an organization: don't rush it.
Ways that founders tend to mess up their first few pilots, so you can try and get yours right.
Lessons learned from working on open source community at HashiCorp and more.
Don't freak out if your first POC doesn't go as planned – failing is actually good, if you can learn to do it well.
Replicable, data-driven frameworks for assessing and closing top candidates.
Two types of developer advocates and how to hire and evaluate them.
The right time to hire your first designer, and why.
Embracing outbound recruiting and how to find compelling talent.
I gathered data over a few months - the results will not surprise you.
How technical founders should think about when and how for your first sales hire.