- evaluating the full cost of Your Trip

A Chrome browser extension that recomputes the real cost of a theme park trip while you shop.

Author  Joanna Honikman

Surface  Chrome extension (MV3)

Stage  Problem: open; MVP scoped

Summary

Disney World's advertised prices are structurally incomplete. A resort room quotes a nightly rate before tax; tickets quote a per-day price that only applies at the longest stay lengths; the line-skipping product (Lightning Lanes), dining plans, daily expenses, special event tickets, and annual passes are all separate purchases made on separate screens, days apart.

The result is a planning process where families cannot answer the only question they actually have — what will this trip cost? — until they have already committed to most of it. Disney Math is a chrome extension that browses on the user’s behalf and applies its own historic pricing knowledge to keep a running, realistic total: every line item, every fee, every add-on, expressed in the units a family can grapple with.

The problem

Price fragmentation isn't a bug in Disney's booking flow. It's a combination of design and a natural consequence of not knowing what a group will spend on vacation without making the booking process incredibly complex. It’s not up to Disney to predict what a family of four, or a group of friends on a fun weekend trip, will spend on souvenirs, but it definitely matters to the person trying to figure out whether the trip can be made affordable. The gap between what can be shown on Disney’s booking pages and the final cost could be large enough to change the decision. Planning a trip involves spreadsheets and a lot of research. It can be incredibly daunting for a first-timer trying to plan a magical family vacation.

For more experienced Disney trip planners, being able to compare dates and structure split stays to minimize spend is a useful tool. And many Disney trip planners simply enjoy the trip-planning exercise.

Why now

• Date-based ticket pricing made costs genuinely hard to compute. Prices now vary by arrival date and trip length, so no static "a ticket costs $X" answer exists, which makes this kind of real-time calculator much more useful.

• Paid line-skipping is now a standard purchase. but it cannot be bundled with the initial purchase. The extension allows the planner to budget for lightning lane purchases ahead of time rather than having to wait til 7 days before the trip to consider the cost.

• Bundled services have been unbundled. Airport transfer, once included, is now a separate vendor decision, one of several costs that moved from invisible-and-free to invisible-and-expensive post pandemic.

• Price sensitivity is high and public. Cost is now the dominant theme in coverage of and conversation about the parks, which means the framing needs no explanation.

Users

First-timer: Planning a once-in-a-decade trip. Has a budget number in mind, but no idea if it's realistic. Needs an early, honest total before making an emotional commitment.
Returning family: Been before, going again, watching costs more carefully this time. Looking at marginal comparisons: is the hopper worth it, is the deluxe resort worth it. What about a split-stay to bring the nightly average down?
Deal hunter: Comparing Disney direct against authorized resellers and package vendors. Normalized totals so two offers are actually comparable.

Primary user for v1: First-timer. Highest pain, least existing tooling, and the clearest moment of need. The other two are follow-on.

Goals for v1

• Show a complete, running trip total on the pages where trips are actually priced.

• Make every added line item legible and attributable — no black-box number.

• Express cost in per-person-per-day, the unit families actually budget in.

• Be trustworthy enough that a user would quote our number to their spouse/partner.

• Assume lowest-cost room

Non-Goals for V1

• Itinerary or ride planning.

• Booking or transacting. We annotate; we don't sell - potential to affiliate with a travel agent

• Parks beyond Walt Disney World. Depth first.

• Predicting discounts or forecasting future prices - some pricing requires maintenance (e.g. dining plan pricing). Affiliation with a travel agent would make sense here.

• Provide different room options (e.g. Fireworks View)

V1 Scope

• The overlay A small persistent panel with selectable options showing the running total, collapsible to a single figure. It browses the Disney site as though it were the user looking at realtime hotel and ticket rates, then and adds the costs the site doesn’t carry based on historical data and spend profile configurations. No account required, no data leaves the device. The extension browses behind the scenes, acting like a user. Note: user doesn’t need to be on the WDW website to use the extension and no long in is required.

• The trip model A lightweight local record of the trip as the user assembles it across sessions: dates, party composition, resort, ticket type, add-ons chosen. The values are sticky.

• The estimate for what can't be read Food and discretionary spending (snack, souvenirs, and so on)is the largest unpriced cost and cannot be scraped from a booking page. V1 ships a transparent, per-person-per-day range by spending style, adjustable by the user, always labeled as an estimate rather than folded silently into the total. Getting this labeling right is the difference between a trusted tool and a discredited one.

• The comparison One derived view: what changes if a single variable changes. Drop a night. Skip the hopper. Move down a resort tier. This is where the product converts from an informational overlay into something that changes a decision.

• Scope discipline Everything is in service of one job: making the true number appear at the moment of the decision. The extension does not offer any reviews or rankings of the resort or dining experiences.

Success metrics

Risks

The name is a liability

"Disney" is aggressively protected, and an extension store listing carrying it invites takedown regardless of the merits of nominative fair use. The product ships under a non-infringing name; "Disney Math" survives internally, as a working title only. Affiliating with a Disney travel agent is key to legitimizing this extension.

The host site could break or block the extension

We depend on reading pages we don't control. Markup changes silently break parsing; terms of service may prohibit automated extraction. Affiliation with a travel agent as a lead-generation tool potentially mitigates this risk. An extension that reads travel pages is asking for meaningful permission at exactly the moment users are most wary of extensions. Request the narrowest host permissions that work, keep the trip model local by default, and say so in the install flow. Do not require log-in by the user to estimate the trip.

Open questions

1. Does the running total produce anxiety and an uninstall?

2. Is a browser extension the right vessel, given that install friction is the highest of any consumer surface?

3. How much of the total can actually be read from the page versus estimated/maintained externally?

4. Does this generalize? The same fragmented-pricing problem exists in cruises, resorts, and event ticketing. Whether v1 is built as a Disney-shaped tool or a general true-cost engine with a Disney first vertical is a decision that gets expensive to reverse later.

Sequencing