Built Custom Burgers

The vendor opportunity at Built Custom Burgers

Built Custom Burgers is a quick-service restaurant concept headquartered in Arizona. According to its 2026 Franchise Disclosure Document, the system consists of 2 franchised units. The number of company-owned locations is not disclosed. Year-over-year unit growth stands at -33.3%, indicating recent contraction. For software vendors, the addressable market is small—just 2 locations—but the centralized purchasing structure means a single HQ conversation can cover the entire system.

Average unit volume is not reported in the FDD, so vendors cannot benchmark per-store software spend against AUV. The royalty rate is 5.0% of gross sales, and the initial franchise term is 10 years. These economics suggest a lean operating model where every technology dollar must justify itself against thin margins.

Who controls software purchasing

The 2026 FDD lists five executives in Item 1: Eric Lefebvre (Chief Executive Officer), Renee St-Onge (Chief Financial Officer), Al Hank (Chief Operating Officer), Jeff Smit (Chief Operating Officer of Kahala Brands), and Jenny Moody (Chief Legal Officer). No dedicated technology leadership—such as a CIO, CTO, or VP of IT—is named. The presence of a Kahala Brands COO in the leadership roster hints at shared services or management ties, though no parent company is on file and the brand appears independently owned.

For a vendor, the likely buying center starts with the CEO and COO. The CFO will weigh in on budget, and the Chief Legal Officer will review contracts. Because the system is small, expect direct involvement from the C-suite on any software decision. There is no operator footprint mapped in our corpus, meaning no multi-unit franchisee influence to navigate.

Mandated and current tech stack

The only mandated technology disclosed in the 2026 FDD is Olo by Olo Inc., which covers digital ordering. No POS provider, back-of-house system, payroll vendor, or loyalty platform is named as mandated or recommended. This leaves open the possibility that franchisees select their own systems for functions outside of digital ordering, though the centralized HQ structure makes it likely that any new vendor would need corporate approval.

Vendors selling into this account should be prepared to integrate with Olo or complement it. A POS that works alongside Olo, a labor scheduling tool, or an inventory management platform could all be relevant—but none are currently locked in by mandate.

Procurement, renewals, and timing

Item 8 of the FDD contains no procurement extract, so the brand’s supplier designation model—whether designated, approved, or open—is not publicly known. This absence itself is a signal: the franchisor has not codified procurement rules in the disclosure, which may mean purchasing processes are informal or handled on a case-by-case basis.

Item 17 outlines renewal conditions. Franchisees not in default and satisfying certain conditions may renew for a single 5-year term, with no further right to renew afterward. The initial term is 10 years. With only 2 units and negative recent growth, the near-term software opportunity is less about new openings and more about replacing or supplementing existing systems at current locations. Contract windows are likely tied to the franchise agreement cycle, but with such a small base, vendors should treat this as a relationship-driven sale rather than a volume play.

How to read the Built Custom Burgers FDD

The 2026 FDD is embedded below. Key sections for software vendors: Item 1 lists the executives who will evaluate your product. Item 11 discloses the Olo mandate and any other franchisor obligations around technology. Item 8, though silent here, is where you would normally find procurement rules. Item 17 defines the renewal clock that shapes when franchisees might revisit their tech stack. Because the system has no mapped operators and no parent company on file, the FDD is the single best source of truth on how this brand buys.

For a ranked target list of franchise systems that match your software, including decision-maker contact paths and tech stack gaps, FranCloud can help.