Baba Saj Restaurant Group

The vendor opportunity at Baba Saj Restaurant Group

Baba Saj Restaurant Group operates as a quick-service restaurant concept headquartered in Illinois. According to its 2025 Franchise Disclosure Document, the system consists of just 2 total units, both company-owned. The number of franchised locations is not disclosed, which suggests the brand has not yet scaled through franchising or that franchised unit counts are negligible. For software vendors, this means the immediate addressable market is confined to those 2 corporate locations. There is no YoY unit growth rate available in the filing, and average unit volume (AUV) is not reported. The royalty rate is set at 5.0% of gross sales, and the initial franchise term runs 10 years.

Given the small unit count, any software sale into Baba Saj will be a headquarters-level decision with a very limited deployment footprint. Vendors should approach this as a relationship-driven, single-entity sale rather than a multi-unit rollout opportunity.

Who controls software purchasing

The 2025 FDD lists two executives in Item 1: Ahmad Ali Alzoubi, CEO, and Yazeed Odeh, Branch Manager & CEO Assistant. With no franchised operator footprint mapped in our corpus and no parent company on file—the brand appears independently owned—these two individuals represent the entire buying center. In a 2-unit, company-owned system, the CEO likely holds direct authority over technology procurement, possibly with input from the branch manager on operational fit. There is no CIO, CTO, or dedicated IT role disclosed, so vendors should expect to engage directly with the CEO or his assistant when pitching software.

Mandated and current tech stack

Baba Saj Restaurant Group mandates Clover by Fiserv, Inc. as its point-of-sale system across all locations. This is the only technology vendor explicitly named in the FDD. No other mandated or recommended systems—such as back-office, inventory, labor scheduling, or loyalty platforms—are disclosed. For vendors selling complementary or replacement technology, the Clover mandate is a critical fact: any new software must either integrate with Clover or justify displacing it at the HQ level. Given the small footprint, displacement is a high-friction path; integration or add-on solutions that enhance the existing Clover environment may find a warmer reception.

Procurement, renewals, and timing

The FDD does not include an Item 8 procurement extract, so the brand’s supplier model—whether designated, approved, or open—is not publicly known. Vendors will need to clarify procurement rules directly with HQ. On the renewal side, Item 17 provides some timing signals: franchisees in good standing can sign a successor agreement for up to two additional terms of 5 years each, unless the franchisor withdraws from the geographic area. However, with no franchised units disclosed, this renewal structure is theoretical for now. For the 2 company-owned stores, software contract windows are not tied to franchise renewal cycles; they are driven by internal HQ budgeting and operational timelines, which are not disclosed in the FDD.

How to read the Baba Saj Restaurant Group FDD

The 2025 Franchise Disclosure Document is the primary source for the data points above. It contains the legal and operational disclosures that define the franchisor-franchisee relationship, including Item 11 (franchisor’s assistance, advertising, computer systems, and training), which is where the Clover mandate appears. Item 1 identifies the executives, Item 8 covers procurement (when included), and Item 17 outlines renewal conditions. For software vendors, the FDD is a due-diligence starting point—it reveals what the franchisor requires, who runs the business, and how the system is structured. Use the embedded viewer below to examine the full filing. When you need a ranked target list of franchise systems matched to your software category, FranCloud can help.