How long does it take to deploy a hotel guest portal?

The deployment timeline depends on four factors: **1. PMS integration depth.** Standalone deployment (no PMS) — 1-2 days. PMS integration (Apaleo as reference, or Mews / Cloudbeds / KWHotel / Profitroom / NFHotel and similar) covers reservation sync, folio posting, and webhook lifecycle — typically 3-7 days once the PMS API access is granted to your property. This is the standard PMS integration pattern: vendors grant API access on a per-property basis once you're their active customer, so we scope and connect during your Guestivo onboarding. **2. F&B menu complexity.** Single-language menu with 30-50 items — 1 day to configure manually, hours with AI menu import. Multi-language menu with modifiers, allergens, time-based availability — 2-4 days. **3. AI concierge knowledge configuration.** Out-of-the-box AI handles common questions immediately. Hotel-specific knowledge (operating hours, local recommendations, policies) — 2-3 days of writing and testing. **4. Staff training.** Reception and housekeeping training on admin panel — typically 4-8 hours over 2-3 days. Add a few days of supervised parallel running before going fully live. For a 30-room boutique hotel without a PMS integration, with a moderately complex menu and full AI concierge: realistic timeline is 7-10 days from contract to live. With a PMS integration (Apaleo, Mews, Cloudbeds, KWHotel, Profitroom, NFHotel, or similar) added on top: 10-14 days, once the PMS vendor grants API access to your property. Compare to a traditional native hotel app build — 4-6 months, €30,000-€100,000, and 5% guest install rate. A QR-launched web guest portal lives in days, scales linearly with property size, and reaches 60-85% of guests because there's no install friction.