GrowthStack + Claude

Run experiments, flags and growth questions from Claude

GrowthStack connects your self-hosted experimentation platform to Claude. Product managers create and change experiments, check who a change will affect, and ask growth questions in plain English, on your own data, with no engineering ticket.

Example
How many customers would see the new checkout if we target mobile users in the UK?
About 18,400 customers match (mobile, country = UK), based on the last 30 days of events. That's 23% of your total traffic. Want me to create the experiment at 50/50?
Book a 15-min demo ▶ Watch the demos

What your team can do from Claude

1 · Build
"Create a flag for the new pricing banner, on for 10% of users in the US."
Create, start, edit and pause experiments. Create flags, change targeting and rollout percentages, and kill a flag live. Build segments from any attribute.
2 · Check before you change
"If I cut the checkout test from 50% to 20% of traffic, who's affected?"
See how many customers a rule would reach before you create it. Before any change to a live experiment or flag, see exactly who stays, who drops out and what they'll see.
3 · Explain
"Why did user 4821 see variant B?"
Ask why a user got a variant or a flag, and see your traffic mix by device, browser or any request attribute over the last 7 or 30 days.
4 · Define your business in chat
"Define a funnel: product_viewed, added_to_cart, checkout_completed, per customer."
Tell Claude what your events mean, once. Map an event attribute to a business metric ("revenue is the amount on checkout_completed") and define funnel stages, at session or customer level. Claude repeats each definition back, including how it's counted and sliced, and saves it only after you confirm.
5 · Ask growth questions
"What's checkout conversion for mobile users this week compared with last week?"
Once your metrics and funnels are defined, ask about them in plain English: conversion, retention, segment behaviour. Every answer states the definition it used, the time window and what was left out, such as visitors who never logged in.

Safe by design

How it works

GrowthStack runs on your infrastructure: a Go service with your own Postgres and Redis. It exposes its tools to Claude over MCP (Model Context Protocol). When your team asks a question, the tools compute the answer on your infrastructure, and only the question and the result pass through Claude.

How it differs from vendor MCP servers. Some hosted platforms now offer MCP servers that run in their own cloud. With GrowthStack the tools run on your infrastructure, every live change is previewed and confirmed, and your business definitions are set up and checked in chat.

See it in action

From experiment to rolloutBuild a segment, preview the reach, start a test, then preview the flag that rolls the winner out, with exact counts.
Agree what revenue means, onceMixed currencies and refunds caught, a net revenue definition confirmed and saved, then used in every answer.

All six 2-minute demos →