Web Development
Custom Website Build
The engineering side of a new site. The visual and structural design decisions are web design, and they are a separate service that usually runs first.
A custom build is a site engineered for your business rather than adapted from a template. The Nexclick scopes what it must do, chooses the platform that genuinely fits, and hands over documented code you own. Templates are cheaper and right for plenty of businesses — we will say when.
Is this you?
What usually prompts the call
- Your current site cannot do something the business genuinely needs and no plugin solves it.
- Every change is quoted as a day because nobody understands how the site was assembled.
- You have outgrown a template and are fighting it rather than using it.
- You need integrations — a CRM, a booking system, an ERP — that a template will not accommodate.
What we do
The actual deliverables
Things that appear on an invoice, not adjectives.
- Technical scoping before anything is designed
- What the site must do, which systems it talks to, what the content model is, and where the awkward cases hide. Written down and agreed before a fixed price is given.
- Platform recommendation, argued
- WordPress, Next.js, Laravel, Webflow or Shopify — chosen for your situation with the trade-offs stated. There is no house platform we push everyone onto.
- A content model your team can use
- Fields and structures that match how you actually think about your content, so editing does not require a developer or a workaround.
- The build itself
- Clean, commented, version-controlled code. No page builder markup, no plugin doing a job forty lines would do better, no dependencies nobody can explain.
- Performance and accessibility built in
- Core Web Vitals green at launch and WCAG 2.2 AA from the first template. Both cost a fraction as much during the build as they do retrofitted.
- Integrations and third-party systems
- CRM, payments, booking, ERP or bespoke APIs, built to survive the other side changing — which they will, without telling you.
- Documented handover
- A recorded walkthrough, written documentation, repository access and every credential transferred. You should never need us to change a phone number.
Decision tree
Do you actually need a custom build?
Custom builds are the most expensive way to get a website and the right answer less often than agencies imply. Work through these before commissioning one — several branches point somewhere cheaper.
01You need a five-page brochure site and nothing more
No. A good template on Squarespace, Webflow or WordPress will serve you better at a fraction of the cost. We will say so rather than quote.
02You sell physical products and nothing unusual about how
Shopify, with a customised theme. A custom ecommerce build is rarely justified below substantial order volume or genuinely unusual logic.
03Your marketing team needs to publish and edit constantly
WordPress or a headless CMS with a properly designed content model. Custom is about the editing experience here, not the front end.
04You need logic no CMS will accommodate — quoting, matching, calculation
Custom, and probably a web application rather than a website. This is where the money is genuinely well spent.
05You need to integrate with an ERP, CRM or bespoke internal system
Custom or headless. Template platforms handle a standard integration; they do not handle a bespoke one well.
06Performance is commercially critical and templates keep failing on it
Custom on a modern framework. This is a legitimate reason and it is more often about the theme and plugins than the platform.
07You want a custom build because the current site "feels dated"
That is a design problem, not an engineering one. A redesign on your existing platform is likely cheaper and just as effective.
How it works
Step by step, with timeframes
Timeframes are typical rather than guaranteed, and they assume we get account access and approvals when we ask.
- 01Week 1–2
Scope
Requirements, content model, integrations and edge cases, turned into a fixed price against a written specification. Anything outside it is quoted before it happens.
- 02Week 2–3
Architecture and design handoff
Technical architecture agreed, and designs — ours or yours — reviewed for anything that will not work in practice before coding starts.
- 03Week 3–8
Build
Development on a staging environment you can open at any point, with fortnightly demos rather than a reveal at the end.
- 04Week 8–11
Test, launch, settle
Cross-browser and device testing, accessibility audit, redirects verified, then launch with daily monitoring for the first fortnight.
What you get
Reporting and ownership
- A staging URL from week three, so you are never waiting to see progress.
- Full repository access from day one — the code is yours while it is being written.
- Lighthouse and accessibility results in writing before launch, not claimed afterwards.
- A recorded walkthrough plus written documentation for whoever maintains it next.
- A 30-day post-launch period where anything not working as specified is fixed at no charge.
Tools and platforms
- Next.js, WordPress, Laravel or Webflow
- TypeScript
- Git & GitHub
- Staging environments
- Lighthouse CI
- axe-core (accessibility testing)
- Playwright
Timeline
How long this actually takes
Scoping takes one to two weeks, the build six to eight for a marketing site, and testing and launch another two to three. Ten to twelve weeks end to end is typical. Web applications and ecommerce run considerably longer. The variable that slips timelines is almost never development — it is content and approvals, which is why we ask for a named decision-maker at the start. One honest note: a custom build is the wrong purchase for a straightforward five-page brochure site. A good template on a hosted platform will serve you better and cost a fraction, and we will tell you that on the first call rather than quoting.
Pricing model
Fixed-price project
Fixed price against a written specification, invoiced across milestones. Scope changes are quoted separately before any work happens, never absorbed and billed later.
Questions
Custom Website Build questions
How do you decide what to build the site in?
From what it has to do. Content-heavy marketing sites edited daily suit WordPress. Anything where performance and bespoke functionality both matter suits Next.js. Business logic that will never fit a CMS suits Laravel or Node. We state the trade-offs rather than presenting a conclusion.
What does "you own the code" actually mean?
The repository is in your organisation from day one, the hosting and domain are in your name, and there are no licence fees payable to us. If you leave, everything stays exactly where it is and another developer can pick it up from the documentation.
Can our team edit the site without a developer?
Yes, and it is designed for that. Content, images and page structure are editable through the CMS. Where a change genuinely needs a developer — a new template, a new integration — we will have said so during scoping rather than after launch.
What happens if the scope changes mid-build?
It gets quoted before anything is done, in writing, with the timeline impact stated. Nothing is absorbed silently and invoiced later. Where a change is genuinely small we absorb it and say so, which keeps the process from becoming adversarial over trivia.
Do you build the design too, or do we supply it?
Either. We design and build, or we build faithfully from your designer’s work. Where you supply designs we will flag anything that will not survive contact with real content or a 320px screen, but the decisions remain yours.
What happens after launch?
Thirty days where anything not working to specification is fixed at no charge. After that, either you maintain it — which the documentation is written to support — or you take a maintenance retainer. There is no obligation to buy one and no lock-in if you do not.
Last reviewed 28 July 2026.
Tell us what you are trying to fix
A 20-minute call, no pitch deck. The Nexclick will tell you what we would do, roughly what it costs, and whether we are the right people for it.