A service team could reach a customer and discover a missing belt, fitting or seal. Costel built a focused pump-specific checklist that put the required parts and a physical loading check in the technician’s hands before departure.
Technicians loaded vehicles from memory. When a small part was missing, the consequences extended beyond the return journey: delayed repairs, a disrupted schedule and a customer still waiting for the service to finish.
The branch needed a dependable list for the selected pump and a way to confirm the items were physically in the vehicle. A broader inventory or ERP replacement was unnecessary for that specific problem.
Costel built a small application that generated a list for the selected pump, including a product photo, parts, materials and accessories. Every item had an empty checkbox.
The list could be printed or emailed. During loading, the technician checked the items with a pen. The application supplied the model-specific information while the technician performed the physical verification.
Project materials showing the workflows and interfaces described in this case.
The service process gained a consistent check between choosing the parts and leaving for the customer. The project history includes a 2019 launch and a later framework and PHP update in 2026 that retained the familiar loading workflow.
The right intervention can be a small tool. The business value comes from where the check sits in the process, not from the number of features. A review should distinguish this kind of bounded workflow improvement from a larger set of systems requiring ongoing technology ownership.
Project contribution: Costel. The scope described above identifies the work behind this case.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.
