Unreasonable Hospitality in Product Marketing: The Book Every PMM Leader Should Read

The product marketing canon is predictable. April Dunford on positioning. Crossing the Chasm for market entry. Maybe a Pragmatic Institute certification on the shelf. These are legitimate resources. They are also well-worn, and the insights they generate tend to look similar across teams that have read the same books.

Will Guidara's Unreasonable Hospitality is not in the canon. It's a memoir about running a restaurant. Guidara co-owned Eleven Madison Park and, over roughly a decade, took it from a competent but unremarkable New York institution to the best restaurant in the world. The book is about what that required. It has no frameworks for messaging architecture. There is no chapter on ICP definition or launch tiering. Nothing in it was written with a PMM audience in mind.

Read it anyway. The arguments Guidara makes about the difference between service and hospitality, about reading a guest versus executing a playbook, about building a culture where everyone owns the experience: these translate into product marketing with more precision than most PMM-specific writing does. This post is about why, and what to do with it.

Service Is Not Hospitality. This Is the Whole Argument.

Guidara draws a hard line early in the book between service and hospitality. Service, in his framing, is the technical execution: the food arrives correctly, at the right temperature, in the right sequence, to the right table. A restaurant can deliver flawless service and leave a guest feeling nothing in particular. Hospitality is different. It's what makes the guest feel seen. It's the difference between executing a process and responding to a person.

Most product marketing operates at the level of service. The one-pager is accurate. The demo deck covers the right capabilities. The battle cards address the likely objections. This is technically correct execution, and it is not enough. A prospect who receives technically correct PMM output understands the product. That's not the same as a prospect who feels understood.

The distinction matters more at the enterprise level, where the buying process is long, multi-threaded, and emotionally loaded. A VP of Engineering evaluating a DevOps platform isn't just assessing features. She's managing her own internal narrative: what happens to her credibility if this goes wrong, which of her peers will resist the change, and whether the vendor seems to actually understand the environment she's operating in. Accurate messaging addresses the first question. Hospitality addresses all three.

| The PMM teams that win at enterprise aren't the ones with the sharpest value propositions. They're the ones whose buyers feel genuinely understood at each stage of the process.

The practical implication is that PMM needs two distinct evaluation criteria for its outputs. The first is accuracy: does this correctly represent what the product does and why it matters? Most teams run this check. The second is reception: does this make the buyer feel like someone thought specifically about their situation? Very few teams run this check, because it requires knowing more about the buyer's internal context than a persona doc captures. That gap is where deals get lost to competitors with comparable products and sharper hospitality.

Reading the Guest Instead of Running the Playbook

One of the more operationally specific practices Guidara describes is a pre-service ritual at Eleven Madison Park. Before each seating, the team would review reservation notes: not just covers and dietary restrictions, but anything a host had captured about who was coming in and why. A birthday. A first date. A business dinner where one party was clearly trying to impress the other. This information shaped how the team approached each table. Not a different menu. A different level of attentiveness to what this particular group of people needed from the evening.

The PMM parallel is buyer context work: the practice of building a picture of what a specific prospect's internal situation looks like before they enter an active sales conversation. Not persona work (most teams have done that). Something more specific: what is this type of buyer worried about right now, who do they have to sell this decision to internally, and what does a successful outcome look like for them personally, not just organizationally?

Most PMM teams produce content for personas, not for situations. The difference is meaningful. A persona tells you something about a buyer's role and general priorities. A situational brief tells you something about the specific pressure they're under when they're evaluating your product. Guidara's pre-service ritual was effective because it was situational. He wasn't running a standard playbook for "table of four on a Tuesday." He was responding to who was actually in the room.

Translating this into PMM practice means win/loss analysis becomes a primary input, not an afterthought. It means sales conversations get debriefed for situational texture, not just for feature gaps. And it means the PMM team's job isn't done when the message is built. It's done when the message is calibrated to the moment the buyer is actually in.

"I've Got It": Why Culture Determines Whether Hospitality Scales

The most distinctive cultural norm Guidara built at Eleven Madison Park was what he called the "I've got it" culture. Any member of the team, at any level, had the standing to notice an opportunity to create a meaningful moment for a guest and act on it. No permission required. The server who overheard that a table had just gotten engaged didn't need to find a manager. She had it. The kitchen could respond. The room could shift. The constraint was judgment, not hierarchy.

This is where the hospitality argument connects directly to how a PMM function is structured and how it relates to the rest of the GTM org. The failure mode Guidara is solving for (a team that sees the opportunity but waits for someone else to act) is exactly the failure mode that produces generic, uncalibrated PMM output at scale.

BlindSpot's Customer Zero framework is built on a related premise: that PMM's most important customer is internal, and that the sales team, CS team, and product team need to be active participants in how the message is carried, not passive recipients of content the PMM team produces. An "I've got it" culture in a PMM context means an AE who hears a specific objection in a late-stage deal has both the standing and the material to respond to it without waiting for a new battle card. It means a CSM who sees a retention risk framed in terms the positioning doesn't address can surface that signal directly to PMM and expect a fast response.

This is also what separates a Chief Evangelist from a content producer. A PMM leader who functions as a chief evangelist builds a culture where belief in the product story is distributed across the commercial org, not concentrated in the marketing function. Guidara's point is that hospitality can't be delivered by one person or one team at scale. It has to be a shared orientation. The same is true for the product story.

| Hospitality can't be delivered by one person at scale. Neither can your product story. Both require a culture where everyone with a customer-facing role feels ownership over the experience.

Why Most Teams Stop at Service

Guidara is clear-eyed about why unreasonable hospitality is rare: it's harder than service, it requires more judgment than a playbook, and the returns aren't immediately visible on a P&L. A restaurant can run a technically correct operation for years without anyone naming what's missing. The same is true in PMM.

The proximate cause is measurement. Service is measurable: content produced, campaigns launched, sales collateral coverage rate, message adoption scores. Hospitality is harder to quantify: whether the buyer felt understood, whether the sales team had the right situational response at the right moment, whether the positioning created confidence rather than just comprehension. The things that are easy to track tend to become the things teams optimize for, and the things that are hard to track tend to get deprioritized.

The structural cause goes deeper. Building hospitality into a PMM function requires investing in buyer context work that doesn't produce obvious artifacts. Win/loss synthesis, situational brief development, ongoing calibration of messaging against real deal texture: this work doesn't show up as deliverables in a content calendar. It shows up as shorter sales cycles, higher conversion at late stage, and retention that holds through contract renewals. Those outcomes have many causes, and PMM rarely gets credit for the hospitality-level work that contributed to them.

Guidara's answer to this at Eleven Madison Park was to make the culture explicit: to name what unreasonable hospitality meant, to celebrate examples of it, and to build it into how the team evaluated its own performance. The PMM equivalent is building buyer experience into how the function measures itself, not as a soft aspiration but as a concrete set of signals the team tracks and acts on.

Work With BlindSpot

If you want to read one book this year that will change how you think about product marketing, read Unreasonable Hospitality. Not because Guidara is writing about B2B SaaS. Because the problems he's solving (the gap between technically correct execution and genuine attentiveness, the challenge of making hospitality scale across a team, the discipline of reading each guest rather than running a standard playbook) are the same problems every PMM leader is navigating, and he has sharper language for them than most marketing books do.

BlindSpot works with enterprise B2B SaaS companies to assess and rebuild their PMM function, including the buyer experience gaps that don't show up in content audits but do show up in win/loss data. Contact us to talk about what a PMM effectiveness assessment looks like for your team.