Tiger Sugar

The vendor opportunity at Tiger Sugar

Tiger Sugar is a quick-service restaurant brand headquartered in New York, known for its specialty bubble tea. For software vendors, the brand presents a small but direct sales target: 63 total US locations, of which 45 are franchised and 18 are company-owned. The brand's unit count declined by roughly 2.2% year-over-year, signaling a period of consolidation rather than rapid expansion. This means the installed base is stable, and any software displacement or new implementation must justify itself against a flat or slightly contracting footprint.

The absence of a disclosed average unit volume (AUV) in the 2025 FDD makes it difficult to model per-unit software budgets. However, the royalty rate sits at 7.0%, which is standard for the segment. Vendors should approach this account knowing that the total addressable units number just 63—small enough that an HQ-level deal could cover the entire system in one motion.

Who controls software purchasing

The 2025 FDD names a single executive in Item 1: Pi-Jye "Calvin" Sun, Chief Operating Officer. In a brand of this size, the COO typically holds sway over operational technology decisions, from point-of-sale to inventory management to labor scheduling. There is no CIO, CTO, or VP of IT listed, which suggests that technology purchasing authority is concentrated in the COO's office. Vendor outreach should be directed to Mr. Sun at the New York headquarters. No multi-unit operators are mapped in our corpus, reinforcing the HQ-centric buying model.

Mandated and current tech stack

Tiger Sugar's 2025 FDD does not mandate or recommend any specific technology systems. This is a critical signal for software vendors: there is no incumbent POS, no required back-office platform, and no preferred vendor list to displace. The tech landscape is entirely open. For a vendor, this means the sales conversation starts from zero—you are not unseating a mandated competitor, but you also cannot rely on a franchisee mandate to pull your product through the system. You must sell the COO on the operational or financial return, and then drive adoption across both company-owned and franchised locations.

Procurement, renewals, and timing

Item 8 of the FDD, which typically outlines procurement obligations and designated suppliers, contains no extract in our corpus. This means the brand's purchasing rules—whether franchisees must buy from a designated supplier, an approved list, or an open market—are not publicly known. Vendors should clarify this early in discovery, as it directly affects whether an HQ endorsement translates into unit-level adoption.

Item 17, covering renewal terms, also provides no data: the conditions and term years fields are empty. Without an initial franchise term or renewal window, it is impossible to project when franchisees might be contractually open to switching systems. The recent negative unit growth further suggests that renewal-driven churn is not a tailwind here. Vendors should plan for a proactive, value-led pitch rather than timing a contract cycle.

How to read the Tiger Sugar FDD

The full Tiger Sugar Franchise Disclosure Document for 2025 is embedded below. This is the primary source for verifying the facts cited on this page—unit counts, executive names, fee structures, and any technology obligations. The FDD is filed with state franchise regulators and updated annually. For software vendors, the key items to review are Item 1 (executives), Item 8 (procurement), Item 11 (mandated systems), and Item 17 (renewal terms). In Tiger Sugar's case, the most actionable finding is what is absent: no tech mandates, a single named decision-maker, and a compact 63-unit system. For a ranked target list of franchise brands matched to your software category, FranCloud can help.