Most hotel tech founders reach the same fork somewhere between the first few reps and the first real sales team. Deals are coming in, the founder is tired of being the only person who knows how they close, and the board wants a forecast it can believe. One camp says hire a VP of Sales. Another says hire a Head of RevOps and fix the data first. Both can be right. The order depends on what is actually broken.

This post is a decision tree. Answer six yes or no questions in order, follow the branch, and you land on one of four outcomes.

Before you start: what each role actually owns

A VP of Sales owns how deals are won: hiring and coaching reps, running the pipeline review, setting the sales process and carrying the number. A Head of RevOps owns the machinery around those deals: the CRM, territories, quotas, commission plans, forecasting, reporting and the handoffs between sales, onboarding and customer success. Jason Lemkin's list of what RevOps is responsible for covers a single source of truth for pipeline, churn and NRR, shared goals across sales, marketing and success, and scalable compensation plans.

The roles overlap at the forecast, which is why the choice feels hard. A useful test: a forecast wrong because reps sell badly is a sales leadership problem; one wrong because nobody can see the real numbers is an operations problem.

The decision tree

Question 1: Do at least two people other than the founder close deals on their own?

No: go to Outcome C. Neither leadership hire is right yet. A VP of Sales with no team spends their first months as an expensive rep, and a Head of RevOps has nothing to systemise. Hire closers first, as covered in your first go-to-market hire, and keep the CRM tidy yourself or with part-time help.

Yes: go to Question 2.

Question 2: Do those reps win deals using a process someone has written down?

Look for a documented path from first call to signed contract: qualification criteria, demo structure, how pricing is presented, what a hotel group's procurement step looks like. If each rep sells their own way and the founder rescues the big deals, the motion is not yet repeatable.

No: go to Outcome A, VP of Sales first. RevOps can scale a process, but it cannot invent how you win against a hotelier comparing three vendors. The signs are listed in signs your sales process has outgrown the founder.

Yes: go to Question 3.

Question 3: Would you bet next quarter's hiring plan on your current forecast?

Yes: go to Question 5.

No: go to Question 4.

Question 4: Is the forecast wrong because of people or because of systems?

People problems look like stale opportunities, reps who never update close dates, deals marked as commit that were never qualified and no consistent pipeline review. Systems problems look like the CRM, billing and onboarding tools disagreeing about how many properties are live, duplicate accounts for each hotel in a group, and nobody able to say what monthly recurring revenue really is.

People: go to Outcome A. A sales leader who runs a weekly pipeline review fixes discipline faster than any dashboard. Systems: go to Outcome B, Head of RevOps first. Our checklist on signs your pipeline forecast cannot be trusted helps you tell which one you have.

Question 5: Will you add several reps, a new region or a new segment in the next 12 months?

Lemkin's rule of thumb is that by the time you have 15 sales reps you need a dedicated RevOps leader to handle training, onboarding, compensation and quotas, and that you should hire the role earlier if you can afford it. For a hotel tech vendor, a new country or a move from independents into management companies multiplies the operational work: new territories, new pricing, new partner channels and longer, seasonal sales cycles to forecast.

Yes: go to Outcome B. Build territories, quotas and comp before the new reps arrive, not after. No: go to Question 6.

Question 6: Does most of your new revenue depend on handoffs after the first signature?

Many hotel tech companies sell one property, then expand across the group, add modules or upsell through a partner. If expansion and retention drive growth, the handoffs between sales, onboarding and customer success decide your numbers. The Bridge Group's 2026 AE research found 38% of AEs now have sole or blended ownership of renewal and expansion, nearly double the 2024 share, so these handoffs are increasingly inside the sales team's own day.

Yes: go to Outcome D, RevOps first, then a sales leader. No: go to Outcome A. Your process works, your data is sound and growth is new logos, so the next constraint is coaching and hiring, which is a sales leader's job.

The four outcomes at a glance

Why the order matters: the cost of getting it wrong

A wrong sales leadership hire is slow and expensive to undo. Kenso's study of 143,761 top sales leaders found the median VP of Sales, CRO or Head of Sales stays 32 months, but only 24 months at companies under five years old. It also found that companies whose only top sales leader left were about 10% smaller than matched peers four quarters later, and only 33.1% of companies with 50 or more employees showed a new top sales leader within a year.

The team that leader inherits also takes longer to get productive than it used to. The Bridge Group's 2026 report puts average AE ramp time at 6.2 months, the highest in its study history, with 48% of reps at quota, down from 51% in 2024. A VP of Sales hired into broken systems spends part of that ramp untangling data instead of coaching. A Head of RevOps hired before there is a repeatable motion builds reports on deals nobody knows how to win.

Gartner has made the case for starting early. Its research note Early-Stage Companies Must Prepare to Adopt RevOps is aimed at early-stage tech CEOs. Lars Nilsson, writing on SaaStr, places a revenue operations lead as the fourth revenue hire, after a marketer, SDRs and a quota-carrying rep, and describes the role as a senior manager-level generalist who implements the CRM and stitches the stack together. That is a first RevOps hire, not a department.

What hotel tech vendors actually hire

Public postings show how the RevOps role grows with the company. A 2025 Mews posting for a VP of Revenue Operations described leading and rebuilding a RevOps team of 35 people, owning Salesforce, Nue, Spiff and Gainsight, and building infrastructure to take Mews from $250M to $500M+ in revenue. SiteMinder is hiring a Regional Revenue Operations Manager in Dallas to partner with regional sales leaders on forecasting, KPIs and sales technology, which is RevOps sitting alongside regional sales leadership rather than replacing it.

At the other end, some vendors put one commercial leader over the whole lifecycle. In June 2026 LodgIQ appointed Mark Charlinski as President and Chief Commercial Officer to lead sales, marketing and customer success and align them around acquisition, adoption and expansion. That is Outcome D compressed into one senior seat, which works when the person has run both sides before.

Three mistakes to avoid at the fork

• Hiring a VP of Sales to fix a CRM. If your CRM setup is the problem, read when to rebuild your CRM setup before you write a sales leadership job description.

• Hiring a Head of RevOps with no owner for the number. RevOps supports a revenue target; someone still has to carry it, even if that is still the founder.

• Copying a unicorn's org chart. A 35-person RevOps team is right for a company targeting $500M. Under five million ARR, see structuring a sales team under five million ARR and consider whether a fractional leader covers the gap.

Both hires sit inside the convert and measure stages of the hotel tech GTM system, so the right first hire is the one that fixes your biggest leak today.

Not sure which branch you are on? Our free GTM leak audit shows whether your revenue is leaking in the sales process or in the systems around it, before you commit to a senior salary.

Frequently Asked Questions