Guy Van Neck

Guy Van Neck's public thinking centers on one recurring diagnosis: the failure point in multi-location retail and hospitality businesses is almost never the people, and it is rarely the data either. It is the translation gap between information and action, the moment a manager stands in front of a team before a shift starts and has to decide what actually matters that day. He returns to this idea across dozens of posts with near-identical phrasing, which is itself telling: "Same brand, same training, same numbers. The difference was never the people" . He frames this as counterintuitive to how most operators think, arguing that "Great managers are not the bottleneck most operators think they are" and that even strong managers looking at "the exact same data" will "often reach completely different conclusions" . His answer to the industry's default explanation, that better training fixes everything, is blunt: turnover and performance gaps "have nothing to do with what anyone was taught" .

This diagnosis is backed by a consistent set of numbers he cites repeatedly: Coresight's figure that operational inefficiency costs "6.4% of gross sales" , and separate data showing workers given less than 72 hours' schedule notice quit within six months at "39%" versus "24%" for those given two weeks or more . He uses these statistics not as isolated trivia but as evidence for a broader claim, that the industry misattributes structural and informational problems to talent or training problems. On scheduling specifically, he pushes back on the language operators use to justify last-minute changes, noting that flexibility "framed" from management's side looks like instability from the employee's side: "You can't plan a life around a job that won't tell you what it wants from you until the same morning" .

His thinking has an evolution he's explicit about rather than glossing over. He describes building an earlier product, Nudgr, based on a "simple concept: use data to tell the employee exactly what to do next," bypassing the manager entirely. He says he was drawn to this because "cutting the middleman made sense... on paper at least," but within months the team "pulled it" because the model had "no room" for real-world disruption, his example being a walk-in fridge dying before service. His conclusion was structural, not just tactical: "A manager does, and knows the whole shift now needs to run differently... No person in the loop who could say yes, no, or not today" . This failure directly shaped Khova.ai, which he describes as being built from "hundreds of hours" of conversations with store managers, ops directors, and multi-location founders, where the same complaints surfaced "almost word for word": too many disconnected tools, unexplained gaps between locations, performance "depending on who happened to be on shift that day" .

He's consistent in describing Khova.ai's purpose in nearly identical terms across multiple posts: pulling together "sales data, the schedule, the reviews, even things like the weather" into a daily brief so a manager isn't "piecing it together when the first customer walks in" . He frames this as solving a problem he calls "entirely solvable," distinguishing it from vaguer organizational issues operators are usually told to fix . He also leans on customer validation to make the case rather than resting on his own framing alone, quoting Alexander Jerejian of Salsa Shop calling the tool a response to "a different era in hospitality" where "the room for guesswork shrinks" .

A separate but connected theme is his critique of how manager roles are actually defined versus how operators claim to prioritize them. Looking at a template job description, he points out that customer experience is mentioned once despite operators insisting it's the top priority, and that the real time split is inverted from what's claimed: "80% customer and team... 20% tools, admin, reporting. Read the list of responsibilities again. That ratio is flipped" . This mirrors his broader argument, that organizations drift into misalignment gradually, through templates, tools, and habits nobody consciously chose, rather than through any single bad decision.

He also draws a direct, stated parallel between endurance sport and entrepreneurship, treating both as training grounds for the same psychological moment: hitting a wall. Announcing an Ironman entry, he says building a company and training for the race "ask the same thing of you... You will hit a wall. Not maybe, you will," and that the only variable is "what you do in that moment" . This isn't decorative for him, it functions as his explanation for resilience under pressure, framed identically whether the wall is physical fatigue or a deal falling through.

The practical takeaways from his own words are consistent: don't blame training or talent for turnover and performance variance across locations, look instead at scheduling notice and pre-shift information flow ; don't assume more dashboards or more data will close a performance gap, since operators already have plenty of both ; and don't fully automate the human decision layer out of frontline operations, since his own product history shows that removing the manager's judgment call breaks under real-world disruption . His stated view, distilled, is that the fix isn't more tools or more training but building "the part that turns all of it into the right call, for the right location, on the right day" .