Insight · Web development
Choosing the Right CMS: WordPress, Headless or Custom
We're experienced with many different content management systems, and we work with each client towards the one that best fits the project and its needs, whether that's WordPress, a headless setup or a fully custom admin.
August 14, 2025 · 6 min read

We connect with the client to determine together what their needs are and how we can best make the system work for them, from who will update the site and how often to what they need to change. That conversation leads to choosing a content management system (CMS), one of the first decisions in a new project and one of the hardest to change later, since the platform affects how the site is designed, how quickly it loads, how secure it is and how easy it is to keep up to date.
Questions to Answer First
The first question is what kind of content the site will hold. A site made mostly of pages describing services is a very different job from one built around news and events or a large library of resources, and the shape of that content decides how the admin should be organized.
Media is part of that question too, since images and video have to be resized and compressed to work well on every screen. We decide early whether the site processes them automatically on upload, whether our team prepares them or whether the client's team processes them before uploading. A team without a designer is usually better served by a site that does that work for them, while a team with its own creative staff may want full control over every image.
Next is how often it changes. A site that a communications team updates every week has different needs from one that changes a few times a year, and the more often people publish, the more it is worth investing in an admin that makes publishing easy.
Then comes who does the publishing. Some sites are run by a single editor and others by several teams with their own permissions and review steps, while some content arrives automatically from other sources, such as an events feed or a system the organization already uses, without anyone typing it in.
Health organizations also need to think about where sensitive data lives. A CMS is a good home for public content, but it is rarely the right place for protected health information, which usually belongs in a separate, purpose-built system.
Comparing the Three Approaches
WordPress is still a strong choice when a team needs a familiar admin and wants to publish content on its own. It has a large ecosystem, it is widely understood and it can be extended well beyond a standard blog. We've used it for national health organizations and research programs, adapting it into portals and learning platforms their teams update without touching code, and for Alpha Kappa Alpha, where each region manages its own pages through custom templates and user roles, with member data coming from Salesforce. The trade-off is upkeep. WordPress sites depend on plugins and themes that need regular updates, and security and performance have to be managed actively.
WordPress is also where much of our deepest work happens. We write custom plugins and themes from scratch, build accessibility in from the first template and add animation that goes well past what a page builder can do, and we harden and maintain every site we launch so it stays secure for years. In our hands, a WordPress site can be as distinctive and as carefully engineered as any custom build.
A headless setup separates content from the front end. The site is custom built, often in a framework like Next.js, and the content comes from a CMS through an API. Paired with a visual CMS, a client's team can create pages and publish news themselves, using components we design, without needing engineers. The site stays fast and consistent with the brand, and the team keeps control of its content. That is how we built the site for Bayer's G4A, on Next.js with Builder.io as its visual CMS, so the G4A team publishes new companies, articles and events themselves.
Headless works well for organizations that want a highly designed, high-performing site and a team that publishes often. It needs more setup up front, and the CMS is usually a paid service.
Some projects aren't really websites. When the core of the product is data, workflows or user accounts, a CMS can get in the way. In those cases we build a fully custom platform, designed around the organization's own processes and data from the start, which gives full control over security, structure and how the platform grows.
For Rapid Sequence, we built the content tools into the platform itself, so physicians write and publish clinical cases in a visual editor designed around how a case actually works, which no off-the-shelf CMS could have handled. A custom build is the right choice when the product has specific requirements like these. It takes more investment, and any editing tools the team needs have to be built as part of it.
Final Thoughts
There is no single best platform for every health organization. Each approach has its strengths, and each comes with costs, whether in upkeep, setup or flexibility. The right choice depends on who manages the content, how often it changes, what the site needs to handle and what it will cost to run over time.
Real life also plays its part, because our clients run busy organizations, and with everything else on their plate some of them prefer to email us their content updates instead of logging into the CMS we set up for them, even when it is simple to use. We understand that completely, and we're always happy to make those changes for them.
Once those questions are answered, the answer usually becomes clear. If you're weighing up a new site, tell us about it and we'll help you find the right fit.