Wings, Etc.

The vendor opportunity at Wings, Etc.

Wings, Etc. is a quick-service restaurant chain headquartered in Indiana with 82 total units—56 franchised and 26 company-owned—and an average unit volume of $1,515,197. Year-over-year unit growth sits at 3.704%, indicating modest but steady expansion. For software vendors, the addressable market is small and concentrated: all mapped operators are in Indiana, and the operator footprint shows only two operators, neither of which is a multi-unit franchisee. The system is overwhelmingly single-unit, which means any software sale must align with a corporate mandate rather than a large franchisee-led buying coalition.

The chain operates on a 10-year initial franchise term with a 4.0% royalty. Renewals are also for 10 years, contingent on good standing, timely notice, signing a general release, paying a renewal fee, renovating to then-current standards, completing current training, and signing the then-current form of Franchise Agreement—which may contain materially different terms. This renewal structure creates natural inflection points where franchisees must upgrade technology to comply with updated standards, opening windows for vendors whose solutions align with corporate mandates.

Who controls software purchasing

Software purchasing authority at Wings, Etc. sits at headquarters. The FDD’s Item 1 lists the executive team: James H. Weaver Jr. (Chairman), Robert Hensmann (President & Chief Executive Officer), Eric Stuczynski (Chief Procurement and Development Officer), George Pasick (Senior Director of Franchise Development), and Charles Moore (Chief Operating Officer). For a vendor making an initial pitch, the most relevant contacts are Robert Hensmann as CEO and Eric Stuczynski, whose title explicitly includes procurement and development. Charles Moore, as COO, likely holds operational veto power over any technology that touches store-level workflows.

There is no parent company on file; Wings, Etc. appears independently owned. The operator footprint confirms the centralized dynamic: only two mapped operators exist across approximately two located units, with zero multi-unit operators in the 2–9, 10–24, or 25+ unit bands. This is not a system where a large franchisee group can drive adoption from below. Vendors must sell into HQ.

Mandated and current tech stack

The 2026 FDD mandates five named systems. For back-office and inventory management, the chain requires COMPEAT/Restaurant 365. Online ordering is handled through Olo by Olo Inc. The loyalty program runs on Punchh. Point-of-sale is locked to Revel by Revel Systems, Inc. Payment processing is mandated through Vantiv Inc. This is a fully prescribed stack with no optionality disclosed in the FDD, meaning any vendor attempting to displace an incumbent must make a compelling case for switching at the corporate level and must account for the integration dependencies across all five systems.

For vendors selling adjacent or complementary software—such as labor scheduling, catering, delivery aggregation beyond Olo, or advanced analytics—the opportunity lies in layering on top of the mandated stack rather than replacing it. The presence of Restaurant 365 suggests the chain values operational visibility, and the Olo-Punchh combination indicates a digital-ordering-and-loyalty flywheel that a vendor could augment with CDP, marketing automation, or AI-driven upsell tools.

Procurement, renewals, and timing

Item 8 of the FDD does not include a procurement extract in the data on file, so the designated-supplier versus approved-supplier distinction is not publicly available. In practice, the mandated-tech list functions as a de facto designated-supplier program for those categories. For categories not covered by the mandate, vendors should assume a corporate approval process led by the Chief Procurement and Development Officer.

The renewal provisions in Item 17 are the clearest timing signal. Franchisees must renovate their restaurants to comply with then-current standards at each 10-year renewal. If the franchisor updates its tech standards as part of those renovation requirements, each renewal cycle becomes a forced technology refresh moment. With 56 franchised units and a 10-year term, a rough average of five to six units come up for renewal each year, though actual clustering depends on when the system began franchising. Vendors should monitor FDD updates for changes to the mandated-tech list, as those changes signal an active evaluation cycle at HQ.

How to read the Wings, Etc. FDD

The 2026 Wings, Etc. Franchise Disclosure Document is the definitive source for the data points that matter to software vendors: Item 1 identifies the executives who control purchasing, Item 11 details the mandated technology systems, Item 8 (when present) describes procurement restrictions, and Item 17 lays out the renewal conditions that drive technology refresh cycles. The embedded PDF viewer below contains the full document. For vendors building a ranked target list of franchise systems, FranCloud normalizes these FDD signals across hundreds of brands so you can prioritize accounts by decision-maker concentration, tech-stack openness, and renewal-driven timing.