Is using a template cheating?

There is an argument that comes round regularly in design circles, and underneath it sits a quiet embarrassment: is starting from a template cheating? Is not being able to tell a client “I designed this from scratch” some kind of failing? Most people asking already sense the answer and hesitate to say it out loud. Let us say it.

Where the objection comes from

It comes from defining our profession by the blank page. A designer is someone who makes something out of nothing; someone using a template took a shortcut. That story is romantic and it produces status inside the field — but it has no equivalent in the client’s world.

Because the client is not buying your process. They are buying the outcome. Where the first pixel of the site came from matters considerably less to them than whether their business grew.

No other trade argues about this

An architect does not reinvent every building. They use standard details, proven typologies, dimensions that come out of regulation, and solutions that have worked a hundred times before. Nobody tells them “you did not design the staircase from scratch, you cheated” — because we look for their value in placing that building on that plot, within that budget, for that person.

Developers use libraries. Photographers reach for established lighting setups. Musicians use chord shapes. None of them carries shame about it. The only reason web design does is that we still measure the profession by handwork.

The value is not in starting from nothing. It is in finishing the right thing. A blank page is not a virtue, only a starting point.

The real question: what are you doing from scratch?

Break a website into its parts. Grid system, typographic scale, button states, form behaviour, mobile breakpoints, accessibility, page speed — these are solved problems. Solving them for the hundredth time earns nobody anything; it eats your hours and opens up surface area for mistakes.

The part that does need doing from scratch is different: why this business exists, what question the visitor arrived with, which section belongs at the top, which sentence earns trust. Judgement, in other words. A template does not take those decisions away from you — it closes off the places where you did not need to be deciding anything.

The client does not notice anyway

The strangest thing about this argument is that it happens entirely among ourselves. No hairdresser, no lawyer, no restaurant owner has ever asked “is this a template?”. What they ask is always the same: when will it be live, will my phone ring, will I be able to update it?

So the embarrassment is not coming from outside. It comes from inside. We are afraid of a colleague’s judgement — and the colleague is not paying your invoice.

Where templates genuinely are bad

Let us be fair: a template is bad when it cannot let you out of the shape it had in mind. That was exactly the problem with the older drag-and-drop tools — you could not ask for anything that was not in the menu, and every site ended up resembling every other. The “templates mean sameness” objection comes from there, and for that era it was correct.

AI changed that equation. A template is no longer a cage but a starting skeleton: real code is written on top of it, you can have components added, you can build the flow you want. The proven foundation stays and the ceiling comes off.

How real is the sameness fear?

The objection you hear most is “if we all use templates every site will look the same”. The fear has a real basis — there was a period when every site shipped with the same hero and the same row of three icons.

But the cause was not the template. It was laziness. Of two designers using the same template, one builds the content, photography and tone genuinely around the client’s business and the other swaps the placeholder text and ships. The two results do not resemble each other. What gives a site its identity is its content, not its grid — and content is precisely the part a template does not give you.

We are all using templates already

A small round of confessions: most designers who say they start from scratch do not. You open your own last project and copy from it. You use somebody’s grid. You pull from your own component library. You take the layout of a site you admire as “inspiration”.

All of that is a template — we just do not call it one. The argument is not really about whether to use one; it is about whether the template is your old work or a skeleton somebody else prepared. And honestly, copying from your own last project is not always the better starting point.

When you genuinely should start from scratch

• When the brand experience is the product — when the strangeness of the site is part of what is being sold.
• When you are building an unusual user flow; a proven structure does not help there, it gets in the way.
• When budget and timeline genuinely allow for exploration.

None of those apply to a hairdresser’s business site. Building that from scratch is not craft, it is waste — and hand-building it on WordPress is usually the same waste in a different form.

What do you put in your portfolio?

Perhaps the real worry hides here: “if I used a template, can I still show this as my work?” You can — but change the story you tell about it. Instead of “I designed this”, say “I built this business’s booking flow, and here is how their phone traffic changed over three months”.

The first sentence makes you an implementer and invites an argument about who pushed the pixels. The second makes you a partner in the outcome and nobody asks about your tools. The second is also harder — which is to say, worth more.

Constraint is not the enemy of creativity

This is the oldest lesson in design education and somehow it is forgotten the moment we choose tools: unlimited options paralyse. A poet uses metre, a photographer the frame, an architect the plot — not as limits but as the place where thinking starts. The idea that a blank page is freedom is romantic and mostly wrong in practice; a blank page usually produces procrastination.

A template is that kind of constraint. The moment you stop arguing about the grid, you have time to argue about what actually matters: what this business promises, why the visitor might leave, which sentence convinces them. Good designers build their own constraints anyway — their own design systems, their own component libraries. Using a template is that same instinct, arriving from outside.

The new version of the question

AI moved the argument one step along. It used to be “did you use a template?”; now it is “did AI make it?”. The same fear in new clothes — as though value increased in proportion to how much surface your hand touched.

That measure was never right. A director does not stop owning the film because they did not hold the camera. We do not say the plate is not the chef’s because they did not chop every vegetable. Creativity is not doing every job yourself — it is deciding which jobs need doing.

So the question is not “is using a template cheating?”. The question is what your client is paying you for: pushing pixels, or delivering something that works for their business. If your answer is the second, it may be time to re-examine your loyalty to the blank page. That loyalty is not protecting your profession — it is attaching it to the part that automates most easily.