A café owner sent me two quotes side by side last month. One was for a website "built on a proven template," priced low and ready in days. The other was mine: a custom website design starting around ₹66,999, with a design phase before any code got written. From the screenshots alone, she couldn't tell why one cost four times the other.
That's not her fault. Most business owners can't tell custom website design from a good template just by looking at a homepage screenshot, because template marketplaces are very good at photographing their demo sites. The differences only show up once you start clicking around, or once the site has to do something specific for your business instead of something generic for everyone.
What a templated website actually is
A template is a pre-built layout, sold or licensed, meant to work reasonably well for thousands of different businesses with minimal changes. You swap in your logo, your photos, your text, and maybe a color scheme. The structure underneath, the section order, the spacing rules, the component behavior, stays exactly as designed for the demo.
There's nothing shady about that. Templates exist because building a full custom design for every single small site would be wasteful in some cases. A single-page site for a short-term event, a placeholder while a bigger project gets scoped, a hobby project with no real budget: a decent template is a legitimate answer to all of those.
The problem shows up when a template gets sold or bought as if it were custom design work, or when a business with a real brand and real growth plans ends up boxed into a layout that was designed to fit anyone, which usually means it fits no one particularly well.
The tells that show up once you look past the homepage
A few patterns give away a templated build fast, once you know where to look.
Go past the homepage to an interior page, like a services or contact page. On a template, these often look noticeably thinner and less considered than the homepage, because the homepage is the one screenshot that had to look good in the marketplace preview. Custom-designed sites tend to keep their design attention consistent across every page a visitor actually lands on.
Check whether the layout could belong to any business at all. If you covered the logo, could this be a plumber's site, a yoga studio's site, and a law firm's site, all with the same bones? That's not automatically wrong, but it's the definition of generic, and generic is the opposite of what most brands are trying to achieve with a website.
Look at how content fits the design, or doesn't. Templates are built first, with placeholder text and stock photos sized to fit. Real content, your actual services, your actual photography, your actual word count, gets forced into boxes that weren't designed around it. You'll see awkward line breaks, oddly cropped images, and text that clearly got trimmed to fit rather than a layout built to hold it.
Where custom design earns its price
Custom website design starts from the content and the goal, not from a pre-built layout. That means research into who the visitor actually is, what they need to find, and what action the business wants them to take, before a single pixel gets placed.
Information architecture built for your business, not a demo business
A template's navigation and page structure is generic by definition. Custom design maps the actual pages a specific business needs, in the order that actually helps a visitor make a decision, instead of forcing your services into somebody else's category labels.
A visual identity that's actually yours
Typography, color, spacing, and imagery style get chosen to fit your brand and your existing materials, not picked from a limited theme options panel. This is the part that makes a site instantly recognizable as yours rather than swappable with a competitor's.
Components designed around your real content
Custom design accounts for your actual photo count, your actual service list length, your actual pricing structure, so the layout holds real content cleanly instead of stretching or truncating it to fit a demo's assumptions.
Questions worth asking before you compare quotes
If two quotes look far apart on price, ask what's actually included before assuming one is overpriced or one is underpriced.
Ask whether the design phase happens before development, with something like wireframes or mockups you can review and change, or whether the "design" is really just picking a theme and dropping content in. Ask whether interior pages get the same design attention as the homepage. And ask who owns the final design files. A studio doing real custom work should be able to hand you editable design files, not just a live website you can't easily redesign later without starting over.
What I actually build
I design before I develop. Every custom website design project starts in Figma with real content and real layout decisions, reviewed with the client, before any React or Next.js code gets written. That order matters: it's much cheaper to change a wireframe than to rebuild a finished page.
I've built templated landing pages too, when that's genuinely the right scope for a tight budget or a short-lived campaign. But when a business needs a site that looks and functions like theirs, not like the demo of a theme thousands of other sites are also running, that's custom website design work, and it starts with design, not a theme picker.
If you're trying to figure out which one your project actually needs, have a look at how I approach website and product design, or tell me what you're building and I'll give you a straight answer about what custom design would actually add for your situation.