Every template starts with a promise: you can skip the hard part. Pick a layout that already works. Swap in your logo, your colors, your copy. Launch by Friday. Move on.
It's a reasonable offer. And for a lot of things — internal tools, landing pages that exist for a month, MVPs that need to ship yesterday — it's the right call. I'm not here to argue against pragmatism.
But if you're building something that's supposed to represent you — your business, your brand, your work — the template's promise starts to hollow out the moment you look at it carefully. Because the thing templates optimize for isn't what you actually need.
Templates solve the wrong problem
The problem templates solve is speed of assembly. Someone made the layout decisions. Someone chose the type scale. Someone figured out where the nav goes and how the hero section behaves on mobile. You're buying all of that pre-made, and it shaves weeks off the build.
That sounds like value. But the metric templates optimize for — time to launch — is not the metric your business runs on. Your business runs on whether people remember you. Whether they trust you before they've spoken to you. Whether the experience of your site reflects the experience of working with you.
When someone leaves your site, do they remember your brand — or do they remember a layout they've seen a dozen times before, now wearing your logo?
Templates can't answer that question well. Not because the people who build them are bad at design — many of them are excellent — but because a template has to work for everyone. And a site that works for everyone can't be built for anyone in particular.
The constraints of the template are the constraints of the average case. Your brand is not the average case. Your brand is specific: a specific personality, a specific audience, a specific promise. That specificity is where trust lives. And specificity is exactly what gets sanded off in the templating process.
Recognition is not the same as familiarity
There's a thing that happens when you look at a lot of websites. After a while, they start to blur together. Not because they look identical — they don't — but because they feel identical. The bones are the same. The rhythm is the same. The hero image, the three-column feature section, the testimonial carousel, the footer with the social icons. You know exactly what comes next before you scroll.
This isn't a problem with any individual template. It's a structural consequence of the ecosystem. When thousands of businesses use the same handful of layouts, the web becomes a visual language where everything rhymes. The individual sites are recognizable — you can tell them apart — but none of them are distinctive.
Familiarity says: I've seen this before. Recognition says: I've seen you before. Only one of those builds a brand.
On the difference between comfortable and memorableFamiliarity is comfortable but forgettable. You don't remember where you read something; you remember that you read something that felt a certain way, in a certain voice, with a certain texture. That texture is almost impossible to create when the frame you're working in was built to be universal.
Recognition — real brand recognition — requires something specific enough to be noticed. A site that has its own logic. Its own gravity. A place that behaves like itself and not like a category.
That requires authorship. You can't get there from a template.
The difference between a website and a place is whether someone notices when they arrive.
Studio principle · HandwiredOriginal design builds trust before anyone reads a word
Here's something that doesn't get said enough: design is communication before copy gets a chance to speak.
A visitor forms an impression of your site — and your business — in the first few hundred milliseconds. Before they've read your headline. Before they've seen your pricing. Before they've decided whether you're the right fit. The visual language of your site has already started answering those questions whether you intended it to or not.
Original design answers them well. It signals that you care about the details. That you thought about what this should feel like before you started building it. That someone made considered choices here rather than selected from a dropdown.
Nobody arrives at your site and thinks, "Hmm, this looks like a Squarespace — I'll trust them less." The response is faster and quieter than that. It's a feeling. And feelings drive decisions in ways that logic rarely overrides.
The contractor who built a beautiful site gets the quote request. Not because the client consciously assessed design quality. But because the site felt like the work of someone reliable. It told the story before the contractor said a word.
That's what original design does. It earns trust before you have to ask for it.
The real cost of the template
Templates are cheap upfront and expensive over time.
The upfront cost is low because the hard thinking has been done for you. But you pay for that in every interaction your site has with a potential client, a potential reader, a potential customer — for as long as the site is live.
You pay in missed recognition — every person who leaves without remembering you. Every return visit that doesn't happen because there was nothing specific enough to anchor the memory.
You pay in eroded trust — every potential client who looked at your site and unconsciously filed it under "generic" before they even started reading. You might never know those people existed. They made their decision without telling you.
You pay in constraint as you grow — templates are built around assumptions about how your site works. When your business grows past those assumptions, you hit walls. Adapting a template to do something it wasn't designed for is often harder than building from scratch in the first place.
I'm not saying this to scare anyone out of using templates. For the right project at the right stage, they make complete sense. But the calculus changes when the site is supposed to be a lasting representation of a real brand. At that point, the cost of generic is real — it just doesn't show up on an invoice.
What "from scratch" actually means
When I say I build sites from scratch, I mean that every visual decision starts from the question: what does this particular thing need to feel like?
Not: what layout does this content fit into. Not: which template is closest to what the client described. But: what is the atmosphere of this brand, and how do we build a place that creates that atmosphere before anyone reads a single word?
That question produces different answers every time. A contractor site needs to feel reliable, established, easy to trust. An author site needs to feel like the writing — the same voice, the same texture. A product pitch site needs to generate excitement and credibility in the same breath. An interactive fiction site needs to feel like somewhere you could get lost.
None of those answers are template-shaped. They require starting from the specific need and building toward it, not starting from a structure and hoping the need fits.
Every project at Handwired starts with a visual concept — palette, type, motion, atmosphere — before a line of code is written. The concept follows from the brand. The code follows from the concept. The result is a site that couldn't belong to anyone else.
The Clocks Made Me site has an hourly chime. Not because that's a standard feature, but because the site is a child's art store and a chime is exactly the kind of detail a child would love and remember. The pendulum loader exists because time is the whole personality of the brand. Those decisions came from the specific project — not from a template that someone else's brand was also using that week.
That's what from scratch means. Every decision made for this project, in service of this brand, with this specific audience in mind. The starting point is the brand, not the template.
The standard
I hold every project to one question: does someone notice when they arrive?
Not: does the site work? Not: is it clean and professional? Those are baseline requirements, not the standard. The standard is whether the site creates a place — a specific, textured, atmospheric place that has its own personality and logic — or whether it's just a vessel for information that could have been poured into any other vessel.
Templates can't reliably clear that bar. They're built to be vessels. They're optimized for content, not for place. And that's fine for what they are. But it's not fine if what you need is a site that does the work of representing you before you've had a chance to speak.
Twelve sites, twelve different visual systems, twelve distinct places. That's the portfolio. Not because I'm opposed to efficiency — building from scratch is slower and harder — but because efficiency isn't the point. The point is a site that people remember. A site that earns trust before the first word is read. A site that couldn't belong to anyone else.
The template can't give you that. The only way to get there is to start from you.