Pudgie's

The vendor opportunity at Pudgie's

Pudgie's is a quick-service restaurant concept headquartered in New York with a total footprint of just 7 units, split between 5 franchised and 2 company-owned locations. For a software vendor, this is not a volume play. The total addressable market is 7 locations, concentrated primarily in New York (8 mapped locations) with a single unit in Pennsylvania. The operator base is small but experienced: of the 5 mapped operators, 4 are multi-unit owners, though all fall within the 2-9 unit band. No operators have scaled beyond 9 units. The brand does not disclose an average unit volume (AUV) in its most recent FDD, and year-over-year unit growth is not available.

This is a lean, tightly controlled system. The small size means a single deal can cover the entire franchise network, but it also means the buyer is likely highly selective and cost-conscious. The royalty rate is 7.0% on gross sales, and the initial franchise term is 10 years.

Who controls software purchasing

All software purchasing authority rests with the brand's Co-Founders and Managing Members, David J. Cleary and Robert A. Cleary. They are the only executives listed in Item 1 of the 2025 FDD. There is no named CIO, CTO, or VP of Technology, which is consistent with a system of this size. A vendor's pitch must be direct, concise, and speak to the operational realities of a sub-10-unit chain. The Clearys are the entire buying center.

Mandated and current tech stack

The 2025 FDD mandates a Proprietary Software Program for all franchisees. No other third-party technology vendors are named in the available disclosures. This suggests the brand relies on a custom-built or white-label system for its core operations, which could include point-of-sale, reporting, or inventory management. The absence of named commercial vendors like Toast, Square, or NCR Aloha is notable and represents either a gap or a deliberate strategy of in-house control. For a software vendor, this means any pitch must either integrate with or replace a proprietary system, requiring a strong technical integration story or a compelling total-cost-of-ownership argument.

Procurement, renewals, and timing

The procurement model is not disclosed in the available FDD extract. Item 8, which typically outlines whether franchisees must buy from designated suppliers, approved suppliers, or have open purchasing, provided no signal. This lack of clarity means a vendor should be prepared for either a centralized, HQ-mandated purchasing process or a more flexible, franchisee-driven model.

Contract renewal timing offers a potential wedge. The initial franchise agreement runs for 10 years. Franchisees have the right to renew for two successive additional periods of 5 years each, provided they meet several conditions. Critically, one condition requires franchisees to complete all maintenance, refurbishing, and remodeling no later than 90 days before the expiration of the then-current term to bring the business into full compliance with then-current standards. This 90-day pre-expiration remodel window is a natural trigger point for technology upgrades. A vendor can time outreach to coincide with these renewal cycles, positioning their software as part of the modernization effort required for renewal. The renewal also requires execution of the then-current form of franchise agreement, which may contain materially different terms, including new technology mandates.

How to read the Pudgie's FDD

The full 2025 Franchise Disclosure Document provides the legal and operational detail needed to build a precise sales strategy. It contains the exact language on technology mandates, procurement restrictions, and renewal conditions summarized here. Review the embedded document below to verify unit counts, operator structures, and executive contacts before outreach. For a ranked target list of franchise systems that match your ideal customer profile, FranCloud can help you prioritize accounts based on tech stack, growth rate, and buyer accessibility.