Building revenue from open-source
Appwrite is an open-source backend-as-a-service platform that provides developers with databases, authentication, serverless functions, and other tools through an intuitive console for managing projects and organisations.
The project
Not long after I started at Appwrite, we launched our Cloud console, a cloud version of our self-hosted dashboard that had attracted developers ranging from engineering students and hobbyists to experienced professionals.
As the company grew, one of my major responsibilities was introducing paid tiers to this previously open-source and completely free platform. This was no small feat. It ended up being a multi-year project that required reimagining Appwrite's console experience while maintaining the developer-friendly ethos that built our community, and without alienating our existing user base.
The project
Not long after I started at Appwrite, we launched our Cloud console, a cloud version of our self-hosted dashboard that had attracted developers ranging from engineering students and hobbyists to experienced professionals.
As the company grew, one of my major responsibilities was introducing paid tiers to this previously open-source and completely free platform. This was no small feat. It ended up being a multi-year project that required reimagining Appwrite's console experience while maintaining the developer-friendly ethos that built our community, and without alienating our existing user base.
The project
Not long after I started at Appwrite, we launched our Cloud console, a cloud version of our self-hosted dashboard that had attracted developers ranging from engineering students and hobbyists to experienced professionals.
As the company grew, one of my major responsibilities was introducing paid tiers to this previously open-source and completely free platform. This was no small feat. It ended up being a multi-year project that required reimagining Appwrite's console experience while maintaining the developer-friendly ethos that built our community, and without alienating our existing user base.
My role & process
Over the course of two years, with plenty of changes and challenges along the way, I led this initiative from conception to launch and beyond. I worked closely with the founder, growth manager, and a small engineering team to conduct research, update console designs, and gather user feedback to facilitate iterations and improvements. Throughout the process, I received strategic input and feedback from our head of design, who served as a key stakeholder in ensuring alignment with our overall design vision.
Guided by our company value of transparency and reinforced by insights from competitor research and user interviews, I reworked the existing console to include new flows for billing management, payment processing during onboarding, and usage tracking. I also designed upgrade prompts and messaging that addressed user concerns around payment security and billing transparency while clearly communicating the value proposition of premium features like priority support and increased usage limits.
With the help of the engineers, we also enhanced the existing console error handling system with integrated notifications to manage payment failures, usage overages, and budget limits through email alerts and in-app notifications, ensuring organisations stay fully informed about their account status. Additionally, I independently developed the messaging framework and content for all user communications via the console and emails.
My role & process
Over the course of two years, with plenty of changes and challenges along the way, I led this initiative from conception to launch and beyond. I worked closely with the founder, growth manager, and a small engineering team to conduct research, update console designs, and gather user feedback to facilitate iterations and improvements. Throughout the process, I received strategic input and feedback from our head of design, who served as a key stakeholder in ensuring alignment with our overall design vision.
Guided by our company value of transparency and reinforced by insights from competitor research and user interviews, I reworked the existing console to include new flows for billing management, payment processing during onboarding, and usage tracking. I also designed upgrade prompts and messaging that addressed user concerns around payment security and billing transparency while clearly communicating the value proposition of premium features like priority support and increased usage limits.
With the help of the engineers, we also enhanced the existing console error handling system with integrated notifications to manage payment failures, usage overages, and budget limits through email alerts and in-app notifications, ensuring organisations stay fully informed about their account status. Additionally, I independently developed the messaging framework and content for all user communications via the console and emails.
My role & process
Over the course of two years, with plenty of changes and challenges along the way, I led this initiative from conception to launch and beyond. I worked closely with the founder, growth manager, and a small engineering team to conduct research, update console designs, and gather user feedback to facilitate iterations and improvements. Throughout the process, I received strategic input and feedback from our head of design, who served as a key stakeholder in ensuring alignment with our overall design vision.
Guided by our company value of transparency and reinforced by insights from competitor research and user interviews, I reworked the existing console to include new flows for billing management, payment processing during onboarding, and usage tracking. I also designed upgrade prompts and messaging that addressed user concerns around payment security and billing transparency while clearly communicating the value proposition of premium features like priority support and increased usage limits.
With the help of the engineers, we also enhanced the existing console error handling system with integrated notifications to manage payment failures, usage overages, and budget limits through email alerts and in-app notifications, ensuring organisations stay fully informed about their account status. Additionally, I independently developed the messaging framework and content for all user communications via the console and emails.
Results
Appwrite’s billing initiative successfully launched in January 2024, maintaining user trust and satisfaction while introducing a revenue stream for the company. We had updated console onboarding flows to include tier selection, integrated Stripe for secure payments and dedicated billing management, and implemented comprehensive usage tracking with monthly cost estimates and payment history.
This project also led to the implementation of user roles in the console and project "pausing" functionality, addressing some technical limitations we had before the project began, and optimising operational costs for the company.
Results
Appwrite’s billing initiative successfully launched in January 2024, maintaining user trust and satisfaction while introducing a revenue stream for the company. We had updated console onboarding flows to include tier selection, integrated Stripe for secure payments and dedicated billing management, and implemented comprehensive usage tracking with monthly cost estimates and payment history.
This project also led to the implementation of user roles in the console and project "pausing" functionality, addressing some technical limitations we had before the project began, and optimising operational costs for the company.
Results
Appwrite’s billing initiative successfully launched in January 2024, maintaining user trust and satisfaction while introducing a revenue stream for the company. We had updated console onboarding flows to include tier selection, integrated Stripe for secure payments and dedicated billing management, and implemented comprehensive usage tracking with monthly cost estimates and payment history.
This project also led to the implementation of user roles in the console and project "pausing" functionality, addressing some technical limitations we had before the project began, and optimising operational costs for the company.
If you'd like to learn more about the full process for this project, please feel free to reach out.
If you'd like to learn more about the full process for this project, please feel free to reach out.
If you'd like to learn more about the full process for this project, please feel free to reach out.
If you'd like to learn more about the full process for this project, please feel free to reach out.