01
Presales and postsales CRM
Customer context, opportunities, follow-ups, handovers, and service relationships now live in one continuous commercial workflow.
Case study 01 / HVAC operations
From legacy PHP
to one operating system.
How Valueye transformed an HVAC company's ageing application into a connected ERP for customers, employees, field work, accounts, and operations.
Read the transformationIndustry
HVAC and field service
Starting point
Legacy PHP system
Transformation
Connected enterprise ERP
Client
Identity confidential
01 / THE CONSTRAINT
The company had outgrown the software running it.
An older PHP-based system had become the centre of day-to-day management. As the HVAC business and its processes expanded, the application was no longer the right shape for sales, people, field operations, accounts, and management visibility.
Legacy state
Core application
PHP system
SalesPeopleFieldAccounts
More workflows kept arriving. The foundation needed to change, not simply receive another patch.
02 / THE NEW SYSTEM
One ERP. Every critical handoff.
The replacement was conceived as an enterprise operating system: modular enough for each function, connected enough for the business to move as one.
02
Human resource management
Employee information and essential HR workflows are connected to the same operating environment as the rest of the business.
03
Field workforce tracking
Teams can coordinate employees working away from the office with clearer assignments, location context, and work visibility.
04
Accounts and finance
Operational activity and financial workflows share a connected system, reducing the distance between work completed and records updated.
05
Operational workflows
Core processes move through defined states, owners, and handoffs instead of depending on disconnected tools and individual memory.
06
Management visibility
Leaders gain a more coherent view of customers, people, field activity, and business operations from the same source of truth.
03 / THE TRANSFORMATION
Not a redesign. A change in operating model.
The visible interface changed, but the deeper work was restructuring how information, responsibility, and workflows travelled through the company.
A legacy PHP application carrying too many responsibilities
A modern ERP designed around distinct but connected business domains
Operational information separated by teams and processes
Shared records that follow the work across sales, people, field, and finance
Limited visibility into work happening outside the office
Field-worker coordination and tracking inside the operating system
A system difficult to extend as the company evolved
A stronger foundation for new workflows, integrations, and scale
04 / THE OUTCOME
A foundation the operation can keep building on.
Teams now work through a purpose-built ERP instead of stretching the legacy application further.
Customer, employee, field, financial, and operational workflows can be understood as parts of the same system.
The platform creates room for the business to evolve without returning to fragmented foundations.
Modernize the operation