GrowthBook

What do you like best about the product?

What I like best about GrowthBook is that it gives teams a practical way to manage feature flags and experiments without making the workflow overly heavy. The interface is generally clear, and it is useful to have experimentation, rollout control, and analysis connected in the same environment. That makes it easier to move from idea to test to decision with more structure and less back-and-forth between teams. I also appreciate the flexibility on the integration side, because it can fit into an existing data stack rather than forcing a completely closed setup. From a ROI perspective, that matters a lot, since it allows teams to get value from experimentation and progressive delivery without necessarily committing to a much larger platform than they need.

What do you dislike about the product?

What I dislike is that some parts of the product still require a certain level of technical comfort, especially when setting up experiments properly, validating data inputs, or making sure the configuration is aligned with the broader analytics environment. The UI is clean overall, but some concepts are not instantly obvious for less experienced users, so onboarding can take a bit of time. Performance is generally good, although the experience depends a lot on how well the underlying setup is implemented. Support and documentation are helpful, but there is still a learning curve if teams are new to experimentation frameworks. On the AI side, this is not really the core reason to use the platform, so its value is much more in control and measurement than in intelligence-led automation.

What problems is the product solving and how is that benefiting you?

GrowthBook solves the problem of releasing features and running experiments without enough control, visibility, or consistency. Instead of relying on ad hoc deployments or fragmented testing practices, it gives teams a more structured way to expose features progressively, define experiments, and evaluate results with a shared framework. For me, that means safer rollouts, better coordination between product and engineering, and more confidence when making decisions based on test outcomes. An additional benefit is that it helps create better discipline around experimentation itself, because teams are encouraged to think more clearly about hypotheses, targeting, and measurement before launching changes. That improves both speed and decision quality over time.

What do you like best about the product?

I use GrowthBook for A/B testing and find it powerful and versatile. The more I set up within GrowthBook, the more I liked it. I appreciate the ability to conduct experiments, which is a key feature for me.

What do you dislike about the product?

The home page could be more intuitive to use and setup key features, and the dashboard could be more immersive. It's a bit barebones for someone just starting without either technical knowledge or having a technical partner. However, I understand that may not be the target demographic.

What problems is the product solving and how is that benefiting you?

I use GrowthBook for A/B testing and product optimization.

What do you like best about the product?

We gather our experimentation data in a separate platform and needed a place to load and analyze it. Growthbook is the only tool we found that allowed us to do that.

What do you dislike about the product?

Nothing so far. I like how the queries are visible so you can see what's happening "under the hood." Other platforms don't allow that.

What problems is the product solving and how is that benefiting you?

Getting accurate analysis from our experimentation data

What do you like best about the product?

It's pretty straight forward if you know your way around other A/B testing tools. Does a really good job at that. Works well in our frontend as well as backend.
Their support is outstanding, we had an issue with our store and I was suspecting growthbook as one of the causes. Quick turnaround and hinting us the right direction did help us fix the real issue of a synchronous script from a third party not loading in time, something I had missed in the network tab myself.

What do you dislike about the product?

Well, could be slightly more opinionated for starters.

What problems is the product solving and how is that benefiting you?

conversion rate optimisation

What do you like best about the product?

The ease of technical implementation, flexibility of connection to data analysis tools and easy management of tests through the tool.

What do you dislike about the product?

I think there could be more use cases and support in the tool's onboarding process

What problems is the product solving and how is that benefiting you?

He helped me make robust customizations within my product by connecting several variables in my code without my technology team having to spend hours on development and also helped me analyze A/B Test data faithfully