Problem: It's hard to know what happened to one customer or one organization in your SaaS. It's even harder if you want a cross-system view.
I found myself building parts of the platform I would need.
The events are stuck in your providers: a Stripe subscription change, a support ticket is open, a SendGrid email bounce.
Reconstructing a view for a single user or a single organization is complex, and your non-technical team does not have access to all the providers.
Each team member should be able to manage their notifications. In the go-to-market and customer success motion, timing is essential. Some event should be followed by an action while some should be ignored, but it depends on the event type and the reader's job.
If you also had those challenges in the past and would like to be among the early birds, sign up on the waitlist at https://corners.dev?utm_source=hn
charles_farfa•1h ago
I found myself building parts of the platform I would need.
The events are stuck in your providers: a Stripe subscription change, a support ticket is open, a SendGrid email bounce.
Reconstructing a view for a single user or a single organization is complex, and your non-technical team does not have access to all the providers.
Each team member should be able to manage their notifications. In the go-to-market and customer success motion, timing is essential. Some event should be followed by an action while some should be ignored, but it depends on the event type and the reader's job.
If you also had those challenges in the past and would like to be among the early birds, sign up on the waitlist at https://corners.dev?utm_source=hn