
How many tests can your release train afford?
A test takes several changes, and each change waits for a release. Count how many tests your calendar allows, and which ones to move off the train.
Topic
Campaigns, paywalls, upgrade prompts and tests, and how growth teams can ship changes without a ticket queue or a release train.
9 posts

A test takes several changes, and each change waits for a release. Count how many tests your calendar allows, and which ones to move off the train.

A failed payment isn't a cancellation. What a screen can do about it (one calm notice, a link to your billing page), and what it can't.

Eight stages from first paywall to win-back: what the user is deciding, which screen fits, which to skip, and where a small team should start.

With a few thousand visitors a month, most tests can't see small wins. How to size a test before you start, read the interval, and what to do instead.

Copy, offers and banners change often, but each change rides a release train. What the wait costs, three ways to cut it, and when to leave it alone.

One question, a few fixed reasons, room to explain. What to ask people who cancel, what to skip, and how to avoid trapping them.

A cheaper price can lift paywall conversion and still lose revenue. Pick one deciding metric, add guardrails, and decide how long to wait for renewals.

We ran identical versions against each other. Looking daily gave a false winner 27% of the time. Code included, with ways to avoid it.

Asking at sign-up is early. Look at triggers tied to a useful moment, how often to ask, and how to log shown and clicked.