About BP Tech Support

Two engineers. Forty years. One vertical.

BP Tech Support was founded by two senior IT engineers who spent their careers inside and around heavy-duty truck dealerships. We started this company because we kept seeing the same pattern: dealers paying generalist MSPs who didn't know the difference between a parts pull and a payroll batch — and dealers suffering for it.

PR

Pramoda Ravi

Co-Founder · Principal Engineer

Two decades of infrastructure engineering, dealership systems integration, and security architecture. Pramoda owns the network, server, and cloud practice — from the Layer-1 cabling in your parts warehouse to the identity policies in your Microsoft 365 tenant.

RW

Robert "Bobby" Whiteley

Co-Founder · Principal Engineer

Twenty years deep in dealership operations and OEM tooling. Bobby leads the DMS and application practice — CDK, Karmak, Procede, Paccar diagnostics, Decisiv workflows. If your service writers are getting kicked out of an estimate, Bobby has fixed that exact problem before.

Why we exist

Generic IT can't run a dealership

We speak both languages

We can talk to your service manager about why a tech can't push an op-code, and ten minutes later talk to your CFO about ASC 842 implications inside the DMS. Most MSPs can do one of those. Some can't do either.

  • OEM diagnostic tooling, license management, and provisioning
  • Parts catalog, EPC, and pricing system integrations
  • Service writer workflows and warranty submission flows
  • F&I systems, deal jackets, e-contracting

We build things to stay up

Your dealership doesn't get to slow down because IT is having a bad day. We design redundant networks, document everything, and rehearse our recovery playbooks. When something fails, we already know what to do.

  • Dual-WAN failover with policy-based routing
  • Backup strategies with off-site immutability and tested restores
  • Documented runbooks per dealership, per system
  • 15-minute SLA for production-down events on managed plans

We don't disappear after onboarding

You get the same two engineers who scoped the work. No tier-1 call center reading from a script, no "we'll escalate" dead-ends. Just direct access to people who know your environment.

  • Direct line to senior engineers on the customer portal
  • Quarterly business reviews and roadmap planning
  • Plain-English reporting your GM will actually read
  • Vendor coordination so you don't have to triage three support queues