The local experience is part of the operating model
At Crust Pizza, ordering at the counter does not mean listening for your name and retrieving a box. Carl Comeaux describes food brought to the table on real plates, refills delivered to the booth and a team that clears the table afterward. Those choices define the kind of place the company wants to be.
In his ChatGTM conversation with Michael Beck and Chad Horn, Comeaux returns to the relationship between neighborhood, product and place. Expansion has to preserve all three. A restaurant can reproduce the logo and the pizza while quietly losing the reason a family wanted to spend an hour there.
That creates a more demanding growth question than how many locations a territory can support. What must each new location be capable of doing, repeatedly, for the brand's promise to remain recognizable? For Crust, the answer includes ingredients, service and a franchisee willing to participate in the community.
Select an operator for the job that actually exists
Comeaux describes two kinds of prospective franchisees. One is an owner-operator learning the business in the first location before developing managers and expanding. The other already operates restaurants, has a management team and wants an additional brand in a familiar market.
Those are different starting positions. Someone with capital but no operating experience needs a different path from a multi-unit team that already knows how to run shifts, support managers and read a restaurant's financial performance. Treating both as interchangeable investors would hide important support needs.
He also expects local involvement. The operator becomes a representative of the brand in that town, not simply the holder of a development agreement. That expectation belongs in selection and onboarding, where it can influence the decision, rather than arriving later as a corporate request to attend community events.
Support has to continue after opening week
Comeaux describes monthly conversations with franchisees about their profit-and-loss statements, operating issues and possible improvements. He emphasizes that the contact continues beyond the initial opening period. The restaurant does not stop encountering new problems when the launch team leaves.
The numbers provide a place to start those conversations. Comeaux sees them as evidence of activities that occurred in the business. A result becomes more useful when the discussion moves toward the ordering decision, schedule or operational behavior behind it.
That approach also requires restraint. He acknowledges how easy it is to get too deep into analysis. Support should help an operator make a decision they understand, not leave them impressed by a spreadsheet they cannot use. One clear action and a date to review its effect may be more useful than a comprehensive lecture on every variance.
Build a route for feedback to travel both ways
Comeaux recalls a period when corporate and franchisees felt as though they were working on separate islands. The response included a franchise advisory council, with franchisees involved in discussing the work and gathering feedback through other operators. The structure gave communication a route beyond occasional announcements.
The company's summit served a different purpose: putting franchisees, managers and vendors in the same room. Comeaux describes a distinctly Louisiana gathering, complete with a crawfish boil and a large float. The memorable social experience mattered because people who normally encountered one another through business issues had time to build relationships.
Neither mechanism replaces the other. A good evening together cannot answer an unresolved operating problem. A council agenda cannot manufacture trust on its own. Growing brands need a reliable way to hear disagreement and enough familiarity for people to raise it before frustration becomes their default relationship with corporate.
Technology should serve the restaurant you promised
Crust's custom technology work reflects Comeaux's team's prior experience building systems. He is clear that this experience affects the build-versus-buy decision. It is not a general instruction for every restaurant company to become a software company.
At the time of the conversation, he describes a customer-facing phase being stabilized in a corporate location before broader rollout, alongside a larger vision connecting operations and information. Keeping those stages distinct matters. An expansion plan and a deployed capability are different things, especially for franchisees planning their own work around them.
The useful test is whether a system helps the people running the restaurant deliver the intended experience. Can managers see the information they need? Does training prepare employees for the actual service model? Are franchisees involved before a change reaches every store? Those questions bring a large growth ambition back to the neighborhood table where the brand has to earn another visit.
