Pricing page layout test
Compares your current pricing layout against side-by-side cards with a recommended plan and an interactive usage slider.
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 pricing layout test
Coming soonBlu builds a step
About this recipe
When to use it
Plan-selection and checkout-start rates can swing significantly on layout alone, before anything about the actual price changes. This tests three layouts directly.
What it delivers
Runs a client-side experiment with three layout variants to find which pricing page layout maximizes plan selection and checkout starts.
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
“Compares your current pricing layout against side-by-side cards with a recommended plan and an interactive usage slider.”
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 pricing layout testCreate a CLIENT EXPERIMENT on /experiences titled "Pricing Page Layout Test". ═══ PATH 1: Top-level configuration (Setup tab) ═══ Experience type: client_experiment Variants: - Control (34%): existing pricing layout - Variant B (33%): side-by-side cards with "Recommended" badge on the middle plan - Variant C (33%): interactive usage slider with dynamic plan recommendation Targeting: - Pages: page URL equals "/pricing" (or "/pricing/*" for nested routes) - 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 of exposure) Secondary metrics: - Click on where target_id starts with "plan-select-" (per-plan click-through) - Checkout created within 7 days of exposed_to_experience - Subscription started within 14 days Guardrail: bounce rate on /pricing must not increase >5% Schedule: 21 days minimum, require 1,000 unique visitors per variant ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control No DOM changes: measures the existing pricing page. Variant: B (side-by-side cards) HTML target selector: .pricing-section (or whatever wraps the existing plan grid) Replacement HTML: <section class="pricing-cards-grid"> <article class="plan-card" data-plan="starter"> <h3>Starter</h3> <div class="plan-price">$X/mo</div> <ul class="plan-features"><!-- features --></ul> <button class="plan-select" id="plan-select-starter" data-variant="b">Choose Starter</button> </article> <article class="plan-card plan-card--recommended" data-plan="pro"> <span class="recommended-badge">Recommended</span> <h3>Pro</h3> <div class="plan-price">$Y/mo</div> <ul class="plan-features"><!-- features --></ul> <button class="plan-select" id="plan-select-pro" data-variant="b">Choose Pro</button> </article> <article class="plan-card" data-plan="enterprise"> <h3>Enterprise</h3> <div class="plan-price">Contact us</div> <ul class="plan-features"><!-- features --></ul> <button class="plan-select" id="plan-select-enterprise" data-variant="b">Contact Sales</button> </article> </section> Variant: C (interactive slider) HTML target selector: .pricing-section Replacement HTML: <section class="pricing-slider-layout"> <div class="usage-slider"> <label for="usage-input">How many users do you have?</label> <input type="range" id="usage-input" min="1" max="500" value="10" /> <output class="usage-value">10 users</output> </div> <div class="dynamic-plan-display"> <h3 class="recommended-plan-name">Pro</h3> <div class="dynamic-price">$Y/mo</div> <button class="plan-select" id="plan-select-dynamic" data-variant="c">Get Started</button> </div> <!-- include lightweight JS to update the displayed plan as the slider moves --> </section> The Visual Editor renders the variant HTML with the user's existing site styles applied; the user refines copy, color, and spacing in the canvas before publishing. Taxonomy notes: - All Click on target_id values starting with "plan-select-" are tracked uniformly so per-plan click rates can be compared across variants. - value on goal_completed_in_experience is set by the platform when the downstream Subscription started.amount is captured.
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-page-layout-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 