Skip to content
Case study · Core

A homegrown website, rebuilt for a global supply chain business.

Core’s site had grown organically for years and stopped reflecting the company it had become. We paired a UX-led rebuild with .NET integrations into Core’s existing tools, in step with its rebrand — on time and on budget.

Client
Core
Project
Website Development
Industry
HS Code Classification
Inside Core

From global homepage to product deep-dive.

Homepage Hero1 / 4
The challenge

A site that outgrew
its own company.

Core’s website had been built up piece by piece as the business expanded globally, and it showed. It no longer reflected the professionalism or capability of a company operating supply chain and sustainability products across international markets.

The brief came alongside a company rebrand — the new site needed to launch aligned with a new visual identity, not patched onto the old one.

Our approach

Four pillars behind the rebuild.

We worked directly with Core’s rebrand consultants so the site and the new brand identity shipped in step, not as two separate projects.

UX-led information architecture

Structure built around Core’s business-critical products — SuppliView, Leaf, TariffTel — and services, not around the org chart.

Custom WordPress build

A flexible, scalable WordPress platform gave Core’s team a CMS they could actually run day to day, without a developer on call.

.NET integrations

The new site connects into Core’s existing backend tools and service portals, so the frontend rebuild didn’t mean rebuilding what already worked underneath.

Brand-aligned design

Visual and interactive design shipped aligned to Core’s rebrand, so the site launched looking like the company it was built for.

The outcome

A site the whole business could point to.

Core today

One global tool,
built to scale.

The rebuilt site is now Core’s central tool for presenting its capabilities globally — to customers, partners and its own teams — not a legacy page nobody wanted to link to.

It was delivered on time and on budget, and built with the scalability to keep growing alongside Core’s international expansion.

Delivered on budgetGlobal CMSBuilt to scale
Start your project

Significant improvement in on-site customer engagement

Better quality leads reaching the sales team

A CMS the internal team can actually manage

One global tool for presenting Core’s full capability

Backend systems integrated, not bolted on

Delivered on time and on budget

Timeline

Strategy to launch in two quarters.

01

Strategy & design collaboration

Q1 2023

02

Development & launch

Q2 2023

03

Ongoing scalability work

Since 2023

Technologies used

What Core is built with.

A deliberately unexciting stack — chosen because it holds up in production, not because it was new.

Microsoft Azure.NETWordPressAdvanced Custom FieldsPHP
The new site finally reflects who we are as a company. High Digital made the entire process simple and collaborative.
MD
Marketing Director
Core Supply Chain Management
Read more client stories
More case studies

Other websites
we've shipped.

See all case studies
FAQ

Questions, answered straight.

The site had grown piece by piece as the business expanded globally and no longer reflected the professionalism of a company operating supply chain and sustainability products across international markets, and it needed to launch alongside a company rebrand.
Around Core’s business-critical products — SuppliView, Leaf, TariffTel — and services, rather than around the org chart, on a flexible WordPress platform the internal team can run day to day.
No — the new site connects into Core’s existing backend tools and service portals, so the frontend rebuild didn’t mean rebuilding what already worked underneath.
A significant improvement in on-site engagement, better-quality leads reaching the sales team, and one global tool for presenting Core’s full capability, delivered on time and on budget.
Let’s talk

Have an outcome in mind?
We'll help you
ship it.

  • You're building a data product and need a team that can deliver.
  • You want to get AI-ready — pragmatically, not theoretically.
  • Your reporting is a mess and you need a real platform underneath it.