Jan-Pro of Washington, DC

The vendor opportunity at Jan-Pro of Washington, DC

Jan-Pro of Washington, DC operates a network of 231 franchised units, all within the home services segment. The brand does not report an Average Unit Volume, but its 10% royalty rate and 12.68% year-over-year unit growth signal a system in active expansion. For software vendors, this growth creates a recurring need for scalable operational tools. The franchise is headquartered in Virginia and appears independently owned, with no parent company on file. The operator footprint is lean: only 2 mapped operators are recorded, none of which are multi-unit owners, with units located in California and Indiana. This structure suggests centralized control over technology decisions, making the HQ the primary target for a software pitch.

Who controls software purchasing

The buying center at Jan-Pro of Washington, DC is clearly defined in the FDD. Chief Executive Officer and Director Randolph Ivey sits at the top of the organization. Brand President Gary Bauer is the next key executive, likely overseeing brand standards that include technology mandates. Vice President of Operations Paul Scales and Vice President of Training, Technical Development and Sourcing Neeraj Gupta are the operational and technical leads. For a vendor selling a training platform, Gupta is the most direct entry point. For a field operations or CRM tool, Scales and Senior Director of Field Operations David Meyer are the relevant stakeholders. The absence of a named CIO or CTO in the FDD means the evaluation process likely runs through these operational leaders rather than a dedicated IT department.

Mandated and current tech stack

The 2025 FDD explicitly mandates JanHub as the core technology platform for the franchise system. No other specific software vendors are named as mandatory or recommended in the disclosure. This presents both a challenge and an opportunity for outside vendors. Any new software must either integrate with JanHub or demonstrate a clear gap in functionality that JanHub does not address. The FDD does not detail the full scope of JanHub's capabilities, so vendors should be prepared to ask detailed discovery questions about whether it handles scheduling, billing, customer management, or training. The lack of a named POS or accounting system mandate suggests these areas may be open for vendor competition.

Procurement, renewals, and timing

The FDD provides no Item 8 procurement signal, meaning the franchisor's policies on designated versus approved suppliers are not publicly disclosed. This lack of transparency means a vendor's first call should aim to uncover whether the franchise imposes purchasing restrictions or preferred vendor lists. The renewal terms offer a clearer timing signal. Franchise agreements run for 5 years, and franchisees must notify the franchisor of their intent to renew between 6 and 12 months before expiration. This creates a natural rhythm where franchisees may evaluate their tech stack in the year leading up to renewal. Additionally, the franchisor can require franchisees to sign the then-current form of agreement upon renewal, which may contain materially different terms, including new technology mandates. A vendor who builds a relationship with HQ before a wave of renewals could find their product written into the updated agreement.

How to read the Jan-Pro of Washington, DC FDD

The full 2025 Franchise Disclosure Document is embedded below. For software vendors, the critical sections are Item 11, which details the franchisor's obligations and the mandated JanHub system, and Item 17, which outlines the renewal and transfer conditions that can trigger technology reviews. Item 1 names the executives who control purchasing. Because no Item 8 procurement restrictions are disclosed, vendors should use the FDD to prepare specific questions about supplier approval processes before engaging the leadership team. For a ranked target list of similar franchise systems ready for a software pitch, FranCloud can provide the data.