Service
WordPress and custom development
We build on WordPress when you need to edit a lot of content yourself, and on lightweight static or custom set-ups when speed, security and low upkeep matter more. Either way you own everything and it is documented.
Who this is for
Development work comes to us in three forms. Businesses that have a design and need it built properly. Organisations with an existing WordPress site that has become slow, fragile or impossible to update. And companies, often research-led firms around Heslington and the science park, or engineering consultancies, who need something lighter than a full content management system: a fast, secure site they update a few times a year.
Choosing the right platform
| WordPress (custom block theme) | Static site | |
|---|---|---|
| Best for | Frequent editing by several people; news, events, vacancies, case studies | Sites changed occasionally; speed and security first |
| Editing | Familiar visual editor in the browser | Simple editor or by request; we can add a lightweight CMS |
| Running costs | Hosting plus regular updates | Very low; can be served from a global network |
| Security upkeep | Needs updates and monitoring | Very little attack surface |
| Speed | Fast when built carefully | Very fast by default |
We have no commercial reason to push one over the other, and we will recommend the one that fits how you actually work.
WordPress, done carefully
WordPress runs a large share of the web because editors understand it and it can grow with an organisation. It gets a bad name from sites stacked with heavy multipurpose themes and thirty plugins, each one a performance cost and a security risk. We build custom block themes with only the plugins a site needs.
- Custom block patterns that match your design, so editors can build new pages without breaking the layout.
- Structured content types for rooms, courses, products, case studies, publications, vacancies or events, with the fields you need.
- Sensible user roles, so a seasonal member of staff can update events without touching settings.
- Security from day one: hardened configuration, two-factor login, limited admin accounts, backups and an update plan.
What is included, step by step
- Technical plan. Platform, hosting, content types, integrations and how editors will work, agreed in writing.
- Staging site. A private copy where you can watch progress and test.
- Build. Templates, components and content types, coded by hand against the design.
- Content entry. We load your content, or train your team to, and set up redirects from old addresses.
- Testing. Phones, tablets and browsers, keyboard and screen reader checks, forms, speed and security.
- Launch. DNS, SSL, Search Console, analytics and a post-launch check of every redirect.
- Handover. Logins, documentation and a recorded walkthrough of the editing tasks your team will do.
Integrations
We connect sites to the tools you already use: booking systems, CRMs, newsletter platforms, recruitment software, payment providers and maps. Where no reliable connector exists, we write a small, documented one rather than installing a heavy plugin that does twenty other things.
Taking over an existing site
If you have a WordPress site built by someone else, we start with an audit: theme, plugins, hosting, security and speed. You get a short report saying whether to maintain it as it is, tidy it, or rebuild, with honest reasons. We do not recommend a rebuild just because it is more work for us.
How long it takes and what drives the cost
Building a designed small site typically takes two to four weeks; larger builds with custom content types and integrations take six weeks or more. Cost is driven by the number of templates and content types, the complexity of any integrations, how much content we load, and whether old content needs migrating and redirecting.
Common mistakes
- Choosing a theme that "does everything" and loading the code for all of it on every page.
- Installing a plugin for each small feature until updates break the site.
- One shared admin login for the whole team.
- No staging site, so changes are tested on the live site.
- Hosting and domain registered in a developer's name rather than the business's.
How we measure it
We test real-world speed (Core Web Vitals) before and after launch, run accessibility checks against WCAG 2.2 AA, and confirm every redirect resolves. After launch we watch error logs and Search Console for any crawl issues in the first weeks.
Ownership
Your domain, hosting account, code and content belong to you. We document how the site is put together so another developer could pick it up if you ever needed one.
Questions
Can you take over an existing WordPress site?
Usually, yes. We start with an audit of the theme, plugins and hosting, then tell you whether to maintain it, tidy it or rebuild.
Do you use page builders?
We avoid heavy visual page builders on new projects because they slow pages down and make updates fragile. We build with the native WordPress block editor instead.
Is a static site harder to edit?
Slightly, for frequent editing. For sites changed a few times a year it is rarely a problem, and we can add a simple editor if needed.
Who owns the code?
You do. It is written for your site and handed over with documentation.
Can you build web applications too?
We build small custom features and integrations. For large web applications we will tell you honestly if a specialist software house is a better fit.