The vendor opportunity at PBC
PBC operates 1,244 franchised units across the United States, with no company-owned locations disclosed in the 2026 FDD. The brand falls within the retail non-food segment and is headquartered in Texas. Year-over-year unit growth stands at 7.612%, signaling a steadily expanding footprint. For software vendors, the entire system represents an addressable market of 1,244 locations, with operators concentrated in Texas (13), Florida (10), Washington (3), Utah (3), and New York (2). The franchisee base consists entirely of single-unit operators—48 mapped operators across approximately 48 located units—meaning no multi-unit owners control blocks of locations. This fragmented ownership structure means a sale into the franchisor does not guarantee adoption across the system, but it also means no single franchisee gatekeeper can block a vendor from the broader network.
Who controls software purchasing
The 2026 FDD names Rutledge Scarborough as Vice President & IT Director, making him the most directly relevant executive for technology vendors. Other HQ leaders include Brandon Gale (President) and Steven S. Weigman (Chief Financial Officer & Business Development). In a system with no mandated technology stack, the IT Director likely evaluates and recommends solutions, while the President and CFO hold budgetary authority. Vendors should prepare to engage Scarborough first for technical fit, then align with Weigman and Gale on financial and strategic approval. The absence of a parent company suggests decision-making remains internal and potentially more agile than in private-equity-backed chains.
Mandated and current tech stack
The 2026 FDD does not capture any mandated or recommended technology systems or vendors. This is a critical data point: PBC either does not require franchisees to use specific software, or it has not disclosed such requirements in its franchise disclosure document. For vendors, this means the system is likely a greenfield opportunity. Without an incumbent POS, ERP, or operational platform named in the FDD, there is no publicly documented competitive lock-in. Sales conversations should start by confirming whether any de facto standards exist at the unit level, but the formal disclosure suggests an open environment.
Procurement, renewals, and timing
Item 8 of the FDD, which typically outlines procurement restrictions and designated suppliers, was not extracted in the available data. This means the procurement model—whether franchisees must buy from designated suppliers, must use approved suppliers, or may purchase freely—is not disclosed. Vendors should clarify this directly in initial discussions. The franchise agreement runs for an initial term of 3 years. Renewal is permitted if the franchisee is in good standing and meets all conditions, but the franchisor requires signing the then-current Franchise Agreement, which may contain materially different terms. This renewal cycle creates natural windows for technology evaluation and adoption, as franchisees re-commit under potentially updated operational requirements.
How to read the PBC FDD
The full 2026 PBC Franchise Disclosure Document is embedded below. Key sections for software vendors include Item 1 (identifying executives like Rutledge Scarborough), Item 8 (procurement restrictions, though not extracted here), Item 11 (mandated technology, which shows no listed systems), and Item 17 (renewal conditions and term length). The FDD is filed with state franchise regulators and provides the legally required disclosures franchisors must give prospective franchisees. Reading it gives vendors the same factual baseline franchisees receive, revealing exactly what the franchisor commits to—and what it leaves open. For a ranked target list of franchise systems aligned to your software category, FranCloud can help.