Template vs. Custom Build: How Designers Should Advise Small Business Clients

A dentist sends you a $79 theme and asks if you can “just make it look like this.” The same week, a bakery owner wants a fully custom site on a budget that barely covers hosting. Both clients are asking one question in different words: template or custom build? The right answer rarely comes down to taste. It comes down to what the business needs its website to do for the next few years, and your real job is helping the client see that before anyone opens a design file.

TL;DR: Recommend a template when the client runs a standard service business, needs a credible site quickly, and works with a modest budget. Recommend a custom build when the site must handle unique functionality, carry a brand that has to stand apart, or support growth a template can’t absorb. For most small businesses in the US, the strongest advice lands in between: a well-chosen template, shaped by a designer who understands the code underneath.

Why Clients Frame This as a Price Question (And Why You Shouldn’t)

Most small business owners treat the decision as a budget line. Templates look cheap, custom work looks expensive, and the conversation ends there unless you redirect it.

The market has shifted under that assumption. A 2025 Clutch survey of US small businesses found that 83% now have a website, up from 64% in 2018, with no-code builders driving much of that growth. Simply having a site no longer sets a business apart. How well the site fits the way customers actually buy does.

That shift explains why industry-specific templates have become so useful. A well-built chiropractor website template, for example, already reflects how patients research a practice: clear service pages, visible location details, and an obvious path to booking an appointment. The designer who chose it didn’t skip strategy to save money. They borrowed strategy that someone had already tested in that vertical.

Fit becomes the lens for every recommendation you make. Price follows from it.

When a Template Is the Right Recommendation

Picture a two-person landscaping company. They need a homepage, a services page, a project gallery, a quote form, and a phone number that works on mobile. Nothing about that business model demands original engineering.

Templates make sense when most of these conditions hold:

• The business model is conventional. Service providers, local retail shops, restaurants, and professional practices follow patterns that template authors have already solved.
• Speed matters. A client opening in six weeks needs a live site more than a perfect one.
• The owner plans to edit content. Platforms like Squarespace, Wix, and WordPress with a block theme let nontechnical owners update hours, menus, and photos without calling you.
• The budget is limited and fixed. A template frees money for photography, copywriting, and local SEO instead of layout code.

A template also lowers risk for a business that hasn’t validated its offer yet. If the client pivots in a year, they won’t have sunk a large investment into a site built around the old model.

Template work isn’t less work, either. Picking the right theme, stripping out the bloat, and adapting it to a real brand takes judgment that clients can’t buy from a theme marketplace.

When Does a Custom Build Earn Its Price?

Some projects outgrow a template before launch. The skill lies in spotting them during discovery rather than halfway through the build.

Point the client toward custom development when you see signals like these:

1. Unique functionality sits at the core of the business. A booking system with custom pricing logic, a member portal, or a deep integration with a CRM or practice management platform will fight a template at every step.
2. The brand is the product. Design studios, boutique hotels, and premium consumer brands sell an experience, and a theme that thousands of competitors share undercuts it.
3. The content architecture is complex. Multiple locations, large product catalogs, or layered service categories need a structure built around them.
4. Performance and accessibility carry real stakes. Bloated themes often load scripts the client never uses, which drags down Core Web Vitals. Businesses that must meet WCAG standards benefit from markup written with accessibility in mind from day one.
5. The client wants to own the platform. Hosted builders can limit access to code, exports, and server settings. A custom build on an open stack removes that dependency.

When two or more of these show up together, a template usually turns into a temporary fix that the client ends up paying for twice.

The Middle Path Most Small Businesses Actually Need

Here’s what rarely makes it into the template vs. custom debate: most successful small business sites are neither. They start with a solid template and then get customized where it counts.

In practice, that hybrid approach follows a clear sequence. You choose a lightweight theme with clean markup, build a child theme or custom stylesheet so updates don’t overwrite your changes, rewrite sections that need better semantic structure, and add schema markup so search engines understand the business. The client gets most of the speed and savings of a template with a result that doesn’t look like everyone else’s.

This path depends on one skill many designers have let slide: reading and editing code. Page builders handle most of a layout, but the final adjustments to heading hierarchy, form labels, image alt attributes, and responsive behavior live in the markup. If your comfort zone ends at the builder’s settings panel, learning HTML online closes that gap faster than most designers expect, and it expands what you can confidently promise a client.

Code fluency also protects you during scoping. When you can see how a theme structures its templates, you can tell a client honestly whether a requested change takes an hour or forces a rebuild.

Questions to Ask Before You Recommend Either Option

Good advice starts with good discovery. Run every small business client through a short set of questions before you mention platforms or prices.

Discovery question	Points toward a template	Points toward a custom build
What must the site do beyond sharing information?	Contact forms, basic booking, a gallery	Custom logic, portals, deep integrations
How soon do you need to launch?	Within a few weeks	Flexible, with room for phased work
Who will update the site after launch?	The owner or a staff member	An agency or developer on retainer
How different do you need to look from competitors?	Professional and credible is enough	The visual brand drives sales
Where do you see the business in three years?	Similar size and services	New locations, products, or revenue models

Answers rarely line up neatly in one column. A mixed result is your cue to propose the hybrid route rather than forcing a binary choice.

Mistakes Designers Make When Advising on This Decision

Even experienced freelancers slip into habits that quietly erode client trust. Watch for these four.

Recommending what you prefer to build. Some designers push custom work because it pays more or feels more creative. Others default to templates because they finish faster. Clients notice when a recommendation serves the designer.

Ignoring total cost of ownership. A template’s sticker price hides recurring costs: premium plugin licenses, theme renewals, builder subscriptions, and the hours spent fixing conflicts after updates. A custom site carries its own maintenance load too. Put both sets of costs in writing so the comparison stays honest.

Skipping the exit plan. Clients on hosted builders often discover too late that migrating means starting over. Tell them up front what moving platforms would involve.

Overselling customization. Promising that a template can do “anything” invites scope creep and frustration. Be specific about where the theme’s limits sit.

Making the Template vs. Custom Build Call With Confidence

The designers small businesses trust most don’t sell a format. They diagnose a situation. A template and a custom build solve different problems, and your value lies in matching the tool to the client’s stage, budget, and ambitions rather than to your own portfolio goals.

Treat the decision as something you revisit, not a one-time verdict. A template that fits a new business today may need custom work in two years, and planning for that transition from the start makes the eventual upgrade feel like growth instead of a costly rescue.

FAQs

Is a template website bad for SEO?

No. A lightweight, well-coded template can rank as well as a custom site. Problems come from bloated themes that slow page loads, poor heading structure, and builders that restrict access to technical settings. Choosing a clean theme and fixing its markup solves most of these issues.

How should designers price template projects compared to custom builds?

Price the judgment, not just the hours. Selecting, adapting, and optimizing a template still requires strategy, content work, and testing. Many designers charge a flat project fee for template work and reserve hourly or phased pricing for custom development, where scope tends to shift.

Can a business move from a template to a custom site later?

Yes, though the effort depends on the platform. Sites on open source systems like WordPress usually migrate more smoothly because content and code stay accessible. Hosted builders often require rebuilding pages from scratch, so clients should understand that tradeoff before they commit.

Do designers still need to know HTML if they use page builders?

Yes. Builders cover layout, but accessibility fixes, structured data, and precise responsive adjustments still happen in the markup. Designers who read HTML confidently scope projects more accurately and deliver cleaner sites.