The vendor opportunity at Airport & College Services
Airport & College Services is a quick-service restaurant concept with 23 total units, 14 of which are franchised and 9 company-owned. The system posted an average unit volume of $1,434,295 in its 2025 FDD, a figure that places individual locations well above many QSR peers. For software vendors, that AUV signals operators with meaningful revenue to invest in operational tools — but the addressable unit count is small and contracting, with year-over-year unit growth at negative 6.667%.
This is not a volume play. The opportunity here is a high-revenue-per-location target where a single deployment can yield a solid account. Vendors should weigh the 23-unit footprint against their own customer-acquisition economics before committing outbound resources.
Who controls software purchasing
The 2025 FDD does not name HQ executives, and no centralized technology decision-maker is identified in the available data. In systems this size, purchasing authority often sits with the franchisor for company-owned units and may be fragmented across franchisees for the 14 franchised locations. Without a published mandate, the buying center is unknown. A vendor’s first call should establish whether the franchisor controls stack decisions or merely makes recommendations — and who signs the contract in either case.
Mandated and current tech stack
No mandated or recommended technology is captured in the 2025 FDD. This absence is itself a signal: the franchisor has not publicly locked the system into a specific POS, back-office, or operational platform. That can mean either a greenfield opportunity or a system where franchisees already use a patchwork of legacy tools. Vendors should come prepared to discuss integration flexibility and migration paths, because any incumbent tech is undocumented in the disclosure.
Procurement, renewals, and timing
Item 8 of the FDD, which typically outlines designated or approved suppliers, contains no extractable signal in the 2025 filing. The procurement model — whether centralized, approved-list, or fully open — is not disclosed. Similarly, the initial franchise term and Item 17 renewal conditions are absent from the available data. Without term length or renewal windows, vendors cannot map contract cycles from the FDD alone. Timing outreach requires direct intelligence: ask about upcoming renewals, current vendor satisfaction, and any planned stack overhauls during discovery.
How to read the Airport & College Services FDD
The 2025 FDD is embedded below. Focus on Item 11 (franchisor’s obligations) for any technology or operational support requirements that may not have been captured in the summary data. Review Item 8 for supplier relationships that could affect software procurement, even if no signal was extracted here. The filing is lodged with state franchise regulators and represents the most current public disclosure for the brand. Reading it directly will help you confirm whether any tech mandates exist and identify the operational pain points that your software can address.
For a ranked target list of franchise systems matched to your software category, FranCloud can help you prioritize outreach based on unit counts, AUV, tech mandates, and procurement signals.