Time to first value is the number of days between a hotel signing and the first moment the product does something useful for that hotel without your team's help. For a booking engine, it is the first direct booking. For a revenue system, it is a rate recommendation the property accepts. For a housekeeping app, it is one full day run from the app with no paper list.

The shorter that gap, the less time there is for the champion to leave, the season to start or the owner to wonder what they are paying for. This guide is a seven-step method for cutting it. It needs no new tooling, only your recent onboardings and a few hours with the people who ran them.

What you need before you start

• A list of the last 20 properties onboarded, with the contract date and the go-live date for each.

• Whatever notes, tickets and emails exist for those onboardings.

• One person from sales, one from onboarding and one from support in the same room.

Step 1: Define first value in the hotel's terms

Write one sentence that describes an event you can see in the product's data and that the hotel would recognise as a result. Went live does not count. That is your milestone, not theirs. If you have never defined this event, how to instrument activation in a hotel tech product covers how to choose it and track it.

Step 2: Measure the baseline

For each of the 20 properties, record the days from signature to first value. Take the median, and note the fastest and the slowest. Expect a wide spread. The fastest shows what is possible with the product as it is today. The distance between the fastest and the median is time you can remove without building anything.

Step 3: Find where the days go

Break every onboarding into the same stages and record how long each one took. Most of the elapsed time is not work. It is waiting.

Mark the longest stage for each property. One or two stages will account for most of the delay across the list. Work on those and leave the rest alone.

Step 4: Move the data request before the signature

The largest wait is usually the hotel gathering information. Ask for it during the sale. A prospect who is choosing between vendors responds faster than a customer who has already signed, and collecting the data early also tests how serious the buyer is. It gives them a concrete plan to look at, which I covered in writing a migration plan that closes deals. By kickoff you should already hold the room types, the rate plans, the channel logins and the name of the person who will do the work.

Step 5: Start from a working default

Do not open a new account with a blank configuration. Build templates for the three or four property types you sell to most, so that the hotel edits sensible settings and does not create them from nothing. A property that sees its own name and rooms in a working system on day one behaves differently from one that sees a setup wizard.

Step 6: Shrink first value to the smallest real result

Many onboardings try to launch everything at once: every channel, every module, every user. Pick the smallest version of first value and get there first. One channel connected and one live booking. One department using the app for one shift. The rest of the rollout follows, and it goes faster because the staff have seen the product work. This matters most at small properties, where the same person is doing the setup and running the hotel, as I described in designing onboarding for properties with no IT staff.

Step 7: Name an owner and a date on each side

Every onboarding needs one named person at the hotel, one named person at your company and a target date for first value that both have agreed. Put the date in the kickoff email and check it every week. When it slips, find out which stage is stuck that day, not at the monthly review.

How to tell it is working

Run the next 20 onboardings with the changes, then measure again.

• The median days to first value has fallen.

• The spread has narrowed, with the slowest properties closer to the median.

• Support contacts in the first 30 days have fallen, because fewer properties are stuck half-configured.

• Fewer accounts reach day 60 without the first-value event.

If the median has not moved, go back to step 3. The bottleneck is probably a different stage from the one you fixed.

Three mistakes to avoid

• Speeding up go-live and not first value. A faster go-live with no usage after it changes nothing for the hotel.

• Adding onboarding staff before removing waits. More people do not shorten the time a hotel takes to send its rate plans.

• Starting in peak season. If the property is full, agree a later start with a firm date. A slow start now usually means a stalled one.

The takeaway

Most of the time between signature and first value is spent waiting for information, for a training slot or for someone to take the first step. Measure where the days go, move the data request into the sale, start from a default and aim for the smallest real result. None of that needs a product release.

If you want to see how activation compares with the other places revenue leaks in your company, the 12-point leak audit takes about twenty minutes and covers demand, conversion, activation and retention.

Frequently Asked Questions