EYT Experiences · Industry analysis

Add-On Demand and Multi-Service Experience Trends

Add-On Demand and Multi-Service Experience Trends

An Add-On request signals interest; it becomes confirmed demand only after authorized acceptance.

  1. Record scoped request
  2. Track proposal
  3. Confirm acceptance
  4. Review service mix
Add-On Demand and Multi-Service Experience TrendsEYT · F7 · Operating frameworkRecord scoped requestTrack proposalConfirm acceptanceReview service mixOriginal operating framework for add-on demand and multi-service experience trends.
Original operating framework for add-on demand and multi-service experience trends.

The operating decision

An Add-On request signals interest; it becomes confirmed demand only after authorized acceptance.

A workable process

Track requested service categories separately from quotes, acceptance and delivered services. A transport inquiry is not transport revenue.

Record the lead time and main-experience context without collecting unnecessary personal details. Compare similar groups before changing staffing or supplier arrangements.

Review why opportunities stop: unavailable supply, timing, scope or a Guest decision. Missing reasons should remain unknown rather than becoming assumed price objections.

Illustrative scenario, not an EYT case study

Hypothetical service review: transport requests increase during a period with more multi-stop group plans. The operator examines confirmed services and unresolved requests separately before changing supplier arrangements. Requests alone are not reported as delivered transport or revenue.

Follow requests through their actual states

A request can fail to become a service for several reasons: timing, availability, incomplete scope, a changed group plan or a Guest decision. Preserve those distinctions when they are known. Keep unknown reasons unknown. Otherwise a report may encourage the team to change pricing when the real constraint was a pickup window or a supplier unable to confirm.

Avoid claiming a market trend from one service mix

An operator serving yacht celebrations may see different requests from a corporate reception team. A shift in their relative activity can change the combined Add-On mix even when each operation behaves consistently. Review comparable formats and periods before drawing a trend conclusion. EYT does not publish the hypothetical service mix here as measured platform demand or as a forecast of provider revenue.

Define what one request means

A Guest may revise the same transport question several times. Decide whether those messages are one evolving opportunity or several distinct requests. Use a stable reference and preserve important scope changes. Otherwise a more responsive Host can appear to generate more demand simply because each clarification is counted again. Keep service category definitions understandable and allow an unresolved category when the brief is not yet specific enough.

Read lead time alongside availability

An otherwise suitable request may arrive too late for the provider to confirm. Measure lead time from a defined event to the requested service time and disclose the timezone. Separate a newly requested service from a change to a confirmed one. If a supplier declines, record the reason only when it is known. Do not automatically treat every unaccepted proposal as a price objection or every unavailable service as a permanent gap in the market.

Review the service sequence

Transport, dining and nightlife can depend on the timing of the main experience. A changed yacht return may alter a pickup and the usefulness of a later dinner. Review how the request affects the existing plan before approving an addition. The authorized Company or provider confirms the commercial terms and relevant payment instructions. A Host’s opportunity record is useful coordination context, not authority to promise supply, accept funds or amend another provider’s cancellation rules.

Treat trends as hypotheses until supported

A higher share of dining requests may reflect a different mix of groups rather than a market shift. Compare similar formats and periods and show the underlying counts. EYT’s proposed future intelligence could eventually help evaluate such patterns with legitimate aggregated data, but this article reports no EYT platform averages, confirmed demand forecast or revenue benchmark.

Operating framework

Decision or measureDefinition / actionInterpretation boundary
Request volumeDistinct scoped service requestsNot bookings
AcceptanceAuthorized accepted proposalsNot delivery
Lead timeRequest to requested service timeUse consistent timezone

Questions operators ask

Does this require replacing our existing systems?

No. Start with clear ownership and consistent states. EYT can sit alongside booking, CRM and payment systems; no automatic technical integration is implied.

Who controls Guest information and commercial decisions?

The responsible Company sets permitted access and retains commercial authority. Give Hosts and Guests the information relevant to their role; a shared Party is not unrestricted access to Company records.

Are service requests a measure of revenue?

No. Distinguish inquiries, scoped requests, proposals, acceptance and delivery. Provider-confirmed commercial records govern revenue and payment.

Sources and evidence

External sources provide industry context. They do not establish EYT customer outcomes or platform benchmarks.