![]() ![]() When an older team of 3 expands to 15, we want to know. When a new company with many users signs up, we want to talk to them. We created a few new columns in our CRM, for teams that might need attention that week. What workflows does this enable? Flag teams that need attention While you could get more granular information in the dedicated tools (Stripe, Mixpanel), the main value is in having a bigger picture in a centralized place that everyone can access.ĭeepnote is a notebook tool that can help you query the modeled data in the warehouse, fetch databases from your Notion pages through the Notion API, join and transform them as a combination of SQL and Python, and finally, update the relevant Notion fields. Keeping our Notion CRM up to date Have a look at the example notebook here. For us, there are three big segments: business users – which are further split by the company size, individual users & hobbyists, and students. Once you've defined the customer journey and associated metrics, you can include additional information about user segments. Sometimes you may want a simple sum (how many projects did all team members create in total), other times the number of users who satisfied certain conditions (what proportion of team members executed at least 5 blocks). Many of the important metrics are defined on a user level, and it's a good idea to think about how to aggregate them to a team level. In this article, I will share how you can build a PLG CRM database in Notion on your own, including: While we don't have our CRM all figured out just yet, in the spirit of building in public, we want to share some of our learnings so far. ![]() We wanted to make sure that they made their way into our Notion database, and enrich the entries with some product metrics and revenue information. It also serves as our CRM, where we manually keep track of every conversation with a customer.Īt companies doing product-led growth ( PLG), the sales conversations usually start with self-serve teams (free or paid). We use it for engineering tickets, hiring pipeline, design docs, meeting notes, policies – pretty much everything. However, our company is not built on Excel, but Notion. We decided to make do with what we have, and invest into Salesforce later once we have our first sales hire. Since our sales is still very early and mostly founder-led, we took this advice. They also came with a warning – “it might be too early for that”, and a recommendation to stick with Excel for now. ![]() "We started on X but eventually ended up using Salesforce anyway" ![]()
0 Comments
Leave a Reply. |