Case Study Business

After several false starts, a marketing team got its website back

Genzeon had approved designs and a site so complicated that changing a headline took a developer. Earlier attempts to fix it had not shipped. We rebuilt it as one plain WordPress site, and launched in about eight weeks.

  • 2025 project year
  • ~8 weeks kickoff to launch
  • ~1,000 pages, posts and files moved
  • 19 page sections marketing can mix

A marketing team that could not touch its own website

Genzeon is a healthcare technology company. Like most companies that sell to other businesses, it relies on its website to explain what it does and to turn interest into conversations. That work belongs to marketing.

When we met the marketing lead, that was exactly what was out of reach. The team had a new design, already approved inside the company, and a website they could not change on their own. A new headline or a landing page for a campaign meant a request to a developer and a wait.

The project meant to fix this had been attempted before, by more than one firm, and it had not shipped. So the team had designs everyone had signed off on and no working site to show for them.

Every change needed a developer, and the fix kept not arriving

The site had been built in two parts. Content lived in WordPress, and the pages visitors saw were produced by a separate system that pulled that content in. Setups like this suit some teams well. For a marketing team without developers on hand, it meant the person writing a page could not see the page. They filled in fields in one place, and the result appeared somewhere else, arranged by code they could not reach.

Day to day, that turned small jobs into requests. Changing the navigation was a development task. So was building any page that did not match an existing pattern. Marketing runs on the calendar of campaigns and events, and this website ran on the calendar of whoever was free to write code.

Meanwhile, the redesign sat finished on paper. People across the company had reviewed and approved it, and each stalled attempt made the next one harder to believe in. What the marketing lead needed was plain: the approved design, live, on a site the team could run themselves.

We made it simpler, and built exactly what they had approved

We rebuilt the site as one WordPress site. Content and pages lived in the same place again, so the person editing a page saw the whole page and controlled it. A wording change took a few minutes of marketing's time, and nobody else's.

We built what had already been approved. The designs were signed off before we arrived, so we matched them and did not reopen the design conversation. Nobody at Genzeon had to walk a new round of mockups through approvals, and the project could finally move.

A Genzeon page made of several distinct content sections stacked one after another
Pages were assembled from sections the marketing team could add and reorder.

We gave marketing building blocks. Each page was assembled from a set of sections the team could add and reorder, so a new landing page started with someone in marketing and not with a request to a developer. The navigation menu, a large one with a panel for each part of the business, was editable from the WordPress admin screen for the same reason.

The Genzeon navigation menu open on one section, showing a panel of grouped links
The navigation menu, a panel for each part of the business, which marketing could edit from the admin screen.

We moved everything. Every page, post, image, and document came across from the old site and was checked, so that nothing the team had published went missing at launch.

What the team could do on launch day

The new site went live about eight weeks after we started. On that day the marketing lead could do what had been out of reach for a long time: change a page and publish it without a developer. The team could build a new page from the sections, edit the menu, and post to the blog on their own schedule.

The design that had been approved long before was the design visitors finally saw. The work the team had already done getting it reviewed and signed off was not wasted, and nobody had to defend it a second time.

This was a project with a beginning and an end. We were brought in to get a stalled rebuild launched and to leave the marketing team in control of it, and when the project wrapped, that is where things stood. The decision that mattered most was also the least glamorous one: choosing the setup that fit the people who would use the site every day.

What changed

  • The approved design went live after earlier attempts had stalled
  • Marketing could build and edit pages from mix-and-match sections without a developer
  • The navigation menu became something the team edited from the admin screen
  • Published pages, posts, images, and documents all came across to the new site

Under the hood

For the developer evaluating us
  • 278custom fields in 12 groups
  • 47SCSS files in 7 tiers
  • 5page header styles
  • 4custom content types
  • 11plugins, 3 required by the host
  • 258pages and posts migrated
  • 741media files migrated

What We Built

  • A full rebuild as a single WordPress site with a custom theme
  • All pages, posts, images, and documents moved from the old site
  • Mix-and-match page sections for building new pages without a developer
  • A large navigation menu editable from the admin screen
  • Built-in search and blog filtering without page reloads

Why the two-part setup did not fit this team

The earlier site was a headless build: WordPress held the content and a separate front end rendered it. That approach has real strengths, and it asks for ongoing front-end development capacity that this team did not have. Editors could not preview a page as visitors would see it, and layout changes lived in front-end code. For Genzeon the better fit was a single WordPress install where editing and presentation share one system.

Theme and page sections

A custom theme on Bootstrap 5, with SCSS compiled by Dart Sass. Pages were composed with ACF Pro flexible content: a fixed library of sections, each with its own fields, which editors could add and reorder. Several page header styles covered the approved designs' variations, and custom content types held the structured content.

The large navigation menu was built on ACF repeater fields, which is what made it editable from the admin screen without code. Site search and blog filtering returned results without a page reload. Sliders used Swiper.

Migration

Published pages and posts and the media library were moved from the old install and checked against it, including documents attached to posts. Counts are in the spec tiles above.

Hosting

Genzeon runs the site on Pantheon, a relationship that predates this project, and the theme was built to run there. Three of the plugins are ones that host requires.

Figures current as of September 26, 2026

After multiple failed attempts with other firms, FatLab rescued our website project and launched it in weeks. They followed our approved design perfectly and delivered a complex WordPress site that's easy to manage.

Alex Lucas Marketing Manager (Head of Marketing), Genzeon

More stories like this

Want a website that earns its keep?

Tell us what your site needs to do, and we will tell you how we would approach it.