This is a guest post from Pete Cheslock. Pete has held a number of roles across product and engineering and likes to help companies, from startups to enterprise, learn how to improve their systems and software delivery. You can find more from Pete on his website and Twitter.
For modern developer-first companies, product led growth has become the standard go-to-market strategy. If your product has an open source component, it’s even more critical to include detailed product analytics and metrics to understand where your users are coming from and if they are successful.
Technical founders often make early investments into their observability stacks, such as metrics/logs/traces, to understand when application errors occur. But often that’s where the investments end, leaving early product teams flying blind when it comes to user acquisition and behavior.
Finally, in those early years of new product development, the founders ARE the sales team: learning the best time to connect with your user can be critical to converting them. Should you email them on install? Should you reach out only after they hit a critical milestone? Can you identify when they get stuck to provide assistance? When you finally hire your first salesperson, how do you show them how prospects and customers are engaging and what stage they are at in their product journey?