Operators answering inquiries inside five minutes convert at roughly 21 percent. Past sixty minutes, that number collapses to around 4 percent. Those figures circulate constantly in STR circles, and they are real enough to act on.

The problem is what operators do with them. They treat a structural problem as a scheduling problem. They set phone alerts. They hire a virtual assistant. They build a manual habit. Then the founder takes a long weekend, or the VA quits, and the five-minute window closes forever because nothing underneath it was ever owned.

Response time is a symptom. The leak is that the inquiry lives on Airbnb's platform, gets routed to a phone notification, receives a reply typed by hand, and then disappears. No record in a CRM. No source tag. No follow-up sequence. No attribution. The conversion either happened or it didn't, and the operator has no way to know why.

This is not a hypothetical failure mode. Open the automation dashboard of a typical 15-unit STR operator and you find the same pattern: a "New Inquiry" workflow in whatever tool they are renting, eleven steps, no source tagging, no owner-side logging, and a single SMS action that fires only if the guest contacted them through one specific channel. Every other channel is manual.

A reflex can be fast. It cannot scale, audit itself, or survive personnel changes. When the founder is the reflex — the one who wakes up to the ping, types the reply, and mentally files the outcome — the business has a person pretending to be a system.

The five-minute rule requires three things to work as a system rather than a habit: automated intake that captures the inquiry regardless of source, a workflow that fires the response without human initiation, and a data layer that logs the interaction with enough context to be reviewed, attributed, and improved later. Most operators have one of the three. Almost none have all three on infrastructure they actually own.

Building a five-minute response sequence inside a SaaS platform you do not control is borrowing against a debt that comes due at re-pricing or an API change. The OTA tightens its messaging rules. The automation platform restructures its tier. The integration breaks. Suddenly the speed-to-lead workflow that took two weeks to configure requires two weeks to rebuild, and during that window, leads are cooling.

Ownership means the logic, the data, and the execution layer live inside infrastructure the operator controls — not infrastructure the operator subscribes to. The distinction sounds academic until the platform changes something and the operator finds out by watching conversions drop.

Before: The founder wakes up to four unread Airbnb inquiries, two direct-site form fills sitting in a Gmail tab, and one Vrbo message that came in at 2 a.m. Each one gets a manual reply. One gets missed because the Gmail tab was in the wrong browser window. None of this gets logged anywhere. By Friday, the founder cannot tell you which channel drove the booking that closed on Wednesday.

After: All four channels feed a single owned intake layer. The response fires in under three minutes regardless of whether anyone is awake. Each interaction is source-tagged, logged, and available for review. The owner of the business can pull up Tuesday's inquiries on Saturday and see exactly what happened, what converted, and where the next leak is. The founder was not the operating system that week. The system was.

Speed-to-lead is a legitimate lever. The operators who actually hold the gain are not the ones who trained themselves to respond faster. They are the ones who removed themselves from the response loop entirely — not by ignoring leads, but by building owned infrastructure that handles intake, response, logging, and follow-up without requiring a human to initiate each step.

The five-minute rule is not a mindset shift. It is an engineering problem. And like every engineering problem, it requires a foundation before it requires a feature.

If you want to know exactly where your current intake flow breaks down — which channel is leaking, where follow-up stops, and what Monday morning would look like with a real spine underneath it — run the free STR Leak Scorecard. It maps the structural gaps in under ten minutes.