Skip to content
B&Br Technology
Operations automationShort-term rentalsLive in production

TurnFlow

The operating system for short-term rental turnovers.

Bookings become cleaning jobs. Jobs can't close without photo proof. Cleaners are paid from a ledger that reconciles itself, and a guardian watches every channel calendar for nights guests can't book.

What we delivered: Product, design, full-stack engineering, AI agent interface

turnflow / bookability
1 critical bookability problem is open.

Bookability

Read-only scan of 6 channel calendars, 180 days ahead · fictional portfolio

  • 153 sellable nights have no price. Guests can't book them.

    Harbor Loft · Booking.com · Standard Rate · missing_price

    critical
  • No price change in 72 hours from the pricing tool.

    Cape House · Airbnb · pricing_stale

    warning
  • Minimum stay 5 is above maximum stay 4 on an open night.

    Cape House · VRBO · restriction_conflict

    warning
  • 7-night minimum on open dates in July.

    Beacon Studio · Booking.com · far_out_min_stay

    info

Interactive preview rebuilt from the real TurnFlow screen, with sample data. Not connected to production.

agent tools · 17 read, 19 write
36
agent tools · 17 read, 19 write
channel calendars scanned daily
25
channel calendars scanned daily
days ahead checked every scan
180
days ahead checked every scan
open nights found with no price on one rate plan
153
open nights found with no price on one rate plan

Figures from the STR-Management README.

The problem

Turnovers were spread across Airbnb, Booking.com, VRBO, a channel manager, a cleaner group chat and a spreadsheet. A missed checkout meant a dirty unit at check-in. A calendar that quietly stopped syncing meant nights nobody could book, and nobody noticed until revenue was gone.

What we built

  • Calendars create the work

    Every Airbnb, VRBO and Booking.com checkout becomes a cleaning job. Date changes move the job, cancellations cancel it, and the cleaner is told.

  • The server demands proof

    A job can't close without its required checklist items and before/after photos, enforced on the server rather than in the UI.

  • Money reconciles itself

    Itemized extras, verified payments, audited corrections and running balances per cleaner. Payout statements and a 1099 view come straight from the ledger.

  • Revenue is guarded

    The Bookability Guardian reads every channel calendar 180 days ahead, daily and on demand, and flags any night that guests can't book across seven rule types.

  • Agents are first-class

    An MCP server and OpenAPI REST API expose 36 tools. Every write needs a scoped token, explicit owner approval, an idempotency key and an audit-log entry.

  • A cleaner app that installs

    Cleaners use an installable PWA with web push: today's jobs, checklists, photo capture and their own pay statement.

Architecture

How it fits together

  1. Channels

    • Airbnb
    • Booking.com
    • VRBO
  2. Channel manager

    • Hostex · iCal feeds
    • Hostex Open API
  3. TurnFlow

    • iCal sync + reconciliation
    • Job state machine
    • Cleaner ledger
    • Bookability Guardian
    • MCP + REST gateway
  4. Data

    • Supabase Postgres
    • Row-level security on every table
  5. People & agents

    • Owner dashboard
    • Supervisor review
    • Cleaner PWA
    • AI agents
Next.js 16React 19TypeScriptSupabase PostgresTailwind v4ZodVercel CronHostex APIMCPVitest

Outcomes

  • ~150manual coordination texts per unit per month, replaced by scheduled jobs (Team-reported on our own portfolio)

Want something like this?

Next project

PharmaGuide

Data & AI platform

Supplement intelligence, built with pharmaceutical discipline.

View the PharmaGuide case study