We often get asked by our users if we can provide notifications for the customers that are approaching a limit in their products. Visibility into that type of information is incredibly useful, particularly for startups trying to identify their most active users or those ready for an upsell conversation.
However, it’s often challenging data both to get and to visualize in a user-friendly way that folks can act on. That’s because this type of data is often locked in application databases.
been thinking about this a lot since having my first kid. having run a couple of early stage startups in the US, guidance around this has always been few and far between. hopefully a good contribution that leads to more discussion around this.
> The United States is the only industrialized nation that does not offer paid parental leave. [109] Of countries in the United Nations only the United States, Suriname, Papua New Guinea, and a few Pacific island countries do not provide paid time off for new parents either through the employer's benefits or government paid maternity and parental benefits.[110] A study of 168 countries found that 163 guarantee paid leave to women, and 45 guarantee paid paternity leave. [111]
Pricing and packaging is such a crucial part of products but it's often implemented as an afterthought in patchy homegrown systems.
Homegrown systems end up costing companies millions of dollars per year as they reach scale. They also carry huge opportunity costs along the way, as engineering is constantly diverted to work on logic that isn’t new value, and the business is regularly delayed in releasing new monetization initiatives.
There's no standard for folks to build from, but the solution we've seen folks arrive at (after a long, painful road) is to decouple business logic from the codebase and create a separation of concerns across components to maximize flexibility and control. We've tried to explore that here so others can benefit from it.
However, it’s often challenging data both to get and to visualize in a user-friendly way that folks can act on. That’s because this type of data is often locked in application databases.