What this tool is, the one rule it always follows, and the weekly rhythm of using it.
Amapas 353 is a condo in Puerto Vallarta that rents as either a two-bedroom or a one-bedroom. The pricing agent is a small tool with one job: help decide what to charge per night for the one-bedroom configuration.
It does three things:
The recommendation is always the higher of two numbers:
The floor always wins. No recommendation ever comes out below a floor you have set. How to set floors is covered on the “Rates, floors, and the season calendar” page.
The tool never changes a price anywhere. It does not touch your Airbnb listing, your booking software, or any website. It ends at a number for you to read; what you do with that number is up to you. (A connection to the booking software is planned as separate work, but nothing here talks to it yet.)
Results are mirrored into the project’s Google spreadsheet — the same one the old process used. After each run, two tabs are rewritten:
Treat those two tabs as read-only: the tool overwrites them completely on every run, so anything you type into them will be erased.
Most weeks you do nothing. The tool is set up to run automatically every Monday morning, refresh the spreadsheet, and save its results. Your recurring tasks are:
The prices are room-rate subtotals. What the tool records is the “$X for N nights” figure from Airbnb’s booking box — the room rate before cleaning and service fees. That is fine for comparing listings against each other, but it is not what a guest actually pays all-in.
Do not assume the automatic run is working until you have seen it work. Airbnb actively resists automated visitors, and the computers that run the Monday job are the kind Airbnb is most suspicious of. The tool is built to fail loudly rather than record garbage — a run where nearly everything comes back empty stops and reports failure instead of pretending. The “The weekly run” page explains how to do a small test run and what to do if it cannot get through.