An industrial plant runs best when its equipment is serviced on a regular schedule, and a company website is no different. Years after launch, the content has grown, the business has added new services, and the way people look for a supplier has changed. At some point, servicing the old site is no longer enough and the better investment is a new one.
In short, JCHEM Engineering, an engineering group and a client since the days of our earlier content management system, had its website rebuilt on NagaCloud in 2025. This is what the rebuild involved, and what we learned from it that applies to any engineering firm planning the same step.
A Long-Standing Client
We first built JCHEM's website on our earlier content management system, and the group stayed with us as its business grew. Over the years the site came to include more services, more products and more news than it was first designed for.
We believe a website should grow with the business behind it. When the structure of a site no longer matches the way a company presents itself, a rebuild on a current platform gives the business a foundation for its next stage, instead of more changes to a structure that no longer fits.
What the New Site Includes
The rebuilt site is organised around what a plant manager or a procurement team wants to find first:
- A page for each service. Each of the group's maintenance services, from chemical descaling to industrial maintenance coating, has its own page.
- Products. The group's products are presented in their own section, apart from the services.
- Events and news. Upcoming events and the latest updates from the group are listed on the home page and in their own sections.
- Gallery and FAQs. Photos of the group's work and answers to common questions, each with its own page.
- Contact and enquiries. A contact page so a prospective client can reach the right team directly.
Built on NagaCloud
The new site is built on NagaCloud, the platform we develop and maintain ourselves. Its pages are put together with the NagaCloud site builder, and the content that changes often, such as events, news, the gallery and the FAQs, is managed from the NagaCloud console. The site was delivered with Google Analytics connected, so the group can see how visitors find and use it.
Because the site runs on our own platform, improvements we make to NagaCloud can reach it over time without another rebuild. You can read how the platform came about in building our own platform, from ASAS to NagaCloud.
What We Learned
- A rebuild starts from what the old site already holds. The services, products and history a company has published over the years are an asset, and the new structure should be designed around them.
- Each service deserves its own page. A buyer searching for one specific service should land on the answer directly, without reading through everything else the company does.
- Content that changes often belongs in its own section. Events, news and photos kept in their own sections are easy to update, which keeps the site current between projects.
How We Rebuild Websites at Valse
Every website project at Valse starts with the business, following our RIDE framework: Review, Identify, Digitalise and Elevate. For a rebuild, the review covers what the current site already does well, so nothing of value is lost in the move. You can read more on our website design and development page.
Thinking about rebuilding your company website? Take the free RIDE Digital Scorecard, or talk to us today.