Modelling a Net Payout Before You Accept a Long Stay

A long stay is a volume decision, not a nightly-rate decision. The number that matters is what arrives after everything else has been taken out.

Last updated: September 30, 2026

A long-stay enquiry usually arrives as a request for a discount, and the easy reply is to compare the proposed nightly rate with your usual one. That's the wrong comparison. A long stay earns across more nights, costs more to service, and passes through more deductions before any money reaches you. This article shows how to start from the gross the guest is quoted, model the deductions that actually apply, and set a floor you won't go below before you answer.

Key Takeaways

• The nightly rate isn't the deciding number. A long stay earns over more nights, so the total that arrives matters more than the rate on any one of them.
• Start from the quoted gross, not from your list price. The guest pays a total; that total is where the arithmetic begins.
• Three deductions decide most of the outcome. The platform side, tax and local levies, and the costs that only exist because the stay is long.
• Model it before you reply. Working the numbers backwards from the guest's request is how hosts agree to a stay that never paid.
• Set the floor once, and say it once. A floor decided in advance is a position; a floor invented mid-conversation is a guess.

Why the nightly rate stops being the useful number

For a two-night booking, comparing nightly rates works: the nights are few and the fixed costs barely move. A long stay breaks those assumptions at once.

The first thing that changes is the denominator. Several weeks turn a nightly figure into a weekly or monthly one, and the guest starts comparing you with a monthly rental rather than with the apartment next door. That's fair from their side, and it's why the discount request arrives at all.

The second thing that changes is the cost side. Some costs are per stay, and a long stay doesn't multiply them: the welcome, the setup, the first clean, the first set of supplies. Others are per night or per turnover, and those grow with the stay. Treat every cost as per stay and you overstate your margin. Treat every cost as nightly and you understate it.

The third is what you give up. A long stay occupies nights you might have sold at peak, at a rate the guest has already anchored low. The trade is only visible across the whole period, not on one night inside it.

So the useful number isn't the nightly rate. It's the net payout for the period: everything the stay brings in, minus everything it costs, divided by the nights it uses. That's the figure to compare with your alternative, which is a set of shorter stays you'd have to actually find.

Starting from the gross the guest is quoted

The guest is quoted a gross figure. That's the total they expect to pay, and it's what they're negotiating around. Your model starts there, because every deduction below comes out of that figure rather than out of your list price.

Write the gross down first, labelled as the guest's total. Put the nights beside it and note the per-night figure that falls out. Now you have a baseline the guest would recognise, which matters later when you explain why a lower number doesn't work.

Then list the deductions in the order they leave the money. The platform side comes first, because it's taken at the booking stage. Tax and local levies come next, because they follow the transaction. Your own operating costs come last, because they're the part you control best and the part most often forgotten when a quiet month is finally filling.

The order isn't cosmetic. Booking-stage deductions reduce what you ever receive; later costs come out of what you've already received. Mixing the two hides the real figure, and a model that hides the real figure always flatters the deal.

One warning about outside numbers. Tax treatment can differ between a resident owner and a non-resident one, and it changes over time. At least one large platform has been moving its service fee to a single-sided structure, with new bookings in the European Economic Area and Switzerland covered from 13 October 2026, according to platform-side information. Use your own figures and your own jurisdiction, and check the platform's current terms rather than a remembered rule.

Three deductions to model before you say yes

These three decide most long-stay outcomes, and each one behaves differently.

The first is the platform side. Whatever structure applies, it's deducted around the booking, so it reduces the gross you're working from rather than arriving as a bill later. Amounts and structures differ by platform, region and date, so plug in your own figures from the channel's current terms. This piece quotes no percentage, because a percentage from another market would be worse than useless to you.

The second is tax and local levies. It's the deduction hosts most often leave out of a long-stay calculation, and the one that scales with the length of the stay rather than the booking. Rules differ by place, and some depend on how long the guest stays. Use the rates and thresholds that apply to your property, from your tax authority, and treat anything you read elsewhere as background.

The third is the cost of the stay itself. Split it in two: a fixed part you'd pay for any booking of that length, and a variable part that grows with it. Utilities, extra cleaning, linen changes and normal wear belong in the variable bucket. If your model calls them fixed, the net payout you calculate will look better than the one you bank. If it calls every cost variable, you'll reject stays that were fine.

Subtract the three and you get a net payout for the period and a net figure per night. Compare that per-night figure with your alternative, because it's the only number that describes both options in the same units. It's also the number your own record supports, since occupancy, average daily rate and revenue per available room for your properties sit together at localsbnb.com, so you can see what those nights have historically been worth before you commit them to one guest.

Deciding the floor you will not go below

A floor is the net figure per night below which the stay stops being worth taking. It isn't a mood or a negotiating tactic. It's a number you decide before the conversation, so the conversation doesn't decide it for you.

Build it from three parts. The first is cost: the point below which you're paying for the privilege of hosting. That part isn't negotiable, because a stay that doesn't cover its own cost is a loss however quiet the month is.

The second is comparison: what those nights have actually earned you, on your own record, in a normal season. If a long stay uses nights you'd usually sell at a higher net rate, it has to offer something in exchange, and that something needs a name.

The third is what the stay buys besides money. A long stay can fill a genuinely dead stretch, cut turnover, or bring a guest who returns. Those are real, and they can justify a lower floor. What they can't justify is a floor you can't state out loud, because a reason you can't articulate can't be reviewed.

Then say it once. When the guest pushes for a lower rate, give them the net figure you can hold to and explain, in one sentence, what it's built on. A host who can explain a floor is harder to push past than one who simply says no, and the guests worth keeping tend to respect the arithmetic. Write the floor down beside the model, too. A floor that lives only in your head resets every time you're tired or the calendar looks thin.

FAQ

Why shouldn't I just compare the requested rate with my usual nightly rate?

Because a long stay changes both the costs and the opportunity, and a nightly comparison captures neither. Two nights and twenty nights don't share a cost structure, so comparing rates says nothing about the whole period.

Which deductions should go into a long-stay model?

Start with the platform side and the tax and local levies that apply where the property sits, then split your own costs into a fixed part and a part that grows with the stay. Use your own figures and the platform's current terms; percentages from elsewhere will mislead you.

How do I set a floor I can actually defend?

Build it from three parts: the cost you must cover, what those nights have historically earned you, and what the stay buys you besides money. Write the number down before the conversation, and when you're asked for more, explain what the floor is built on rather than moving it.

A long-stay decision is an accounting decision wearing the clothes of a negotiation. Start from the guest's total, take the three deductions out in order, and compare the net figure per night with what those nights would otherwise earn. If you want your own occupancy, average daily rate and revenue per available room in front of you while you work through it, localsbnb.com keeps those figures for your properties, so the floor you set rests on your record rather than on a feeling about the month.

---

This article is general guidance for hosts and isn't financial or tax advice. Tax treatment, platform fees and local levies differ by place and change over time; use your own figures and the rules that apply where the property sits.