Savings format test
Compares showing a discount as a dollar amount, as a percentage, or as a struck-through compare-at price, scored on revenue.
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 savings format test
Coming soonBlu builds a step
About this recipe
When to use it
Dollar-off, percent-off, and compare-at framing all present the same discount differently, and this is universally cited as one of the highest-impact pricing tests you can run. This measures it on your own pricing page.
What it delivers
Tests three savings-display formats on the pricing page - dollar amount off, percentage off, and compare-at framing (e.g. $120 to $96).
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 showing a discount as a dollar amount, as a percentage, or as a struck-through compare-at price, scored on revenue.”
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 savings format testCreate a CLIENT EXPERIMENT on /experiences titled "Pricing Display Savings Format". ═══ PATH 1: Top-level configuration (Setup tab) ═══ Experience type: client_experiment Variants: - Control (25% traffic): existing savings display (whatever the current page shows) - Variant B (25%): dollar-amount framing: "Save $24" with the discount value as the headline - Variant C (25%): percentage framing: "20% off" with the percentage as the headline - Variant D (25%): compare-at framing: "$120" struck through with "$96" displayed prominently Targeting (experience-wide): - Pages: page URL contains "/pricing" OR product detail pages where discounts are shown - 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 OR Placed order within 7 days of exposure) Secondary metrics: - Click on where target_id starts with "plan-select-" or "add-to-cart-button" (CTA click-through per variant) - Checkout created within 7 days - AOV: average value of orders attributed to the variant Guardrail: bounce rate on the page must not increase >5% Schedule: 21 days, require 1,000 unique visitors per variant minimum ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes) Variant: B (dollar-amount framing) HTML target selector: .pricing-savings-display (or whatever wraps the existing savings text) Replacement HTML: <div class="savings-display" data-variant="b" data-format="dollar-amount"> <span class="savings-headline">Save $24</span> <span class="savings-context">on annual billing</span> </div> Variant: C (percentage framing) HTML target selector: .pricing-savings-display Replacement HTML: <div class="savings-display" data-variant="c" data-format="percentage"> <span class="savings-headline">20% off</span> <span class="savings-context">with annual billing</span> </div> Variant: D (compare-at framing) HTML target selector: .pricing-savings-display Replacement HTML: <div class="savings-display" data-variant="d" data-format="compare-at"> <span class="original-price"><s>$120</s></span> <span class="current-price">$96</span> <span class="savings-context">/year</span> </div> The Visual Editor allows the user to refine typography, color (red vs. green for savings), and exact dollar/percentage values to match their actual pricing. Taxonomy notes: - The actual savings amounts ($24, 20%, $120 to $96) must reflect the merchant's real pricing: these are placeholders that the user adjusts in the Visual Editor. - For ecommerce, the goal fires on Placed order.total_price; for saas, on Subscription started.amount. - Compare-at pricing requires the merchant's actual original price to be available; if pricing varies dynamically, the recipe assumes a stable comparison baseline.
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-display-savings-format-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 