Who Are We Building Webiny For?

When building enterprise software, we need to have a clear picture of who our ideal customer is. This is important because it helps us make better decisions when it comes to prioritizing features, and it also helps us focus our efforts on the right things.

Our Ideal Customer Profile ("ICP")

Our ideal customer is a company that is building a digital product. This can be a website, a web application, a mobile application, or any other type of digital product. They are usually a medium to large-sized company, and they have an internal team of developers who are responsible for building and maintaining their digital products.

As an organization, they are a tech-forward innovator and prioritize staying at the forefront of technological advancements. They are also a fast-growing company and are looking for ways to scale their operations and accelerate their growth. Finally, they prioritize transparency in their business practices and place a high value on trust and partnership in their vendor relationships. Things like open source, open data governance, and open communication are important to them.

It’s also important to note that there are clear differences between the types of personas we’re serving within the ICP. We’ve got the buyer persona, the user persona and the developer persona. Let’s dive into each of these.

Buyer Persona

The buyer persona is the person who is responsible for deciding to purchase Webiny. This is usually a CTO, a VP of Engineering, or a similar role. This person is usually not a developer, but they are technical enough to understand the value that Webiny brings to the table.

For us, that persona is an important one as we’re usually working closely with them to understand their long-term plans and goals, and how Webiny can help them achieve those goals. This in turn helps us make better decisions when it comes to prioritizing features and planning our roadmap.

The buyer persona cares about things like the total cost of ownership, driving the innovation within the business, the return on investment, and the long-term value that Webiny brings to their organization. They also care about things like the security and reliability of the platform, as well as the quality of the support they get from us.

User Persona

Users are the ones who use the platform daily to do their work. They are usually content editors, marketers, or similar roles. They are not very technical, and they don’t need to be. They are usually the ones who are most excited about Webiny because it helps them do their work faster and more efficiently.

With those users, we love to talk about their daily struggles and how Webiny can help overcome them. We also love to hear their feedback on how we can improve the platform to make their lives easier. They usually have a lot of great ideas, and we love to hear them out. Even a small improvement to the user experience can make a huge difference for them given the frequency of their interactions with the platform.

These users deeply care about things like the performance and reliability of the platform as the impact of those on their work is huge. They are also the ones who are most likely to recommend Webiny to their internal peers, so we want to make sure they are happy with the platform.

Developer Persona

Developers are the ones who are responsible for building the applications that are powered by Webiny as well as customizing Webiny to fit their internal requirements. They are usually backend developers, frontend developers, or full-stack developers. This definition extends a bit as we tend to also include DevOps engineers and similar roles that are responsible for deploying and maintaining the infrastructure that Webiny runs on.

Developers tend to be the most active users in our community channels. They raise issues, ask questions, and provide feedback. Our goal is to ensure they have a great experience when it comes to configuring Webiny, making customizations on it, running project upgrades as well as operating it in production.

Developers care about things like the performance and reliability of the platform, as well as the quality of the documentation and the support they get from us. They also care about the extensibility of the platform, and how easy it is to customize it to fit their internal requirements.