If you are developing your first hotel, there are things nobody tells you until it is too late. Not because people are withholding information, but because the industry assumes a level of knowledge that first-time developers simply do not have. The process is long, complex, and full of decisions that feel minor at the time but have significant consequences down the line.
I have worked with first-time hotel developers throughout my career, and the pattern is remarkably consistent. The ambition is there. The capital is often there. What is missing is a realistic understanding of what the process involves, how long it takes, and where the risks lie.
This is an honest guide based on twenty years of watching people navigate it — including the mistakes that cost the most.
How long it actually takes
The first surprise for most first-time developers is the timeline. From initial concept to opening day, a hotel project typically takes between two and four years. For conversions of existing buildings — particularly listed properties — it can be longer. For new build projects with complex planning, it can be longer still.
This timeline is not primarily driven by construction. Construction is often the shortest phase. What takes time is everything that comes before it: feasibility, planning, design development, procurement, contractor appointment. These are the stages where the project is defined, de-risked, and prepared for delivery. They are also the stages that first-time developers most want to compress, because they feel like waiting rather than progress.
Compressing these stages is almost always a false economy. A feasibility study that takes eight weeks but identifies a fundamental constraint is cheaper than discovering that constraint mid-construction. A design development phase that runs for twelve weeks but resolves every coordination issue is cheaper than resolving those issues on site at ten times the cost. The process exists for a reason, and the reason is to protect your money.
Where the money goes
Hotel project budgets divide broadly into four categories, and understanding the proportions helps first-time developers set realistic expectations.
The building itself — whether purchased or constructed — is the largest single cost. For conversions, this includes the acquisition price plus the structural, mechanical, and electrical works needed to bring the building up to modern standards. For new build, it is the shell and core construction. This typically represents 50-60% of the total project cost.
The interior fit-out — furniture, fixtures, fittings, finishes, and equipment — typically represents 25-35% of the total. This is the area where the design team’s decisions have the most direct impact, and where the choices between quality and cost have the most visible consequences for guest experience and long-term maintenance.
Professional fees — architects, interior designers, engineers, project managers, quantity surveyors, specialist consultants — typically represent 10-15% of the total. This is invariably the area where first-time developers try to save money, and it is invariably the area where cutting costs has the most damaging downstream effects. I will come back to this.
Contingency should be 10-15% of the construction and fit-out costs, higher for conversions of historic buildings where unknowns are greater. First-time developers often resist allocating contingency because it feels like planning to waste money. In reality, it is planning to manage the unexpected without derailing the project. I have never worked on a hotel project that did not need its contingency. The projects that run into serious trouble are the ones where the contingency was inadequate or absent.
Why you need a project manager
You would be surprised how many first-time developers question whether they need a project manager. The logic is usually that they want to retain control, save the fee, or because they believe they can manage the process themselves.
This is always a mistake. A project manager does not remove the developer’s control — they enable it. They coordinate the design team, manage the programme, monitor costs, oversee the contractor, and ensure that the dozens of moving parts in a hotel project are aligned and on track. Without one, the developer is left coordinating specialists they do not fully understand, making programme decisions without the technical knowledge to assess the consequences, and absorbing risk they are not equipped to manage.
The project management fee is typically 3-5% of the construction cost. The cost of not having one — in programme delays, coordination failures, cost overruns, and quality compromises — is consistently higher. It is not an indulgence. It is the most cost-effective insurance a first-time developer can buy.
Why cutting design fees costs you more
First-time developers frequently negotiate design fees down, sometimes aggressively. This is understandable — fees are a visible cost, and reducing them feels like a tangible saving. But the consequence is that the design team cannot afford to think properly. Feasibility gets abbreviated. Design development gets compressed. Coordination issues get missed. Specifications get simplified. The project arrives on site with unresolved problems that cost multiples of the fee saving to fix.
I have seen this play out too many times. A developer saves £30,000 on design fees and spends £200,000 on variations during construction because the drawings were not properly coordinated. Or saves £15,000 on a services engineer and discovers mid-build that the ceiling heights cannot accommodate the mechanical ventilation. Or saves £10,000 on a feasibility study and buys a building that cannot deliver the room count the business plan requires.
Design fees are not a cost. They are an investment in a process that de-risks every other cost in the project. The right design team, given adequate time and fees, will save you many times their cost through better-coordinated designs, smarter specifications, and problems caught on paper rather than on site.
What a good design team looks like
For a first-time developer, choosing the right design team can feel overwhelming. There are hundreds of interior design and architecture practices, many with impressive portfolios, and it is hard to know what distinguishes genuine expertise from good photography. In my opinion, this is what to look for:
Sector experience. Hotels are not residential projects, offices, or retail. They have specific operational requirements, technical standards, regulatory frameworks, and commercial pressures that general practices may not understand. A practice that has designed and delivered multiple hotel projects will navigate the process faster, make fewer costly mistakes, and produce a product that works operationally as well as aesthetically.
Technical capability. The hospitality industry has, in recent years, become dangerously focused on visual trends. Many designers can produce a beautiful image. Fewer understand how buildings actually work: how services integrate, how materials perform under heavy use, how spaces function operationally. The designers who understand construction — not just styling — are the ones who protect your investment.
Supply chain knowledge. A design team that knows its suppliers deeply — that has visited factories, understands manufacturing processes, and can distinguish genuine quality from visual approximation — will specify products that last longer, perform better, and cost less over their lifetime. This is knowledge that comes from years of engagement, not from a catalogue.
Honesty. The most valuable thing a design team can offer a first-time developer is honest advice, even when it is unwelcome. If the budget is unrealistic, you need to hear it now, not after you have committed. If the building cannot deliver what you want, you need to know before you buy it. If a material choice will create problems in five years, you need someone who will say so rather than deferring to your preference.
The mistakes that cost the most
Having worked with first-time developers for twenty years, the same mistakes recur with dispiriting regularity.
Starting with the design rather than the strategy. Before anyone draws anything, the project needs a clear strategy: what is the product, who is the customer, what are the financial targets, and is the building capable of delivering them? Design without strategy is decoration without purpose.
Underestimating the programme. Every first-time developer wants to open sooner than is realistic. The pressure to start generating revenue is understandable, but an unrealistic programme creates compressed decision-making, inadequate coordination, and costly mistakes. Better to set a realistic programme and beat it than to set an aggressive one and miss it.
Not investing in the plan. I have written about this before, but it bears repeating. The plan is the cheapest part of the project and the most valuable. Feasibility, design, coordination, specification — these are where the project is won or lost. Everything that follows is execution. If the plan is right, execution is straightforward. If the plan is wrong, no amount of effort on site will fix it.
Confusing cost with value. A reduced design fee costs more than a full one when the coordination issues surface on site. Cheap procurement, cheap consultants, cheap materials — they all lead to the same place: a more expensive building that does not perform as well as it should.
The reward
I do not want to leave the impression that developing a hotel is nothing but risk and difficulty. It is challenging, but it is also deeply rewarding. A well-designed, well-run hotel creates something that matters: a place where people gather, celebrate, rest, and connect. It supports local employment, local suppliers, and local communities. It adds value to its setting and to the lives of the people who use it.
The first-time developers who succeed are the ones who invest in the process, assemble the right team, set realistic expectations, and maintain the patience to let the project develop properly. They end up with a building they are proud of, a business that works, and the knowledge to do it even better next time.
That is worth getting right.
