Advisor-led agency operating layer

The private operating layer behind every high-touch trip.

Maison Voyageur is for advisor-led agencies planning complex custom trips where approvals, supplier terms, private notes, payment timing, and client follow-up need to stay connected.

Not for consumer itinerary hobbyists, supplier marketplaces, or booking-engine-only teams. Founder access starts with a workflow audit.

Product cockpitSample agency data - not a live account

Controlled beta
Founder cohort only
Role separation
Advisor, owner, client, founder
Audit posture
Sensitive actions traceable
Workflow first
Audit starts with agency process

Workflow audit

Start with the agency workflow, not an account form.

The founder-cohort path begins with a review of how your agency handles requests, proposals, approvals, payments, supplier notes, and follow-up. No password, card, migration commitment, or client data is required. The audit is free for qualified agencies while cohort slots are open.

Request workflow audit

01

Intake friction

Where new requests arrive, stall, or lose traveler context.

02

Proposal production

Where advisors duplicate work across docs, email, and itinerary tools.

03

Client approval

Where decisions, changes, comments, and payment timing become unclear.

04

Payment follow-up

Where deposits, balances, service fees, and owner visibility leak attention.

05

Supplier operations

Where private contacts, holds, commissions, and confirmations live today.

06

Fit recommendation

Whether Maison Voyageur is a fit now, later, or not at all.

Workflow proof

A client request becomes a confirmed trip workspace.

Maison Voyageur is built around the actual agency loop: receive the request, shape the proposal, get client approval, track payment follow-up, and keep supplier work visible. Supplier bookings and travel fulfillment remain advisor and vendor responsibilities unless separately verified; live payment collection is enabled only after Stripe setup and launch-gate verification.

  1. 01

    New request

    Italy family journey

    4 travelers - $42k target

    Intake received

    A client request becomes a structured trip record with travelers, dates, budget, and preferences.

    No more copying intake details from forms into spreadsheets.

  2. 02

    Proposal draft

    9 itinerary blocks

    2 supplier holds

    Advisor builds proposal

    The advisor adds hotels, flights, activities, private notes, and supplier holds in one itinerary editor.

    The proposal and the operating checklist stay connected.

  3. 03

    Client portal

    Approve proposal

    3 visible trip days

    Client reviews and approves

    The client sees a polished portal with approval actions, messages, and only the information meant for them.

    Internal notes stay private while the client experience feels high-touch.

  4. 04

    Deposit follow-up

    $7,500 pending

    Reminder queued

    Deposit follow-up tracked

    Payment follow-up stays attached to the trip, so the advisor and owner can see what is requested, pending, or overdue.

    Money timing becomes visible operational work.

  5. 05

    Today

    Supplier reply due

    Client change request

    Follow-up tracked

    Supplier tasks, traveler questions, balance reminders, and advisor notes stay in the trip workroom.

    The agency does not depend on memory to keep service moving.

Role boundaries

The private operating layer is the product.

Agencies need two truths at once: the advisor team needs economics, supplier terms, holds, and reminders; the traveler needs a calm itinerary, messages, approvals, and payment requests. Maison Voyageur keeps the boundary visible.

Locked internal view

Private Advisor Layer

Internal discretion notes and traveler sensitivities
Supplier contacts, hold deadlines, and booking procedures
Margin, commission, payment state, and owner-visible risk

Visible to advisors and agency owners only

Shared traveler portal

Client-Visible Layer

Polished itinerary with approved trip copy
Approval actions for proposal changes
Payment request and receipt status

Shared with the traveler

Product tour

Inspect the operating layer behind every client trip.

Move through the same surfaces an agency uses every day: advisor command center, client portal, itinerary builder, payments, supplier knowledge, and owner oversight. All values shown here are sample product data.

Swipe product areas

Daily command center

The advisor sees the trip, the client, the money, and the next task together.

A request is not buried in email. It becomes an active workroom with status, client context, message history, payment exposure, and internal notes.

Sample indicators

Trip status

Proposal drafting

Open balance

$7,500 deposit

Next action

Confirm hotel terms

Example workflow state

Client request summary

Traveler

Victoria Kensington

Primary contact

Request

Italy family journey

14 nights, 4 travelers

Constraint

Quiet luxury, private access

Advisor-only context attached

Apply this to your agency

Want to see where Maison Voyageur fits your actual intake, proposal, approval, supplier, and payment workflow?

Request workflow audit

Product depth

The operating pieces are visible, not implied.

These panels show the core surfaces that replace scattered docs, inboxes, spreadsheets, payment links, and ad hoc CRMs for advisor-led custom-trip work.

Plan the trip

Itinerary editor

Build day-by-day trips with lodging, flights, transfers, activities, draft states, and client-visible copy.

Know the traveler

CRM and client profile

Keep preferences, household context, documents, loyalty details, and advisor-only discretion notes attached to the client.

Keep context

Message thread

Client replies stay tied to the trip, so questions, changes, and advisor answers do not vanish into email.

Track and follow up

Payment lifecycle

Prepare deposit and service-fee follow-up, monitor pending states, and keep reminders visible after payment setup.

Protect agency memory

Supplier directory

Store vendor contacts, commission terms, booking instructions, amenities, and confirmation references privately.

Agency-grade controls

Audit and permissions

Role-scoped access keeps advisor, owner, client, and founder surfaces separated while audit-ready actions remain traceable.

Evidence, not hype

Buyer trust improves when the boundaries are visible.

Agencies can evaluate the operating workflow now, with clear separation between available beta surfaces, sample data, and capabilities that require live setup before use.

Product evidence

Controlled-beta walkthroughs and sample agency workflows are available for diligence.

Security posture

Role-scoped permissions and audit-logged actions are built into reviewed workflows.

Payment boundary

Payment follow-up can be modeled now; live Stripe collection is enabled only after setup and verification.

Launch status

Limited founder cohort access, not a general-availability launch.

What would change the recommendation

  • A consented real pilot trip completed end to end
  • External pen test and WCAG review completed
  • Production payment webhook proof for trip deposits
  • Human launch signatures and disaster-recovery evidence

Founder cohort access

Apply only if your agency runs complex custom trips.

Founder access is for advisor-led agencies that want to replace inboxes, docs, spreadsheets, and payment-link follow-up with one operating workflow. The first step is a workflow audit, not an automatic account setup.

The audit is free for qualified agencies while cohort slots are open. Founder pricing is discussed after qualification and depends on agency size and workflow scope.

Not for consumer itinerary hobbyists, supplier marketplaces, or agencies looking for a booking engine only.

Founder path

Request a workflow audit. We review fit before account setup, migration planning, or payment.

The audit covers intake, proposal production, approvals, supplier operations, and payment follow-up.