The vendor opportunity at Marathon Petroleum
Marathon Petroleum operates in the automotive services segment, headquartered in Ohio. For software vendors, the opportunity is defined more by what is unknown than what is confirmed. The 2026 Franchise Disclosure Document does not report total units, franchised versus company-owned splits, or year-over-year unit growth. Average unit volume (AUV) is also absent. This lack of disclosed scale makes it difficult to size the addressable market with precision. Vendors should approach Marathon Petroleum as a potential account where the tech stack is partially visible—Jobber* is named—but the full operational footprint and decision-making structure remain opaque. The absence of unit data means any total addressable market estimate must be treated as speculative until further intelligence is gathered.
Who controls software purchasing
The FDD does not identify a centralized software buyer, a technology committee, or a named executive responsible for procurement. No HQ executive contacts are on file in the FranCloud database. In franchise systems where the franchisor does not disclose a clear purchasing hierarchy, authority can rest with a corporate IT function, a multi-unit operator group, or individual franchisees. For Marathon Petroleum, the decision-maker level is classified as Unknown. Vendors should prepare for a potentially fragmented sales process, where influencing both corporate and location-level stakeholders may be necessary. Without Item 8 procurement language, it is also unclear whether the franchisor exerts formal control over supplier selection or leaves it to the franchisee.
Mandated and current tech stack
The only technology signal in the 2026 FDD is Jobber, a platform commonly used for scheduling, invoicing, and customer management in field-service and automotive businesses. No additional POS, inventory management, or back-office systems are disclosed as mandated or recommended. This narrow window suggests that Jobber may serve as the operational backbone, but it does not rule out other tools in use at the unit level. Vendors offering complementary or replacement solutions should investigate whether Jobber* integrations, data migration paths, or co-selling opportunities exist. The absence of a broader mandated stack means the competitive landscape is largely undefined, which can be both a risk and an opening for early movers.
Procurement, renewals, and timing
Item 8 of the FDD, which typically outlines procurement restrictions, designated suppliers, and purchasing cooperatives, was not available in the extract. Without this, the procurement model remains unclassified—it could range from a tightly controlled designated-supplier program to a fully open market. Similarly, Item 17 renewal terms and the initial franchise term length are not disclosed. This removes the usual signals vendors rely on to time their outreach around renewal-driven technology evaluations. In the absence of contractual cycle data, vendors should consider a continuous engagement approach, building relationships and demonstrating value without relying on a predictable RFP window.
How to read the Marathon Petroleum FDD
The 2026 FDD is the primary source for verifying the claims above. It is filed with state franchise regulators and embedded below for direct review. When reading, focus on Item 11 for the franchisor’s obligations around technology and support, Item 8 for any purchasing restrictions, and Item 17 for renewal and transfer terms that might trigger software evaluations. Item 20 can provide unit count and turnover data if populated, though in this case those figures appear absent. Cross-reference any Jobber* mention with Item 11 language to determine whether it is a true mandate or a recommendation. For vendors building a ranked target list, FranCloud can help prioritize systems where tech mandates and decision-maker visibility align with your product.