There is an asymmetry almost nobody looks at directly. A company invests months of work, travel and fees in reaching a particular meeting. And then it hands the final stretch — the meal, the one moment with everyone's guard down, where the real conversation happens — to whichever supplier answered the email first.
It isn't a question of spend. It's a question of proportion. And when something goes wrong, it almost never goes wrong in the kitchen.
Why a corporate lunch is judged by a different measure
Among friends, a twenty-minute delay is an anecdote. In a leadership committee that has set aside the whole morning, those same twenty minutes pull apart a schedule someone spent weeks assembling.
That's the difference. In a corporate setting nobody is judging the food: they are judging whether the meeting went the way it needed to go. The bar is set by the context, not by the menu.
The seven failures, one by one
These are the ones that recur most. If you organise leadership lunches or client dinners, at least three will be familiar.
Set-up runs late and pulls the schedule apart
The team arrives late, or arrives on time but needs more room and more minutes than anyone allowed for. The meeting is cut short, or the food arrives exactly when the conversation had found its stride.
When it was decided: the day nobody asked about loading times, the service lift and the exact hour the room becomes free. It is settled in the preparation, never in the execution.
Dietary requirements arrive too late
Someone is coeliac, someone doesn't eat pork, someone flagged an allergy that never reached the kitchen. The outcome is always the same: a guest explaining out loud, in front of everyone, what they cannot eat. And a separate plate that singles them out rather than including them.
When it was decided: the moment requirements were requested after the menu was closed rather than before. Gathered in time, they are designed into the proposal and nobody notices. Gathered late, all that's left is improvisation.
Staff don't know the menu or the protocol
A guest asks about an ingredient and nobody can answer. Or the service interrupts precisely when the conversation had reached the point that mattered. The floor team isn't an accessory to the menu: they set the rhythm of the meeting.
When it was decided: when staff were assigned the day before, with no prior briefing and having never seen the space. With rotating staff, every service starts from zero.
Information is split across several contacts
The account manager agreed one thing, the head chef understood another, and whoever is actually in the room on the day heard neither. Every layer of intermediation is one more place where something can be lost.
When it was decided: at the point of engaging a structure with more than one point of contact. It's the quietest failure of the seven, because it stays invisible until it has already happened.
The most expensive failure isn't the one visible at the table. It's the one nobody caught while it could still be corrected.
The venue lacks the equipment needed
There's no water point nearby, the office kitchen has no oven, the only available socket is on the far side of the room. It's discovered on the day, when there's no margin left. From that moment, the whole service suffers for it.
When it was decided: when nobody assessed the space before the proposal was closed. Half an hour of checking beforehand prevents ninety per cent of these.
The budget grows after the proposal
Items appear that were never there: a staffing supplement, travel, tableware hire, a venue levy. The final figure bears little resemblance to the one that was approved, and somebody has to account for that internally.
When it was decided: on accepting an open estimate instead of a closed figure in writing. Transparency isn't a gesture of goodwill: it's a decision about format.
Coordination consumes the internal team's hours
It usually lands on an executive assistant or on HR. Calls, emails, confirmations, last-minute changes, invoices that don't reconcile. Hours from someone who should be doing something else, spent chasing a supplier.
When it was decided: in the engagement model itself. The more suppliers involved, the more internal load is created by a commission that was supposed to remove it.
The pattern: none of them happens at the table
Read them again in sequence and the common thread is obvious. Not one of the seven is a cooking problem. Not one is solved by cooking better.
All of them are preparation problems: what was asked beforehand, what was put in writing, who answers for it. They are decided in the preceding weeks and revealed during two hours of a meeting, when nothing can be done about them.
That is where Strategic Hospitality comes from: treating the corporate table the way any other business decision is treated, with the same anticipation and the same rigour. It isn't another tier of service. It's a working method.
Everything visible here was decided weeks earlier.
What changes when hospitality is treated as a process
What changes is where the effort goes. Instead of concentrating it on the day of the service, it is concentrated beforehand: in a thirty to forty-five minute conversation that establishes the purpose of the meeting, who will be at the table, what the requirements are, what the space is like, and what the occasion needs to achieve.
That conversation isn't a sales formality. It is the product. It's where the seven failures above are closed off, one by one, before they exist.
Everything else follows from it: a menu designed for that specific occasion, closed pricing in writing within 48 hours, a single point of contact from start to finish, and a service that never draws attention to itself.
Frequently asked questions
Can a leadership lunch be served at our own offices?
Yes. The Gabinete format is built precisely for that: served at the client's own premises, with no event set-up, for groups of 4 to 18. What determines whether it works isn't the space itself but access to water, power and a work surface — all of which is checked at the briefing beforehand.
How far in advance should a corporate lunch be booked?
Two to three weeks is a comfortable margin for working with seasonal produce and settling the logistics without rushing. Shorter notice can be accommodated, but the tighter the timeframe, the less room there is to resolve problems before they reach the table.
How are allergies and diets handled in a large group?
Requirements are gathered before the menu is closed, not after. That allows them to be designed into the proposal rather than solved with a separate plate. The aim is that no guest has to explain at the table what they can't eat.
Can the price be fixed in advance?
Yes. After the briefing you receive a proposal with closed pricing in writing, within 48 hours. The figure doesn't change even if the meeting runs long. Any additional item — travel beyond the city of Madrid, or equipment the venue doesn't have — is set out in that same proposal, never afterwards.
