Website Development for UK Organisations

It depends on the number of page templates, the integrations, how much content needs migrating and whether design is included. A discovery sprint from £2,000 produces a sitemap, a content model and a fixed-price quote. Improvements to an existing site can run on flexible hours from £20 an hour.

We plan in two-week sprints with a demo at the end of each. A focused marketing site is usually measured in weeks rather than months; large content migrations, multi-site builds and complex integrations take longer. After discovery you get a dated plan rather than a guess.

WordPress on its own suits many sites: familiar to editors, inexpensive to host and backed by a huge plugin ecosystem. A headless setup — Sanity or WordPress as the content source with a Next.js front end — suits sites that need top performance, several channels or a smaller security surface. We recommend based on who edits the site and what it has to do.

The risk comes from how the migration is handled rather than from the rebuild itself, and it is manageable. We map every old URL to its new home with permanent redirects, keep the content that ranks, carry over metadata and structured data, and watch Search Console and traffic after launch. Nobody can promise rankings, but these steps remove the usual causes of a post-launch drop.

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, and that includes services delivered online. Public sector bodies also have specific duties under the 2018 accessibility regulations. WCAG 2.2 AA is the standard most organisations work to, and we build and test to it — legal questions stay with your own adviser.

They are Google’s measures of real-user experience: how quickly the main content appears (LCP), how fast the page responds to taps and clicks (INP) and how much the layout shifts while loading (CLS). They feed into Google’s page experience signals, but the bigger cost of a slow page is visitors who leave before it loads.

If the site sets non-essential cookies or similar tracking — most analytics and advertising tags do — PECR generally requires consent first, and the ICO expects rejecting to be as easy as accepting. Some low-risk analytics may not need consent, with conditions, so we configure consent against the ICO’s current guidance and check that tags genuinely wait for it.

Yes. We can build from Figma files produced by your in-house team or an agency. We review the designs early for performance, accessibility and responsive behaviour, so issues are resolved in the design file rather than discovered halfway through the build.

That is what the content model is for. Editors build pages from approved blocks, preview before publishing, schedule changes and manage media, while the component library keeps pages fast and on-brand. We train editors at handover and leave a short guide for new starters.

You do: code, content, design files, domain, hosting and analytics accounts. Everything is set up under your accounts from the start, so you can keep us on for support or move to another supplier without anything to untangle.