The most common question I get from a founder who is close to bringing in outside go-to-market help is not about price or scope. It is some version of what actually happens once we start. It is a fair question, because most consulting engagements are described in outcomes and delivered in meetings, and the gap between those two things is where trust breaks.

This is a plain account of the first thirty days, week by week, as I run them with hotel tech companies. Other advisors work differently. But whoever you bring in, you should be able to ask for something like this and get a straight answer.

For context, I spent 14 years at eZee Technosys, now YCS, moving from software support through training, international sales, enterprise sales and inbound. The products I worked on run in more than 33,000 hotels. Since then I have worked with hotel tech companies as an outside GTM lead. What follows is what that looks like from your side of the table.

Before day one: what I ask you to prepare

The first month goes twice as fast if three things exist before it starts.

Twelve months of funnel data, however messy. Leads by source, demos booked, demos held, proposals sent, deals closed, go-live dates, and churn with reasons where you have them. It does not need to be clean. It needs to exist.

Access. Read access to the CRM, the analytics, the billing system and whatever you use for support tickets. I am not there to reorganise your tools. I am there to read what they already know.

A list of people. Five to ten customers across segments who would take a thirty-minute call, and two or three deals you lost that you still have a contact for. The customers tell me why they bought and what nearly stopped them. The lost deals tell me what your pipeline reporting cannot.

If you cannot produce these, that is itself a finding, and we start by fixing it.

Week one: reading the company

The first week is almost entirely listening and reading. I go through the funnel data and rebuild it as a single picture: how many properties enter at the top, how many reach each stage, how long each stage takes, and where the numbers fall off a cliff. I read the last fifty closed-lost notes. I read the support tickets from the first ninety days of the newest twenty customers. I sit in on two or three live demos, saying nothing.

I also spend an hour with you on the question of what you are actually trying to achieve. Founders often say growth. Growth is not a target. Forty new properties by March at a blended sales cycle under ninety days is a target. The first week ends with that number written down.

What you should notice in week one is a lot of questions and no proposals. An advisor who arrives with a plan already written is selling you a template. The plan should come out of your data, and your data takes a week to read.

Week two: customer and lost-deal conversations

Week two is mostly calls. I speak to the customers and lost deals you introduced, and I ask the same questions in the same order so that the answers can be compared. What was happening in your hotel when you started looking? Who else did you consider? What almost stopped you? What was the first week after go-live like? Would you recommend it, and to whom?

These conversations do something your CRM cannot. They surface the unstated objection, the one that the sales team never hears because the prospect was too polite to say it. In hospitality that objection is usually about risk rather than features: will this break during my peak season, will my staff cope, has anyone like me survived the switch.

Gartner's 2025 buyer research found that 61 percent of B2B buyers prefer an overall rep-free buying experience, and that 69 percent report inconsistencies between what a vendor's website says and what its sellers say. Those inconsistencies are exactly what customer conversations expose, and in a trust-driven industry they cost deals.

By the end of week two I have the numbers from week one and the reasons behind them from week two. That combination is the diagnosis.

Week three: the leak map

Week three is when you get the first real deliverable: a ranked leak map. It lists every place revenue is escaping, in four areas: demand, conversion, activation and retention. Each leak has a measure, your number against a benchmark, and a rough estimate of what it costs you per quarter.

The ranking is the point. Most founders can list their problems. Few can rank them by cost, and the ranking determines everything that follows. It is common for the loudest problem, usually failed demos, to be the third most expensive one, while activation, which is silent for ninety days and then shows up as churn, sits at the top.

We spend a working session going through it. You will disagree with some of it, and you should, because you know things about your company that the data does not show. The leak map that survives that conversation is the one we act on.

The week ends with a decision: which leak we fix first, what done looks like in a number, and by when. One leak. Not three. Fixing in the wrong order actively hurts, because improving conversion while activation is broken simply pushes more properties into a process that does not work.

Week four: the first fix begins

Week four is the start of building. What gets built depends entirely on which leak came first. If it is conversion, that might mean restructuring the demo around operator risk, rewriting the proposal so that it includes a migration plan, and setting up reference calls at the right stage. If it is activation, it might mean defining first value, instrumenting the days after go-live, and redesigning onboarding for properties with no IT staff. If it is demand, it might mean repositioning against the incumbent and rebuilding the top of the funnel around the buyers you actually win.

Whatever it is, week four is not a slide deck. It is the beginning of changes in your CRM, your sales process, your onboarding flow or your messaging, made with your team rather than handed to them.

You should also see the measurement set up. Whatever number we chose as done, by the end of the first month it is being tracked, with a baseline written down. Without a baseline, nobody can tell three months later whether anything worked.

What you will not see in 30 days

You will not see revenue move. Hospitality sales cycles are long and seasonal, and activation takes weeks. A fix started in week four will show up in the numbers between sixty and one hundred and twenty days later, depending on the leak. If an advisor promises revenue results in the first month, ask which metric they mean. It is usually activity, dressed up as results.

You will not see a rebrand, a new website or a content programme. Those may come later if positioning turns out to be the leak, but they are almost never the first fix, and an engagement that starts with them is usually avoiding the harder work.

What it costs you beyond the fee

Be realistic about your own time. The first month asks for two to four hours a week from the founder, front-loaded into the first fortnight when I need answers and introductions. Your sales and success leads will each spend a few hours in weeks three and four. After the first month it eases, but the decisions remain yours, and I will keep bringing them to you.

There is also the cost of being told things you would rather not hear. A leak map is a list of what is not working, presented with numbers. Some founders find the first review uncomfortable. The ones who get the most from the engagement are the ones who argue with it and then act on it.

Consider a channel manager company at two million ARR

Picture a channel manager vendor whose founder believes the problem is demand. Leads are down and the sales team is idle. In week one the funnel data shows lead volume is actually flat. What has changed is the proposal-to-close rate, which has halved over a year. In week two, lost-deal conversations reveal that a larger incumbent has started bundling a channel manager into its PMS, and prospects are choosing the bundle because it feels safer, not because it is better.

The leak map in week three puts conversion at the top, with a clear cost per quarter, and demand near the bottom. The first fix in week four is a repositioning of the proposal around integration risk and a reference programme that puts prospects on the phone with hotels that chose the standalone product over the bundle and are glad they did. None of that would have happened if the engagement had started with the founder's diagnosis.

Warning signs in the first month

An advisor who does not ask for your data. One who presents a fix before showing you a diagnosis. One who talks in frameworks rather than in your numbers. One who has not spoken to a single customer by the end of week two. Each of these means you are buying a playbook rather than a diagnosis, and playbooks are what got most hotel tech companies into trouble in the first place.

Where to start

If you want a preview of what week three looks like, run the 12-point leak audit on your own numbers. It covers the same four areas with the same measures and takes about twenty minutes. You will come out with a first version of your own leak map, and whether or not you bring in outside help, you will know which leak to fix first.

Frequently Asked Questions