Price a capacity reservation before promising availability

A customer who reserves capacity can consume resources without submitting a single task. If the agreement requires a technician to remain available, a production slot to stay open or a service team to respond within a fixed window, the business has made a commitment. Price that commitment using the capacity you must protect and the alternatives you give up.

Start with the exact promise. Ten hours of work delivered sometime during a month differs from ten hours available every Monday morning. The second arrangement can prevent other bookings even when the customer uses only six hours. Record the reserved period, response requirement, staffing qualifications, maximum simultaneous requests and any restrictions on using idle capacity for other clients.

Ask operations to describe how it would fulfill the promise during an ordinary busy week. If delivery requires an extra person, a backup supplier or overtime, include that consequence before discussing a discount for predictable recurring revenue.

First identify spending caused by accepting the reservation. This may include an additional shift, contractor minimum, dedicated equipment or a required backup resource. Second identify costs already committed for the period. Those costs matter to overall profitability, but the short-term acceptance decision changes only if the contract increases or avoids them.

The third amount is the contribution from work you would reasonably decline. This opportunity cost requires evidence. Use recent booking patterns, credible demand and the actual overlap in dates. A theoretical full-price job that has never materialized should not be treated as certain lost revenue. Equally, a reservation during the busiest delivery week should not be valued as though all capacity would otherwise sit idle.

Keep the three calculations visible. Combining incremental spending, allocated overhead and displaced contribution into one hourly rate can count the same constraint twice. A finance reviewer should be able to trace each amount to a staffing decision or an alternative use of capacity.

Consider an illustrative support team with 160 available hours next month. A customer wants 40 hours reserved, whether used or not, and the team expects to deliver 24 hours of actual work. Suppose providing those hours creates $1,440 of additional delivery cost. Backup coverage needed for the promised response time costs another $600.

Operations also expects the reservation to displace 12 hours of other work. Each displaced hour would contribute $90 after its own incremental delivery cost. The estimated displaced contribution is therefore $1,080. Adding that to the $2,040 of incremental spending produces a $3,120 economic threshold for the reservation under these assumptions.

A proposed $3,600 fee leaves $480 above that threshold. It is not automatically the contract's accounting profit: shared overhead, the reporting basis and other costs may still matter. The calculation answers the narrower question of whether this reservation improves the modeled alternative. Change the displaced-hours assumption to zero and the decision looks materially different.

Average usage can conceal the period that makes an availability promise expensive. Model a request arriving immediately before the response deadline, several requests arriving together and a request requiring the one employee qualified to handle it. Where the contract permits requests at any time, the customer can use that flexibility even if historical usage was quiet.

Use separate scenarios for usage and displacement. High customer usage does not always mean high incremental cost if the team already has paid idle time. Low usage can still be expensive when blocked capacity prevents other bookings. Describe the operational reason for each outcome so the model does not become a collection of arbitrary percentages.

Also test illness or equipment failure. If the price assumes a single resource is always available, the contract may contain an unfunded backup obligation. Ask whether availability should be expressed as a service window, a queue position or a specific response commitment, then price the version the business can deliver.

A release deadline determines whether unused capacity can be sold again. Compare a reservation released a week ahead with one released ten minutes before delivery. If late release makes replacement work unlikely, a cancellation fee or minimum commitment may be needed to cover the reserved period. Have the agreement reviewed for the applicable commercial and legal terms.

Rollover creates a separate exposure. Forty unused hours carried into a later month can compete with that month's new allocation. Model the maximum accumulated balance, expiry rules and simultaneous demand before promising unlimited carryforward. A cap that appears generous on paper may still exceed the team's practical ability to serve requests during a peak week.

Any right to substitute staff or delivery slots should be explicit. Finance should not assume substitution is allowed while sales promises a named specialist. Record who approves exceptions and how the fee changes if the customer asks for additional reserved capacity.

Include travel or location restrictions in that discussion. A specialist reserved for an on-site visit may lose more usable time than the appointment itself because travel prevents another assignment. If remote delivery can satisfy the requirement, compare the two offers with the customer instead of assuming both consume the same capacity. Document whether preparation and follow-up count toward the reserved hours, so actual usage reports measure the promise that was priced.

After delivery, compare reserved hours, used hours, release timing and declined opportunities. Preserve the evidence behind declined work: the date requested, required skill, expected contribution and whether the work moved to another period. A canceled inquiry is weaker evidence than a confirmed booking that could not be accepted.

Recalculate the next renewal using the customer's actual request pattern and the coming period's demand. The initial agreement may have been attractive while capacity was plentiful and become costly after other clients expand. Conversely, dependable early release can make a reservation easier to support than the initial conservative scenario assumed.

Keep the customer discussion specific. Explain which availability promise drives cost and offer priced alternatives, such as a longer response window or fewer protected peak periods. Approve the renewal only after operations confirms that the proposed capacity remains available in the delivery calendar.