Every hotel tech company reaches a point where nobody trusts the CRM. The forecast is built in a spreadsheet, the pipeline review starts with ten minutes of arguing about which deals are real, and the customer success team keeps its own list of properties because the CRM's version is wrong. The question is whether to tidy up what is there or tear it down and rebuild it. Those are different projects with different costs, and choosing the wrong one wastes a quarter.
This self-assessment helps you decide. It has twelve yes-or-no questions in four groups. It takes about twenty minutes if you answer honestly, and it is best done with whoever runs sales and whoever runs customer success in the same room.
How to score
Answer each question yes or no. Score one point for every no. A no means the CRM is failing at that job. If you are not sure, the answer is no.
Group A: Does the structure match how you sell?
Can the CRM show a hotel group, management company or owner and every property linked to it?
Do your deal stages describe what the buyer has done, such as attended a demo or received a proposal, rather than what your team hopes?
Can you tell a new property deal apart from an expansion into an existing customer's other properties?
Most hotel tech CRMs start life holding individual properties, because that is who the first customers were. Once you sell to groups, that structure stops working, and the problem looks like messy data when it is really missing structure. The difference is set out in selling to a hotel versus selling to a hotel group.
Group B: Can you trust the data?
Does every open deal have a next step with a date that is in the future?
Is the source of each deal recorded in a way you could report on?
Are closed-lost deals tagged with a reason someone could act on?
Group B is the clean-up group. These problems come from habits, not design, and they can usually be fixed with required fields, a weekly review and someone who chases the gaps. If closed-lost reasons are the weak point, setting up closed-lost tagging that tells you something shows how to make them useful.
Group C: Does it serve customers after the sale?
Does the CRM show which properties are live, onboarding or at risk?
Is the change of a key contact at a property, such as a new general manager, recorded and visible?
Can you see renewal dates for every customer and filter by the next ninety days?
Hotel tech companies often run sales in the CRM and customers somewhere else. That split means the people renewing and expanding accounts cannot see the sales history, and the people selling cannot see which customers are unhappy.
Group D: Does anyone rely on it?
Is the pipeline review run from the CRM rather than from a spreadsheet?
Could a new salesperson learn the stages and required fields in a single afternoon?
Is there one named person responsible for the CRM's setup and data quality?
Reading your score
Score | What it suggests | What to do |
|---|---|---|
0 to 3 | The CRM is working. A few habits need tightening | Fix the specific gaps and review again next quarter |
4 to 7, mostly in Group B | The structure is fine and the data is not | Clean up: required fields, a weekly hygiene check, an owner |
4 to 7, mostly in Groups A or C | The structure no longer matches the business | Plan a rebuild of the affected objects and stages |
8 to 12 | The CRM is not the system of record for anything | Rebuild, starting from how you sell today |
Clean up or rebuild: the difference
Clean-up | Rebuild |
|---|---|
Keeps the stages, objects and fields | Redesigns them around current customers and deal types |
Weeks, mostly behaviour change | A quarter, including migration and training |
Fixes missing and wrong data | Fixes data that has nowhere correct to live |
Owned by the sales leader | Needs sales, customer success and finance agreeing the design |
The most common mistake is a clean-up when the score points to a rebuild. The team fills in every field, the data looks better for a month, and then it decays again because the fields describe a business the company no longer is.
If you rebuild
Write down how you sell today before touching any settings: segments, deal types, stages and who is involved at each
Define every stage by an action the buyer has taken
Model groups, owners and management companies alongside properties from day one
Bring customer success into the same system, with live status, contacts and renewal dates
Keep the old data readable, and migrate only what is still accurate
Name an owner and schedule a monthly data review
Time it for your quieter selling months, and expect the first pipeline review in the new setup to be uncomfortable. That is the CRM showing you what was always there. If your sales team is growing at the same time, structuring a hospitality sales team under five million ARR covers how roles and territories should map onto the new design.
The takeaway
Rebuild when the CRM's structure no longer matches how you sell. Clean up when the structure is right and the habits are wrong. Score yourself, look at where the noes cluster, and choose the project that fits the problem rather than the one that feels most thorough.
If you cannot tell where your pipeline is leaking because the data will not say, the 12-point leak audit takes about twenty minutes and gives you a starting point that does not depend on the CRM.
Frequently Asked Questions
How do I know if my CRM needs rebuilding rather than cleaning up?
How should a hotel tech CRM handle properties and hotel groups?
How long does a CRM rebuild take for a small hotel tech company?
Should we switch CRM software when we rebuild?
Who should own the CRM after a rebuild?
Get the latest strategies, trends, and expert advice to help your hotel tech business stay competitive and grow.
Where is your revenue actually leaking?
Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.
Get the free leak audit
