Ackcio
Ackcio's wireless mesh sensors watch tunnels, bridges, mines and rail lines around the world, but a small website change took two to three weeks through an outsourced Webflow setup. We rebuilt the site on WordPress and handed the keys back.
A WordPress rebuild that replaced a locked Webflow site with a platform Ackcio’s team updates themselves, still carrying the business as it has grown into North America and Europe.
What we were solving
Ackcio is a Singapore deep-tech company that makes wireless mesh monitoring systems for geotechnical and structural sensors. Its nodes and gateways sit on MRT stations in Singapore, the Tuen Mun-Chek Lap Kok link in Hong Kong, bridges in Indonesia and gold processing facilities in Western Australia. Fresh off its Series A round, the company was selling worldwide through a growing distributor network.
The website wasn’t keeping up. It ran on Webflow, managed by a remote team in Vietnam, and Ackcio’s own staff had no access to the CMS. Even a small text change took two to three weeks to go live. Case studies and press releases sat on a separate HubSpot blog subdomain; there were no clear calls to action, and nothing helped a monitoring engineer work out whether Ackcio’s kit fitted their instruments.
Success meant a site the marketing team could update the day they wrote something, and a structure that spoke to the specialists who specify this equipment.
How we tackled it
Start with the business, not the homepage
The engagement opened with a business strategy review, not wireframes. Ackcio sells to geotechnical engineers, structural monitoring specialists and mine surveyors who search by instrument name, so keyword research ran early, with Ackcio’s own engineers marking the must-have terms: vibrating wire piezometers, in-place inclinometers, tailings dam monitoring. That research shaped the sitemap before it shaped any copy. The dominant competitor ranked for tens of thousands of keywords, so the plan targeted the long-tail terms where a focused deep-tech company could win.
A platform the team runs themselves
We rebuilt the site on WordPress with Beaver Builder, hosted on WP Engine. The structure follows the product line the way a buyer evaluates it: nodes, gateways, the mesh network and the Snape software on top, with solution pages for infrastructure, structural health and mining. Case studies and press releases moved from the blog subdomain onto the main site, and the single About page split into company, leadership and investor sections. A landing page system and HubSpot forms feeding the sales pipeline gave marketing somewhere to send people.
Launch, then stick around
Pre-launch reviews ran page by page with Ackcio’s marketing team on the WP Engine staging site, down to partner logo ordering and cookie policy links, and the site went live in 2022. Chillybin has hosted and maintained it on a Website Care plan since. Four years on, the site is still the same WordPress build, now fronting a company with offices in Singapore, Calgary and Malmö.
What we delivered
Ackcio now publishes case studies, employee spotlights, partnership announcements and event pages itself, on its own domain, the day they are ready. The two-to-three-week edit cycle is gone. The site presents the full system (hardware, mesh, software) in the language its buyers use, and the landing page and HubSpot machinery gives campaigns somewhere to land.
The build has carried Ackcio through four years of growth, from a Series A startup in Singapore to a company with North American and European offices and recognition from Forbes, ConTech and Ground Engineering. The platform hasn’t needed replacing, just running.
What we learned
When the buyer is an engineer, the sitemap is a spec sheet. Ackcio’s customers don’t search for “monitoring solutions”; they search for the exact instrument they need to connect. Having the client’s engineers vet the keyword list (must-haves in green, irrelevant terms in red) put domain knowledge into the site structure that no agency could have supplied alone.
CMS ownership is a business capability, not a technical detail. The most valuable thing we shipped wasn’t any single feature; it was the removal of the queue.
