Bill’s Car Service & Transport in Pittsburgh was considering whether a broader business-system change could reduce the manual effort involved in trip intake, dispatch, bookkeeping, and customer coordination. Triple Speed Technology evaluated Odoo as a potential ERP platform and examined how its built-in applications could support a more connected operating workflow.
Challenge
Customer details arrived by phone, text message, email, web form, or referral. Staff copied those details into a shared Google Sheet trip roster and then copied them again into Google Calendar dispatch events. Bookkeeping information was maintained separately in local Excel files.
The repeated entry created opportunities for inconsistent details, missed information, and avoidable coordination work. A broader migration also needed to be weighed carefully: replacing QuickBooks and moving operational data into a new platform would affect cost, training, adoption, data migration, and day-to-day continuity.
What we did
We consulted the current intake and dispatch workflow documented as part of previous work, stood up an evaluation instance of the Odoo environment (no cost), researched its relevant applications, and considered how the business could build its workflow inside the platform. The goal was not to recommend an ERP based on a feature list, but to understand whether Odoo could support the work Bill’s Car Service actually needed to do by actively exploring the platform.
Evaluated the Odoo ERP platform
Reviewed a broader modernization path for appointments, invoicing, fleet, employees, contacts, and related business operations.
Prototyped the appointments workflow
Stood up an example Odoo instance to understand how appointment scheduling could fit into the platform and connect with the rest of the business.
Researched available add-ons
Found and studied a prebuilt add-on, then provided advice about whether it would meaningfully improve the proposed workflow.
Compared migration tradeoffs
Considered platform scope, infrastructure, cost, migration risk, adoption, and the effort required to replace the current tools.
Instance of Odoo Enterprise running in Odoo.sh (PaaS), importing one previous tax-year of data:
- Invested Effort: 2h
- Estimated Effort to MVP: 44h
- Actual Effort: evaluated; not pursued
Example Images
The Odoo workflow was explored in an example environment, and the project report captured both the appointments view and the evaluation of a prebuilt add-on:
Takeaway
An ERP can provide a strong foundation when a business wants appointments, invoicing, fleet, employee, contact, and other operational information in one platform. It can also introduce substantial migration and adoption work. The right question is whether the platform’s broader capabilities justify the cost and disruption for the business at its current stage.
The project prioritized a quicker first step: extending the existing Google workflow while defining a focused custom intake and dispatch application for the next stage. Odoo remains a compelling long-term modernization option for Bill’s Car Service because of its broad operational capabilities.
Contact Triple Speed Technology to start a conversation about your workflow modernization, ERP, or custom application needs.
See the full Bill’s Car Service: Trip Intake & Dispatch case study→