Found Is Testing a $200 vs $100 Bonus — With Different Deposit Terms Baked In

The ABWatcher blog

Found Is Testing a $200 vs $100 Bonus — With Different Deposit Terms Baked In

Found is running a two-funnel bonus test on found.com — $200 with 20-day deposit terms vs $100 with 60-day terms. Here's what we caught and what it means for your own offer tests.

Diego Hernandez

Growth Marketer · · Updated

TL;DR

  • Detected 95% confidence via url_cluster_variant method on found.com/shipt200.
  • Variant A (/shipt200): $200 bonus offer with 20-day deposit terms.
  • Variant B (/shipt100): $100 bonus offer with 60-day deposit terms.
  • Routing is server-side, meaning the split happens before the page even renders.
  • Same brand, same page type (landing), two completely different economic offers.
  • Hypothesis: does a bigger upfront bonus beat a smaller one once deposit-timing friction is factored in.

What did Found actually change?

Found didn't just swap headline copy — it routed users into two different financial offers entirely.

Visitors landing on /shipt200 see a $200 bonus with a 20-day deposit requirement. Visitors bucketed into /shipt100 see a $100 bonus, but they get 60 days to hit the deposit threshold. That's not a cosmetic test. It's a live tradeoff between incentive size and commitment window, running on real signups, right now.

This is a pricing-page test in spirit even though it lives on a bonus-offer landing page. Found is essentially asking: will people take a smaller reward for more breathing room, or do they want the bigger check fast? That's a real behavioral economics question, not a button-color test.

Why does the deposit window matter as much as the dollar amount?

The deposit deadline is doing as much psychological work as the bonus size — shorter windows create urgency, longer windows reduce perceived risk.

A $200 bonus with only 20 days to deposit is a race. Users who convert will move fast, but drop-off from people who can't fund an account that quickly is a real cost. A $100 bonus with 60 days is a slow-burn offer — less exciting, but way more forgiving for someone still shopping around or waiting on a paycheck.

This is the classic "pain of paying" tension CRO researchers have documented for years. Convert's research on pricing tests points out that friction around money — even just how it's presented — changes willingness to act. Found isn't hiding the price here, but it is manipulating the time pressure around the financial commitment, which is arguably a stronger lever than the dollar figure itself.

Takeaway: test the deadline, not just the dollar amount. Most teams only vary the incentive size. Found is varying the clock too — that's the more interesting variable.

How does this compare to typical pricing A/B tests?

Most pricing tests vary one dial — price, discount, or trial length — not two variables stacked together like Found's bonus-plus-deadline combo.

Variant Bonus Amount Deposit Window URL
A $200 20 days found.com/shipt200
B $100 60 days found.com/shipt100

Compare that to standard pricing-test guidance from Unbounce's pricing A/B testing playbook, which usually recommends isolating a single variable so you can attribute lift cleanly. Found's test bundles amount and timeline together, which makes it harder to know which lever is driving the win — the bigger number or the tighter deadline. That's a tradeoff: faster signal on "which funnel wins overall," slower signal on "why."

If you're running something similar, decide up front whether you care about the winning combo or the winning mechanism. Those are different experiments.

What's the risk when server-side routing controls the offer?

Server-side bucketing means the same shared link can quietly point different users, partners, or channels to completely different financial terms without any visible flag.

This is the sharpest part of the detection. Two people could share the "same" Found link in a Slack channel or affiliate post and land on different bonus economics entirely. For a fintech-adjacent product, that's not a small thing — users compare notes, screenshot offers, and post them on Reddit. If someone sees a friend got $200 in 20 days while they're staring down $100 over 60, that's a trust problem, not just an experiment.

Our internal note on this one is blunt: always confirm which funnel variant a link actually lands on before you compare performance, screenshot a competitor's offer, or brief a client on "what Found is doing." URL clustering catches this stuff because the surface path differs (shipt200 vs shipt100), but plenty of server-side splits don't even give you that hint.

Takeaway: audit your own outbound links for silent variant leakage — paid ads, affiliate codes, and email links can all point to different treatment arms without your team noticing.

What should growth teams borrow from this test?

Teams should test incentive size and time pressure as separate, then combined, variables — and instrument every outbound link so no one is comparing apples to $200-bonus oranges.

Found's test is a good reminder that pricing and incentive experiments aren't just about the number on the page — they're about the full deal: amount, timeline, and how forgiving the terms feel. As Optimizely's list of CRO ideas notes, personalization and tailored terms by segment often outperform blunt, single-variable price tests. Found is doing a version of that here, just framed as a straight A/B split.

Common questions

What does "server-side routing" mean in an A/B test like this?

It means the variant decision happens on the backend before the page loads, rather than via client-side JavaScript after the page renders. Users never see a flicker between versions — they just land directly on their assigned offer, making the split harder to detect without URL or funnel-level monitoring.

Why would Found test a smaller bonus with a longer deposit window?

A longer window likely reduces drop-off from users who need more time to fund an account, even if the dollar incentive is smaller. Found may be testing whether total signups (not just bonus-driven urgency) go up when the deposit deadline stops being the bottleneck.

Is testing two variables at once (amount + deadline) a good practice?

It's faster for picking an overall winner but weaker for understanding causation. If you need to know why one funnel wins, isolate variables. If you just need a decision fast, a combined test like Found's is a legitimate shortcut.

How was this detection made with 95% confidence?

ABWatcher's url_cluster_variant method flagged two live URLs (/shipt200 and /shipt100) serving structurally similar landing pages with materially different offer terms, then confirmed the pattern via vision-AI analysis of both rendered pages.

What should other DTC and fintech brands do with this insight?

Check whether your own bonus, discount, or trial-length tests are also silently changing secondary terms like deadlines or eligibility windows. Document every live variant's full terms, not just the headline number, so support and marketing teams never contradict each other.

Read next

More from the ABWatcher blog

From the glossary

Vocabulary the article uses. See all terms →

  • Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
  • Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
  • Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
  • Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
  • Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
  • Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.

See more like this

ABWatcher catches A/B tests like this across 1,000+ brands.

Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.