Ask a hotel tech founder how many properties they signed last quarter and you will get an exact number. Ask how many of those properties are now getting the value they bought the product for, and the answer is usually a pause followed by an estimate. That pause is where revenue leaks.

Activation is the least measured stage in most hotel tech companies I work with. Sales is tracked because commission depends on it. Churn is tracked because finance sees it. The stretch in between, where a signed property either becomes a working customer or quietly does not, is often visible only in support tickets and in the instinct of the onboarding team.

Start with a definition, not a dashboard

Before any tracking, write down what activation means for your product in one sentence. It should describe value in normal operation, not a milestone in your process. Go-live is your milestone. Activation is the hotel's.

For a channel manager, activation might be seven consecutive days of rates and inventory syncing to every connected channel with no manual correction. For a guest messaging tool, it might be the front desk answering guest messages through the product on three consecutive shifts. For a revenue management system, it might be the first month in which the property accepted most of the recommended rates.

The test of a good definition is simple: if a property reaches it, would they be upset if you switched the product off? If the answer is no, the definition is too early.

Choose the events that lead to it

Work backwards from the definition. List the steps a property must complete to get there, in the order they usually happen. For most products this is five to seven events: contract signed, configuration complete, integrations connected, first real transaction, first use by someone other than the person who was trained, and the activation event itself.

Each event needs a timestamp and a property identifier. That is all. Resist the temptation to track everything. The point is to see where properties stall, and a long list of events hides the stall.

Add one more thing to each event: who triggered it. A configuration completed by your onboarding team is not the same as one completed by the property. A first transaction processed by your support staff on a screen-share is not the same as one processed by the night auditor on their own. The distinction matters, because an activation that depends on your team is not yet activation.

Use the data you already have

Most of these events already exist somewhere. Contract dates are in the CRM. Configuration and integration status are in your admin tools. Transactions are in your product database. Support tickets are in the helpdesk. The first activation report is usually a spreadsheet that joins these by property, built by someone who knows where each lives.

That is enough to begin. A dedicated analytics tool becomes useful later, when you want to look at behaviour inside the product in more detail. The hard part is agreeing the definition, not buying the software.

The report that matters

The most useful activation report has one row per property signed in the last six months and one column per event, showing the date each was reached. From that you can see three things: what share of properties have activated, how long it takes, and which step they get stuck on.

Then cut it by segment. Independents against groups, properties with IT staff against those without, properties that came through a partner against direct deals. The differences are usually larger than anyone expects, and they point directly at what to fix. Properties with no one technical on site, for instance, often stall at configuration, which is why onboarding for properties with no IT staff needs its own design.

Review the report weekly, not quarterly. Activation happens in the first few weeks after go-live, so a quarterly review finds problems after the properties concerned have already formed their habits. A short weekly look at properties that have not reached the next event on schedule lets the onboarding team intervene while it still makes a difference.

Consider a guest messaging product

Consider a hypothetical guest messaging company that signs forty properties a quarter. Its onboarding team reports that go-lives are on time. When it builds its first activation report, it finds that go-live is on time, but only around half of properties ever reach three consecutive shifts of front desk use. The rest were trained, went live and then drifted back to the old phone and email habits.

Cutting by segment shows the drift is concentrated in properties where only the general manager was trained. The fix is inexpensive: train a front desk lead as well, and check usage on day ten rather than waiting for a quarterly review. None of that was visible while the company was measuring go-live.

Connect activation to what happens next

Activation matters because it predicts everything downstream. Properties that activate slowly churn more, expand less and refer less. Once you have the report, compare activation dates with renewals and churn. Many of the churn problems that surface around month three started as activation problems in week two.

If you run trials, the same logic applies earlier. What hoteliers do in a trial is a preview of activation, and what they actually do with a free trial tells you which events to watch first.

Finally, give the number an owner. One person, usually the head of onboarding or customer success, should be accountable for the activation rate, with product responsible for the events being recorded correctly. When sales, onboarding and product each own a slice and nobody owns the whole, the number is reported but never moves.

Where to start

If you do not yet know your activation rate, the 12-point leak audit includes the activation measures I use in engagements. It takes about twenty minutes and will show you whether this is where your biggest leak sits.

Frequently Asked Questions