What we build
Operations systems
Scheduling, dispatch and workload planning, technician workflow, customer calls and texts, and the reporting owners run the business on, built around how each operation actually works.
Data integrations
Connections to the providers a repair business relies on: vehicle identification, labor and maintenance data, parts catalogs and ordering, accounting and telephony.
Hosting and support
Each client's system runs on its own dedicated infrastructure, backed up nightly and supported directly by the people who built it.
The software
Shown with sample data.
How we work
- One client, one system.Each client's data lives in its own system. It is never pooled with another client's and never sold.
- Least access.Connections to outside systems are read-only by default. A write is added only when the client decides the work needs it.
- Licensed data stays licensed.Provider data is used only as its license allows, and integration work is built and tested on vendor-issued development accounts or test data, never a client's live accounts.
- Secured.Encrypted connections, single sign-on with per-person permissions, credentials kept out of source code, and nightly backups.
Team
Andrew Bishop owns and runs two auto repair shops in Greater Cincinnati. Bishop Software Group grew out of them: the software those shops run on every day, built because nothing off the shelf ran a shop the way it actually works. The people who use it shape it.
For data and parts providers
We integrate with vehicle data, parts and service history providers on behalf of our clients. If you offer an API or a partner program, we would like to hear from you.