Customer Context
Business Context
Luxury Escapes is scaling their tours division but their current technical landscape is limiting growth. October 1, 2026 target for Kaptio integration driven by December 1, 2026 ERP migration to NetSuite. Tours are purchased from ~50 DMCs and sold directly or as bundled packages (LTLEs). Bundles include: another tour from the same or different DMC, a cruise sourced from a cruise operator, hotel accommodation from their internal bedbank, and extensions/upgrades. Their current Salesforce implementation (6+ years, third-party built) is cumbersome — opportunity tracking only supports one supplier per tour, sliding scale payment terms are unreliable with variable pax counts, and critical commercial data lives in text fields. Result: finance, product load, and commercials teams cannot trust the data. AP team (~1 FTE) manually recalculates every departure payment. Settlement job has not been running. PCMs spend ~4 hours entering a single campaign. 80 concierge tickets/day, 10 manifest checks/day. LE has a 50+ person dev team and own payment service (Stripe, PayPal, PayTo, PayID) — payment integration is a deal-shaping constraint per cheatsheet hard line. Key questions the current system cannot answer: What is the current margin on a specific departure? What is the financial risk exposure across future departures? How does profitability change as load factors increase?
Timeline
Team
Competitive Context
No named competing vendors in evaluation. Tauck referral brought LE to Kaptio (Scott Avera/Daniel Monk connection). LE aware of Kaptio's Intrepid work in Australia. Evaluation appears Kaptio-specific, not a competitive bake-off. Primary alternative is LE building it themselves.
Assumptions
- •Kaptio becomes the core reservation system for tours (Inventory, Product, Pricing, Bookings, Departure Management, Supplier Invoices, Accounts)
- •Salesforce org strategy (greenfield vs same-org) to be decided in Phase 0 architecture workshop — this is the key unresolved architecture question
- •Hotel/accommodation business remains on Admin platform and is entirely out of scope for Kaptio
- •LE sales agents (100+) will NOT use Kaptio UI — integration with existing Zendesk/Admin workflow required; back-office team uses Kaptio/Salesforce
- •Booking data flows directly from Admin to Kaptio via API — real-time integration preferred over batch (confirmed by LE engineering)
- •Kaptio targets Extranet (not legacy Vendor Portal) for DMC integration — bidirectional data exchange
- •October 1, 2026 is a phased milestone (core booking + pricing integration live), not full go-live
- •LE willing to migrate Tours separately from ERP to avoid blocking December 1 NetSuite deadline
- •Phase 0 must sign by mid-April 2026 or October target is off the table (cheatsheet Circle range 16–22 weeks counting backward)
- •Data migration and full ERP sync continue as parallel workstreams through December 2026
- •Phase 0 is mandatory: LE qualifies (5+ external systems, 50+ engineering team, architecture questions unanswerable from demos). Output: Architecture Decision Record + go/no-go
- •Phase 1 Foundation is Kaptio Consulting IP — never outsourced, never free, never optional. Time-boxed; if validation does not fit the window, re-scope, do not extend
- •No build without signed SOW — the SOW is the output of Phase 1 Foundation
- •Anything not in Phase 1 outputs is a change order with its own estimate and acceptance criteria
- •Customization comes after baseline validation — customer validates Golden Config in UAT before customization scope is finalized
- •Budget 20–30% rework after first UAT into the schedule from day one (cheatsheet Pattern 3)
- •Payment integration approach must be resolved in Phase 0: Kaptio Pay with Stripe as gateway for tours is the recommended path per cheatsheet hard line
- •LE retains full payment ownership for hotel/accommodation — Kaptio records payment events for tours but does not process hotel payments
- •Revenue data from BigQuery/order service to ERP (NOT from Kaptio). AP data (supplier invoices) from Kaptio to ERP. Payment confirmations from NetSuite back to Kaptio
- •Phase 1 clean start: forward-dated departures and active customers only. Historical data remains in existing SF instance (read-only)
- •Full historical data migration is a Phase 2 workstream — LE needs internal archiving exercise before scope can be finalized
- •Existing Salesforce custom automations (Manifest, Inventory, Sliding Scale, LTLE inventory sharing) must be mapped before migration
- •Zendesk integration is explicitly out of scope for Phase 0 and Phase 1
- •Sliding scale is the primary commercial catalyst — if architecture workshop reveals gaps in Kaptio handling, confidence drops sharply
- •Tours are non-refundable ($300/person exception at management approval)
- •Lux Plus membership pricing to be supported via Kaptio pricing engine
What We Know
Discovery progress and unanswered questions that affect estimation confidence.
Discovery Progress
87% Complete4 Unanswered Questions — Blocking Estimation Confidence
Delivery Plan
18 outcomes across 4 phases — what we deliver and how we get there.
aWhat We'll Deliver
Core Foundation
(4 included)Product Experience
(5 included)Channel
(4 included, 1 deferred)Advanced
(5 included, 2 deferred)bHow We'll Get There
Implementation Phases
4 phasesPhase 0 — Technical Feasibility Validation
Paid architecture engagement. Data flow mapping, integration pattern validation, sliding scale precision testing, go/no-go recommendation. Cheatsheet: "Enterprise only — covers data flow mapping, integration pattern validation, and technical feasibility assessment."
LE qualifies for Phase 0: 5+ external systems (Admin, Extranet, NetSuite, Zendesk, SendGrid), 50+ person engineering team, architecture questions unanswerable from demos. Must resolve: Salesforce org strategy (greenfield vs same-org), payment gateway approach, Admin/Extranet API feasibility, data migration assessment, sliding scale precision against hardest edge cases. Output: Architecture Decision Record + go/no-go recommendation. If not signed by mid-April, October target is off the table.
Phase 1 — Foundation
Cheatsheet: Requirements Map, Gap Analysis, Solution Design, Golden Config Spec, Estimation & Milestones, Statement of Work. Platform setup, service catalog (~50 DMCs, 6 currencies), pricing/sliding scale configuration, tour packages, customer model, security.
Kaptio Consulting IP — never outsourced, never free, never optional. Time-boxed. Output: signed SOW for implementation. Sliding scale validation against real DMC scenarios is the critical gate. Phase 1 clean start: forward-dated departures and active customers only. No build without signed SOW.
Phase 2 — Golden Config, Working Software & Integration
Customer validates Golden Config in UAT. Booking workflows, Admin integration (API, real-time), Extranet integration (bidirectional), departure management, supplier payments, documents, communications. Target: core booking + pricing integration live by October.
Cheatsheet: customization comes after baseline validation. Customer validates Golden Config in UAT before customization scope is finalized. Budget 20–30% rework after first UAT. Integration is the long pole (cheatsheet Pattern 2): Admin API, Extranet bidirectional, NetSuite ERP integration (AP out, payment confirmations in). October milestone: core booking + pricing live.
Phase 3 — Scoped Customization, Reporting & Iterate
Customization after baseline validation. Commercial reporting/dashboards, supplier payment management, financial reconciliation. Data migration and full ERP sync continue as parallel workstreams.
Reporting is a primary value driver — CFO Natalie and finance team need trusted departure-level margin, risk exposure, and profitability data. COGS accrual mechanism to resolve interim margin distortion. Full historical data migration and ERP sync continue through December. Full go-live follows post-ERP stabilization.
Risks & Next Steps
Known risks and open questions that need answers before finalizing.
Risks (11)
ERP collision — October 1 target compressed by December 1 NetSuite go-live. The ERP program drives the entire schedule and is not a soft target.
Mitigation: Cheatsheet Pattern 1 (Timeline Gap): sell the realistic timeline. October is positioned as phased milestone (core booking + pricing), not full go-live. LE willing to migrate Tours separately from ERP. Phase 0 must sign by mid-April or October is off the table.
Data migration scale — 10+ years of Salesforce data with custom automations (Manifest, Inventory, Sliding Scale, LTLE inventory sharing). Very high volume; LE acknowledges internal archiving exercise needed before scope can be finalized.
Mitigation: Phase 0 produces data migration assessment as a core deliverable. Recommend clean start: forward-dated departures and active customers only (drops migration multiplier from 1.6x to ~1.0x). LE starts internal archiving in parallel. Full historical migration as Phase 2 workstream.
Unpaid architectural drift — LE engineering team (Josh, Ed, Fabian, Jake) wants deep technical workshops (API review, sliding scale integration design, ERP mapping, booking flow architecture). This is services territory, not pre-sales.
Mitigation: Frame the architecture workshop as part of a paid Phase 0 engagement. Cheatsheet deal pattern: "position a services person for architecture discussion while Tomas runs demos." Rebecca and Daniel have discussed paid discovery — Daniel was receptive.
Sliding scale complexity — multi-DMC tours, LTLE bundles (parent + child inventory), partial refunds must recalculate per-pax costs retroactively, cross-departure inventory. Jake: "it just doesn't really work very well." Cheatsheet: complex pricing = 1.4x multiplier.
Mitigation: Pre-build the hardest scenario in a demo org before the architecture workshop. Test: multi-DMC LTLE, 3 bookings at different pax tiers, cancel the first, book a fourth — verify sliding scale recalculates correctly across all supplier invoice lines. If workshop reveals gaps, confidence drops sharply.
Salesforce org strategy ambiguity — greenfield Kaptio instance vs same-org install is unresolved. Same-org risks data conflicts and governor limit collisions with 10+ years of custom SF. Greenfield is cleaner but doubles migration workstream.
Mitigation: Architecture workshop must address this explicitly. Prepare a clear decision framework with tradeoffs for both approaches. Let Josh's engineering team make the call with Kaptio's recommendation. Do not walk into the workshop without a clear position.
Payment gateway hard line conflict — LE uses own payment service (Stripe, PayPal, PayTo, PayID). Cheatsheet hard line: "No custom payment integrations — Stripe, Braintree, Adyen through Kaptio Pay." LE's custom payment service is a deal-shaping constraint.
Mitigation: Position Kaptio Pay as the payment layer for tours, with Stripe as the gateway. If LE needs deposit scheduling and credits, those are Kaptio Pay features (Auto Pay). Do NOT commit to integrating with their custom payment service — that is a 1.4x multiplier for a reason.
Momentum loss — 12 sessions over 6 months (September 2025 to March 2026). Risk of LE deciding to shelve the initiative, or custom-build alternative gaining traction with their 50+ dev team while we coordinate across timezones.
Mitigation: Maintain weekly cadence. Share API docs promptly. Book architecture workshop within 2 weeks. Rebecca keeps Daniel warm. Do not wait for an onsite to prep the workshop.
APAC timezone friction — Tomas joined the architecture session at 5am Iceland time. Sustained workshop-intensive engagement will require repeated early mornings or a dedicated APAC-timezone resource.
Mitigation: Michael Diamond (Octurious, Sydney) handles in-person workshop facilitation and day-to-day LE contact. Tomas does targeted sessions (demos, technical deep dives) at scheduled early slots. Rebecca (Brisbane) is the local relationship anchor.
COGS accrual timing mismatch — revenue recognized at booking, but supplier invoice (COGS) not finalized until handback. Overstated profit in interim months. Michael Brockway: "we'll see 100% margin and then basically a negative 50."
Mitigation: Supplier invoice lines can be generated monthly to capture COGS accrual. Supplier variance report (cost due vs cost invoiced vs variance) exists in Kaptio. Tomas to confirm with Kaptio finance experts the exact mechanism for monthly re-issuance.
Salesforce admin capacity unknown — LE has existing Salesforce but admin capacity for a Kaptio instance is unconfirmed. Cheatsheet red flag: "No Salesforce admin — affects BAU model."
Mitigation: Flag in Phase 0. LE will need admin capacity (internal hire or managed service) for BAU operations on Kaptio.
UAT rework budget — cheatsheet Pattern 3: "Budget 20–30% rework after first UAT." LE's integration-heavy architecture (Admin, Extranet, NetSuite) means integration testing is the real UAT bottleneck. Go-live during October while ERP migration is underway compounds adoption risk.
Mitigation: Build 20–30% rework expectation into the schedule from day one. LE's 100+ agents will not test in Kaptio directly — integration testing with Admin/Zendesk is the critical UAT path.
Open Questions (16)
Sorted by priority — high priority questions have the biggest impact on estimation confidence.
Salesforce org strategy: greenfield Kaptio Salesforce instance or same-org install on existing Salesforce?
highKEY ARCHITECTURE DECISION. Same-org risks data conflicts and governor limits with 10+ years of custom SF. Greenfield is cleaner but doubles migration. Michael Diamond positioned "separate Captio Salesforce instance" early. LE leans toward separate. Architecture workshop must produce a clear decision framework.
Payment integration approach: Kaptio Pay with Stripe, or integration with LE's custom payment service?
highDEAL-SHAPING CONSTRAINT. Cheatsheet hard line: "No custom payment integrations — Stripe, Braintree, Adyen through Kaptio Pay." LE uses own payment service (Stripe, PayPal, PayTo, PayID). Recommended position: Kaptio Pay with Stripe for tours. Must be resolved in Phase 0.
What are the Extranet API capabilities for the bidirectional DMC data exchange?
highLE migrating DMC functions from legacy Vendor Portal to new Extranet. Kaptio should target Extranet, not Vendor Portal. Bidirectional: manifests/occupancy out, product/pricing/availability in. API documentation needed before architecture workshop.
What is the detailed Admin API contract for real-time booking integration?
highAdmin-to-Kaptio integration is core. Real-time confirmed by LE engineering. Need: data format, booking fields, amendment handling, error/retry patterns, rate limits.
How many Kaptio Salesforce licenses are needed for the back-office team?
highSales agents (100+) will NOT use Kaptio UI. Back-office team (operations, PCMs, campaign managers, finance, concierge) will use Kaptio/Salesforce. Drives licensing cost and security model. Cheatsheet red flag: SF admin capacity also TBD.
NetSuite integration design: flowchart of financial artifacts showing order to Kaptio to ERP, and where each document originates.
highLE requested this. Revenue from BigQuery/order service to ERP. AP from Kaptio to ERP. Payment confirmations from NetSuite back to Kaptio. Bank reconciliation: how Kaptio + ERP data reconcile against bank.
COGS accrual mechanism: how to avoid interim margin distortion when revenue is recognized at booking but COGS not finalized until handback?
mediumMichael Brockway (Finance Transformation): "we'll see up 100% margin and then basically a negative 50." Supplier invoice lines can be generated monthly — Tomas to confirm exact mechanism with Kaptio finance experts.
Itinerary change flow: can itinerary data flow end-to-end through Kaptio?
mediumLE wants itinerary changes to flow all the way through (not just pricing). 30–40% of tours have itinerary changes. This is the area of least Kaptio confidence per Architecture Session. Hayley: "we just have disconnects and lack of visibility."
Commission/override payments to DMCs: secondary monthly calculation based on percentage of LE margin. How does Kaptio handle this?
mediumSpecific DMCs receive secondary monthly payment = percentage of LE margin on amounts paid in prior month. "20% commission, we have to pay them 12%" — Anita/Hayley. Recently changed to markup on net rate for at least one supplier (ICS).
FOC packs / influencer bookings: how to handle passenger-level price manipulation without breaking sliding scale?
mediumInfluencers/celebrities need booking records with cost but zero sell price. Currently done via promo codes that break sliding scale and payment calculations.
Data migration phasing: what is the minimum viable migration for Phase 1 (forward-dated departures + active customers)?
mediumAccount strategy recommends clean start to drop migration multiplier from 1.6x to ~1.0x. LE needs internal archiving exercise. Volume of records, custom objects, and automations to be assessed in Phase 0.
Is Zendesk integration with Kaptio required, or does Zendesk continue operating independently?
mediumZendesk is primary agent workflow tool. Currently integrated with Salesforce, Admin, and Vendor Portal. Explicitly scoped OUT of Phase 0 and Phase 1. Migration to Kaptio would sunset existing CS processes in Salesforce.
Is SendGrid integration with Kaptio required, or will Kaptio handle email communications natively?
mediumSendGrid for automated emails (confirmations, reminders). Kaptio Courier available for bulk email processing. Decision depends on whether LE wants to consolidate email or keep SendGrid.
Post-handback incremental bookings: what mechanism for additional pax after DMC payment has been made?
lowAdditional passengers booking after DMC payment requires incremental payment. Current system cannot handle this cleanly.
Does peak booking season overlap with the October go-live window?
lowCheatsheet red flag: peak season overlaps go-live. LE peak seasons not captured. Need to verify no Oct–Dec peak booking period conflicts with cutover.
Does the phased approach need to include Agent Hub (B2B), or is that a future engagement?
lowAgent Hub currently <2% of tours revenue. Not critical for initial go-live. Future phase opportunity.
Statement of Work
Draft SOW status and link to the generated document.
No SOW Draft
No Statement of Work has been generated yet for Luxury Escapes.
Ask Cursor: "generate SOW for luxury-escapes"