# Custom website development, no templates

URL: https://rootcr.com/custom-website-development/
Updated: 2026-08-23

# Custom website development, no templates

> **In short:** Custom website development means the design and the code are made for your company, rather than assembled from the settings of a purchased template. It is worth it when the site has a job to do: bring in enquiries, take orders, serve a process. At RootCR a custom website starts at $350 (€300) with a fixed-price quote, is typically finished in a few days if all the material is available, and the source code stays yours.

## What does "custom" mean here?

Not that I recolour a template. That every line of the site — the design, the HTML, the stylesheet, the server code behind the form — is written for this project. That has three consequences, and all three are measurable:

**Speed.** The page loads only what your content needs. No page-builder framework, no stylesheets from thirty plugins, no external font server. At handover you get a measurement report: load times on real devices, Core Web Vitals values, and the method of measurement, so you can repeat it yourself six months later.

**Security.** Behind every form there are multiple layers: origin check, honeypot field, size limit, human verification, IP-based rate limiting. This is not promised by a plugin but done by server-side code, which you get documented at handover. What that looks like in practice: [the pekarunagyker.hu quote form case study](/case-studies/pekarunagyker/).

**Findability.** The site is built with complete structured data: Google and the language models (ChatGPT, Perplexity, Google AI) get it in machine form too — what you do, at what price, and where. This is not an SEO package bolted on afterwards but part of the build — the method is spelled out in [what structured data is](/guides/what-is-structured-data/).

## When is a custom site NOT worth ordering?

If your site is a digital business card — address, phone number, three paragraphs — then a decently set up template site is enough, and I will say so in the first conversation. Custom development is worth buying when the site brings in money or saves working hours: collects enquiries, takes quote requests, handles bookings, or replaces an internal process.

In that case the limits of the template — the slowness, the fragile plugin chain, forms that cannot be tailored — cost money every month, they just never show up on an invoice. I walk through the decision here: [when is a custom website worth it instead of WordPress](/guides/wordpress-vs-custom-website/).

## What is in the price?

A custom website starts at $350 (€300) (net); the exact price depends on scope, and in the quote it is a fixed amount with a fixed deadline. The price includes:

- custom design — from sketch to finished page, with two rounds of feedback,
- the full build: HTML, CSS, JavaScript, server-side code,
- a protected contact or quote request form,
- complete structured data and technical search engine optimization,
- a measurement report at handover,
- handover of the full source code and every access credential.

Not included by default, available as separate items: copywriting, photography, logo design, ongoing operations. Detailed pricing with typical project sizes: [pricing](/pricing/).

## How does it work?

Four steps: a conversation (free of charge — this is where it turns out whether I can genuinely help), a written quote with a fixed price and deadline, the build with a working demo every two weeks, and handover with a measurement report and full transfer of access.

The most common reason for delay is not development but missing content — which is why you get the list of required material at the very start.

## What does this connect to?

If the site also has to take orders, that is [a custom web store](/ecommerce-development/). If there is repetitive manual work behind the site — copying data between systems — then [process automation](/process-automation/) is the answer. In reality half the projects touch both, so the quote handles them together.

## Frequently asked questions

### How long does it take?

Typically a few days, if all the material — text, images, company details — is available; the quote states a fixed date. The deadline is not an estimate: if it slips, there is a reason, and I tell you in advance.

### Who owns the code?

You do. Full source code, every access credential, no licence fee and no mandatory monthly fee. Any developer can take it over.

### Can you write the copy as well?

I provide the structure and the headings, the professional content comes from you; on request I bring in a copywriter as a separate item.

### What happens to my old site?

I handle the switchover: redirects from the old addresses, so your existing Google positions are not lost. I have written separately about taking over an existing site: [fix it or rewrite it](/guides/taking-over-an-abandoned-website/).

### Will it be just as fast on mobile?

That is the goal, and I prove it by measurement, not by promise. The measurement report contains both mobile and desktop values, because the two are not the same.