Skip to main content
← Back to search
KI

Operational Systems Manager

Kelso Industries

Salary undisclosed

Draper, UTFull-timeOn-siteIntermediate

Need a reasonable accommodation to apply or interview? Contact us.

JobMinglr uses automated technology to recommend jobs based on profile information and job preferences. Match Score does not determine eligibility for a position, prevent a user from viewing or applying to a job, or make hiring decisions on behalf of an employer.

Description

Together We Build – Partnership, Innovation, Excellence, and Safety

At Kelso Industries, 5,000+ employees across 40+ companies work together to deliver exceptional HVAC, mechanical, plumbing, refrigeration, and electrical solutions nationwide. Join us to grow your career, make an impact, and be part of a team where innovation, excellence, and safety come first.

Recruiter Notice: We respectfully ask external recruiters and staffing agencies not to submit candidates. We only accept direct applications.

 

The Operational Systems Manager owns the platforms that run Kelso's revenue and field operations: Salesforce Sales (CRM) and Salesforce Field Service Management (FSM), from implementation through adoption and continuous improvement. This is both a delivery role and a platform administration role: the person is accountable for implementing FSM, getting CRM into the hands of operating companies that do not yet have it, administering the platform day to day, and making both platforms measurably better for the people using them.

It is also a player-coach role: the person performs senior Salesforce administrator work directly, manages a junior administrator, and over time extends into the wider operational systems portfolio.

What the Role Owns

  • Salesforce FSM implementation: Delivery lead from design and configuration through testing, training, cutover, and hypercare, starting with the pilot operating company and each wave after.

  • CRM rollout: Brings the remaining operating companies onto Salesforce Sales, including newly acquired ones, at a pace that outruns acquisition. Builds a repeatable deployment playbook so each wave costs less than the last.

  • Senior Salesforce administration: Hands-on ownership of Sales Cloud, Service Cloud, and Field Service: users and permissions, flows, validation rules, release management, license management, recurring data audits, and integration health across MuleSoft and NetSuite.

  • Adoption: Drives real usage rather than assuming it follows go-live. Partners directly with OpCo operations, service, and sales leaders; owns role-based training and change management; runs the Salesforce Champion forum; and coaches OpCo leaders on pipeline and work order discipline. Runs recurring data audits across the operating companies: stale pipeline, duplicate records, missing required fields, unworked opportunities, and takes the findings back to OpCo leadership as a coaching conversation rather than a report. Measures adoption, license utilization, data completeness, mobile usage in the field, cycle times, and intervenes where usage is lagging.

  • Standardization: Defines and holds one standard process and configuration across the operating companies. Maps current state, redesigns toward the Kelso standard before configuring to it, and treats OpCo variation as a documented, approved exception rather than a silent fork.

  • Continuous improvement: Owns the enhancement backlog end-to-end (intake, triage, prioritization, build, test, release) on a predictable release cadence. Turns Champion forum feedback, audit findings, and field observation into platform improvements, and applies Eliminate–Simplify–Automate so redundant steps and duplicate data entry get removed rather than automated in place.

  • Governance and vendors: Operational lead to the Salesforce Operational Steering Committee; manages implementation partners against their statements of work and reports honest status into the IT portfolio update.

  • Team: One direct report to start, a Junior Salesforce Administrator/Project Manager.

What Success Looks Like

  • FSM stable in production at the pilot OpCo, configuration documented, next wave underway.
  • Additional OpCos live on CRM, with deployment time falling wave over wave.
  • Measured adoption at live OpCos against defined thresholds, not just deployment counts.
  • Exceptions to the enterprise standard documented, approved, and declining over time.
  • A predictable enhancement release cadence with a visibly shrinking backlog of workarounds.
  • A data quality baseline established and audited on a regular cycle.
  • Onboarding pace for newly acquired OpCos ahead of the acquisition rate.

Requirements

  • 5+ years in business systems implementation or administration, including 3+ years hands-on with Salesforce.
  • Hands-on Service Cloud administration, not Sales Cloud alone: cases, queues, escalation rules, entitlements, console, omni-channel routing. Field Service is built on Service Cloud; a Sales Cloud-only background does not qualify.
  • Senior admin capability demonstrated personally: configures the platform, rather than directing a consultant to do it.
  • At least one full-lifecycle Salesforce implementation owned end-to-end.
  • A demonstrated track record driving adoption and standardization across multiple sites or business units: able to show what usage looked like before and after, not just that a system went live.
  • Field service, work order, or dispatch experience.
  • Data migration and data quality remediation experience.
  • Supervisory experience, or clear readiness for a first direct report.
  • Credibility with field operations leaders; willingness to travel to OpCo sites.
  • Salesforce Administrator certification, or attainment within six months of hire.

Preferred Qualifications

  • Salesforce Field Service implementation experience; Service Cloud or Field Service Consultant certification.
  • MEP, trades, construction, or commercial field service background.
  • Multi-site or multi-entity rollout experience in an acquisitive environment.
  • NetSuite or comparable ERP exposure; familiarity with MuleSoft and Domo.
  • Process improvement and organizational change management training.
  • EHS or field productivity platform experience.

 Why Join Kelso Industries? 

Join us and be part of a team dedicated to creating efficient, sustainable, and high-performance environments that make a lasting impact across the industrial, commercial, and institutional sectors.  

Here you will experience:  

Growth Opportunities: Develop new skills, take on exciting challenges, and advance your career in meaningful ways.  

Company Culture: You’ll thrive in an environment that supports your growth, values your contributions, and makes work fulfilling and enjoyable. 

Impact: Your work directly contributes to meaningful outcomes, allowing you to see the difference you make and feel a sense of purpose every day. 

Competitive Compensation & Benefits: You’ll be rewarded fairly for your contributions while enjoying perks that enhance your financial security, health, and overall well-being. 

 

Kelso Industries celebrates diversity and is committed to creating an inclusive environment for all employees. We do not discriminate in any aspect of employment based on race, color, religion, national origin, ancestry, gender, sexual orientation, gender identity and/or expression, age, veteran status, disability, or any other characteristic protected by federal, state, or local employment discrimination laws where Kelso does business 

About this role

Kelso Industries is seeking an Operational Systems Manager to lead the design, deployment, and continuous improvement of Salesforce across its 40+ operating companies. You'll own both the Field Service Management implementation—starting with a pilot rollout and scaling through subsequent waves—and the CRM expansion to operating companies not yet on the platform. This combines hands-on senior Salesforce administration with strategic platform governance: you'll configure flows, manage users and permissions, run data audits, oversee integrations with NetSuite and MuleSoft, and build a repeatable deployment playbook that makes each rollout faster and cheaper than the last.

The role is as much about adoption and change as it is about technical configuration. You'll partner directly with operations, service, and sales leaders across the business to drive real usage rather than assume it follows go-live. You'll run a Salesforce Champion forum, coach operating company leaders on pipeline and work order discipline, measure adoption against defined thresholds, and turn field observations and audit findings into platform improvements. Standardization across the operating companies is core to the work: you'll document current state, redesign toward enterprise standards, and treat exceptions as approved deviations rather than silent forks.

You'll manage a junior Salesforce administrator and report to the Operational Steering Committee. The role requires 5+ years in business systems implementation with at least 3 years hands-on Salesforce experience, including demonstrated Service Cloud administration (not Sales Cloud alone). You need at least one full-lifecycle implementation under your belt, a track record of driving adoption across multiple sites, field service or work order experience, and credibility with field operations leaders. Salesforce Administrator certification is required or must be attained within six months. This is an in-office role based in Draper, Utah.

How this employer is doing

solid

  • Expanding
  • Recently Raised Funding

This role's local market on JobMinglr

Pay for this role

The employer didn't post a pay range for this role. That usually means pay is set in negotiation, which favors whoever arrives with numbers. Check ranges on comparable Operational Systems Manager postings in Draper, and analyze any offer before you accept it.

How JobMinglr reads this job

Every listing here is scored against your profile before you apply: skills overlap, experience level, location and work arrangement, each weighted and explained. You see the score and the reasons, not just a list. How the matching works.