Build
New sites and stores built to a modern standard: fast, accessible, structured for SEO from the first page, and set up so your team can publish without calling us.
A CMS your team will actually use
We model your content around the pages you really publish, wire it into the front end, and hand it over with training. Twelve systems supported, one flat monthly plan.
- 12 CMS platforms
- Migrations included
- Editor training
What we do on every CMS
Whatever system your site runs on, the work we do falls into five buckets. Every request you send lands in one of these, and every plan includes ongoing coverage across all five.
Migrate
Moving from Wix, Squarespace, a legacy WordPress theme, Magento or a hand-rolled system into WordPress, Shopify or a headless stack, with content, URLs and rankings carried across.
Maintain
Core, theme and plugin updates, backups, uptime checks and a monthly health report, so the site keeps working while you focus on the business.
Speed up
Image and asset optimisation, caching, query and app-script audits, and Core Web Vitals fixes for sites that have picked up bloat over the years.
Secure
Hardened logins, firewall rules, malware scanning and cleanup, and a patch cadence that closes known vulnerabilities before they are exploited.
WordPress, done properly
WordPress still powers more sites than anything else, which means it also attracts more bad practice: bloated page builders, abandoned plugins, and no update discipline. Here is how we keep a WordPress site fast, secure and easy to edit.
Themes vs custom blocks
A well-built commercial theme is often the right call for a marketing site on a budget; it ships faster and is easy to hand over. For anything with distinct brand patterns — a pricing calculator, a filtered directory, a bespoke hero — we build custom Gutenberg blocks so editors get real, constrained controls instead of a wall of page-builder settings.
Plugin policy
We run a short list of plugins we trust for forms, SEO, caching and security, and avoid stacking five plugins that each do a sliver of the same job. Every plugin we install is one we are willing to keep updated and account for in the maintenance report.
Updates
Core, theme and plugin updates are applied on a staging copy first, checked against a visual and functional checklist, then pushed to production. You get a changelog every month, not a surprise white screen.
Staging
Every WordPress site on a maintained plan gets a staging environment that mirrors production, so new pages, redesigns and updates are reviewed before anyone outside the team sees them.
Malware cleanup
If a site has been compromised, we isolate it, remove injected files and database entries, identify the entry point (usually an outdated plugin or a leaked credential), patch it, and re-scan on a schedule for the following weeks.
Shopify, run for growth
Shopify handles payments, tax and fulfilment so you do not have to build any of that yourself. Our job is the storefront experience, the app stack and the product operations that keep a growing catalogue manageable.
Theme customisation
We work inside Shopify's Online Store 2.0 sections and blocks so merchandising changes stay easy for your team, and reserve custom Liquid and JavaScript for the layouts a stock theme genuinely cannot do.
Apps
We audit your app list for overlap and page-speed cost before adding anything new, and we favour Shopify's native features (metafields, bundles, subscriptions) over a third app where they cover the same ground.
Checkout limits
Shopify's checkout is locked down by design. We tell you upfront what is and is not customisable at your plan tier — script editor, checkout extensibility on Shopify Plus, or the standard checkout everyone else gets — so there are no surprises mid-project.
Product ops
Bulk product imports, variant and inventory cleanup, collection rules and metafield structures for filtering, so the catalogue stays manageable as it grows past a few hundred SKUs.
Headless CMS, when content has to go further than one website
A headless CMS such as Sanity, Contentful, Storyblok, Payload or Strapi separates content from presentation: editors work in structured fields, and that content can feed a website, a mobile app, digital signage or a partner feed from the same source.
It fits when...
- Content appears on more than one surface
- You need strict content structure across many pages
- Design will change more often than the content model
- You want the fastest possible front end
It is overkill when...
- You have one marketing site and one small team
- You want the widest plugin and template ecosystem
- Editors want a WYSIWYG page view, not fields
Editor experience
We design the content model around how your editors actually think about a page, add live previews wherever the CMS supports them, and set roles so contributors can draft without being able to publish by accident.
Editor experience and training
A CMS is only as good as the people publishing on it. Every build we hand over includes:
Live walkthrough
A recorded screen-share covering publishing, media and SEO fields for your specific site.
Written playbook
A short reference document your team can come back to, instead of re-asking us the same question.
Role-based access
Editors, contributors and admins are set up so people can only do what their role needs.
Ongoing support
Questions after handover go to your usual request queue, not a one-off training invoice.
How a CMS build runs
Content migration is where most re-platforming projects lose rankings and content. This is the process we follow every time, on every CMS.
- 01
Model
We map page types, components and fields to how you publish.
- 02
Build
Schemas, previews, roles and validation wired to the front end.
- 03
Migrate
Existing content scripted across with redirects preserved.
- 04
Train
Live walkthrough plus a written playbook for your editors.
Performance and SEO after migration
A re-platform that quietly loses traffic is a failed project, however good the new design looks. We treat these as non-negotiable checks before and after go-live:
301 redirect map
Every legacy URL that carried traffic or links gets a mapped redirect, checked against your analytics before launch.
Metadata parity
Titles, descriptions, canonical tags, Open Graph and structured data are carried across or improved, never dropped.
Core Web Vitals
Images, fonts and scripts are optimised so the new site loads at least as fast as the old one, usually faster.
Post-launch monitoring
Search Console and analytics are watched daily for the first two weeks so any dip is caught and fixed fast.
How the systems compare
| System | Best for | Editing | Ecommerce | Hosting |
|---|---|---|---|---|
| WordPress | Content-heavy marketing sites, blogs, publishers | Familiar block editor, huge plugin ecosystem | Possible via WooCommerce, not its strength | Included on every plan, managed by us |
| Shopify | Online stores, from a single product to full catalogues | Section-based theme editor, less flexible for pure content | Purpose-built: checkout, payments, tax, fulfilment | Shopify's own infrastructure, we manage the storefront |
| Headless CMS | Content feeding multiple surfaces: web, app, email, kiosk | Structured fields, strongest for non-technical accuracy | Bring your own commerce layer (Shopify, custom API) | Included on every plan, we manage the front end |
Every system we build on
WordPress
Traditional or headless
The most familiar editor on earth, rebuilt properly: custom blocks, no bloated builders, hardened hosting and managed updates.
- Custom Gutenberg blocks
- WooCommerce ready
- Multilingual with WPML
- Role based workflows
Sanity
Headless, real time
Structured content with live preview and real time collaboration. Our default when a team wants content modelled properly across many surfaces.
- Portable Text
- Live visual preview
- GROQ queries
- Versioning and drafts
Contentful
Headless, enterprise
Mature governance, environments and localisation. A safe choice when compliance, approvals and multi brand content are part of the brief.
- Content environments
- Field level localisation
- Granular roles
- Enterprise SLAs
Storyblok
Headless, visual
Component based editing with a true visual editor, so marketers assemble pages from the same blocks we build in code.
- Visual block editor
- Nestable components
- Built in i18n
- Marketer friendly
Payload
Headless, self hosted
TypeScript native and self hosted next to your app. Perfect when content, auth and custom business logic live in one codebase.
- TypeScript config
- Runs in your infrastructure
- Custom admin UI
- Access control in code
Strapi
Headless, open source
Open source and endlessly extensible. Good fit when you want to own the CMS entirely and extend it with your own plugins.
- Open source
- Plugin ecosystem
- REST and GraphQL
- Self host anywhere
Prismic
Headless, slices
Slice based page building that maps cleanly to a component library, with a light editor your team learns in an afternoon.
- Slice machine
- Fast onboarding
- Preview workflows
- Simple pricing
Ghost
Publishing and memberships
Editorial and newsletter first. When content marketing, memberships and paid subscriptions are the growth engine.
- Newsletters built in
- Membership paywalls
- Clean editor
- Great default SEO
Shopify
Commerce content
Products, collections and metaobjects as your content layer, wired into whichever front end we build.
- Metaobjects
- Markets localisation
- Storefront API
- Merchandising rules
Webflow CMS
Visual, hosted
Hosted collections with a visual editor for teams that want to publish without any deployment step.
- Collection templates
- Editor mode
- Hosted publishing
- Localisation add on
Directus
Data first
A CMS layer over your existing SQL database. Ideal for migrating legacy data without reshaping everything first.
- Works on existing SQL
- Granular permissions
- Automation flows
- Open source
Drupal
Enterprise, public sector
Heavy duty content modelling, accessibility and workflow compliance for large organisations and public sector sites.
- Complex taxonomies
- Accessibility focus
- Editorial workflows
- Long term support
One flat monthly price, whichever CMS you need
CMS choice does not change your bill. Build, migration, maintenance, speed work and security are all part of the same flat monthly subscription — no separate quote for "WordPress hours" versus "Shopify hours". You send requests one at a time, we deliver them, and the plan you are on decides how many run in parallel and how fast they turn around.
Compare plansCMS questions
Which CMS should we choose?
If your team publishes daily and wants the most familiar editor, WordPress. If content feeds several surfaces such as web, app and email, a headless CMS like Sanity, Contentful or Storyblok. We recommend one in your first request, with reasons.
Can you migrate our existing content?
Yes. We map your current content model to the new one, script the migration, keep URLs and redirects intact and run a diff before launch so nothing is lost.
Do you set up multilingual content?
Yes. Localised fields, translated routes and hreflang tags are included on Growth and Scale, whichever CMS you pick.
Who owns the CMS account?
You do. Projects are created in your organisation, or transferred to it, and we work as invited collaborators.
Will our team be trained?
Every CMS build ends with a live walkthrough and a written playbook covering publishing, media, SEO fields and previews.
We already have a WordPress or Shopify site. Do we have to rebuild it?
Usually not. If the foundation is sound we clean up, patch and optimise what exists. We only recommend a rebuild when the theme, plugin stack or checkout is actively holding you back.
Can you fix a hacked or malware-infected WordPress site?
Yes, that is one of our most common emergency requests. We isolate the site, remove injected code, patch the entry point, rotate credentials and put monitoring in place so it does not happen again.
Do you build custom Shopify apps or only use the App Store?
Both. Most stores are well served by a short list of vetted apps. When a workflow genuinely needs custom logic — a bespoke configurator, a loyalty scheme, an ERP sync — we build it as a private app on Shopify's API rather than bolting on another subscription.
What happens to our SEO rankings during a CMS migration?
Protecting rankings is treated as a launch requirement, not an afterthought. Every legacy URL gets a mapped 301, metadata and structured data are carried across, and we monitor Search Console for a month after launch to catch anything early.
Pick a CMS, brief your first page
We recommend the right system in your first request, then build and migrate it on the same flat plan.
Choose your plan