Why we built the stack page

A map of the tools that sit behind a well-run short-term portfolio, and how to read it.

The stack page sets out the tools that run a short-term rental operation, grouped by the job each one does. Pricing, distribution across the booking channels, property monitoring, payments, guest messaging, cleaning coordination, review management, and the smaller pieces that sit between them. More than fifty in total, laid out in one place.

Read it by function rather than by brand. Each category answers a question the operation has to answer somehow: how the nightly price is set and moved, how the channels stay in sync so the same night is not sold twice, how a guest gets through the door, how a clean gets booked and checked between stays. The page shows what fills each of those gaps, so you can see where your own setup is thin, or understand what a managed portfolio is running on your behalf.

We built it because this work is invisible. An owner sees a listing and a nightly rate. They do not see the apparatus required to produce them reliably, night after night, across a portfolio. The scale is the point. Running short-term property well is a full operation with many moving parts, not a task you fit around something else, and the page is the most honest way we have found to show that.

So whether you run your own properties and want to pressure-test your setup, or you are weighing up handing them to someone who does, the stack is a fair picture of what good actually requires. It is a reference, not a sales page. Start with the function you are least sure about and work outward from there.