In this article
Free wifi attracts the guest who orders one coffee and stays for four hours. Whether that costs you anything doesn't depend on the guest. It depends on the clock.
Free wifi is on almost every checklist of what a modern café or bistro should offer, and rightly so — it's the reason a guest with a laptop walks in at all instead of choosing a place three doors down. What's on no checklist anywhere is the other half of that story: the same wifi, plus a power outlet within reach, also invites the guest who orders one coffee at 11:00 and is still there at 15:00, while the lunch rush at 12:30 needed a table that never freed up.
Every independent café or bistro owner in Europe recognises this guest instantly. What almost nobody actually calculates is what that guest costs — and the few who try usually get it wrong, because they price every hour of the day the same, as if one table hour is worth the same at 15:00 as it is at Saturday lunch peak. That's exactly the mistake this article sets out to fix.
The answer isn't "ban laptops" — that's about the worst thing a small operator can do to their own business. The remote worker who orders lunch at 11:00, then a coffee, then leaves a good Google review on the way out is very often the exact same person as the guest with the screen open. Chase that guest away and you don't just lose one table — you lose a regular.
This article builds a different answer, around one insight most owners overlook: the same laptop guest costs you a wildly different amount depending on when they sit down. Four fixes, ranked from unnoticeable to direct, and a calculator that turns your own numbers into a concrete weekly figure — not an average guest who is worth the same at every hour.
Why the hour matters, and the guest doesn't
A table sitting empty at 15:00 on a Tuesday was never going to sell anyway. Nobody was queuing for that seat; the "revenue" a laptop guest "takes" there never existed before they sat down. That same table at 12:30 on Saturday could, with near certainty, have carried two or three full lunch turns in the time the laptop guest occupies it. The guest is identical. The cost is not.
Most owners react to the guest — a look, a sigh, eventually a sign by the door — rather than to the clock. That's the order reversed. The moment you reframe the problem from "this guest is staying too long" to "this table is scarce right now and isn't at other times", the whole set of fixes changes: not how to move one guest along, but how to design and run the room so scarcity manages itself without anyone ever having to say a word.
That distinction is also why this piece isn't a sequel to table turnover strategies, which covers five general tactics for guests who are actively dining — course pacing, RevPASH, the usual levers. A laptop guest isn't eating slowly; they aren't eating. That needs a different mechanism, and this isn't a loose-tips listicle for it: it's a framework of four fixes, each ranked on what it recovers AND what it risks with a good regular.
Ultimate guide Every financial decision in a restaurant The complete guide to revenue, costs and margins Read the guideThe four fixes
The first two fixes are structural: the layout and the menu decide, and no guest is ever spoken to personally. The third is a posted note — everyone reads the same words, nobody is singled out. Only the fourth is interactional: a staff member has to say something to that one specific guest. Build them in this order, and use the calculator below to see which ones are worth your own numbers.
One thing worth knowing before you start: the fix that wins back the most money isn't automatically the most direct one. The posted note by the door — which never addresses anyone personally — recovers MORE in the chart below than the timed wifi code, which does address someone directly. Structural often beats interactional, on the euros as well as on the relationship.
1. Read the floor, not the guest
The simplest fix costs no words and no sign at all: split the room into zones in advance. Small tables by the window or at the bar, with no outlet in reach — fast, short-stay seats. Tables at the back or in a corner, with an outlet — the spot where staying a while is clearly welcome. A guest with a laptop hunts for the outlet themselves, which means they sort themselves into the right zone without anyone ever having to say a word.
This is exactly why interior design and layout do more than set a mood — a well-thought-out floor plan steers behaviour long before any conversation is needed. The decision is made once, at fit-out, and then it works on its own, every service, forever.
The result is modest — you win back the peak-hour window and bar tables, not the quiet corner at the back, and that corner was never going to sell during the lunch rush anyway. But it costs nothing, asks nobody to say anything, and it's the first layer you can almost always apply before reaching for anything more direct.
Climb further if: the peak-hour tables by the window or the bar stay occupied despite the layout — then the issue isn't where people sit, it's how long they stay once seated, and that calls for the next layer.
2. Let the menu set the pace
Plenty of cafés already run a different menu between breakfast, lunch and evening. The same logic solves part of the table problem: let the full, longer menu step aside for a shorter, faster-to-cook lunch menu between roughly 12:00 and 14:00 — exactly the window when the room is tightest. Less decision fatigue, faster cooking, faster turnover, and nobody experiences it as a rule — it just reads as "the lunch menu".
It also works in the laptop guest's own favour: a short menu of quick dishes invites a quick lunch, not an afternoon anchored to one table. The kitchen itself sets the room's pace, without a sign ever being needed.
This is the same thinking behind the course pacing covered in table turnover strategies, applied here to a guest who isn't actively eating rather than a guest who eats slowly — the menu itself nudges toward a shorter visit.
Climb further if: the faster lunch tempo does speed up actively-dining guests, but the laptop guest — who was never ordering more than that one coffee anyway — stays unmoved by it. That's the exact signal the next layer is needed, because structural fixes only work on guests who are buying something.
An illustrative café day pattern — the same laptop guest, a wildly different impact at each point in the day.
This pattern is illustrative, not a measurement of your own venue — swap in your own sense of when your room genuinely fills up, and use the restaurant benchmark tool to check your own occupancy numbers against a real market band.
3. Say the peak hours out loud — on paper
A small, friendly note on every table or menu that simply names the window when tables are needed back — "Between 12:00 and 14:00 we turn tables a little faster, thanks for understanding" — is the first fix that actually speaks the policy out loud. But it speaks to everyone at once, never to one specific guest, and that difference is exactly why it lands more softly than a conversation at the table.
That's the counter-intuitive point of this whole article: this fix recovers MORE revenue in the chart below than the timed wifi code further down, and yet it feels less confrontational. A rule that applies to everyone and that nobody reads out loud to you personally is rarely experienced as unfriendly — a staff member singling out one guest is, even when the message is identical.
Feel free to pair it with a soft peak-hour expectation without making it a rule — "during the lunch rush, we'd love our window tables to be full lunches" isn't a minimum spend the way a minimum spend for a group booking is (that solves a different problem entirely — pricing a reserved room for a set amount), it's a soft, general expectation that sets the tone for whoever still needs to have that one conversation.
Climb further if: the note already improves most guests' behaviour, but a small handful of regular laptop guests simply ignore it — often exactly the people who are there every week and have stopped reading the sign. For that group, a structural, automated limit works better than yet another note.
4. Timed wifi, not banned wifi
A code printed on the receipt or handed over at the counter, valid for roughly 90 to 120 minutes, renewable with a fresh order at the till. The wifi stays 100% free — nobody pays for it — but it's no longer a lifetime lease on the table. Anyone who wants to stay longer simply orders something else, which is exactly the behaviour you want to encourage.
This is the only one of the four fixes that's interactional: a staff member hands over the code, and the guest notices themselves when it runs out. That's exactly what makes it the most direct of the four — and, despite that, not the one that recovers the most. It's a supplement to the posted note above, meant for that small group of regulars who ignore the general message, not a replacement for it.
So bring it in only once the first three layers are already in place — the layout, the lunch tempo and the note. For most of your guests, those already solved the problem without a single conversation ever being needed; the timed code is there for the remaining minority that didn't respond to it.
This is explicitly not the same problem as dine-and-dash guests, which covers guests who leave without paying — a very different and far more urgent issue. A laptop guest pays just fine, and simply overstays afterwards; that calls for patience and a well-timed limit, not incident handling.
The most direct fix isn't the one that recovers the most — the posted note is, and that's exactly why the order matters.
Revenue recovered is an estimate of how much of the opportunity cost each fix typically covers; relationship risk is a judgement of how personal the interaction feels to the guest, not of how much revenue it earns.
The number that actually decides what a laptop guest costs
Opportunity cost per table hour is what a fresh walk-in party would likely have spent in that same stretch of time, minus what the laptop guest spends themselves — never a flat hourly rate, because that first figure only exists if there was genuine demand for the seat at that moment.
| Fix | What it asks | Recovered | Relationship risk |
|---|---|---|---|
| Read the floor, not the guest | Nothing — the layout decides | 20% | Low |
| Let the menu set the pace | Nothing — the menu decides | 35% | Low |
| Say the peak hours out loud — on paper | Reading a note | 65% | Medium |
| Timed wifi, not banned wifi | Reordering for a new code | 55% | Higher |
Notice that the posted note (fix 3) recovers more than the timed wifi (fix 4) AND carries a lower relationship risk. That isn't a coincidence — a rule that applies to everyone and that nobody reads out to you personally weighs less than a conversation with one specific guest, even though the latter feels more direct. Build in this order: structural before interactional, never the other way round.
What is this actually costing you, per week?
Fill in the four numbers that actually decide this, based on your own peak hours — not a guess about an "average" guest. The calculator uses the same logic as the table above: what a table normally earns in that window, minus what the laptop guest spends themselves, times how often it happens each week.
The result shows a weekly and yearly figure, and which combination of the four fixes — based on the size of that figure — is worth putting in place.
Your numbers, your figure
Four fields. No account, nothing saved.
—
This is a rule of thumb for deciding which layer is worth it, not accounting advice. The model assumes a laptop guest reorders roughly every ninety minutes — adjust that in your head if your own guests do it more or less often.
A figure of zero or close to it is an answer too: if your peak hours rarely see a laptop guest at all, there's simply no problem to fix, and every option above — even the free layout — costs more effort than it's worth.
When you can skip this
Venues with a short lunch peak and a long, quiet afternoon — most bistros and restaurants without daytime terrace trade — rarely have a real laptop problem: there's simply no hour where the table is scarce enough for the cost to add up. The calculator above confirms that quickly: plug in your own numbers, and if the weekly figure stays small, there's nothing to change.
Venues that deliberately target the laptop guest as their audience — a coworking café, an espresso bar next to an office block that builds its whole identity on exactly that — need to flip this framework rather than apply it: there, the long stay is the product, not the problem, and the real question is how to get those guests paying for the table time they actually use, through memberships or day passes rather than any of the four fixes above.
What's rarely a good idea is skipping straight to the timed wifi code because a posted note "won't work anyway". The numbers above say the opposite — the note usually recovers more, with less friction, and skipping it is skipping exactly the step that would have been cheapest.
Your next move
Don't start with "how do I get this guest to leave". Start with the calculator above and your own peak hours — the figure it produces decides which of the four layers is worth it, and for most venues that's the first two: free, structural, and never worth a conversation.
Is the figure small? Then there's no problem to fix, and free wifi can keep doing exactly what it's for — bringing guests in, not keeping them out.
Is the figure bigger than you expected? Then table turnover strategies is the logical next step for the rest of your room — the same discipline, applied to the guests who are actively dining.