Work with EYT

You handle the experience. EYT keeps the Party connected.

EYT Partner Platform

EYT connects independent experience companies with the people behind their experiences.

Discuss fit in your city

City pages describe planning context and pilot conversations, not confirmed inventory or availability.

Connect your team and Guest relationships

Relevant operators include DMCs, corporate and incentive event teams, nightlife companies, promoter networks, yacht operators, concierge companies, hospitality teams and private experience businesses. Event production teams benefit where they also coordinate clients and Guests. Fit depends on the actual workflow, rather than industry label alone.

DMCs, concierge operators and experience companies retain local expertise, suppliers and fulfillment. Assign your own Hosts, Promoters, concierge staff or local coordinators to help Guests discover, join and move through the experience. EYT does not need to supply the Host.

Hosts support coordination, arrival and check-in and may surface Add-On opportunities. Partners retain pricing and payment authority. Distribution outcomes depend on your audience and offer.

EYT can sit alongside the tools you already use. Keep your booking, CRM and payment systems; no technical integration is implied.

Workflow capabilities and practical operating guides

About EYT · Explore experiences · Destination guides

EYT operating guide

EYT Partner Platform

Explore Partner participation, company authority and the practical boundaries of the EYT operating model.

  1. Fit discussion
  2. Authority review
  3. Controlled workflow
  4. Operating review
EYT Partner PlatformEYT · A5 · Operating frameworkFit discussionAuthority reviewControlled workflowOperating reviewFit discussion → Authority review → Controlled workflow → Operating review. Conceptual operatingsequence; actual workflow availability is confirmed with the Partner.
Fit discussion → Authority review → Controlled workflow → Operating review. Conceptual operating sequence; actual workflow availability is confirmed with the Partner.

Partner participation begins with an operating fit discussion

Explore Partner participation, company authority and the practical boundaries of the EYT operating model.

Layer 2 means the companies delivering and coordinating experiences. Partner onboarding should identify who owns clients, who approves services and who can act for the company before introducing a controlled workflow.

Bring an authority map to onboarding

A useful Partner conversation identifies the company contact, people allowed to approve services and the people allowed to coordinate Guests. Add the external suppliers whose confirmations remain necessary. This exercise can reveal a mismatch between an informal job title and the decisions that person actually makes. Discuss the proposed scope with the people who are accountable for fulfillment, rather than assuming a demonstration establishes commercial authority.

Keep the initial Pilot reviewable

Choose a bounded operating process with a recognizable beginning and end. Agree what successful coordination would look like and which questions remain outside the Pilot. A conversation about a private hosted evening need not imply a commitment to every service category or destination. Review access, support and exception handling before expanding participation. Partner interest does not announce an approved local operator roster, exclusivity or a volume commitment.

Illustrative operating scenario

The following is a hypothetical workflow example, not an EYT customer case study. A DMC brings its own supplier relationships and local coordinators. An initial Partner conversation focuses on a manageable group workflow rather than a promise of new inventory or guaranteed demand.

Ask what participation actually enables

A Partner demonstration should identify the specific operating scope, access rules and support arrangements being discussed. Ask which parts can be exercised in the current controlled workflow and which describe the broader platform model. Keep a record of those distinctions so the company does not brief its team on a capability that was only discussed as a future direction.

Keep Preview separate from public promises

A private Preview helps a sales conversation; it does not establish that every shown behavior is accepted for universal Production use. Public Partner messaging should describe the reviewed pathway and operating boundaries. It should not expose access codes, private client information or an unapproved roster of suppliers.

Commercial boundary

For this workflow, the Company retains clients, suppliers, availability, pricing, approval, relevant payment collection and fulfillment. Its terms govern cancellation and refunds. Keep the tools that already work for you; no automatic integration or replacement is implied.

Operating framework

CheckpointQuestion to resolveResponsible context
Fit discussionWhich bounded process is being evaluated?Company and Partner team
Authority reviewWho may approve services and access?Company decision maker
Pilot reviewWhich enabled capabilities were actually tested?Operating team

Questions operators ask

Does this replace our existing operating systems?

No automatic replacement or integration is implied. Confirm the proposed workflow alongside the booking, CRM, payment and supplier systems that already work for your company.

Is every described capability available to every Partner?

No. Current availability and permissions depend on the controlled Partner workflow. Platform-model and future-direction descriptions should be confirmed during onboarding.

Who retains commercial authority?

The responsible company retains pricing, supplier approval, fulfillment and the relevant payment and cancellation decisions under its own terms.