Skip to content
Case study - SaaS web app

MetaRate IQ: pricing intelligence for independent hotels.

Competitor rates for the next 90 nights, a suggested price with a reason for every night, and a website price that can now update itself. Built end to end for MetaHotels in about 15 weeks.

MetaRate IQ dashboard and rate calendar on a desktop monitor and a laptop
Client
MetaHotels
Industry
Hospitality SaaS - hotel pricing
Timeline
July - November 2026
What we did
Product design, Web app development, Data pipeline, Booking-engine integration
  • ~15 wksFirst commit to automatic price matching in production
  • 90 nightsForward rate horizon for every tracked hotel
  • 3 appsHotelier app, admin console and API in one codebase
  • 64End-to-end test suites
Overview

The client

MetaRate IQ is a multi-tenant SaaS platform KloudBoy built for MetaHotels. It shows an independent hotel what its competitors are charging for the next 90 nights, tells it what to charge on its own website, and can now update that website price by itself.

It is three applications in one codebase: a hotelier app for owners and their teams, an internal admin console for the MetaHotels team, and background workers that collect and check rates every day. The first market is Dubai.

KloudBoy delivered it end to end: product specification, system architecture, database design, both apps, the data pipeline, the Mirai booking-engine integration, automated testing and production deployment.

The challenge

Where they started

Large hotel chains have revenue managers and enterprise pricing tools. Independent hotels set room rates on gut feel, last year’s numbers or a quick look at Booking.com, usually as one of ten other jobs. MetaHotels saw two costly gaps.

No clear view of the market

Hotels could not easily see where they stood against nearby competitors, night by night.

A website priced on autopilot

Direct bookings carry no OTA commission, yet many hotels priced their own website higher than Booking.com, effectively paying commission to send guests to the more expensive option.

Tools built for chains

Enterprise pricing tools and dedicated revenue managers are built for large chains, not for an owner or general manager with ten other jobs.

Minutes, not hours

The brief: one number, one reason and one action per date, in under two minutes a day.

The solution

What we built

A hotelier app, an admin console and a data pipeline, shipped in stages that each added trust before automation.

01

The hotelier app

A clean, focused workspace for hotel owners and their teams.

  • 90-day rate calendar

    The hotel’s own rate against its competitors’ lowest, median and highest rate for every night, with a plain "2nd of 8" position, weekend shading and data freshness on every cell.

  • Smart pricing suggestions

    A transparent, rules-based engine suggests a rate for each night with a one-sentence reason ("3 of 6 competitors are sold out on Friday"). Hotels can accept, adjust or dismiss, and every decision is logged.

  • Recommendation controls

    Minimum and maximum price per day of the week, seasonal strategies, rounding rules, direction (raise only or lower only) and a minimum change threshold, so owners are not flooded with tiny tweaks.

  • Rate parity check

    Compares the hotel’s own website against its OTA listings, shows the gap before and after commission, and flags every night where the website is the more expensive option.

  • Opportunities and daily digest

    A short, finishable list of the 3-5 dates that need attention, emailed at 8:00 local time and skipped when there is nothing to do.

  • Market context

    City demand from Amadeus Demand360 data, local events, occupancy tracking, Booking.com search ranking and review scores over time, short-term rental comparison and a smart insights page.

  • Guided onboarding

    Paste a Booking.com, Agoda or booking-engine link, and the platform recognises the hotel, fetches a live rate and asks the owner to confirm: a populated calendar in under 15 minutes.

  • Teams and security

    Admin, Editor and Viewer roles per hotel, two-factor sign-in, invitations and a full activity history.

02

Automatic price matching

The headline feature, built in three stages, each adding trust before automation.

  • v0.3 - one-click send

    Sends a saved rate straight to the hotel’s Mirai booking engine, with a preview, a confirmation and a read-back that checks Mirai actually stored the price.

  • v0.4 - scheduled updates

    Automatic price updates, switched on by the platform and opted into by the hotel. Live in production from 1 November 2026.

  • v0.5 - a one-way parity guard

    Whenever the hotel’s website is priced above its own Booking.com (or other OTA) price, it lowers the website price to a margin the hotel chooses, always within the hotel’s own minimum and maximum and skipping blackout dates.

  • Every change accounted for

    Each automatic change is read back from the booking engine and listed night by night, so the hotel can always see what changed and why. It never touches OTAs or channel managers.

03

The admin console

A separate internal workspace for the MetaHotels team to run the platform.

  • Platform management

    Hotel groups, users, cities, channels, room categories and plan limits, plus a shared property registry with merge tools to keep hotel records clean.

  • Traceable data

    Watch every data-collection run, retry a single fetch and open the original page behind any price, so "why did we show this rate?" is answered in minutes.

  • Quality controls

    Parse-health monitoring and a quarantine for suspicious prices, Amadeus demand workbook uploads, event management and test emails. Every admin action is recorded in an audit log.

04

The data pipeline

Background workers that collect and check rates every day.

  • Swappable data providers

    Reads Booking.com, Agoda, Google Hotels and hotels’ own Mirai booking engines through swappable providers, with Firecrawl, Apify and an in-house fetch layer.

  • Smart scheduling

    The next 14 days refresh daily and later dates weekly, keeping data costs low without losing what matters.

  • Shared data across customers

    A hotel that is one customer’s property and another’s competitor is fetched once and stored once. Each new hotel in a city makes the platform cheaper to run, and new customers get price history from day one.

  • Safety checks before anything is shown

    Prices that jump implausibly are held back for review instead of displayed: a wrong price is treated as worse than a missing one. Every raw page is archived, so any number can be traced back to its source.

05

Engineering for trust

  • Strict data isolation between hotels

    Competitors can share public rate data, but one hotel’s occupancy, suggestions or settings are never visible to another. This is enforced in the database with PostgreSQL row-level security and two separate connection pools, and checked automatically before every release.

  • Tax-correct by design

    Rates with and without VAT and city taxes differ by 12-28%, more than most pricing decisions. Every price stores its tax basis, and the platform refuses to mix bases rather than guess.

  • Commission-aware

    Prices are shown before and after channel commission wherever a decision is made, so the hotel sees what it actually keeps.

  • Three zones, one app

    A single Next.js application serves the hotelier app, admin console and API on separate domains, routed by hostname: simple to deploy, cleanly separated in use.

  • Observable

    Errors and parsing failures report to Sentry, product usage is measured with PostHog, and a pilot-readiness report tracks data freshness and adoption goals.

The result

Inside the platform

Screens from the live MetaRate IQ app. Hotel names, people and every rate are blurred to protect the client's data.

Rate calendar: the hotel against its competitors for every night, with a position label on each date
Rate calendar: the hotel against its competitors for every night, with a position label on each date
Dashboard: tonight’s position, the suggested rate and nights where the website costs more than the OTA
Dashboard: tonight’s position, the suggested rate and nights where the website costs more than the OTA
Demand: market occupancy by segment and the biggest demand movements ahead
Demand: market occupancy by segment and the biggest demand movements ahead
Channels: the hotel’s website against its OTA price, night by night
Channels: the hotel’s website against its OTA price, night by night
Impact

Before and after

AreaBefore KloudBoyWith KloudBoy
Market viewBeforeRates set on gut feel, last year’s numbers or a quick look at Booking.comAfterA 90-day calendar of the hotel against its competitors, night by night
Direct priceBeforeHotel websites often priced above their own OTA listingsAfterAn automatic parity guard keeps the website below the OTA price, within the hotel’s own limits
Daily effortBeforePricing squeezed in as one of ten other jobsAfterOne number, one reason and one action per date, plus a short daily digest
Getting startedBeforeEnterprise tools built for chainsAfterPaste a listing link and get a populated calendar in under 15 minutes
DeliveryBeforeFirst commit, July 2026AfterAutomatic price matching live in production from 1 November 2026
Our role

End to end, in about 15 weeks

KloudBoy delivered MetaRate IQ end to end for MetaHotels: product specification, system architecture, database design, the hotelier app, the admin console, the data pipeline, the Mirai booking-engine integration, automated testing and production deployment.

The result gives independent hotels enterprise-grade pricing tools: they see their competitors’ rates for the next 90 nights, get a clear suggested price with a reason, and can let the platform keep their own website cheaper than Booking.com, safely and within limits they set.

Technology

Platform & tools

  • Next.js 16
  • React 19
  • TypeScript
  • PostgreSQL
  • Drizzle ORM
  • Firecrawl
  • Apify
  • Cheerio
  • Mirai XML API
  • Amadeus Demand360
  • Brevo
  • Cloudflare R2
  • Sentry
  • PostHog
  • Playwright
  • Dokploy & Docker Swarm
Services used

Need the same?

Next case study

Meta Gap Analysis

Meta Gap Analysis command centre and geo map on a desktop monitor and a tablet
Hospitality - hotel revenue management

Meta Gap Analysis

A rate parity and revenue intelligence platform that ingests six daily data feeds and shows where 47+ hotels lose direct bookings to OTAs, with AI action plans and automated reports.

  • Product design
  • Full-stack development
  • Data engineering
  • Cloud & AI integration
Read the case study

Building a SaaS product?

Tell us what your platform needs to do - data, integrations, automation. An engineer, not a salesperson, will reply.