Billing toggle default test
Tests whether defaulting the pricing toggle to annual rather than monthly earns more, counting annual plans at full annual value.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Set up the toggle default test
Coming soonBlu builds a step
About this recipe
When to use it
Defaulting the pricing toggle to annual is cited for a direct LTV impact, but the effect size depends on your own price sensitivity. This tests annual-default against monthly-default directly.
What it delivers
Tests defaulting the pricing page billing toggle to annual versus monthly, measuring the direct revenue and LTV impact.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Tests whether defaulting the pricing toggle to annual rather than monthly earns more, counting annual plans at full annual value.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Set up the toggle default testCreate a CLIENT EXPERIMENT on /experiences titled "Pricing Toggle Default". ═══ PATH 1: Top-level configuration ═══ Experience type: client_experiment Variants: - Control (33%): existing default state (whatever the page currently shows: most often monthly) - Variant B (33%): default to ANNUAL billing toggle position with savings highlight ("Save 20% with annual") - Variant C (34%): default to MONTHLY billing toggle position (most-likely current state, but explicit) Targeting: - Pages: page URL contains "/pricing" - Devices: any - Audience: all visitors - Display frequency: always Primary metric: goal_completed_in_experience where experience_id = <this> AND value > 0 (revenue from Subscription started within 7 days, weighted by billing-period: annual subscriptions count for full annual value) Secondary metrics: - Subscription started where billing_period = "annual" (annual conversion rate per variant) - Subscription started where billing_period = "monthly" (monthly conversion rate per variant) - Toggle-interaction rate (Click on where target_id = "pricing-toggle") - AOV per signup (annual signups have ~12x higher first-payment value than monthly) Guardrail: total Subscription started rate must not drop >3% (the test shouldn't suppress overall conversion; it should shift mix toward annual) Schedule: 21 days, 1,000 visitors per variant minimum ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes) Variant: B (annual default + savings highlight) HTML target selector: .pricing-toggle (the toggle UI between monthly and annual) Replacement HTML: <div class="pricing-toggle" data-variant="b" data-default="annual"> <div class="toggle-buttons"> <button class="toggle-option" data-period="monthly" id="pricing-toggle-monthly">Monthly</button> <button class="toggle-option toggle-option--active" data-period="annual" id="pricing-toggle-annual"> Annual <span class="savings-badge">Save 20%</span> </button> </div> </div> Lightweight JS: - On page load, programmatically set the toggle to "annual" position - Update all displayed prices to annual values - Add a `data-billing-default="annual"` attribute on body for analytics Variant: C (monthly default: explicit baseline for comparison) HTML target selector: .pricing-toggle Replacement HTML: <div class="pricing-toggle" data-variant="c" data-default="monthly"> <div class="toggle-buttons"> <button class="toggle-option toggle-option--active" data-period="monthly" id="pricing-toggle-monthly">Monthly</button> <button class="toggle-option" data-period="annual" id="pricing-toggle-annual"> Annual <span class="savings-badge">Save 20%</span> </button> </div> </div> The Visual Editor allows the user to refine the savings-badge copy, toggle styling, and animation. Ensure the toggle-button Click on events fire properly in both variants so the toggle-interaction rate metric works. Taxonomy notes: - Most modern SaaS pricing pages already have a monthly/annual toggle: this experiment changes the *default* state on page load. - Subscription started.billing_period (or equivalent) must be populated to measure the annual-vs-monthly mix shift. If your subscription event doesn't track billing period, add it. - Annual default tends to lift annual conversion rate by 30-50% with little impact on overall conversion: the savings come almost entirely from mix shift, not from new conversions. - For trial signups (which usually start as a free trial then convert to paid), this experiment is more impactful at the trial to paid step than at the trial-signup step. Plan your downstream measurement window accordingly.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /pricing-toggle-default-test in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 