For Gateley, in the first month after the relaunch.
Why it matters
Most professional services websites are organised the way the organisation is structured, not the way its clients buy
Service lines down the menu. Partner bios with the best proof buried inside them. A homepage that tries to speak to everyone. It shows how the organisation is structured, not what the client came for. The three audiences that read your site, human buyers, search engines and AI assistants, all struggle with it for the same reason: it doesn't say who you help, how, or why you.
Service-led, when buyers are audience-led
01
A general counsel, a pension trustee and a founder arrive with different jobs. A site organised by service line leaves each of them to work out which service they need. Many give up before they do.
The proof is trapped
02
The case examples, the named sectors and the testimonials that would win the work sit in partner bios and pitch decks, where nobody looking for a service will find them.
The platform holds the team back
03
Every change needs a developer. Every acquisition means another site. Every four years, a rebuild. The website becomes a project you keep starting again rather than something that improves year on year.
What we build
More than a website
Everything we build runs on JUMP Suite Enterprise, our open-source platform, so a tool added in year three sits inside the same platform, design system and content model as the site launched in year one.
Websites
Content-rich sites for single organisations and multi-brand groups, with services, people, articles, events, locations and testimonials connected to each other, so a partner's profile links to her articles, events and practice area without an editor wiring anything up.
Lead-generation tools
Calculators, scorecards, decision trees and benchmarking surveys that give the visitor something useful, a figure or a scored report, in exchange for a conversation.
Portals and gated content
Quote-and-order, membership, distributor and client portals, careers and vacancy systems, and payment gateways, behind a login where they need to be and on the same platform as the public site.
Integrations
CRM, ERP, marketing automation, HR and analytics, connected so that a form submission, an order or an enquiry ends up where your teams already work. Connecting a new system is configuration, not a rebuild.
How we work
A build is the third stage of a process, not the first
We view every project through the three lenses of our Lean Innovation framework: understanding the audience, creating innovative solutions, collaborative delivery. A website is what the third stage looks like when the first two say a new site is the right answer.
So a build starts with audience mapping: one audience, the jobs they need done and the journeys they take, combined with your data and your experts' knowledge. That produces the value propositions the site has to carry and the metrics it will be judged by. Only then do we design and build, in sprints, with your team.
Three things we do differently:
- Audience-led architecture. The site is organised around the jobs your audiences need done, not your service lines. Content pages are designed first and the homepage last, because as many as three quarters of your visitors will never see it.
- Measurement built in. The key metrics are identified during journey mapping, so the site launches able to show what each audience is doing and whether it's working.
- Independent, not dependent. Your team works in the platform as we build it, so by launch they can run it without us.
Understand01Audiences, jobs and journeys
Audience mappingYour dataYour experts
Who the site is for, what they need done, and where it fails them today
Innovate02Explore and exploit
Value propositionsPrioritised planKey metrics
What the site must say and do for each audience, and how success will be measured
Deliver03Build, measure, learn
Architecture and UXDesign systemBuild and integrationsContentMeasurement
The site and tools, built in sprints with your team, live in around three months, measuring from day one
Then: exploit what's working, explore new ideas. Analytics, Search Console and server logs, Second Site tracking every change, and a quarterly Outside World Review
A build, step by step
Clear stages, clear sign-off points
You'll always know what's being decided, who decides it and what happens next. Sponsors and project leads on both sides, a weekly call, and one place where every decision is recorded.
Book a 30-minute intro callStep 1
Scoping
Two workshops. The first on your audiences, their jobs and your objectives across every channel, not just the website. The second on scope, responsibilities, phasing and what comes later. Scoping is the most important part of the project because it defines what gets delivered.
Step 2
Architecture, design and content, in parallel
Three workstreams run side by side: the site structure and navigation, the design system, and the content strategy. They come together as full page designs using your real content, which is the first time you see the new site as your visitors will. That's a sign-off milestone, because the next step is code.
Step 3
Build and content load
We build the templates, tools and integrations on JUMP Suite Enterprise while your team loads content, so every template is tested with real material.
Step 4
Testing
Template by template as we build, then a full functional and cross-browser test, then user acceptance testing with scripts, run by up to 20 people from outside the core team.
Step 5
Launch and knowledge transfer
Editor training, an editorial guide, an analytics workshop and a full post-launch review. By this point your team has been working in the platform for weeks, so launch is not a handover.
Scope
Scoped to what you need, not to a package
A build is made of parts you can commission separately. We price each one, and we tell you which ones you need.
That includes telling you which ones you don't need. If your brand is fine, we'll say so. If your existing site can be fixed with structure and content rather than replaced, we'll say that too, and it will cost you a lot less.
Audience mappingWho the site is for and what they need done
Architecture and UXStructure, navigation and page design
ContentNew, reworked or migrated
BrandOnly if yours needs work
Design systemThe components every page is built from
The buildTemplates, tools and integrations
Technical auditAn independent review of your current site
Knowledge transferTraining, an editorial guide and an analytics workshop
Where a build usually starts
Usually with something smaller.
All our clients come via referrals, not pitches, and every organisation that runs its site with us started somewhere smaller: a Second Opinion, an audit, or one audience mapped through audience mapping. The work proved the method before anyone committed to a platform.
If you already have a brief or an RFP, we'll respond to it, and we'll tell you where we'd have written it differently. If you don't, an independent technical audit of your current site is a low-commitment first step, and it's useful whoever you go on to work with.
Building and paying
What you build and how you pay for it are separate decisions
Any of these can be paid for in any of these ways. The site is the same whichever you choose; only the timing of the cost changes.
What do you want to build?
Usually decided after audience mapping, not before.
Move what you have
Your existing design moved onto our platform, with your content migrated and the site set up properly. No design phase.
When the site works but the platform doesn'tA new site on our platform
Our standard modules, restyled to your brand, built around your audiences, with your content migrated.
When the structure needs to change but the brand doesn'tA bespoke build
A new creative direction, a new structure from the audience work, and bespoke templates, tools or integrations.
When the brief is about how you're positionedHow do you want to pay for it?
We show the three- and five-year cost of each option side by side.
As a project
The build up front, then a monthly fee for the ongoing service.
When there's a capital budgetHybrid
Part up front, part monthly: a smaller set-up fee, with the rest of the cost spread across the monthly fee.
When procurement needs a project figure, but a smaller oneWebsite as a service
Little or nothing up front. The build is spread over the first three years, after which the monthly fee drops to the ongoing service alone.
When there's no capital budget for a new siteWhichever you choose, the site stays current.
- Hosting, monitoring, security and support
- Every platform version upgrade, included
- A creative refresh every four years, included
- New platform modules as they're released
On top of that, you can add work as you need it: quarterly audience sprints, reporting, Second Site, or one of us as your part-time head of digital.
The results
What the platform has done for the organisations on it
Conversions
+
36
%
AI citations
+
245
%
For Efficio in 2025, on a five-language site that is AI-ready by default.
Speed
82.5
%
Faster on average after Gateley's 2024 relaunch. The top 40 law firm's site is now net zero.
Partner since
20
17
Newbury Building Society, with a 2025 refresh and bespoke mortgage and savings calculators on the same platform.
"There's more of a partnership with Compound. They don't just build the site and leave you to get on with it. They're part of the evolution."
Client research, 2026
"I have recommended Compound Partners many times before, and I would continue to recommend them."
Vikki Whittemore, Gateley
Read the case studies: Gateley and Efficio.
After launch
A platform that keeps improving, not a project that ends
Your site gets better over time, including from work other organisations asked for. When we improve something for one client, every site on the platform gets it, because every module on JUMP Suite Enterprise is our own code. Security fixes, performance work and new capability roll out to everyone at once. Nobody is left on last year's version.
The monthly service covers hosting, monitoring, support, every version upgrade and a creative refresh every four years, so the site stays current without a capital bill every few years. Anything beyond that, from a new tool to a quarterly audience sprint, is work you choose, not a compulsory retainer.
The platform itself, and the hosting and security detail, are on the JUMP Suite Enterprise page.
What that means in practice:
- Hosted on AWS through Divio, with daily backups, automated patching and separate development, staging and live environments
- Cloudflare in front of every site: CDN, firewall, DDoS protection and bot management
- Annual independent penetration testing, with fixes applied across every client site
- No third-party plugins, so no plugin vulnerabilities and nobody else's release schedule
- Open source at the core: no licence fees and no lock-in
- A creative refresh every four years on the same architecture, included in the monthly service
Who it's for
Organisations that have outgrown their website, and their platform
Our typical clients are professional services organisations that have found themselves in one of two situations:
- Your site is underperforming and the reasons are structural: organised by service when the buyers are audience-led, with no way to fix that in content alone.
- Your organisation is growing and acquiring, and needs a platform built for continuous change rather than a rebuild every few years.
If you're a small practice with a brochure site that does its job, we're not the right investment, and we'll tell you so on the call.
FAQ
The practical questions
Timing, platform, content and what happens to what you already have.
We aim for around three months from scoping to launch for the first phase, and up to four where there's a significant integration. Larger estates and multi-brand groups are phased. The biggest risk to a timeline is usually a brand project running alongside, so we plan around it from the start.
Most of it falls at three points. Two scoping workshops at the start, with the people who know your audiences and objectives. Sign-off at the design stage, when you see full page designs with your real content. And content loading and testing towards the end, when your team works in the platform alongside us. In between, there's a weekly call with your project lead, and one place where every decision is recorded.
Not if the move is planned properly, and we plan for it from the start. Every existing page is mapped to its new home and redirected, so the people and search engines that know your old addresses still arrive in the right place. After launch, we watch Search Console and your server logs for anything that's been missed and fix it quickly. And because the new site is organised around the questions people are asking, it usually gives you more to rank for, not less.
No. Strategy, architecture, design and content can be delivered on your existing technology, and we'll say when that's the better answer. The build component is on JUMP Suite Enterprise, our open-source platform, because it's the platform we have built and supported for more than ten years.
Audience mapping places every existing page against the journeys it should serve. Some content is rewritten for the audience it should have been written for, some is restructured, some is retired, and the proof buried in bios and pitch documents is brought out where people can find it. Migration runs in parallel with the build, so the new templates are tested with real content.
Either can work. We can write audience-led service pages, sector pages and articles from interviews with your experts, or brief your team and review what they write. Your experts approve every word before it's published.
Yes, and by design rather than as an add-on. Structured data is applied automatically across every template, content plugins add it as editors work, and FAQ and How-To tools carry machine-readable answers. But markup is the last 10 per cent. What makes a site readable to AI assistants is the same thing that makes it useful to people: it says clearly who you help, how, and why you.
Yes. You can pay for the build up front as a project, pay a smaller set-up fee and spread the rest (hybrid), or spread the whole build over the first three years of the monthly fee (website as a service). The site and the service are the same whichever you choose, and we'll show you what each option costs over three and five years before you decide.
No. The platform is built on django CMS, which is open source, there are no licence fees, and your content is yours. If you leave, you keep the code for your site and a licence to keep running it; what you'd be leaving behind is the shared improvements we make to the platform.
Yes. We often build alongside a rebrand, and we've done it many times with Frank Bright & Abel. We'll plan the build so the design work doesn't hold up the strategy and architecture, which don't depend on it.
Tell us about your site.
We'll look at it before the call, so we start with what we've seen. If you have a brief or an RFP, send it with the form. We'll come back within one working day to find a time.