The opening plan has a layer underneath it
A new restaurant needs financing, people, equipment and customers. It also needs the connected systems in the building to work together. That last requirement has a way of becoming urgent at precisely the wrong time.
At the Restaurant Franchising Innovation Summit, Daniel Martinez of QNS joins Beck to talk about the infrastructure beneath restaurant growth. His concern is what happens when a brand selects the technology it wants without giving enough attention to the network and physical foundation supporting it.
The conversation includes point-of-sale, loyalty, cameras and other connected systems. Each can have a useful role. Adding them does not automatically produce an environment that is reliable, understandable or easy to repeat in the next location.
Martinez advocates doing that planning before the operation reaches the point where changing it is painful. The lesson is straightforward: include infrastructure in the growth discussion while there is still time to make deliberate choices, rather than treating it as a problem for someone to solve just before opening.
Start with the operation, then examine the equipment
Martinez begins by asking what is happening in the business. Is it growing, shrinking or changing? What resources are available? Where are the constraints in capital, ongoing expense or people? Those answers shape what a useful plan can realistically accomplish.
He describes developing an approach that can be repeated across locations. That matters because a growing brand can otherwise end up solving the same basic questions differently at every opening. Differences that seem manageable in one restaurant become harder to support across a larger footprint.
Reviewing the environment can also expose services or systems that no longer justify their cost. Martinez discusses savings he has found, but the interview does not establish a guaranteed result for another operator. The value of the exercise is finding out what the business actually has and what it still needs.
For a leadership team, a good starting question is whether someone can explain the purpose, ownership and dependencies of the current setup. If that answer relies entirely on one person’s memory, the next location may inherit more uncertainty than anyone intended.
Yesterday’s decisions are still plugged in
Beck compares layers of inherited technology to an archaeological dig. A leader introduces a system, moves on, and leaves the next team to determine what it does. Martinez recognizes the pattern: remove what you understand, leave the unfamiliar pieces alone and keep building on top.
That can be a rational short-term response to a busy operation. It can also leave the business carrying decisions nobody would make again today. The interview’s discussion of technology debt is especially practical because it concerns real equipment, services and dependencies rather than an abstract problem somewhere in IT.
Martinez’s example of a coffee shop in a parking lot shows how physical the planning can become. Power and water may be addressed, and conduit may be installed for telecommunications. The remaining question is whether that route reaches the carrier’s actual service and supports the intended connectivity plan.
A cheaper device deserves similar scrutiny. The purchase price is visible immediately. Support requirements, replacement work and operational disruption become visible later. Martinez argues for considering the cost over time and negotiating for an appropriate solution, rather than letting the lowest initial price settle the decision.
The best result may be a quiet phone
Martinez describes satisfaction in helping a smaller brand prepare for the growth it wants to achieve. The appeal is participating early enough to make a difference in how the business develops, not simply arriving after it has become large.
One anecdote captures the unusual visibility problem of infrastructure work. He asks an executive whether the team has mentioned his work. The response, as Martinez recalls it, is that the absence of complaints is itself evidence that things are going well.
That is a customer anecdote, not a performance study. It still identifies a familiar operating reality: people notice the systems most when they interrupt the job. Reliable infrastructure gives a restaurant team attention back for the things customers actually came for.
The conversation closes on trust and responsibility. Beck’s enthusiasm for Martinez is personal, but the operational question applies to any provider: will this partner understand the business, explain the choices and remain accountable for the work? A growth plan needs that clarity as much as it needs another opening date.
