When the platform holds you back

If every change waits for a developer, or the platform is out of support, it's time to build it properly.

  • Campaigns and launches wait for a developer to change the site.

  • The platform is out of support, hard to secure, or held together by workarounds.

  • Your editors can't publish what they need without breaking something.

  • You have several sites or logins that should be one.

  • Your back-office systems aren't linked, so staff key the same information in twice.

  • You have a new product to build and want to start fresh, not bolt it onto the old platform.

Disconnected systems and slow sites cost you

Most business systems still don't talk to each other, many sites fall short on mobile, and apps that disappoint get uninstalled fast.

  1. Marketing sites

    Built on a CMS your team can use, with pages they can build and change themselves.

  2. Customer portals and platforms

    Logged-in products where customers buy, renew, manage accounts and get things done without calling you.

  3. Integrations

    Connections to your CRM, billing, product and data systems, so information goes in once.

  4. Testing and launch

    Automated tests, accessibility and performance checks, and a launch plan with a way back if something goes wrong.

  5. After launch

    We stay on to host, support and keep improving it, if you want us to.

Before you rebuild

Three things worth knowing about platforms and CMSs.

Headless isn't automatically faster

A headless CMS can be quicker and more flexible, or slower and harder to edit. It depends on how it's built and who has to use it.

The CMS isn't the strategy

Choosing a platform is one decision among many. The content, the journeys and the integrations matter more to whether it works.

You should own it

The code, the content and the data should be yours, with documentation good enough for another team to pick up. If they aren't, ask why.

Ready to rebuild?

Five questions before you brief anyone.

  • Do you know which pages and journeys bring in most of your leads or revenue?
  • Who will edit the new site, and have you asked them what slows them down now?
  • Which systems does it need to connect to, and who owns each one?
  • What content are you moving, and what can go?
  • Who owns the code, hosting and data today, and who should after launch?

Clear answers to these make any rebuild quicker and cheaper to quote.

The things people usually ask

Plain answers about web, app and platform development, what's involved and what we need from you. Anything else, just ask.

Which CMS do you build on?

Whichever fits your content, your team and your budget. We partner with several CMS platforms, including Sanity, Webflow, WordPress, HubSpot and Concrete CMS, and we'll build on what you already have when that makes more sense.

Who owns the code?

You do. It lives in your repository, and the documentation is written so another team could take it on.

Can you take over a site someone else built?

Usually, yes. We start with a review of the code and hosting so you know what you're inheriting before you commit.

Do you build mobile apps?

Yes. We build iPhone and Android apps from one codebase, in React Native or Flutter, and keep them up to date with Apple's and Google's yearly requirements. If your web team works in React, React Native usually fits best.

Ways to get started

  • Projects

    Bigger products and platforms, built end to end or with our specialists in your team.

    Typical range
    £50k to £250k+
  • Ongoing support

    Hosting, maintenance and support, on a service level set to your needs.

    Service level
    Set to your needs

If we sound like a good fit, let's talk.