VediPop

So after multiple interviews, turns out there's a need for a much more complicated product for SaaS folks. Especially as the lifecycle of the customer get's harder.

When talking to these marketers another concerned I have heard is how to respond to their inbound leads. Am turning to look more at general marketing automation.

Here is my first post about building in public.

Current Users: 0

Revenue: 0

Stage: Getting PMF

I've come across the pain of in-product messaging at every SaaS company that I've worked at. Say you want to let customers know that a certain feature is being killed - marketing will set up email campaigns and CSMs will reach out to their book; however, everyone knows that no one reads. This is why you send the email 6 weeks in advance, again 2 weeks out, one more a week out, and then another the day of.

As part of this campaign, someone realizes, "Hey, our users are in the product, we should let them know that the change is coming in product". This is great idea except that updating content inside a webapp usually requires coordination with a product team, engineering to "build it", and if it is time sensitive, coordination with the team that deploys code.

Over my 10 year career in product, I've probably spent 100 hours simply coordinating these messages. I'm building Vedipop because messaging your customers should be easy.