Template or Custom Build? A UK Business Guide to Getting Your Website Right the First Time
An honest UK guide to choosing between Wix, Shopify and a custom Next.js build, covering cost, scalability, WCAG 2.2 accessibility, UK GDPR and maintenance.
Why This Decision Matters More Than It Looks
Most websites are not rebuilt because they look dated. They are rebuilt because they can no longer do what the business needs. Perhaps the checkout cannot handle a new pricing model. Perhaps the membership area relies on four plugins that conflict with each other. Or perhaps an accessibility complaint has revealed problems that run through every page.
Choosing between a website builder and a custom build is a commercial decision, not just a technical one. It affects your running costs, how quickly you can launch new features, your legal exposure and how easily you can change direction later.
This guide sets out an honest framework for UK businesses. It explains when a template platform is the right answer, when a custom Full-Stack build pays for itself, and what to expect from a delivery partner from discovery through to long-term maintenance.
When Wix, Squarespace or Shopify Is the Right Call
The first point needs saying plainly: a custom build is not always the right answer. Website builders are well-designed products, and for many businesses they are the sensible choice.
A template platform is often the better option when:
- Your needs are standard. A brochure site, a portfolio or a small catalogue with conventional checkout fits well within the platform.
- Speed to launch matters more than flexibility. You need to validate an idea or start trading within weeks.
- You have no technical owner in-house and prefer a managed, all-in-one service.
- Your integrations already exist as maintained apps in the platform's marketplace.
If that describes you, start there. Reinvesting your budget in content, photography and marketing will probably serve you better than custom engineering at this stage.
When a Custom React.js or Next.js Build Pays Off
The picture changes once your website becomes a core part of how your business operates, rather than a digital shop window. Common signals include:
- Complex business logic. Tiered memberships, bookings with real-world constraints, quotes or multi-vendor marketplaces.
- Bespoke integrations. Connecting to a CRM, ERP, payment provider, logistics API or internal database that no plugin supports properly.
- AI-powered features. Document summarisation, intelligent search, recommendation engines or support assistants built on your own data.
- Growing plugin and subscription costs. Monthly app fees can quietly add up to more than a maintained custom feature would cost.
- Vendor lock-in concerns. Moving content, customer data and URLs off a proprietary platform can be harder than many businesses expect.
- Performance and accessibility ceilings. You cannot fully control the underlying markup, scripts or page weight.
If several of these apply, a custom application is often the lower-risk option over a three-to-five-year horizon, even though the upfront cost is higher.
What the Stack Actually Means for Your Budget
Technical publications explain these tools to engineers. Here is what each one means for the people paying for the project.
- React.js is a library for building interfaces from reusable components. A button, form or product card is built once and reused everywhere. Business outcome: consistent design and lower cost when adding new pages.
- Next.js is a framework built on React.js. It can pre-render pages on the server or generate them in advance. Business outcome: faster load times, stronger search visibility and a single codebase for the website and its API routes.
- TypeScript adds type checking to JavaScript, so many errors are caught while the code is being written rather than by your customers. Business outcome: fewer production bugs and easier handover to future developers.
- TailwindCSS is a utility-first styling system that keeps the design consistent and stylesheets lean. Business outcome: faster interface development and smaller page weight.
- Prisma is a type-safe layer between the application and the database. Business outcome: safer data changes, clearer data models and simpler migrations as the product grows.
- Node.js runs JavaScript on the server, so the frontend and backend share one language. Business outcome: a smaller, more efficient team and simpler maintenance.
Together, these tools form a widely adopted, well-documented stack. That matters commercially, because you are never dependent on one person who understands an obscure setup.
Accessibility: Engineered In, Not Bolted On
In the UK, digital accessibility is a legal consideration as well as a matter of good practice. Under the Equality Act 2010, service providers must make reasonable adjustments so that disabled people are not put at a substantial disadvantage, and this is widely understood to apply to websites and apps. Public sector bodies have more specific duties under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, including publishing an accessibility statement. WCAG 2.2 at level AA is the standard most organisations should work towards. For your specific obligations, take legal advice.
The most expensive way to handle accessibility is to treat it as an audit at the end. A better approach is to build it into the development workflow:
- Semantic components. Headings, landmarks, buttons and form labels are coded correctly once in shared React.js components, so every page inherits them.
- Keyboard navigation and focus management. Menus, modals and checkouts are fully usable without a mouse, with visible focus states. WCAG 2.2 strengthened requirements in this area.
- Colour contrast in the design system. Contrast is checked when TailwindCSS design tokens are defined, not page by page later.
- Automated and manual testing. Automated checks in the build pipeline catch common issues. Manual testing with a keyboard and screen readers catches what tools cannot.
A Word on Overlays
Some vendors sell accessibility overlays, which are scripts that claim to fix a website automatically. They cannot repair inaccessible underlying markup. Many disabled users and accessibility specialists report that overlays can interfere with the assistive technology people already use. An overlay is not a substitute for accessible code.
UK GDPR and Responsible Data Handling
Any site that collects enquiries, accounts or payments processes personal data under UK GDPR and the Data Protection Act 2018. A custom build gives you direct control over several areas:
- Data minimisation. Collect only the fields you genuinely need.
- Hosting location and processors. Know where data is stored and which third parties can access it.
- Consent that works. Analytics and marketing scripts should load only after the user agrees, rather than before the consent banner appears.
- Access and deletion requests. A well-modelled Prisma schema makes it easy to export or erase a user's data.
On a template platform, some of these decisions are made for you. That is acceptable, as long as you understand what you have agreed to.
A Project-Style Walkthrough: Membership Platform
Here is an anonymised example of how architecture decisions connect to business problems.
The problem. A training organisation ran its courses through a website builder, a separate payment tool and spreadsheets. Members had several logins, staff reconciled payments by hand, and content gating was unreliable.
The stack decision. Next.js for the public site and the member area in one codebase. TypeScript throughout. Prisma over a relational database to model members, tiers and course progress. TailwindCSS for an accessible design system. Node.js API routes for payment webhooks and email notifications.
Integration challenges. The hardest part was not the interface. It was keeping payment status, membership tier and content access in sync. Webhooks were made idempotent, so a repeated payment event could never grant access twice or revoke it by mistake.
The outcome. One login for members, automatic access control and an admin view that replaced the spreadsheets. Because the components were accessible from the start, there was no separate remediation project later. The same approach applies to e-commerce stores and AI-powered tools: start from the business workflow and choose the stack to serve it.
Performance Is a Sustainability Decision
Every kilobyte transferred and every script executed uses energy, on servers, across networks and on your visitors' devices. Performance-first engineering reduces that footprint and improves the experience at the same time:
- Static generation serves pre-built pages instead of rebuilding them on every request.
- Image optimisation delivers modern formats at the right size for each screen.
- Lean JavaScript bundles ship only the code each page needs.
- Careful third-party scripts avoid loading tracking tools nobody reviews.
The result is a lighter, faster site that tends to perform better in search, converts more reliably on mobile, and aligns with sustainability commitments your customers increasingly care about.
The Full Lifecycle: What Working Together Should Look Like
Unclear communication sinks more projects than bad code does. A well-run engagement should be transparent at every stage:
- Discovery. Workflows, users, integrations, compliance needs and success measures are agreed before any code is written.
- Architecture and design. Stack decisions are explained, with the trade-offs stated openly.
- Iterative build. Work is delivered in short cycles to a staging environment you can click through, with regular, predictable progress updates.
- Testing. Functional, accessibility and performance checks run before each release.
- Deployment. Automated pipelines, environment variables kept out of the codebase, and a rollback plan.
- Monitoring. Error tracking, uptime alerts and performance monitoring from launch day.
- Maintenance. Dependency updates, security patches and a roadmap for the next features.
Scorecard: Rate Your Current Website
Score one point for each statement that is true:
- Pages load quickly on a mid-range phone over mobile data.
- The whole site can be used with a keyboard alone.
- You have an up-to-date accessibility statement.
- Non-essential cookies load only after consent.
- You know exactly which third parties receive your customers' data.
- Adding a new feature does not require another paid plugin.
- You could export your content and data without heavy manual work.
- Someone is responsible for updates and security patches.
7 to 8: you are in good shape. 4 to 6: targeted improvements will help. 0 to 3: it is worth reviewing your platform strategy.
Questions to Ask Any Development Partner
- Why this stack for my project, and what are the trade-offs?
- How is accessibility built into your components and tested?
- How often will I see progress, and in what format?
- Who owns the code, the hosting accounts and the data?
- What does post-launch support include?
- How would another developer pick this project up in future?
Build It Right the First Time
There is no universally correct platform, only the right fit for where your business is now and where it is heading. If a template serves you well, use it with confidence. If your website has become core business infrastructure, it deserves engineering that is accessible, performant, compliant and maintainable from day one.