Supabase
The open source Firebase alternative
Start new thread
Rory

AMA session on Product Led Growth with Rory - Head of Growth at Supabase ⚡️

by•
As the leader of Supabase's growth team from our early days of just hundreds of users, I'm thrilled to say that we now have hundreds of thousands of incredible users 🚀 Our open-source database tooling and product-led growth approach have made us a well-known name in the developer community We have also been called a meme company that builds databases Today Supabase has over >46K Github stars and >65K twitter followers - Supabase has consistently been one of the fastest growing open-source developer tools since our launch I’m here to answer all your questions related to product-led growth, open-source, meme marketing, hiring for growth, launch weeks, community building, remote work, and of course….Supabase! If you ask a question we will pick some random winners for the final few (extremely limited edition) gold Supabase snapback caps I'll answer all questions by March 13th, 23:45 PST
106 views

Add a comment

Replies

Best
Oleg Kurochka
What was your most surprising insight from a growth campaign/experiment? Any did that change your broader growth strategy?
Aquib Baig
Top of the Lyne
Open source has a ton of advantages to improve software but it comes with its own limitations; such as dependencies with developer schedules which can hinder internal release cycles. What rules does your team follow in ensuring you have predictable release cycles keeping in mind the dependencies from the vast multitude of developers that contribute to supabase?
Rory
@aquibbaig This one is a bit harder for me to answer compared to others in the team as it sits a bit more inside engineering. Inian and Copple have some "product principles" that the team use as a guiding light when making decisions that are geared towards enabling the team to move as autonomously as possible.
Gayatri Gaidhani
Top of the Lyne
Hey Rory, I have two questions for you: 1) Which channel has proven to be the strongest lever of distribution post-launch for Supabase? 2) Do you layer in elements to ensure the creation of user-generated content during the launch planning? p.s.HUGE fan of your work 🫡
Rory
@gayatri_gaidhani 1. Tech twitter is pretty buzzing and it's amazing how willing folks are to engage on there. It's an extremely valuable source of feedback for us too. 2. IMO this comes back to building useful features (which are stable enough for release) and good documentation. Supabase is a developer tool first and foremost. If we get these things right folks want to build and showcase the problems they can solve. Also, because Supabase is Postgres under the hood, a lot of the time we are just helping folks get more out of a database which is already amazing. p.s obviously we are big fans of Toplyne too :D
Souvik Sarkar
How do you approach user onboarding and activation, and what strategies have you found to be most effective in getting users to engage with your product? How important is customer feedback in your decision-making process, and how do you effectively gather and analyse it?
Rory
@souvik2003 User onboarding and activation is definitely an interesting topic.....Wes Bush talks about "product bumpers", "conversational bumpers", and "empty states" [1] as a good starting point. I would say activation starts really before the users even start using Supabase and relates to the product decisions we make. Downstream from this, content and examples coming both from our own devrel team and the community are essential here. If a developer can clearly see how our developer experience can help their workflow then using Supabase becomes an obvious choice. Developers have a lot of different jobs to be done and at this point Supabase is a diverse tool that can be used to solve many problems for developers. Solid fundamentals are key here - content, examples, and solid documentation geared getting developers on a straight path to achieving their objective. Feedback for us comes from a whole bunch of sources: community (which includes twitter, github and other social sources), support tickets, calls with our users. We also have a feedback widget in our dashboard and occasionally run an exit survey if someone deletes a project. As our user base has grown exponentially, the feedback has too. We are still iterating around the best process to triage, prioritise and route it to the right team. We regularly review all the feedback that comes in and factor it into the decision making process for each of the feature teams. The product teams at Supabase take a lot of ownership over the features they are working on as experts in their own product and review feedback weekly during the team syncs. We also make a lot of use of notion to facilitate getting information moved around to the team. [1] https://productled.com/book
Ankit Jena
CodeRabbit
How do you prioritize product features, keeping in mind open source contributors. Does ideas come from your team, or you take in suggestions from the community too?
First
Previous
12