There was a time when calling yourself a web designer meant something specific. It meant you understood colour theory, typography, and visual hierarchy. It meant you could translate a business problem into a visual solution. It meant you could write the code that brought your vision to life. Today, that definition has been stretched so thin as to be meaningless.
The modern web design industry has produced a generation of professionals who have never written a line of production code. They cannot explain the difference between a div and a span. They have never debugged a CSS specificity conflict or optimised a database query. Yet they confidently present themselves as web designers, commanding fees that suggest expertise they simply do not possess.
These are not designers. They are configurators.
The Rise of the Configurator Class
The configurator emerged from a genuine market need. As the internet became essential for business, demand for websites outstripped the supply of skilled developers. Something had to give. The solution came in the form of visual page builders, drag-and-drop interfaces, and an ever-expanding ecosystem of plugins that promised to democratise web development.
In theory, this democratisation was positive. Small businesses could establish an online presence without hiring expensive specialists. Entrepreneurs could prototype ideas quickly. The barrier to entry dropped dramatically.
But something insidious happened along the way. What began as tools for non-technical users became crutches for an entire industry. Agencies discovered they could hire staff at entry-level wages, train them on Elementor or Divi in a fortnight, and bill them out as designers. The economics were irresistible.
The configurator class was born—and with it, a fundamental shift in what the industry considered acceptable work.
Configuration Is Not Design
True design begins with understanding. It requires sitting with a client, listening to their challenges, studying their competitors, and identifying opportunities that the client themselves may not have articulated. It demands empathy, strategic thinking, and the ability to translate abstract business goals into concrete visual and functional solutions.
Configuration skips all of this. The configurator opens a template, swaps the logo, adjusts the colours to match the brand guidelines, and calls it custom. They arrange pre-built sections like furniture in a showroom, never questioning whether the layout serves the client's specific needs. They install plugins to add functionality without understanding what those plugins actually do or how they impact performance and security.
The output looks professional enough to the untrained eye. The client, who likely has no frame of reference for what good web development looks like, accepts the deliverable. Money changes hands. Everyone appears satisfied.
But the client has been short-changed. They paid for design and received assembly. They expected a solution tailored to their business and received a template that could belong to any of a thousand competitors. The website may function, but it does not differentiate. It does not solve problems unique to that business. It simply exists.
The Skills Gap Nobody Discusses
The uncomfortable truth is that many working professionals in the web design industry lack fundamental technical competencies. They cannot hand-code a responsive navigation menu. They cannot write a media query from memory. They cannot explain how the CSS box model works or why their layout breaks on certain screen sizes.
This is not an exaggeration. It is the reality of an industry that has prioritised speed and scalability over craft and competence. When your primary tool abstracts away all the complexity, you never develop the understanding that comes from wrestling with that complexity directly.
The configurator knows which buttons to click but not why clicking them produces a particular result. They can follow tutorials but cannot troubleshoot when something goes wrong. They are dependent on their tools in a way that true craftspeople never are.
This dependency creates fragility. When a plugin update breaks the site, the configurator is lost. When a client requests functionality that falls outside the template's capabilities, the configurator must either decline or install yet another plugin, adding to the bloat. When performance suffers because the page loads fifteen unnecessary JavaScript libraries, the configurator reaches for a caching plugin rather than addressing the root cause.
The Client Pays the Price
Businesses hiring web design agencies operate on trust. They trust that the agency possesses expertise they lack. They trust that the recommended solutions serve their interests. They trust that the final deliverable represents genuine value.
This trust is being exploited at scale.
The client who pays five thousand pounds for a "custom" website does not know they are receiving a fifty-pound theme with modified colours. They do not know that their site loads slowly because it is burdened with page builder bloat. They do not know that the thirty plugins powering their functionality represent thirty potential security vulnerabilities. They do not know that their "designer" has never written a line of code.
They discover these truths later—when the site is hacked, when Google ranks them below competitors, when they try to make changes and discover they are locked into the agency's ecosystem. By then, the damage is done.
Reclaiming the Title of Designer
Design is a discipline with centuries of history. It encompasses architecture, industrial design, graphic design, and yes, web design. At its core, design is about solving problems through intentional decisions. Every element serves a purpose. Every choice reflects consideration of the user, the context, and the constraints.
The configurator makes no such decisions. They accept the defaults provided by their tools. They arrange pre-made components without questioning whether those components serve the client's needs. They mistake activity for accomplishment and completion for quality.
Those of us who still practice the craft of web design must be clear about what distinguishes our work. We begin with discovery, not templates. We write code that serves specific purposes, not generic functionality. We make decisions based on the client's unique situation, not the limitations of our tools.
We are designers. They are configurators. The distinction matters.
The Path Forward
The web design industry will not regulate itself. There is too much money in the configuration model for agencies to voluntarily abandon it. The change must come from clients who demand more and from practitioners who refuse to compromise.
If you are a business owner seeking a website, ask questions. Ask to see code samples. Ask whether the proposed solution uses a page builder. Ask about performance benchmarks. Ask how the site will be maintained and what happens if the agency relationship ends. The answers will reveal whether you are hiring a designer or a configurator.
If you are a practitioner who has relied on configuration tools, recognise that you have built your career on a foundation of sand. The tools will change. The platforms will evolve. If your skills are entirely dependent on a particular interface, you are vulnerable. Invest in learning the fundamentals. Write code by hand. Understand what happens beneath the abstraction layer.
The configurator's dilemma is this: they have optimised for efficiency at the expense of competence. When the efficiency gains disappear—and they will—only competence will remain valuable.
Choose to be competent. Choose to be a designer.