A Hypothetical Calculation Model: How Could Daytime Bookings Add 30% to Revenue?
This is a hypothetical educational article, not a case study or an actual operating result. It explains, in accounting terms, how daytime bookings could turn into additional revenue under specific, declared assumptions, while clarifying sensitivity, opportunity cost, substitution risk, and stopping limits.
1) Educational introduction: this is a hypothetical model, not an operating outcome
When a revenue manager talks about daytime bookings, the real question is not: does this model always work? The real question is: when could it work, on what accounting basis, and with what risk limits? That is why this article begins with complete clarity: it is a hypothetical educational example, not a case study, not a report on a specific hotel, and not a claim that any hotel has actually achieved a 30% increase. Every number here is based on declared assumptions, and every table, equation, or comparison is for explanation only. The goal is to help a revenue manager think like an operating accountant, not like a marketer.
In this model, we set a simple base: reference revenue of 100,000 Saudi riyals, then we assume 200 completed additional daytime bookings, with a hypothetical net average of 150 riyals per booking within the hotel agreed in the example. That produces an additional 30,000 riyals, bringing the total to 130,000 riyals, which is a 30% increase over the reference base. This calculation does not include net profit and does not deduct operating variable costs; it is based on revenue before variable costs, which is a very important basis so revenue is not confused with profit.
2) Why daytime bookings deserve a place in the revenue manager’s file
In many hotels, some daytime hours remain underused, whether in rooms, suites, meeting spaces, or certain entertainment facilities that may be sold according to the published offer in the live catalog. Those hours do not mean there is free capacity with no cost, but they may create an additional income window if priced and controlled carefully. The important point is that they should be viewed as a complementary revenue stream passing through constraints of capacity, scheduling, cleaning, and operations, not as a magical product that automatically lifts performance.
A revenue manager who thinks about daytime bookings needs to ask two questions at the same time: does this demand truly add new revenue, or does it pull demand away from another product that would have been sold anyway? And does this revenue create enough value after accounting for substitution effect, cleaning time, entry and exit intervals, no-show risk, and facility consumption? That is why any talk of 30% must begin with gross revenue before variable costs, then move to sensitivity analysis, then to a stop-or-scale decision.
3) Defining the accounting base: 100,000 riyals are neither profit nor a forecast
Let us define the base clearly. In this hypothetical example, the reference revenue is 100,000 Saudi riyals. This figure represents total revenue for a specified period before adding the assumed daytime bookings, and it is not net profit, not operating profit, and not an indication of real historical performance. Using the base this way is important because it prevents us from jumping to exaggerated conclusions. If revenue rises by 30,000 riyals, that does not mean profit rises by the same 30,000 riyals, because variable and operating costs may absorb part of the increase.
By contrast, if we begin the comparison from net profit directly, the operating team may become confused. Some decisions that look weak at the margin level may still be beneficial if they use spare time capacity that does not displace higher-value sales. And some decisions that look profitable on paper may be poor if they displace guests who would have paid better rates. So we start from reference revenue, add the possible incremental revenue, and then review its economic quality through both qualitative and numerical analysis.
4) The core calculation assumption: 200 additional daytime bookings at a net 150 riyals each
The central assumption here is simple and limited: 200 additional completed daytime bookings during the period used in the example, and a net of 150 riyals per booking after the pricing agreed within the example. The arithmetic result is 200 × 150 = 30,000 riyals. When added to the reference revenue of 100,000 riyals, the total becomes 130,000 riyals. The increase ratio equals 30,000 ÷ 100,000 = 30%. This is the method used to reach the headline of the model, and it contains no claim that the result is realistic for every hotel, every season, or every city.
Because the number assumes a net 150 riyals per booking, it is essential to understand that this is an internal educational number for this example, not a published market average, not a recommended price, and not a return promise. A revenue manager can use the same method with any other value: replace the number of bookings, the net price, or the reference base, and then see whether the increase is worth operating. The key is that every assumption must be visible to the team, written down, monitored, and reviewed regularly.
5) Why we say before variable costs and not profit
The biggest risk in fast offers is confusing the language of revenue with the language of profit. The incremental revenue here is 30,000 riyals before variable costs. But what happens after that? There is cleaning, supplies, electricity and water consumption, perhaps handling staff, perhaps additional support from reception, security, or emergency maintenance, and perhaps a lost opportunity cost if the same selling unit could later be sold at a higher price. Therefore, a revenue manager cannot announce final success before seeing the true margin after variable costs.
Even so, measuring revenue before variable costs has practical value. It shows the product’s ability to generate new income and gives the team a fair starting point for evaluating the experiment. If 30,000 riyals is incremental revenue and it covers variable costs easily with an acceptable margin, the signal may be positive. If variable costs and indirect effects consume most of the increase, the apparent number may be misleading. That is why the model needs two layers: the revenue layer, then the economic viability layer.
6) Sensitivity table: 100, 150, and 200 additional daytime bookings
It is a mistake to rely on one scenario only. A revenue manager needs a simplified sensitivity check to test the decision. In this hypothetical example, if only 100 additional bookings are achieved at a net of 150 riyals each, the increase is 15,000 riyals, and the total becomes 115,000 riyals, which is a 15% increase. If 150 bookings are achieved, the increase is 22,500 riyals, and the total becomes 122,500 riyals, which is a 22.5% increase. If 200 bookings are achieved, the addition is 30,000 riyals and the total becomes 130,000 riyals, which is 30%.
This hypothetical table teaches us something important: the increase is not a fixed feature of the product, but the result of actual demand levels, operational discipline, distribution speed, capacity management, and clarity of rules. A decision may be viable at 200 bookings and not viable at 100 if variable costs are high or if substitution is strong. For that reason, the opportunity should not be evaluated from one single number; it should be evaluated from a full decision zone that includes the minimum acceptable level and the maximum possible level.
7) Substitution: when new demand eats into old demand
The most sensitive question is substitution. If daytime bookings attract new customers who would not have bought a night room that day, then it may be genuine incremental revenue. But if those bookings absorb sales that would have happened in another product, such as a higher-rate night room or a suite with better margin, the growth may look beautiful on paper while being less valuable than it appears. That is why substitution analysis must be part of every decision, not a late appendix after launch.
A revenue manager can place an assumed substitution rate inside the model, such as 10%, 20%, or 30%, and then monitor its effect. If, out of 200 daytime bookings, only 40 replace demand that would have arrived through other channels, the net incremental revenue before variable costs will be lower than 30,000 riyals even before discussing expenses. This does not mean rejecting the product; it means the evaluation must be disciplined at the portfolio level rather than at the level of a single product.
8) Opportunity cost: what did we give up when we sold the daytime window?
Every hour sold to a daytime guest is an hour that cannot be sold again to that same unit. Therefore, opportunity cost is not just an academic concept; it is a daily decision tool. If the room, space, or facility can generate higher revenue in a later window, then selling too early may be unwise even if it looks occupied. But if the relevant window is historically low in demand, or the unit would otherwise remain partially idle, daytime sales may be better than leaving the asset unused.
Opportunity cost should be recorded in the operating meeting with the same precision used to record price. The revenue manager needs to know: what price could have been obtained if this window had not been sold during the day? What is the probability of achieving that price? And what level of risk are we willing to accept? In some hotels the opportunity cost may be practically zero for a specific hour; in others it may be very high. That is why there is no fixed answer, only a decision framework repeated every day.
9) No-show, cancellation, and scheduling: small numbers can change the result
In daytime bookings, as with any short-duration product, no-show rates or late cancellations can change the picture. Even if the model assumes 200 completed bookings, the actual completed number may not be fully achieved in reality. So the team must ask: what percentage of bookings turn into actual arrivals? What effect do cancellations have on staffing, cleaning, and shift planning? And how much time is available to resell cancelled windows?
Scheduling itself is a core element. If the cleaning gap between guests is not sufficient, operating risk may rise. If entry and exit times are unclear, conflicts can arise with other bookings. That is why the rules of the daytime product must be defined precisely: a clear time window, a delivery and handover method, a cleanliness standard, a confirmation mechanism, and who has the authority to close sales when capacity is full. All these details are not added after the sale; they must exist before launch.
10) A hypothetical operating example for one hotel: how does a revenue manager think every day?
Let us assume one hotel in this hypothetical educational example. In the morning, the revenue manager reviews the expected night-room occupancy, remaining same-day demand, and the hours that can be sold without disrupting the core occupancy. If some rooms are likely to remain empty during a certain window, the manager may open a limited number of daytime bookings. If night demand is very strong, the manager may close the daytime product, raise the assumed price, or reduce capacity.
This approach is not based on luck, but on clear signals. When night demand is low, daytime bookings may be very useful. When night demand is high, they may become a burden if not handled carefully. So the decision changes from day to day, from week to week, and from season to season. The financial model alone is not enough; it must be read alongside occupancy forecasts, operational constraints, and the local demand profile.
11) How do we use a baseline-control cohort in practical terms?
If a hotel wants to measure the effect more rigorously, it can use a baseline and an internal control group, but only in a teaching and methodological sense, not as a published scientific study here. The idea is to compare similar periods that do not differ much in overall demand. For example: a period in which daytime bookings were introduced, versus a comparable period in which they were not, while trying to hold other factors as steady as possible. This does not prove causality completely, but it helps reduce numerical illusion.
Periods can be divided into close units, such as similar weekdays or similar monthly windows, and then the team can watch the difference in incremental revenue before variable costs. If the difference remains positive and still acceptable after costs, that is an encouraging sign. But if the results fluctuate sharply or disappear after deduction, it may mean the improvement came from a temporary circumstance rather than a repeatable model. That is the value of a control group: not to prove glory, but to reveal whether the model truly works under similar conditions.
12) Higher sensitivity: what if the net price changes to 100, 180, or 220 riyals?
Because the net price in this example is educational, it is useful to see the effect of changing it. If the price is 100 riyals per booking with 200 bookings fixed, the addition becomes 20,000 riyals, and the total becomes 120,000 riyals, which is 20%. If the price is 180 riyals per booking, the addition becomes 36,000 riyals, and the total becomes 136,000 riyals, which is 36%. If it is 220 riyals, the addition becomes 44,000 riyals, and the total becomes 144,000 riyals, which is 44%. This does not mean that higher pricing is always better; it may reduce demand, increase substitution, or weaken conversion rates.
The message is that a revenue manager should not ask: what is the highest possible price? The better question is: what price gives the best revenue adjusted for risk and operational viability? Sometimes a medium price is better because it generates higher volume and reduces sensitivity to fluctuations. Sometimes a higher price is better if capacity is very limited or demand is strong. And all of this should remain inside a declared hypothetical framework, not inside an exaggerated marketing promise.
13) Clear stop signals: when should the experiment be stopped or reduced?
Any experimental product needs stop limits. If analysis starts to show that substitution has risen above the acceptable threshold, or that no-shows exceed what operations can handle, or that variable costs have consumed most of the uplift, or that the operating team can no longer maintain service quality, then the signal is not to expand further but to reduce or stop. There is nothing wrong with stopping early when the data is not encouraging; in fact, the real mistake is continuing simply because the idea sounds attractive.
A hotel can define simple thresholds before launch, such as: if the margin before variable costs falls below a target level, or if the product causes repeated operational disruption, or if it repeatedly conflicts with night demand, then the experiment is frozen. These limits do not mean failure; they are part of sound governance. A successful revenue manager is not proud only of the channels opened, but also of the ones stopped at the right time.
14) Linking revenue and operations: rooms, suites, and meetings are not one product
It is a mistake to treat all hotel assets as if they were one commodity. A daytime room is different from a suite, a suite is different from a meeting room, and entertainment facilities are different from a restaurant, buffet, club, or pool, and each one has a different duration, capacity, and operating logic according to the offer published in the live catalog. So one product’s logic cannot be imposed on all products. What works for a short-duration meeting room may not fit a long-use suite, and what suits a daytime room may not suit a facility with special operating requirements.
From a revenue perspective, this means the hotel needs a portfolio map: which daytime products can be opened, at what hours, in what priority order, and with what age or operating restrictions stated in the offer itself. One cannot assume benefits, access, or added services that are not present in the offer. This point matters greatly because revenue growth depends on accuracy, not random expansion.
15) A hypothetical internal decision example: when do I say yes and when do I say no?
Assume the hotel receives daytime requests during a normal business day. If the expected night occupancy is low, cleaning can be scheduled, the net price is 150 riyals per booking, and demand does not displace higher-value sales, the answer may be yes. But if the hotel faces an expected busy night, or if special events raise night demand, or if capacity is very limited, the answer may be no even if the daytime opportunity looks attractive. The right decision is not the boldest one; it is the one most consistent with demand reality and resource limits.
It may be useful to adopt a simple rule: open daytime bookings only if sufficient protection margins remain for potential night demand, and if the operations team can absorb the product without any loss of quality. In that way, the model becomes more than a marketing idea; it becomes an implementable revenue policy.
16) Executive summary for the revenue manager: how do I read the 30% without being misled?
The 30% figure in this article is not a slogan. It is a hypothetical result derived from 30,000 riyals of additional revenue above a 100,000 riyals reference base, with an assumption of 200 completed daytime bookings and a net 150 riyals per booking, all before variable costs. If those conditions remain true, the arithmetic picture is clear. But a professional revenue manager does not stop at arithmetic clarity; the manager asks about substitution, opportunity cost, no-show behavior, cleaning, capacity limits, and risk-adjusted return.
The practical conclusion is that daytime bookings can be a very useful tool if used as part of a flexible portfolio, with clear limits, a controlled experiment, and periodic review. But if they are presented as a universal solution or as categorical promises, they become an administrative risk. Therefore, the best reading of this model is that it is a decision tool, not a sales outcome, and every number inside it must be field-verified again before being relied upon.
17) Pre-launch checklist: questions that should not be ignored
Before opening any daytime product, ask: what is the actual unused capacity? What specific product is included in the published offer? Is the time window compatible with operations? Have variable costs been calculated? Is there a high substitution risk? Are there clear rules for access, departure, and cleaning? Does the team know when to reject a request and when to approve it? Have stop limits been written down? Has the effect of this product on night demand been tested?
If the answers to most of these questions are incomplete, then an early launch may create more confusion than benefit. But if the answers are clear, then the real value begins: not just in one good revenue figure, but in an operating system that can be repeated and scaled with caution.
18) Practical invitation for hotel owners: turning the theoretical idea into a real opportunity
This article explains a hypothetical model that can be customized, but it does not replace an operating decision based on your hotel’s data, your actual offer, and your available price. If you manage a hotel and want to explore how to present daytime products in an organized way through a specialized booking platform, start by reviewing what fits your current portfolio and what can actually be offered according to the live catalog, then test the effect on revenue and operations before any expansion.
List your hotel on FUNDIQI https://fundiqi.com/en/partners