Intrepid Travel — TailorMade

Assumptions

• •Packages locked (Mar 3). Single package per itinerary. Package Search + Itinerary Builder, no Booking Wizard for TailorMade at all. Kaptio supports setup of initial ~10 packages, Intrepid builds the rest
• •Pay Per Passenger (PPP) confirmed as pricing approach (Mar 12, reconfirmed Mar 20 with caveats: careful default margin setup, group pricing bands by pax count, separate pricing for optional upgrades)
• •CRM handover is an MVP dependency — Intrepid SF CRM org → Kaptio org. Technical contact identified: Ruwantha Lankathilaka. No concerns over mapping to Starship Opportunities (workshop covers this, not SOW-dependent). Seamless booking shell creation UX and booking ref format are workshop items
• •Permissions and permission sets: Intrepid leads; Kaptio supports. Must extend the permission structure delivered in Group Touring Phase 2b/2d
• •AR/AP managed manually — Kaptio exports payment + invoice files for D365 upload. D365 import template to be provided during detailed discovery (not blocking SOW). Phase 3 brings full integration
• •Edge Docs for all TM documents — PandaDocs interim rejected (Mar 3). Option A — content in Kaptio; work starts Phase 1, completes Phase 2. Intrepid leads design and content load; Kaptio models/maps storage
• •Content loading: led by Intrepid, Kaptio supporting — Kaptio defines where content lives for documents; Intrepid loads/inserts MVP content
• •Adyen via Kaptio Pay — existing merchant accounts and integration. Payments in Phase 2 per Ragnar (Apr 2026)
• •No Starship, no Elements for TM — confirmed bypass (Mar 3)
• •Itinerary-level margin control for MVP via channel MarkupJSON and quantity minimums on service prices. Manual sell price override per service (ManualSellPrice__c). Price breakdowns by category deferred. Sliding-scale margin deferred. Intrepid acknowledges bulk margin change limitation and will design pricing structure to minimize consultant overrides
• •Cancellation: legacy flow for TM; customer cancellation policies in scope. Supplier cancellation workflow is Operational Itinerary–only — OOI for TM MVP. PLPP off initially; Cycle 15 Channel/Itinerary PLPP for Phase 3 Group Touring (R010 corrected). No Booking Wizard for TM
• •Vouchers deferred from pilot. Promotions technically work with PS+IB (code-verified Mar 13) but deferred from pilot to keep pricing simple — can enable post-launch without rework
• •Flight placeholders deferred from pilot
• •BU/Channel structure used as-is — existing TM channels per DMC Business Unit, no changes
• •Morocco DMC primary for pilot — UK source market, ~30 TM specialist users plus DMC users (internal Kaptio users fulfilling operational steps). ~10 packages (exact count during discovery). Scope: services that make up the Morocco pilot packages (may include Spain/Portugal for multi-country). Target Q4 2026 — more realistic than Q3, though still a demanding timeline
• •TM cost/pricing loading required (excluded from Phase 2B import). Data loading: bulk or manual, Intrepid leads with Kaptio supporting. Manual entry is Intrepid's responsibility
• •DMC content requires central editorial oversight before publishing
• •TM MVP pilots through Q4 2026 timeline before broader Phase 3 alignment. Minimize throwaway work
• •Staged DMC onboarding — core destinations first, not all at once
• •On-request packaging model — no fixed inventory at launch. Supplier bookings handled by DMC users (internal Kaptio users) line by line via Supplier Bookings tab, supported by reports and exports
• •Reporting requirements still pending — Intrepid cannot provide in time for SOW. Still determining if essential data is in SF or DWH. SOW should scope reporting as discovery-dependent. If DWH integration is required, Intrepid owns/manages it (Kaptio consults). For SF reports, Kaptio creates example/template reports that Intrepid clones and adjusts. Waiting on their clarifications
• •Stacking confirmed to work with payment schedules and the MVP cancellation flow (Mar 26, Caine). Available post-MVP without rework
• •SOW must be agreed by end of March 2026 — Richard travelling 3 weeks then on leave Apr 6-17
• •Booking reference number format needs documentation — Intrepid wants to understand generation logic and whether format is configurable (cross-cutting: affects TM and Core)
• •Combo Trips, operational itineraries, and TM vs Group Touring selling itinerary differences — Caine resolving as a training piece
• •DMCs are internal Kaptio users — TM itineraries have both Sales users (selling) and DMC users (fulfilling operations) within Kaptio. For MVP, supplier comms managed by DMCs outside Kaptio with statuses updated in Supplier Bookings. No automated supplier email/link confirmation scope; enable-supplier-connectivity outcome excluded. Any CoreDev extension is subject to internal discussion (Rebecca, Mar 30)
• •Data migration (AS013): if referenced in SOW, means booking/itinerary customer data cutover needs if they arise — not supplier/service/pricing catalog loading (Intrepid leads catalog load with Kaptio support)
• •SoW R010 retired (Apr 2026): prior org-only assumption incorrect — Channel/Itinerary-level controls remove the material conflict risk for PLPP-related planning