The vendor opportunity at Boba Arena
Boba Arena is a quick-service restaurant concept headquartered in Oregon, with a total of 5 units, all company-owned. No franchised locations appear in the 2024 Franchise Disclosure Document, and year-over-year unit growth is not disclosed. For software vendors, the immediate addressable market is extremely small—just 5 locations under direct corporate control. There is no parent company on file, and the brand appears independently owned. Average unit volume (AUV) is not reported, making it difficult to model per-location software spend. The royalty rate is set at 5.0%, but the initial franchise term length is not stated in the available data.
This is a nascent franchise system. Vendors should view Boba Arena as a potential early-stage partner rather than a volume play. If the brand begins selling franchises, the software stack will likely be defined by the HQ team before any franchisee onboarding, creating a narrow window to influence technology decisions at the corporate level.
Who controls software purchasing
All software purchasing authority sits with the two named executives in the 2024 FDD: Isaac Xie, listed as Member and Founder, and Snow Zhang, Franchise Operations Manager. With no franchisees and no multi-unit operators mapped in our corpus, there is no distributed buying center. Xie, as founder, likely holds final sign-off on any technology investment, while Zhang may manage day-to-day operational tools. Vendors should direct outreach to this pair, framing conversations around how a solution supports a small but potentially growing corporate footprint.
Mandated and current tech stack
The 2024 FDD does not capture any mandated or recommended technology systems. No POS vendor, no back-office platform, no online ordering provider, and no loyalty or marketing tech is named. This absence of a mandated stack means Boba Arena either has not standardized technology across its 5 units or has not disclosed those standards in the FDD. For a vendor, this represents a blank slate—but also a signal that the brand may not yet view technology as a franchise-wide requirement. Any pitch should emphasize ease of deployment across a small number of stores with the ability to scale if franchising accelerates.
Procurement, renewals, and timing
Item 8 of the FDD, which typically outlines procurement restrictions and designated suppliers, contains no extract in our data. Without this signal, it is unclear whether Boba Arena requires franchisees to purchase from specific vendors, maintains an approved-supplier program, or allows open purchasing. The renewal terms, drawn from Item 17, state that a franchisee in good standing may renew or extend the franchise for periods matching the renewal or extension periods of the lease or sublease. The initial term length is not disclosed. With no franchised units currently operating, there are no upcoming renewal-driven software evaluation cycles. Vendors should monitor for any franchise sales activity, as the first franchise agreements will likely trigger technology standardization discussions.
How to read the Boba Arena FDD
The 2024 Boba Arena Franchise Disclosure Document is embedded below for full reference. Key sections for software vendors include Item 1 (identifying the franchisor and its executives), Item 8 (procurement obligations), Item 11 (franchisor assistance, where mandated technology often appears), and Item 17 (renewal and termination). Because the brand is small and early-stage, much of the detail a vendor would normally use to build a business case—such as unit counts, AUV, and tech mandates—is either minimal or not disclosed. Always cross-reference the FDD with direct discovery conversations to fill gaps. For a ranked target list of franchise systems that match your software category, reach out to FranCloud.