Templates get you online fast, and sometimes that's the right call. Here's what a custom build is actually for, and when I'd pick one.
Most of my work starts in an empty folder. No theme, no starter kit — just the project and the pages it needs. That's a deliberate choice, but it's not because templates are bad. It's because they're a different tool for a different job.
When a template is the right call
If you need something online this week, don't care much about having a custom layout, and just want the basics to work, a template can do the job. Thousands of businesses run fine on them. I've recommended templates to people before.
Where templates start to limit you
- The layout is fixed. You fit your content into it, so the structure tends to look like everyone else using it.
- The theme comes with features you may not use, and that extra weight can slow the site down.
- Changing how things work usually means working around the theme's assumptions, not just editing content.
What a custom build gets you
- The design is made for your content, not the other way round.
- The site only contains what you actually need — no unused features.
- You get the source code, so nothing about the site is locked to a theme.
A template is usually the fastest way to get a website up. A custom build is the pick when the layout matters to you.
The tradeoff
The honest tradeoff is time and cost. Custom takes longer and costs more than installing a theme. That's why I price per project, agree the scope first, and show the design direction before writing code — so you only pay for what you approved.
If a template is the better answer for your project, I'll tell you. If a custom site is worth it, I'll explain what you're getting for the extra time and cost.