SaaS Growth Experimentation Course

Fair warning before you enrol: this course will tell you not to run most of the tests currently on your backlog. Not because the ideas are bad, but because at your traffic level the result would be unreadable and you would ship it anyway based on a 9% lift that was noise. That is the problem the three lessons are built around.

Who should take this

Growth marketers and product managers at B2B SaaS companies with limited traffic. Call it 2,000 to 50,000 sessions a month, a few hundred signups, and a boss who has started asking about experiment velocity.

If you run a consumer product with millions of sessions, skip it. Standard experimentation practice works fine when you can detect a 2% lift in four days. The whole design of this course comes from the opposite situation, where a homepage test needs eleven weeks to resolve and the homepage will have changed twice by then. The wider context on where experiments fit sits in SaaS Growth Marketing.

What you will be able to do after each lesson

Lesson	Time	Capability you gain	Material
1. Find the constraint	30 min	Locate the one funnel step where a 10% improvement changes revenue, and ignore the rest	Constraint worksheet
2. Design a readable test	35 min	Calculate minimum detectable effect at your traffic and kill tests that cannot resolve	Sample size calculator
3. Decide and scale	25 min	Write the decision rule before launch and run the post test meeting in ten minutes	Decision rule card

Lesson one is funnel arithmetic, not brainstorming. You will compute the revenue impact of a 10% improvement at each step, and in almost every case one step dominates so heavily that everything else becomes a distraction. Teams routinely discover their constraint is trial to paid, then realise every test they ran last quarter was on the signup form.

• Lesson two is where the backlog gets cut. You enter your weekly traffic and baseline conversion rate, and the calculator returns the smallest effect you could actually detect in four weeks. If that number is 35%, no button copy change qualifies, and you need a structurally different test: a new offer, a removed step, a changed pricing display. Building a growth experimentation program goes deeper on how to build a backlog that survives this filter.

Lesson three is the part that saves relationships. The decision rule gets written into the brief before launch: what result ships it, what result kills it, what result means run it longer. Without that, the post test meeting becomes a negotiation between whoever wants the feature and whoever wants to be right.

The materials

Three files, all editable, all delivered by email as you work through the lessons.

• Experiment brief template. Hypothesis, primary metric, guardrail metric, minimum detectable effect, decision rule, owner, end date. The growth experiment brief template is the same file, available separately if you only want that.
• Sample size calculator. Input weekly traffic and baseline rate, output minimum detectable effect and required run length.
• Decision rule card. One page, printed or pinned in Slack, that the post test meeting follows.

How this differs from generic CRO training

The core assumption. Standard CRO material teaches you to test constantly and let volume find the winners, which is correct advice at consumer scale and actively harmful at 8,000 sessions a month.

Here the advice inverts. Run fewer, bigger tests. Accept that some decisions will be made on directional evidence and label them as such in writing. Use qualitative research, session replay and sales call review to generate hypotheses, because at your traffic the hypothesis quality matters more than the test count. Tooling choices follow from that, and A/B testing tools for SaaS compares what PostHog, Amplitude and the rest actually give a low traffic team.

What the course does not cover

Statistical theory beyond what you need to act. There is no derivation of the t test, no Bayesian versus frequentist debate, and no discussion of multi armed bandits, which are genuinely useful and genuinely irrelevant until you have enough traffic to feed them.

It also does not cover SEO testing, which behaves differently because the unit is the page and the feedback loop runs in months. SaaS SEO Sprint handles that. And it assumes you already know your funnel definitions; if you do not, take the SaaS marketing foundations course first.

Time commitment and format

About 90 minutes of reading and worksheet time, delivered one lesson per day over three days. Every lesson page is fully readable on the site without an email address. The sign up exists to pace the lessons and send the templates, not to gate content.

Realistically, add two to three hours in week one to actually compute your funnel constraint with real data, because pulling clean numbers out of Amplitude or your warehouse is always slower than the arithmetic itself.

Start here

Begin with lesson one, or if experimentation is one part of a broader growth remit, read B2B SaaS growth for where it sits alongside channel work. For the tactics that get mislabelled as experimentation, growth hacking for SaaS is the honest version.

Pull your funnel numbers before you start lesson one. The course is close to useless without them.