Match before you double

Two weeks of bookings is not a month

Find the next stay on Hotelist, then keep spend flat until finance can point at the cash.

Mikko Atienzamoney7 min read

Two weeks of first bookings is a stack of confirmations. It is not a month. Double it in your head and you will spend like the second half already cleared. It has not. Dispute windows still sit on that cash. Chargebacks still sit on that cash. The only honest move this week is to find the next room where the ranking cannot be bought, book it, then match each confirmation to a payout or a card line before anyone raises spend.

Your next room is already a ranking decision

Someone on your team will sleep in a city this month. Sales has a client visit. Ops has a site week. You have a conference. The hotel will get picked the usual way: the chain on the card, the listing with a 4.7, the result that paid to sit on top. That ranking is the work. It is not a side task for the person who "does travel."

Pieter Levels (@levelsio), who ships products in public and posts the cash instead of a deck, built Hotelist because those 4.7s are the product. Booking sites rank by commission. Review sites flatten every stay into the same number. He wanted a search that could not be bought. Then the search started taking bookings, and the cash showed up faster than he had planned.

@levelsio

First hotel bookings revenue from Hotelist. $3,240 in first 2 weeks. So about $6,480/mo. Much more than I expected.

Pieter Levels (@levelsio)

That is the moment a shop of twenty usually gets sloppy. First cash beats the guess. Someone treats two weeks as a run rate. Ads go up. The travel SOP changes. A partner feed starts pushing rates. None of that is a trial of Hotelist. It is a forecast eating a sketch.

Hotelist is the search, then the cash

You do not need another travel policy. You need one stay found where the ranking cannot be bought, then booked, then matched.

Hotelist pulls ratings from the usual sites and stretches them so a packed 4.7 is not a ten. Vision models score the room photos, not the brochure. It reads trip reports and forum posts and writes the consensus, the pros, the cons. Hotels that paid a higher commission do not float. Then someone books. That booking is now revenue on his side, and a charge or a payout on yours.

This week the object is that second half. Open hotelist.com on the city you will actually pay for. Do not demo Paris if the trip is Cleveland. Sort by Hotelist Score. Open the listing. Read consensus and the photo rating. Complete the booking or write a named hold a colleague can pick up. Send the confirmation to finance the same hour.

If the stay is three weeks out, still run Hotelist this week. Park the hold. Finance can start the row before anyone sleeps there. A shop that never travels still pays for rooms: a contractor, a recruit, a vendor on site. Use that city. Do not invent a trip.

The sketch does not go in the forecast

First cash that beats the forecast feels like a green light. It is a yellow light. Levels doubled two weeks out loud because that is what a founder does when the number is real and surprising. Your books cannot do the same trick.

Finance's job this week is ugly and small. One row per Hotelist booking. Confirmation id. Amount. The payout or card line it should match. The last day a guest, a card, or a partner can still claw it back. If any cell is empty, the row is open. Open rows do not raise the travel budget. Open rows do not turn on automated price or inventory sync to a partner. Open rows do not buy more ads against "the new channel."

Nobody has a credible figure for how often first-channel booking cash later reverses. Count the open rows. That is the only number that belongs on Friday's desk.

If you sell rooms, packages, or anything a partner can reprice, the same hold applies to your own feed. Hotelist converting for him is not a reason to auto-push your rates to the next OTA. A person still approves the sync, and only after a matched row exists for the stay you actually ran.

The owner is the only scale switch

If three people can raise spend, the match never happens. Name the roles before Monday.

The booker is ops, the EA, or the salesperson on the road. They open Hotelist. They pick by score and consensus. They book, or they hold with a reason a colleague can read on Monday. They do not "check a few sites and go with the 4.7." They do not paste a screenshot into chat and call it a policy.

Finance owns the row. They do not forecast. They match. They reply with matched or still open. That reply is the only document the owner reads. A confirmation email in the finance inbox is not a close. A payout, a card line, or a named miss is a close.

The owner is the scale switch. Ad spend, the travel budget, and any automated sync to a partner stay human. Tools can draft a rate change. A person still clicks it, and only after a match. If you are tempted to make Hotelist the default in the SOP because the first stay felt cheap or the score felt honest, that is still a scale decision. It waits.

Figure 1

Ops opens Hotelist for the real city
Decision: Finance can match confirmation to cash?
One of these
NoFinance holds the row
YesOwner may raise the next stay budget
Owner keeps spend flat
Booker books the next stay the same way
Booker waits on the hold
Figure 1

The handoff is the point. Ops can love the score. Finance can still say the cash has not landed. Until that answer exists, the owner does not move the line.

What you put on Friday's desk

MeasureCount
Hotelist bookings with no matching payout or card line
Rows past the dispute window that still have no closer

Fill the cells from your own rows. Do not copy his $3,240 into your sheet. That number is his two weeks, not your Friday.

Run one city through Hotelist before Friday

  • Open hotelist.com on the city of the next stay you will actually pay for, sort by Hotelist Score, and book or hold
  • Send finance the confirmation, the score, the consensus, and the total the same hour
  • Keep travel budget, ads, and partner sync flat until finance answers matched

You can run this on one room, this week, without buying another stack.

Sources

hotelistbookingsreconciliationtravelpayouts

If one workflow is eating your week, tell me which one. I'll tell you if it's worth deploying — and if it isn't.

Message Mikko on LinkedIn

Previous

Jev will sort it in seconds. A refund still needs a name.

Signed bins