Skip to content

Case Study: Supabase #11434

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joethreepwood opened this issue May 7, 2025 · 0 comments
Open

Case Study: Supabase #11434

joethreepwood opened this issue May 7, 2025 · 0 comments
Assignees

Comments

@joethreepwood
Copy link
Contributor

Going to do a case study with Supabase. You may have heard of them.

Questions below, but there's also going to be a chance to do some co-marketing here. I'll chat to Dave when it's done and have put it on his radar already.


Tell me about yourself. What's your background?
And what about Supabase - what do you do, what's your role?

How long have you been using PostHog?
How did you discover PostHog?
What were you using before PostHog?

Why did you choose PostHog rather than other tools?
Are there products you've replaced with PostHog?

We launch a lot of features. What do you use?
What betas are you in, if any?
How have these helped shape the decisions you make?

Supabase and PostHog are both popular within YC. Why do you think that is?
What makes tools like ours so great for founders?

How has your PostHog usage changed over time?
What have you learned about your users, usage, and errors?
Are there any direct changes you've made as a result of this?

How are you sharing your discoveries and acting on them?
What's the biggest advantage you've discovered from using PostHog?
Is there anything we missed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant