Elevate

Elevate is a UK B2B telecoms business formed from a 2024 rebrand. I was brought in to keep it moving, which in practice means new pages, new CMS structures, filter work, form integrations and the kind of diagnostic work that only shows up on a build with real history in it.

The site runs to over 130 pages with hundreds of form records and shared components used across dozens of them. Briefs come in from the client side and get turned into working sections, usually against a sensible timeframe and always against a site that people are using right now.

The site was rebuilt by Tahi Studio, who have published their own case study on the engagement. The continuous campaign and lead magnet work they describe there is the phase I came onto.

• Add new sections and pages without commissioning a rebuild
• Make the CMS flexible enough to handle content that does not fit the original structure
• Capture leads reliably and get them into Salesforce cleanly
• Fix problems at the cause rather than patching over the symptom
• Keep the live site stable throughout

I joined the account after the site was live, and working in a build you did not start is a different skill from building from scratch. Nothing is where you would have put it. Components are shared across pages you have not opened. A thank-you page is reused by six different forms, so a script that looks local turns out to be global.

The default assumption has to be that anything you touch is load-bearing until you have proven otherwise. Most of the real work is reading the site correctly before changing it.

Multi-category filtering. The community page filters were built on a single reference field, so a card could only ever belong to one category. I added a multi-reference field alongside it and surfaced it through a nested collection list, which is the only way to get a multi-reference into a Finsweet filter. Cards can now appear under every category they belong to.

Podcast video playing on the site. Episode videos were sending visitors out to YouTube. I added a video field to the podcast collection, populated it across the back catalogue, and wired the lightboxes so episodes play in place. Traffic stays on the site.

A filter that is actually a link. The client wanted one item in a filter row to navigate to a different page rather than filter the list, while still looking like the rest of the row. I built it as a link block inside the collection item, controlled by conditional visibility so the real filter and the link never render together.

Gated content and tracking. A gated form needed to deliver a guide and register the lead in Salesforce. The first two versions of the brief pointed at an on-page download, and I found that the success page was shared across several unrelated forms, which meant an auto-download there would fire for everyone. Flagging that changed the approach. The final version routes the submit straight to the tracked Pardot link, which handles delivery and attribution in one step and needs no custom script at all.

Diagnostics. Traced a synced component that had been overwritten site-wide, and identified CMS binding and date-field issues affecting how content displayed.