Cloudbeds review: what a quarter-billion in funding buys you

I run an 80-room city hotel in Amsterdam. My margins are not generous. Every software subscription gets a row in my spreadsheet: monthly cost, cost per room, measurable return, and a column I call “would I notice if this disappeared.” If a tool can’t justify its own row after three months, it goes. So when I sat down with Cloudbeds, a PMS backed by $244.9 million in venture capital including a cheque from SoftBank, my first question wasn’t about features. It was about price. And they wouldn’t tell me.

That’s not a great start, but I’ll get to it.

This review is part of our property management comparison, where the team is testing eight PMS platforms across different property types and priorities. I’m also reviewing Amenitiz in this category, which sits at the other end of the pricing spectrum: transparent, published, starting at €39 per month. The contrast between the two tells you a lot about where this market is headed and who each vendor thinks its customer is.

The pricing question (because I always start here)

Cloudbeds runs four plan tiers: Flex, One, Experience, and Enterprise. You won’t find a price next to any of them on the website. You’ll find feature comparisons, benefits lists, and a “Get a Quote” button. I clicked it. I filled in the form. I waited for the call.

The sales conversation was professional and not pushy, I’ll give them that. The rep walked me through the tiers, asked about my property size, my current stack, my pain points. After about twenty minutes, I had a number. For my 80-room property on the One plan (which is where most mid-sized independents land), the quote came in at roughly $350 per month, or about $4.38 per room per month. That includes PMS, channel manager, booking engine, and the basic revenue management module. Moving to Experience for the full revenue management suite and guest engagement tools pushed it closer to $500 per month, or $6.25 per room.

Let me put that in context. Amenitiz, which I’m reviewing separately, publishes its pricing on the website: €39–69 per month for their three tiers, though their feature set is built for smaller properties (under 30 rooms, ideally). For an 80-room hotel, Amenitiz actually becomes less competitive because its toolset wasn’t designed for that scale. Mews, which Anna reviewed and rated 8/10, starts at around €300 per month but requires a two-year commitment on the higher tiers and charges separately for payment processing. Cloudbeds sits between these two: more expensive than the budget tier, less expensive than the European enterprise options, and it bundles more into the base price than most.

What I dislike, and I need to be clear about this, is the opacity. I shouldn’t need a 20-minute phone call to find out whether a product is in my budget. The argument from vendors is always that pricing depends on property size and needs, which is true, but Amenitiz manages to publish a price grid and Mews at least shows starting figures. When a company hides pricing, it’s usually because they want to anchor the conversation around value before revealing cost. I understand the sales logic. I just don’t respect it as a buyer.

I calculated the total cost of ownership for year one. The Cloudbeds One plan at $350 per month comes to $4,200 annually. Add the Experience upgrade at $500 per month and you’re at $6,000. There’s no setup fee (they waived it during my evaluation, and I’m told this is common). No commission on direct bookings, which matters: some competitors take 1–3% of direct booking revenue, and on an 80-room hotel running at 72% occupancy with an ADR of €135, that commission model would cost me more than the subscription. Cloudbeds charges zero. That’s a material saving.

What’s in the box

The all-in-one pitch is Cloudbeds’ central promise, and I’ll admit it’s the right pitch for a property like mine. I don’t have an IT department. I don’t have a revenue manager. I have a front desk team, a housekeeping team, and me. Every separate system I add means another login, another invoice, another integration to maintain, another vendor to call when something breaks. Managing multiple vendors is exhausting, and if Cloudbeds can consolidate that into one relationship, that alone has value.

Cloudbeds bundles five things that I’d otherwise buy separately:

PMS. The core property management system handles reservations, check-in and check-out, room assignment, housekeeping status, guest profiles, invoicing. The interface is cloud-based, works in a browser, and doesn’t require any local installation. It’s not the prettiest PMS I’ve seen, and I’ll be blunt about that in my complaints section below. It is functional. Everything I needed to do on a daily basis, I could do without consulting documentation.

Channel manager. This is where Cloudbeds is strong. They connect to over 300 booking channels, and in my testing, rate parity and availability sync worked correctly across Booking.com, Expedia, and the handful of Dutch OTAs I use. Updates pushed within minutes. No overbookings during my trial. For a European independent that relies heavily on OTA distribution (and we do; about 58% of my bookings come through channels), the channel manager quality matters more than the PMS aesthetics. I’ve heard from several colleagues that the channel manager is the reason they chose Cloudbeds and the reason they stay. That tracks with my experience.

Booking engine. The direct booking engine integrates with your website and feeds reservations straight into the PMS without re-entry. The design is customisable enough to match most hotel websites without looking like an embedded widget from 2015. The conversion rate data was useful: I could see abandonment points, average booking value, and compare direct versus OTA performance. This is the kind of data I can actually use.

Revenue management (Pricing Intelligence Engine). This was the feature that pushed me from Flex to One during my evaluation. It analyses demand patterns, competitor pricing, and historical data to suggest rate adjustments. I tested it against my own manual rate-setting process (which involves a spreadsheet, booking pace data, and a lot of staring at Booking.com’s extranet). Over a four-week test period, the automated suggestions were within 5–8% of what I would have set manually on most days, and arguably better on three specific dates where local events drove demand I hadn’t spotted.

The revenue management isn’t a replacement for a skilled revenue manager at a large hotel. But for an 80-room independent where I’m doing this work myself between managing operations, having the system flag pricing opportunities I might miss is worth something concrete. I estimated the four-week test generated an additional €1,200–1,800 in revenue from rate optimisation on days I’d have under-priced. Annualised loosely, that’s in the range of €15,000–22,000. Even at the conservative end, it more than covers the annual subscription.

Guest engagement. Automated pre-arrival emails, post-stay surveys, and upselling templates. Functional, not remarkable. I’ve seen better guest communication tools (and worse; my askng.it review documents the “worse” end in detail). The upselling module lets you offer room upgrades, early check-in, and packages through pre-arrival emails, which generated a modest but trackable €340 in ancillary revenue during my four-week trial. Not transformative, but measurable. I like measurable.

Testing at my Amsterdam property

I ran Cloudbeds alongside my existing system for six weeks. The onboarding took about ten days, which included data migration, channel manager connections, rate plan configuration, and two training sessions with my front desk team. Cloudbeds assigns an onboarding specialist, and ours was based in Lisbon, which meant we were in the same time zone and could schedule calls without the “your morning is my evening” problem that comes with US-based support.

The onboarding itself was excellent. Our specialist knew the product inside out, responded to questions within the hour, and walked my team through specific scenarios relevant to our property. I want to be clear about this because it makes what I heard later from a colleague more jarring. But more on that in a moment.

The daily workflow settled quickly. My front desk team (four people, various levels of tech comfort) adapted within a week. The reservation grid is intuitive. Housekeeping updates sync in real time. The reporting dashboard gives me the numbers I care about: occupancy, ADR, RevPAR, channel mix, booking pace. I could export everything to CSV for my spreadsheets, which is a small thing but matters to me.

I did notice the reporting dashboard was slow to load on several occasions, particularly when pulling longer date ranges or more detailed breakdowns. Not unusable, but enough that I’d click, wait, and wonder whether the page had frozen. For someone who opens reports first thing every morning, those extra seconds add up to irritation. A colleague who runs a 120-room hotel in Barcelona told me the slowness gets worse at scale and during peak booking periods. She described it as “fine at 8am, painful at 11am.” For a cloud-based product backed by this much funding, the interface should feel snappy regardless of when you’re using it.

One specific scenario: during a busy weekend coinciding with a music festival in Amsterdam, we had 23 reservations arrive within a three-hour window. The system handled check-ins smoothly, room assignments were pre-allocated correctly, and the channel manager closed out availability the moment we hit full occupancy. No double bookings. No manual intervention needed. The previous system I was comparing against would have required at least two manual checks during that kind of rush.

The channel manager also handled a cancellation cascade well. A group booking for six rooms cancelled 48 hours before arrival. Cloudbeds reopened the inventory across all connected channels within minutes. Three of the six rooms re-sold through Booking.com within 24 hours, one through the direct booking engine. I can’t prove the channel manager speed caused those re-bookings, but the availability was live fast enough to capture last-minute demand.

The support cliff

I need to flag something that worries me, even though my own onboarding experience was positive.

A colleague who manages two hotels in Porto (about 90 rooms combined) went through the same onboarding process I did. Dedicated specialist, responsive communication, structured migration. She was happy. Then the handover happened. Once her properties were live and the onboarding specialist moved on to the next customer, the support experience changed. Responses got slower. The people answering tickets were less familiar with her setup. Answers started feeling templated, like they were being pulled from a knowledge base rather than coming from someone who understood her configuration.

She described it as a “support cliff.” The dedicated attention during onboarding evaporates once you’re no longer a prospect being converted into a customer. You become a ticket in a queue.

I can’t verify this from my own trial because six weeks isn’t long enough to test ongoing support patterns. My trial support was fine. But her experience matches something I’ve heard from other hoteliers who run Cloudbeds at independent properties: the gap between onboarding support and day-to-day support is noticeable. If Cloudbeds’ sales pitch leans on the quality of their support (and it does), this gap matters. You’re making a buying decision based on the onboarding experience, and then living with something different.

The numbers you can’t trust

This one bothers me more than the UI complaints or the support question, because it goes to the core of what I need from a PMS.

The same colleague in Porto showed me something during a call that made my stomach drop. Her commission reports were displaying figures that bore no relation to reality. One channel was showing an 890% commission rate. Not a rounding error. Not a decimal in the wrong place. An 890% commission. She’d been manually reconciling every report against her OTA extranets for months because she couldn’t trust what Cloudbeds was showing her.

I didn’t encounter this specific bug during my six-week trial. My commission figures looked correct when I spot-checked them against Booking.com and Expedia. But I also wasn’t running the system long enough or at enough scale to surface edge cases in financial reporting.

Here’s my problem with this: I live in spreadsheets. My entire approach to running a hotel is built on trusting the numbers that come out of my systems. If I can’t trust the commission figures, I can’t trust the revenue reports. If I can’t trust the revenue reports, I can’t trust my P&L. And if I can’t trust my P&L, the tool doesn’t work for me, regardless of how good the channel manager is or how clever the pricing engine might be.

I also heard from a hotelier at the Independent Hotel Show who described losing over $22,000 in deposits due to payment processing errors in the system. I have no way to verify that figure independently, and payment processing issues can involve multiple parties. But it reinforces a pattern: the financial reporting and accounting side of Cloudbeds appears to be less reliable than the operational side. For a numbers person, that’s not a minor issue. It’s the issue.

I want to be fair. Every PMS has bugs, and large platforms with thousands of properties will have edge cases. The question is whether these are isolated incidents or symptoms of something structural in how Cloudbeds handles financial data. I don’t have enough data to answer that definitively. What I can say is that if you adopt Cloudbeds, you should plan to reconcile your financial reports manually for the first few months. Don’t assume the numbers are right just because they’re in a dashboard.

The SoftBank question

I need to talk about this because it’s on my mind every time I look at the invoice.

Cloudbeds raised a $150 million Series D in 2021, led by SoftBank Vision Fund, with additional investment from Viking Global and PeakSpan Capital. Total funding sits at $244.9 million. They made the Deloitte Fast 500 in 2024. They’re growing fast, hiring aggressively, and expanding their product footprint.

None of this is inherently bad. But I’ve watched SoftBank-backed companies in other industries, and the pattern is familiar: subsidise growth, capture market share, then raise prices or pivot to a model that serves investors rather than customers. WeWork is the cautionary tale everyone knows. OYO is the hospitality-adjacent one. I don’t think Cloudbeds is heading there; the product is too solid and the customer base too distributed for that kind of implosion. But $245 million in venture capital needs a return, and the exit options (IPO, acquisition, or simply raising prices across the existing base) all have implications for customers.

I asked my Cloudbeds rep about long-term pricing commitments. The answer was professional but non-committal: they don’t plan to raise prices significantly, they’re focused on adding value, and the funding supports product development and expansion. That’s the correct thing to say. It’s also not a contractual guarantee. No vendor offers that. But with a bootstrapped or profitably-run company, pricing stability comes from the business model itself. With a VC-backed company, pricing stability lasts exactly as long as the growth metrics satisfy the investors.

This isn’t a reason not to use Cloudbeds. It’s a reason to negotiate your contract carefully and avoid multi-year lock-ins if you can.

American headquarters, European hotel

Cloudbeds is headquartered in San Diego, California. For a European hotelier, that creates a few practical considerations.

Data residency: Cloudbeds hosts European customer data on servers within the EU (they use AWS, which has data centres in Frankfurt and Ireland). I confirmed this during my evaluation. Guest data doesn’t cross the Atlantic for processing. The company complies with GDPR and processes data under standard contractual clauses. Marc would dig deeper into the sovereignty angle (he always does), but from a practical compliance standpoint, I didn’t find a gap.

Support hours: this matters more than you’d think. Cloudbeds has support teams in multiple time zones, and my experience during the trial was decent. Response times averaged under two hours for non-urgent queries during European business hours. For urgent issues, they have 24/7 coverage. The Lisbon-based onboarding specialist was excellent, as I’ve said. But the core product team sits in California, which means feature requests and bug reports follow American business cycles. A critical issue reported at 9am Amsterdam time gets seen at midnight San Diego time. That’s just how time zones work, and it’s a structural disadvantage compared to Mews (headquartered in Amsterdam, literally around the corner from me) or RoomRaccoon (based in Breda, an hour south).

Cultural fit: this is subtle but real. American software companies tend to design for American hotel workflows first and adapt for Europe second. Cloudbeds is better than most because they have massive traction in Southern Europe (Spain, Portugal, Italy, Greece) and Latin America, which means their product already handles multi-language, multi-currency, and European tax structures. The invoicing templates comply with Dutch fiscal requirements. The VAT handling works. But small things betray the American origin: default date formats, terminology choices (“front desk” instead of “reception” throughout the interface), and a slight bias toward US-style revenue management assumptions in the pricing engine defaults. None of these are dealbreakers. They’re paper cuts.

Where Cloudbeds sits in the market

I’ve spent enough time with the PMS landscape this year to see the segments clearly. Let me map it out the way I think about it.

Budget tier (under €100/month): Amenitiz lives here. Transparent pricing. Built for properties under 30 rooms. Good for a Greek guesthouse, not for my 80-room city hotel. I’ll have more to say in my Amenitiz review, but the short version is: the price is right, the product is limited, and the target customer isn’t me.

Mid-market (€200–500/month): Cloudbeds, RoomRaccoon, Clock PMS+, and Guestline compete here. This is where 80-room independents like mine live. Cloudbeds wins on breadth (the all-in-one bundle) and global distribution (300+ channels). RoomRaccoon wins on simplicity. Clock PMS+ has strong European roots. Guestline has deep UK market penetration.

Upper mid-market to enterprise (€300–1,000+/month): Mews dominates this segment in Europe. More expensive, more polished, stronger payment infrastructure, but also two-year contracts and a higher total cost of ownership. If I had 150 rooms and a revenue manager on staff, I’d probably be looking at Mews instead.

API-first/technical (quote-based): Apaleo, which Thomas is reviewing, sits here. Built for hotel groups with technical teams who want to assemble their own stack. Not for me.

For my specific situation (80 rooms, no IT staff, need channel management and revenue tools, Europe-based, budget-conscious), Cloudbeds is the most feature-complete option at a price that makes mathematical sense. That’s not the same as saying it’s the best PMS. It’s saying the cost-per-feature ratio works for a property of my size.

What I personally disliked

The pricing opacity is the big one, and I’ve already covered it. But there’s more.

The user interface feels like it belongs to a different era. It works, and I won’t pretend it doesn’t. But it lacks the design polish of Mews or the clean simplicity of RoomRaccoon. Dashboard widgets can’t be rearranged. The colour palette is fine but uninspired. The mobile experience is adequate for checking occupancy from home, not adequate for running a full shift from your phone. Thomas would have things to say about the component design and interaction patterns; they feel inherited from an earlier version of the product rather than designed with intention. For a company with $245 million in funding, the front-end should look like 2026. It looks like 2023, maybe early 2024. That’s not a trivial complaint. Design signals investment in the product, and right now the interface signals that engineering resources are going elsewhere.

Reporting customisation is limited on the lower tiers. The standard reports cover the essentials (occupancy, revenue, channel performance), but building custom reports requires the higher-tier plan. I want to slice my data by day of week, booking lead time, and cancellation source. On the One plan, some of that requires workarounds or CSV exports to my own spreadsheets. On Experience, it opens up. But charging more for the ability to understand your own data is a pricing philosophy I disagree with.

The guest engagement module is mediocre. It handles the basics, pre-arrival and post-stay emails, but it’s not competitive with dedicated guest communication tools. The email templates are rigid. The personalisation options are limited. If guest engagement is a priority (and at a city hotel where reviews drive bookings, it should be), you’ll end up supplementing Cloudbeds with a standalone tool, which partially undermines the all-in-one value proposition.

And the learning curve for the revenue management module is steeper than it should be. The tool is capable, but the documentation assumes a level of revenue management literacy that many independent hoteliers don’t have. I understand yield management. Elena, running a 30-room seasonal resort, would find the terminology and configuration options intimidating. An onboarding session dedicated to revenue management would help. The current approach drops you into a sophisticated tool with a generic help article.

The maths, because that’s what I do

Let me lay out the numbers for my 80-room property over 12 months.

Cloudbeds One plan: approximately $4,200 per year ($350/month). That’s $52.50 per room per year, or about $4.38 per room per month.

What it replaces: I was previously paying for a legacy PMS (€180/month), a separate channel manager (€89/month), and no booking engine or revenue management tool. Total: €269/month, or about €3,228 per year. Converting at current rates, that’s roughly $3,500.

The delta: Cloudbeds costs about $700 more per year than my previous stack. But the previous stack didn’t include a booking engine or revenue management. A standalone booking engine runs €50–100/month. Revenue management tools like Atomize (now owned by Mews) or RoomPriceGenie start at €100–200/month for 80 rooms.

If I add those separately: €269 + €75 (booking engine average) + €150 (revenue management average) = €494/month, or €5,928 per year (roughly $6,400). Cloudbeds at $4,200 saves me approximately $2,200 per year by bundling.

Revenue attribution from the trial: The revenue management module contributed an estimated €1,200–1,800 in four weeks. Even at the low end, annualised conservatively (accounting for seasonal variation), that’s €10,000–12,000 in incremental revenue. The booking engine drove 12 direct bookings during the trial that would have otherwise gone through OTAs. At an average commission saving of €22 per booking (15% commission on €148 average booking value), that’s €264 in saved commissions over four weeks, or roughly €3,400 annualised.

Total estimated annual benefit: €13,400–15,400 in revenue gains and commission savings against a subscription cost of roughly €3,850 ($4,200). The ROI is positive. Comfortably so.

I don’t love that I had to build this analysis myself. Cloudbeds should provide an ROI calculator on their website that lets prospects model these numbers before the sales call. They’d sell more software if buyers like me could see the maths before hearing the pitch.

What I’d tell a colleague

If a fellow independent hotelier with 40–100 rooms asked me about Cloudbeds, I’d say this: the product works. The all-in-one approach saves real money compared to buying components separately. The channel manager is excellent and connects to more channels than you’ll ever need. The revenue management module, once you learn it, generates measurable returns. The onboarding is well-handled, especially if you get a European-based specialist. Zero commission on direct bookings is a straightforward cost advantage that compounds over time.

Then I’d add the caveats. The pricing is opaque and you’ll need to call sales, which means you can’t comparison shop efficiently. The UI is functional but dated, and doesn’t reflect the investment a $245 million company should be making in its front-end. The guest engagement module is the weakest link in the bundle. The American headquarters introduces small frictions around support timing and cultural defaults that a European-headquartered competitor wouldn’t. And the SoftBank funding, while not a red flag today, is a yellow one for anyone thinking about where their PMS vendor will be in five years.

I’d also tell them to check the financial reports carefully. Don’t just trust the dashboard. Export, reconcile, verify. The operational side of Cloudbeds is solid: reservations, channel management, availability sync. But the accounting and reporting side has question marks that I haven’t been able to fully resolve. If you’re the kind of hotelier who runs on vibes and rough figures, you might never notice. If you’re like me and every number needs to tie back to a source, build in time for manual checks.

And I’d mention the support. Your onboarding specialist will be great. Enjoy it while it lasts, because the ongoing support experience may not match. Plan for that. Document your setup, keep notes from onboarding calls, and don’t assume you’ll get the same quality of help six months in.

Compared to Amenitiz, Cloudbeds is a different category. Amenitiz is for smaller properties upgrading from spreadsheets; Cloudbeds is for mid-sized independents consolidating their tech stack. They’re not really competitors at my property’s scale, though they overlap at the 20–30 room mark.

Compared to Mews, it’s a closer fight. Mews is more polished, better designed, and has stronger European roots. But Mews costs more, requires longer contracts, and charges separately for components that Cloudbeds bundles. For an 80-room independent watching every euro, Cloudbeds offers more per dollar spent. For a 150-room lifestyle hotel with a bigger budget and higher expectations, Mews is probably the better choice.

The number I keep coming back to: $4.38 per room per month for PMS, channel manager, booking engine, and revenue management. That’s a price point I can defend in my spreadsheet. The question is whether the company behind it will keep that price stable, whether the financial reports will be accurate enough to rely on, and whether the support will be there when I need it six months from now.

For now, the maths works. I’ll keep watching the invoices and double-checking the reports.

Sophie, for all six of us