Service CRM & Field Service Management

Service operations ran on a legacy system: scheduling technicians, recording service visits and following a job from request to report all depended on manual hand-offs. The goal is to make that workflow reliable and automatable without stopping the business.

• Architecting the service CRM and field-service management platform.
• Backend and API improvements on the existing CodeIgniter platform.
• Service-visit reporting and technician scheduling workflows.
• Modern front ends in Next.js and TypeScript alongside the legacy system.

1. 01

   Legacy core

   CodeIgniter remains the system of record for existing service data and workflows.

2. 02

   API layer

   Services and REST endpoints are improved in place and exposed to newer front ends.

3. 03

   Modern UI

   Next.js and TypeScript interfaces for scheduling, visit reports and operations views.

• Modernise incrementally: improve the API surface of the legacy platform and build new UI beside it, rather than a risky big-bang rewrite.
• Model a service visit as a clear lifecycle so reporting and scheduling share the same source of truth.

• Working inside an existing schema and conventions while introducing cleaner boundaries.
• Keeping live service operations running while the platform evolves.

• Implemented: CRM and field-service workflows, service-visit reporting, backend/API improvements.
• Planned: further migration of legacy modules to modern services. This is roadmap, not delivered work.

Planned migration work is kept separate from what is implemented.