The vendor opportunity at Wiki-Licious
Wiki-Licious is a quick-service restaurant brand headquartered in Alaska with 49 total units—48 franchised and 1 company-owned—as disclosed in its 2025 Franchise Disclosure Document. The system grew unit count by 54.8% year-over-year, adding locations primarily in Arizona (11 units), Utah (10), Texas (8), Idaho (5), and Alaska (3). All 53 mapped operators are single-unit franchisees; no multi-unit operators exist in the system. For software vendors, the addressable market is 49 locations, but the growth trajectory and geographic clustering suggest a scaling brand where early technology partnerships could expand with the system.
Average unit volume is not disclosed in the FDD. The royalty rate is 18.0%, and the initial franchise term is just 2 years—shorter than industry norms—with renewal options for 1, 2, or 3 additional years. This compressed term structure means franchisees face frequent re-commitment points, which can create recurring opportunities for technology evaluation.
Who controls software purchasing
Software purchasing authority sits squarely at the franchisor level. The FDD mandates that franchisees use systems designated or created by the franchisor for POS, payment processing, online ordering, and accounting. The executive team listed in Item 1 includes Amy Johnson (Founder and CEO), Mary Cannon (COO), and Stephanie Prestwich (President of Franchise Operations). These three individuals represent the likely buying center for any software vendor seeking to become a designated or approved supplier. There is no parent company on file; Wiki-Licious appears to be independently owned.
Mandated and current tech stack
The FDD explicitly mandates four technology categories. First, franchisees must use an online ordering program that the franchisor either creates or adopts. Second, they must use the franchisor’s designed merchant services or payment processor. Third, a POS system designated by the franchisor is required. Fourth, franchisees must use specific accounting software. All of these fall under the Wiki-Licious® brand umbrella per the disclosure. The FDD does not name third-party vendors for these systems, indicating the franchisor may be building or white-labeling proprietary solutions.
Procurement, renewals, and timing
Item 8 of the FDD—which typically discloses designated suppliers, approved suppliers, and any revenue streams the franchisor receives from procurement—was not extracted in the available data. Without that extract, it is unknown whether the franchisor derives rebates or other income from mandated technology vendors, or whether there is an approved-supplier process for non-mandated categories.
Renewal conditions, drawn from Item 17, require franchisees in good standing to modernize their business to then-current standards, pay a successor franchise fee, and sign the then-current successor agreement—which may have materially different terms. Franchisees must provide renewal notice between 3 and 6 months before expiration. With an initial term of only 2 years and renewal terms of 1, 2, or 3 years, the system has frequent, predictable decision points where technology standards could be updated and rolled out across the network.
How to read the Wiki-Licious FDD
The full 2025 Wiki-Licious FDD is embedded below for your review. It contains the franchisor’s disclosures on fees, territory, obligations, and the technology mandates summarized here. Key sections for software vendors include Item 11 (franchisor’s assistance, advertising, computer systems, and training) for the mandated tech stack, Item 8 for procurement restrictions, and Item 17 for renewal and modification conditions. The document is filed with state franchise regulators and reflects the brand’s current operating requirements as of 2025. For a ranked target list of franchise systems matched to your software category, FranCloud can help you prioritize outreach.