Most founders spend weeks choosing an outside go-to-market advisor and about an hour briefing them. Then they are surprised when the first month is slower than expected, because the advisor spends it asking for things that could have been provided on day one.

The briefing is not admin. It is the highest-leverage hour of the whole engagement. A good one lets the advisor start diagnosing immediately. A poor one means paying an experienced person to reconstruct what you already know.

I spent 14 years at eZee Technosys, now YCS, on products that now run in more than 33,000 hotels, and I have since worked with hotel tech companies from the outside. This is the briefing I wish every founder sent me before we started, and it is the one I now ask for. I have written separately about what happens in the first thirty days. This is what makes those thirty days count.

Start with the target, in numbers

The first line of the brief is what you are trying to achieve, expressed as a number and a date. Not growth, not traction, not a stronger pipeline. Forty new properties by the end of the next low season. A blended sales cycle under ninety days. Net revenue retention above a specific percentage.

If you cannot write that line, write down why not, because that is the first thing to work on. An advisor without a target will optimise whatever is loudest, which is usually the wrong thing.

Add the constraint alongside the target. How much cash and time are available, whether there is a fundraise or a board deadline in play, and what cannot be changed, such as a pricing model the investors have signed off or a segment the founders are committed to. Constraints sharpen the diagnosis rather than limiting it.

Twelve months of funnel data, however messy

The core of the brief is the funnel, month by month, for at least the last twelve months. Leads by source. Demos booked and demos held. Proposals sent. Deals closed, with contract value and segment. Go-live dates. Churn, with whatever reason was recorded.

Send it in whatever state it exists. Founders often delay because the data is inconsistent, lives in three tools, or has gaps. That is fine. The gaps themselves are findings. An advisor who sees that go-live dates were never recorded has learned something important about how the company thinks about activation.

What matters is that it arrives before the first working session. The single most common delay in the first month of an engagement is waiting for a data export that could have been attached to the brief.

The customer base, by segment

List every current customer with segment, room count, region, previous system, contract value, start date and whether they are on the original plan or have expanded or downgraded. Most companies can pull this from billing and the CRM in an hour.

This list answers the question that shapes everything else: who do you actually win and keep? Founders routinely describe a target customer that is different from the one in the billing data. When those two disagree, the billing data is usually right, and an advisor needs to see it to know.

The sales process as it actually runs

Not the process in the playbook. The one that happens. Who takes the first call, what a demo looks like and how long it lasts, what is sent afterwards, who follows up and how often, how pricing is presented, and where deals typically stall.

Include the artefacts: the demo script if there is one, the proposal template, the standard email sequence, the pricing sheet, the last three proposals actually sent. An advisor learns more from one real proposal than from a page describing the process.

This is also where inconsistency between what the website promises and what sellers say tends to show. Gartner's 2025 buyer survey found that 69 percent of B2B buyers report inconsistencies between the vendor's website and what its sellers tell them. In a trust-driven market like hospitality that gap costs deals, and it is only visible if the advisor can compare the two.

The last twenty lost deals

Pull the last twenty closed-lost opportunities with whatever notes exist, and for each one, who the contact was and whether they would take a short call. Lost deals are the most honest data a company has, and they are almost never analysed systematically.

Add the last ten churned customers in the same format. Where you have an exit reason, include it, but flag which reasons came from the customer and which were the account manager's guess. The difference matters.

What you have already tried

Every founder has already attempted fixes. A new pricing page, an SDR hire, a content push, a partnership with an OTA, a referral scheme. List them, with roughly when, what it cost, and what happened. Be specific about what happened, including nothing.

This prevents the advisor from proposing what you have already done, and it reveals patterns. A company that has tried four demand fixes and no activation fixes is telling you where it has been looking and where it has not.

Your hypothesis, labelled as one

You almost certainly have a view on what is wrong. Write it down, clearly marked as your hypothesis rather than as the brief's conclusion. The advisor needs it because it explains what the team has been optimising for. But if the engagement starts from your diagnosis as fact, you have paid an outsider to agree with you.

The most useful version of this section names the hypothesis and then says what evidence would change your mind. That single sentence sets the tone for the whole engagement.

Access

Read access to the CRM, product analytics, billing, support tickets and website analytics, granted before the first session. Advisors who have to chase access in week one lose that week. If some systems cannot be shared, say which and why, so the advisor can plan around it.

What to leave out

The pitch deck, unless the advisor asks. It describes the company as you want it seen, which is useful context but not diagnosis. Long histories of the product. Competitor teardowns written by your own team, which are rarely objective. And anything that exists to make the company look good rather than to describe it accurately. The brief is a private document for someone you are paying to be honest with you. Write it that way.

Consider a booking engine founder who briefed well

Picture a direct booking engine company whose founder sends a brief before the first call. It states the target as thirty new properties in the next two quarters and names the constraint as a bridge round closing in five months. It attaches a funnel export with a note that go-live dates only exist from January. It lists eighty customers by segment, twenty lost deals with contacts, and four fixes already tried, three of them on demand generation. The founder's hypothesis is that lead volume is the problem, and the evidence that would change their mind is a stable lead count.

The advisor reads the funnel before the first call and sees that lead volume is flat and proposal-to-close has halved. The first working session starts from that fact rather than from the founder's hypothesis, and the engagement is a month ahead of where it would otherwise be. Nothing about that required a clean dataset. It required a founder willing to put the real picture in one place.

Where to start

Block a day. Write the target line first. Pull the funnel and the customer list. Write the honest sales process, the lost deals, what you have tried, and your hypothesis with its counter-evidence. Send it before the first session, not after.

If you want to arrive at the briefing with your own view of where the leaks are, the 12-point leak audit covers demand, conversion, activation and retention with a measure for each. It takes about twenty minutes on your own numbers and makes an unusually good first page for the brief.

Frequently Asked Questions