The Math Behind the Popup: Forecasting Recovery Revenue for Rent the Runway

Marketing Academy · Field Work●Conversion Rate Optimization

All projects·From: Exit Intent and Recovery

CoreForecast· 45 minutes

Rent the Runway

Objective: Given real traffic and abandonment numbers plus the lesson's published conversion benchmarks, forecast the revenue difference between a generic exit popup and a segmented, cart-specific one, and recommend which to build first.

Rent the Runway's growth team is deciding whether to invest engineering time in segmented exit-intent popups or ship a single generic popup this quarter. You've been asked to model the revenue difference before the roadmap gets locked.

Use the lesson's benchmark conversion rates for generic versus cart-specific exit popups to forecast monthly recovered revenue under both scenarios, then recommend one.

Before you start

What you'll need

Free path (everything below is enough to finish)

Google Sheets

FreeBuild the revenue forecast model comparing generic and segmented exit-intent scenarios

Free, sufficient for a straightforward multiplication-based forecast

Paid upgrades (optional, faster/deeper)

VWO(optional)

PaidRun the actual A/B test between generic and segmented popups once the forecast justifies building both

Full-stack experimentation platform with built-in significance calculation for validating the forecast against real results

No access? Google Sheets can track a manual before/after comparison if a dedicated testing tool isn't available yet

The process

2 steps

Step 01 of 02

Detection

The lesson's data section reports a general exit-intent conversion rate of 2.81% to 3.94%, while cart-specific exit popups convert at 17.12% (OptiMonk, 2025), more than six times higher.

Rent the Runway has 4,000 daily visitors who add an item to cart and then show exit-intent signals, with an average order value of $95. What is the monthly revenue difference between a generic popup and a cart-specific one, using the lesson's benchmark rates?

Google Sheets— Build a simple forecast model: daily exit-intent visitors x conversion rate x AOV x 30 days.

Procedure

Generic scenario: 4,000 x 2.81% = 112 recovered/day x $95 AOV x 30 days
Cart-specific scenario: 4,000 x 17.12% = 685 recovered/day x $95 AOV x 30 days
Calculate the monthly revenue for each scenario and the delta between them

Sample output

Generic exit popup:      112/day  x $95 x 30 = $319,200/month
Cart-specific popup:      685/day  x $95 x 30 = $1,952,250/month
Monthly delta:                                  $1,633,050

Healthy

The forecast shows a large enough delta that the recommendation is to build the cart-specific, segmented version even though it takes more engineering time.

Unhealthy

Recommending the generic popup because it ships one sprint faster, without ever running the revenue math to see what that speed costs.

What this means

A conversion-rate gap this large compounds fast at scale. The forecast turns an abstract 'segmentation is better' claim into a specific dollar number leadership can weigh against engineering cost.

So what do I do about it?

Symptom	Action	Effort
The roadmap defaults to the fastest-to-ship popup version	Attach a revenue forecast to each option before prioritization, not after	30 min

YouYou can do this yourself, no engineering access required.

Step 02 of 02

Capture

The lesson's Stage 4 cites Popupsmart's 2025 benchmark: 2-field forms convert at 5.1% while 4-field forms convert at 8.6%, with conversion dropping sharply past 6 fields.

The proposed cart-specific popup currently asks for name, email, phone, and a marketing-consent checkbox, 4 fields. Does the benchmark data support keeping all 4, or cutting to 2?

Google Sheets— Add a second forecast row comparing the 2-field and 4-field capture-rate benchmarks.

Procedure

Note that 4-field forms outperform 2-field forms in the cited benchmark (8.6% vs 5.1%)
Cross-check whether phone number is actually needed for the immediate use case (email confirmation of the discount)
Recommend keeping the fields that both match the benchmark's better-performing configuration and serve a real downstream need

Sample output

2-field (email, consent):   5.1% capture rate
4-field (name, email, phone, consent): 8.6% capture rate
Recommendation: keep 4 fields, the benchmark favors it and phone enables SMS follow-up

Healthy

The team keeps 4 fields because the data, not an assumption that 'shorter is always better,' supports it.

Unhealthy

Cutting the form to 2 fields by default because 'fewer fields' sounds like standard CRO wisdom, without checking what the benchmark for this specific case actually shows.

What this means

Form length isn't a universal rule, it depends on what the extra fields unlock. The lesson's own benchmark shows 4 fields outperforming 2 here.

So what do I do about it?

Symptom	Action	Effort
A 'shorten every form' policy is being applied without checking benchmark data for the specific case	Check the relevant conversion benchmark before defaulting to the shortest possible form	5 min

YouYou can do this yourself, no engineering access required.

Final deliverable

A monthly revenue forecast comparing generic versus cart-specific exit popups, plus a form-length recommendation, with a final build recommendation for the roadmap.

See a reference example

Sample output

MVMT, exit-intent revenue forecast (excerpt)

Generic popup: 2,000 visitors/day x 2.81% x $70 AOV x 30 = $118,020/month
Cart-specific: 2,000 visitors/day x 17.12% x $70 AOV x 30 = $718,720/month
Recommendation: build the cart-specific version first, delta justifies the extra sprint

Success criteria

You're done when you can:

Correctly calculates monthly recovered revenue for both scenarios using the lesson's benchmark rates
Recommendation is backed by the calculated dollar delta, not a general preference
Form-length recommendation cites the specific benchmark numbers rather than a generic 'shorter is better' rule