Product Manager

About the role

Vehlo was founded in 2019 to become the industry’s favorite provider of repair shop technology. Today, over 30,000 customers generate more than 50 million annual repair orders using Vehlo’s founder-led products that power the entire service lane experience — communication, workflow automation, touchless payments, valet pickup, and more. The company’s purpose is customer success, and every team member (“Veep”) moves the ball forward daily for customers or each other.

This is a dedicated product manager role for the Shop‑Ware product. You will be Shop‑Ware’s only product manager, reporting to the Principal Product Manager for the Shop Management Suite and working daily with Shop‑Ware’s engineering team. You will also collaborate closely with onboarding, support, customer success, sales, and marketing.

Responsibilities

• Roadmap ownership, end to end. Decide what earns a place in the product and what doesn’t, and explain those decisions to a shop owner, a seller, and an engineer in the same week. Keep the roadmap current and honest; make trade‑offs explicit when requests outnumber capacity.
• Workflow and information architecture. Understand how a repair order moves through a shop — from estimate and authorization through parts, labor, inspection, invoice, and payment. Restructure a mature workflow product so it gets simpler as it grows.
• Multi‑location capability as a layer, not a fork. Own the next stages of MSO capability: permissions and role inheritance, cross‑store data and inventory, corporate‑level views, and migrating existing single‑store customers to a multi‑store model without disruption. Plan for migration and adoption risk up front.
• Pricing intelligence. Own the AI‑assisted parts pricing matrix that helps shops price for profitability. Make it trustworthy: define activation, surface the value delivered, and enable owners to audit overrides made at the counter.
• Integrations as product. Parts catalogs and ordering, payments, vehicle data, and API partners are core to Shop‑Ware. Own the in‑product experience of these integrations and the trade‑offs between them, in close partnership with the PM who owns the API program and analytics suite.
• Customer discovery. Spend real time every month with service advisors, technicians, and owners — mostly over video and screen share — watching how they actually work. Build job maps from observations and bring back insights that change decisions. Engage with the customer advisory board and Shop‑Ware customer office hours.
• Product practice. Run backlog refinement, release readiness, stakeholder roadmap reviews, and documentation and enablement for the teams who sell and support Shop‑Ware. Write clear specs and acceptance criteria so engineering builds the right thing without daily rescue. Ceremonies are part of the job, not the job; most time goes to discovery and strategy.

Requirements

• 5+ years in product management with full ownership of a core product. You were the accountable PM for a whole product that customers run their business on (e.g., scheduling, point of sale, job management, field service) and you shipped it. You know the difference between a feature customers try and a workflow they depend on.
• Multi‑location experience. You have designed or shipped hierarchy, permissions, role inheritance, or cross‑location capability, and you have moved existing single‑location customers onto it without losing them. This carries the most weight after full product ownership.
• A domain learned from customers. Automotive experience helps but isn’t required. Critical is insight into the small‑business owner‑operator mindset and willingness to put in the work to learn a new space quickly. Evidence that you became the most knowledgeable person in the room about how a customer’s business runs — by spending time with customers and watching them work, not just reading about it.
• Outcomes, not output. You can name a metric you moved (adoption, retention, expansion, support volume, time to value) and a feature you sunset with an explanation of why.
• Technical fluency. You don’t write production code, but you can read a schema, reason about data flows between systems, work through an integration contract with engineers, and spot when an estimate or design is wrong.
• Self‑direction. You set direction, keep a team pointed at it, and push back on the direction you were handed when it’s wrong — without needing week‑to‑week steering.
• Hands‑on and AI‑forward. You prototype, pull your own data, and use AI tools to write, research, and analyze faster. Experience shipping AI‑assisted features to customers and handling cases where the model was wrong in front of them is a strong plus.

Preferred qualifications

• Experience shipping AI‑driven product surfaces to customers, including handling accuracy, evaluation, user trust, and being wrong in front of a customer. Extra points for leading consumption‑based pricing and COGS management.
• Background in vertical or SMB SaaS; dealer service, fleet, or field‑service software; parts catalog, pricing, or procurement workflows; embedded payments; partner and integration ecosystems; and lean engineering teams that include contract developers.