The Transparency Document
Most consultants in the AI space won’t publish this. I will, because the hotel industry has been burned enough times to deserve honesty before commitment.
“The consultants and vendors who came before me overpromised and underdelivered. Hotel owners know this. I know this. This document exists because trust has to be rebuilt before it can be used.”
Why this document exists
The hospitality industry has a specific kind of scar tissue when it comes to technology and consultants. Hotel owners have sat through presentations where the demo looked flawless and the ROI projections looked compelling. Then they signed the contract. Then reality arrived.
Failed PMS migrations that took 18 months instead of 6. Revenue management systems that promised dynamic pricing and delivered confusion. Social media consultants who posted for three months and disappeared. AI vendors who sold “transformation” and delivered a chatbot.
This is the environment I am working in. And it is the reason I have written this document before asking for anything from you.
What I do
✓ Identify the 2–3 AI applications that will create the most value for your specific operation before recommending anything.
✓ Work alongside your team in focused, time-bounded engagements, not open-ended retainers.
✓ Translate industry research and AI developments into plain language your team can act on.
✓ Build your team’s internal capability so you do not become permanently dependent on external support.
✓ Tell you when something is not the right fit for your hotel, even if that means a shorter or simpler engagement.
✓ Work with trusted technology partners including Cloudbeds and Quinta where they are the right fit, and help hotels implement AI strategy with whatever tools they already use or prefer.
What I don't do
✗ Recommend tools based on commission rather than fit. I partner with select platforms including Cloudbeds and Quinta where I believe they genuinely serve independent hotels, but if your hotel already uses a different system, or prefers a different direction, the strategy comes first. The tool follows. Always.
✗ Recommend AI for its own sake. Some hotels don’t need more AI right now. I will tell you if yours is one of them.
✗ Run long-term retainers without defined outcomes. Every engagement has a clear end point and a clear deliverable.
✗ Pretend the hotel AI landscape is settled. It isn’t. I will be honest when something is early-stage or unproven.
✗ Replace your team’s judgment with mine. The goal is to build yours, not substitute it.
What success looks like
Typical outcomes I work toward:
• A reduction in the operational hours your team spends on tasks AI can handle
• An increase in direct booking rate as AI tools reduce friction in your direct channel
• A team that can evaluate and implement AI independently without ongoing external support
I do not promise specific percentages before I understand your starting point. Anyone who does is selling you, not helping you.
What happens if it doesn't work
– If an engagement is not tracking toward the agreed outcome, I will tell you, not at the end, but as soon as I see it. You will know before the invoice does.
– If something I recommended did not work, I will own that directly. The goal is your hotel’s outcome, not my reputation. The two are the same thing over time.
– Many independent and boutique hotels still operate on legacy systems — on-premise PMS platforms, siloed data, and technology that does not connect to anything new without significant work. This is more common than most consultants admit, and it matters for AI adoption.
– AI tools need data to work with. If your hotel’s systems cannot share data — if your PMS, your booking engine, your guest communication platform, and your revenue tools all operate in separate silos — AI cannot bridge those gaps without a foundation in place first.
– In many cases this means a cloud migration comes before AI implementation, not alongside it. Moving from a legacy on-premise system to a cloud-based platform like Cloudbeds is not just a technology upgrade. It is the infrastructure that makes everything else possible.
– I will tell you this at the start of every engagement — not halfway through it. If your current systems cannot support the AI applications we have identified, we will address the infrastructure first. You will know what is involved, what it costs in time and resource, and what the realistic sequence looks like before you commit to anything.
– This is not a setback. Hotels that make this transition consistently report that the clarity and operational control they gain from moving to a connected cloud system is itself worth the effort before a single AI application is added.
Why the platform is free
> The hotels that need this most are the ones who have been burned worst by vendors who put the pitch before the value. Making the platform free means you can use it, learn from it, and judge its quality before deciding whether to go further.
> That is how trust gets rebuilt, not through testimonials, but through experience.
> This is a journey of collaboration. We are all learning as the hotel AI landscape develops, and the way we work together reflects that.
> Revenue can come at any stage of the journey, not just at the end of it. Some hotels find value in a single strategy session early in their exploration. Others engage for a full implementation sprint. Some find that the right technology partnership moving to a cloud platform or integrating a specific tool — is the most valuable next step, and we support that transition too.
> There is no single prescribed path. The engagement looks different for every hotel because every hotel’s starting point, team, and market is different.
> What stays consistent is the principle: every recommendation is made because it serves your hotel’s outcome. Not because it generates a specific type of revenue for us. If the free platform is all you need right now, use it. If you want to go further at any point, the door is open.
> This is a long-term relationship, not a transaction. The hotels that get the most from this work are the ones that treat it that way, and so do we.
Realistic timelines — because most consultants lie about this
| Milestone | Realistic timeframe |
|---|---|
| First AI application live | 4–8 weeks from engagement start |
| Team using it with confidence | 8–12 weeks |
| Measurable operational impact | 12–20 weeks |
| Full AI operating system in place | 4–6 months |
| Independence from external support | 6–9 months |