Someone emailed me last week asking whether they should buy a template from here or spin the site up in a drag and drop builder. It is the most common question I get, and the answer is not the one most builder marketing pages want you to arrive at. The honest version is that each tool wins a different trade, and the trade is almost always the same shape.
Who is going to edit the site a year from now. If the answer is you, or anyone comfortable opening a text editor, a plain HTML template is the correct choice almost every time. If the answer is a client who does not want to open an editor, and who will be adding pages and swapping images on their own, a no-code builder earns its monthly fee.
Everything else, performance, cost, lock in, SEO, is downstream of that question.
A no code builder is faster on day one for a non technical owner. The visual canvas, the component library, the preview that updates as you drag, those are real wins when the person doing the editing is the person who will keep editing. You pay for that convenience as a monthly subscription for the lifetime of the site, and you pay again if you ever need to leave and bring the design with you.
Builders also win when the site needs behaviour I would rather not hand-roll. A simple CMS collection for a blog, a form that posts to a managed inbox, a members area with gated content. You can bolt those onto a static site but you are stitching four services together to do it.
Fixed layout content sites. A one page business brochure, a local service page, a product landing page, a portfolio, an about page for a solo operator. Anything where the content changes rarely, or where the change is going through a developer anyway. A template from the catalog gives you a clean HTML and CSS starting point for five dollars, and the file sits on a static host for two cents a month in bandwidth. The whole lifetime cost is less than one month of the builder's cheapest plan.
Templates also win on performance by default. The files are tiny because they are tiny. No runtime that loads a whole framework before it draws the hero image. No tracking script baked in. A properly built static site hits a one second time to interactive on a cold cache without any work on your part.
There is a hidden cost to builders that nobody writes about on their pricing page. When you want to leave, the export is almost never a drop in. The HTML looks like generated HTML. Class names are machine readable rather than human readable. The design tokens are inlined instead of centralised. If you plan to stay on the builder forever, this does not matter. If you suspect you might want to migrate in two years, buying a template at the start and growing from there costs you less time.
I ask one question. Will you ever want someone other than me, or you, to be able to update this site. If yes, a builder. If no, a five dollar HTML template plus the fifteen minutes it takes to swap copy and images, and the client owns the files forever.
Our pricing page gives the full math on the hosting side. The short version is that a static site on any flat host runs you cents, and a builder plan runs you dollars every month, which stacks up.
Sometimes I build the brochure as a static WebTemps template and run the blog on a managed CMS mounted at /blog. The marketing pages are fast and portable, the blog is editable by the client. Nobody has written a listicle on that pattern because it is boring to configure, but it is what I end up at nine times out of ten.
Every HTML template on WebTemps is a flat five dollars with instant email delivery. Open the catalog or see the pricing page.