Should Every Website Change Need a Developer?
By Matt Everson
Principal at Astuteo
Every CMS implementation falls somewhere on a spectrum of editorial control. On one end, the marketing team can update anything – design, content, plugins, and even site structure. On the other, even small adjustments require a developer. Every manufacturing marketer has experienced one extreme or the other, and both create problems.
The blame usually gets pointed at the software, but the difference is rarely which CMS you decided on. Instead, it's where you decided to draw the lines.
Too Much Control
Unfortunately for many marketing managers, having too much control is a common WordPress experience – especially when using Elementor, Divi, or WPBakery. Admins tweak design elements, install plugins, and build layouts from scratch. This works for small sites with a single person who has strong design instincts, but breaks down on manufacturing sites with different editors and content that needs to stay consistent across dozens of pages.
The flexibility that feels productive in month one becomes a liability by month six. Pages drift off-brand. Mobile layouts break. Product specs get formatted differently depending on who built the page. Search rankings suffer. Buyers lose confidence. The real cost isn't the eventual rebuild. It's the years of underperformance leading up to it.
Too Little Control
When a site is built as a set of rigid page templates – either because the budget didn't allow for more, or because the team that built it didn't have enough experience supporting in-house teams – the result is too little control. Content is editable through defined fields, but the structure, order, and composition of each page is practically set in stone.
It works for regulated industries, knowledge bases, and simple editorial sites. It breaks down when marketing stops pushing for improvements because every new initiative involves a ticket, a quote, and an invoice. The site ends up frozen in place, not because it's good, but because changing it takes too much time and energy.
The Sweet Spot: Curated Components
Editors choose from a full set of page blocks – hero sections, feature grids, spec tables, testimonial displays, CTA blocks, content sections – and control the content of each block. The design system is enforced by the templates. Editors decide which components appear on a page and in what order, but don't invent new ones on the fly.
What editors can do:
- Add, remove, and reorder page components from the approved set
- Edit all content within blocks
- Create new pages using tested & approved blocks
- Manage content relationships and cross-references
What editors can't do (and shouldn't):
- Change the design system – fonts, colors, spacing, and responsive behavior are enforced by the templates
- Add new sections, plugins, or key features without a development conversation
- Restyle global elements like the header, footer, and navigation
This sweet spot is where manufacturing marketing teams are most successful. With meaningful control over content and page composition without the ability to break a proven foundation. Every extension makes the site more capable over time, not more fragile. And there's no point three years out where you're forced to give up and say, "We need to start over."
Diagnosing Your Situation
Can your team create a new landing page for a trade show without developer involvement?
If not, editors have too little control.
Could an editor accidentally break the site's visual consistency?
If yes, editors have too much control.
Has your team stopped requesting changes because the process is too slow or expensive?
That's too little control.
Does your site look like it was built by multiple people with different design sensibilities?
That's too much control.
Does the admin experience feel like navigating a condemned building?
Is it sluggish, fragile, and layered with years of debris? That's too much control, compounded.
For most industrial websites with small marketing teams, the sweet spot is where moving quickly and design integrity coexist. It's where your digital marketing evolves daily through content changes but never drifts off-brand. It's rarely about which CMS you choose.
Your developer manages the site, but your organization should own the accounts. That means a company-owned GitHub account (for your code) and internal control of your DNS. Web hosting access is a nice-to have, but not always realistic with today's cloud infrastructure. You don't need to touch any of this day-to-day, but if the relationship changes, you need to be able to hand the keys over to someone new.
Curated components enable your team to build and publish pages independently, regardless of who's maintaining the site. Compare that to a page-builder site that's often unmanageable even with a developer, or a hard-coded site where only the original developer knows how it works. When you do need a new developer, the curated component approach is the most portable of the three. Any CMS dev can take a look and quickly understand what's going on.
Because the work isn't the same. A lower-cost WordPress site is typically assembled using a theme and a page builder – often by a generalist, not a developer. The component-driven approach might take a web developer, but results in a consistent platform you can build upon indefinitely. Both might look similar on launch day, but components offer better quality control.