
Found Quietly Tested a 25% Price Cut on Its Pricing Page
We caught Found running a live pricing A/B test with an annual billing toggle that drops Found Plus from $35 to $26.25/mo. Here's what changed and why it matters.
Diego Hernandez
Growth Marketer · · Updated
TL;DR
- Found (found.com/pricing) is running a live pricing structure test, detected via week-over-week diff with 90% analyst confidence.
- Visit 1: no billing toggle, Found Plus at $35/mo, Found Pro at $80/mo.
- Visit 2: new Monthly/Annual toggle, Found Plus drops to $26.25/mo, Found Pro drops to $60/mo (both a 25% cut when billed annually).
- Variant 2 also renames sections — "Contractor Management" replaces "Contractor payments" — and restructures the feature lists.
- FAQ content differs between the two versions, suggesting copy and objection-handling are part of the test too.
- This is a full pricing/plan-structure test, not a caching glitch — both captures are fully rendered and internally consistent.
What exactly did Found change on their pricing page?
Found is testing a complete pricing page overhaul, not a single-variable tweak. The baseline version shows flat monthly pricing with no discount lever: Found Plus at $35/mo, Found Pro at $80/mo, no toggle in sight. The variant adds a Monthly/Annual switch and drops the annual-equivalent price to $26.25/mo for Plus and $60/mo for Pro. That's a straight 25% discount for committing annually — a clean, easy-to-communicate number that's simple for the sales copy to lean on.
But the pricing isn't the only thing that moved. The variant also renames "Contractor payments" to "Contractor Management," reshuffles what features sit under each tier, and swaps out FAQ content. That's at least four variables changing at once: price anchor, billing cadence, feature taxonomy, and objection-handling copy.
Takeaway: when you see a pricing test this broad, assume the brand is testing a full narrative, not just a number.
Why test an annual toggle and a price cut at the same time?
Found is likely trying to shift the mix toward annual commitments while making the plans feel more generously priced. A 25% annual discount is a classic lever — it's the same mechanic Netflix, Notion, and nearly every SaaS company uses to lock in cash upfront and lower churn risk. The research on pricing page A/B testing is clear that price testing isn't just about the number — it's about how the price is presented. Found changing both the toggle mechanic and the underlying number at once suggests they're testing the full purchase decision, not isolating one variable.
The risk: if Plus and Pro both convert better in the variant, Found won't know if it was the lower sticker price, the annual framing, the renamed sections, or the new FAQ copy that did the work. Pricing experimentation research from Wingify is blunt about this — the whole point of price testing is to measure revenue, not just conversion rate, and multi-variable tests make that attribution messy fast.
Takeaway: a discount toggle is a cheap way to boost conversion optics — make sure you're also tracking LTV, not just sign-up rate.
How do the two pricing structures actually compare?
Here's the side-by-side breakdown of what we caught in the diff:
| Element | Visit 1 (Baseline) | Visit 2 (Variant) |
|---|---|---|
| Billing toggle | None | Monthly/Annual toggle added |
| Found Plus price | $35/mo | $26.25/mo (annual) |
| Found Pro price | $80/mo | $60/mo (annual) |
| Discount implied | 0% | 25% on annual billing |
| Section naming | "Contractor payments" | "Contractor Management" |
| Feature lists | Original structure | Restructured/simplified |
| FAQ content | Version A copy | Version B copy |
The math is tidy — both tiers get hit with the same 25% discount rate, which tells us this isn't a random price test, it's a deliberate annual-incentive structure baked in from the start.
Takeaway: round discount percentages (25%, 20%, 33%) test better than odd numbers because they're instantly legible — Found clearly knows this.
What does this tell us about how fintech brands run pricing experiments?
Found is a fintech/tax product for self-employed users, and pricing clarity matters more here than in most SaaS categories — people are already nervous about money software. Renaming "Contractor payments" to "Contractor Management" is a positioning move, not a cosmetic one. "Management" implies a broader, more active tool; "payments" sounds like a single feature. That's a bet that broader framing justifies the price tag better than a narrow feature callout.
This lines up with general guidance on pricing page optimization, which flags layout, feature emphasis, and payment plan structure as separate test variables — Found is running several of them concurrently, which is aggressive but not unusual for a team trying to ship a full repricing fast.
Takeaway: if your product serves an anxious buyer (money, health, legal), test positioning language with the same rigor you test the price itself.
Common questions
Is Found actually lowering prices or just discounting for annual plans?
Based on the detection, the headline monthly prices ($35 and $80) appear unchanged in the variant — the $26.25 and $60 figures are the annual-equivalent monthly rate. So it's a loyalty discount structure, not a permanent price cut, assuming Found keeps monthly billing at the original rate alongside the toggle.
Why would a company test four things at once instead of isolating one variable?
Pure isolation is the textbook approach, but in practice many teams test a full redesign because shipping incremental pricing page changes is expensive from a dev and legal-review standpoint. Fenyx's CRO testing guidance warns this muddies attribution, but it's a common tradeoff when speed matters more than clean data.
How confident is ABWatcher that this is a real test and not a bug?
Our analyst confidence is 90%, based on a week-over-week diff where both captures were fully rendered, internally consistent, and used the same browser environment. A rendering artifact wouldn't produce two complete, coherent pricing structures with matching feature-to-tier logic.
Should other companies copy the 25% annual discount exactly?
Not blindly. The right discount depends on your margin structure and churn profile. Priceable's pricing test framework recommends iterative narrowing — test a wide discount first, then tighten toward the number that maximizes revenue, not just sign-ups.
What should I watch for if I want to detect my competitors' pricing tests?
Check pricing pages weekly for toggle additions, price deltas, and copy changes in feature names or FAQs. Structural, internally consistent differences across visits — not broken layouts — are the signal. That's exactly the week-over-week diff method that flagged Found's test.
Your move this sprint
If you haven't tested an annual billing toggle yet, this is your sign. Found's version proves the pattern is still alive and well in 2026 — round discount number, toggle front and center, feature copy reframed to match. Before you copy it, pick one variable to isolate first. Ship the toggle alone, measure revenue per visitor for two full billing cycles, then layer in the copy and feature changes once you know the discount mechanic itself is pulling its weight.
Read next
More from the ABWatcher blog
Nov 22, 2026
Snake River Farms Tests a $25-Off Popup on Its Ad Landing Page
We caught Snake River Farms split-testing an email-capture form and $25-off modal on its landing page. Here's the math on what it would take to call a winner.
Nov 21, 2026
Snake River Farms Tests Mid-Page Email Capture on Its Ad Landing Page
SRF is A/B testing a mid-page lead-capture block and a $25-off popup against a simpler hero-only promo banner on its paid landing page, detected 2024 week-over-week.
Nov 20, 2026
Attio Is Testing a New Tier, Higher Prices, and a New Pitch
Attio is running a live pricing page test with a new $1,000 "Ultra" tier, higher Plus/Pro prices, and a new headline — here's what we caught and what it means.
Nov 8, 2026
Astro Proves "Zero Lock-In" With a Live Code Demo, Not a Claim
Astro's homepage replaces a trust badge row with a working, clickable framework demo — here's the hierarchy and interaction design behind it, detected 60% rare on astro.build.
Nov 7, 2026
Basecamp's Big Numbers: Why Hyper-Precise Stats Beat Vague Social Proof
Basecamp's homepage swaps "trusted by thousands" for 1.7 billion to-dos and 5 petabytes of data. We break down why precision beats vagueness as social proof — and how to test it.
Nov 6, 2026
Windsurf's Contrarian Bet: Selling "No Lock-In" as the Hero Message
Codeium Windsurf's homepage leads with model-agnostic positioning instead of its own model — a contrarian CRO play worth studying before you copy it.
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.