Ilios Rentals · E11EVEN · the operating model · one picture

How Ilios works.

The whole business, end to end. Guests discover and book, properties and owners supply the inventory, a single software spine ties the two together, vendors deliver the Miami experience, money moves, and a three-person team steers it all. Read it top to bottom. Tap any block to light up what it touches.

Booking flow Money flow Data flow Built Wired / creds in Planned Partner / external

Tip: tap any card to expand its detail and light up everything it wires to. The rest dims so the relationship reads at a glance.

I Demand guests find us, book, stay Every channel funnels into one direct booking through the Ilios brand. The guidebook keeps earning after check-in.
guests reserve a unit, the spine picks it up
II Supply buildings, units, owners ~25 units onboarding toward ~55. Each unit is its own record (often its own LLC and bank).
Buildings & units
Owners & onboarding
both sides meet in the software spine
III The software spine the engine in the middle D1 is the source of truth, Notion mirrors it for the team. The pipeline brings units live, the dashboard and agent run the days.
Onboarding pipeline · trigger → action → state, per unit (manual first, then automated)
the moment reserve is pressed, one booking sets off four chains
What one booking sets off four parallel chains, fired from a single reservation
The booking
  1. Guest books direct or via an OTA
  2. Guesty locks the dates, blocks every channel
  3. Reservation lands in D1 + the ops dashboard
The concierge
  1. QR guidebook + checkout offer the upsells
  2. Yacht / chef / Sprinter / catering / club table requested
  3. Vendor confirmed, added to the stay
The turnover
  1. Checkout date triggers a clean
  2. Cleaner confirmed in the 48h ops view
  3. Agent catches it if it is ever missing
The money
  1. Stripe captures the payment + evidence
  2. Payout routed to that unit’s owner LLC
  3. Statement flows to the owner portal
a booking fires concierge + turnover
IV Vendors & concierge the Miami experience, and the turnover Upsells lift revenue beyond the nightly rate. Operational vendors keep units ready.
Concierge experience (revenue)
Operations (keep it running)
every charge and payout runs through money
V Money in from guests, out to owner LLCs Per-unit, not per-owner: each unit usually has its own LLC and bank, so payouts and disputes are scoped to the unit.
the team watches all of it through one dashboard
VI People the three who run it A thin team, which is exactly why the spine and the always-on agent matter.
Read the model

One booking, all the way around

A guest books on the hub, the funnel, or an OTA. The spine writes the reservation, fires turnover + concierge, runs Stripe, pays the owner LLC, and surfaces it to the team. One loop, top to bottom.

Demand to supply

The spine is the matchmaker

D1 holds every unit and its stage; Notion mirrors it for the team. New supply enters through onboarding and instantly becomes bookable demand on the hub and channels.

Why D1, not Notion-only

Money is per-unit

Each unit is often its own LLC and bank, so payouts route per unit. The owner portal and chargeback evidence need a real store, which is why D1 is the source of truth.

The Miami experience

A stay is more than a room

The QR guidebook and checkout add-ons route to yacht, chef, Sprinters, catering, and E11EVEN tables. Concierge revenue layers on top of the nightly rate.

Customers → properties → software → vendors → team. One picture. Demand discovers and books, the spine runs it, supply delivers it, vendors elevate it, money settles it, the team watches all of it.