Skip to content
Viewing: all (26)
  1. Roger Whittlesea What does collaboration look like at the proposal stage? Digital strategyTechnical validationBrand automation
  2. Matthew Froggatt Internal work has no client Digital strategyMarketingContent strategy
  3. Barry Cumberlidge The gift of time Digital strategyBrand automationMarketing
  4. David Lowbridge From fixed values to behaviours Brand automationUX & UIDigital strategy
  5. Mike Leonard The web is fun Motion designUX & UITechnical validation
  6. Jara Santamaria Martinez Every year is a new brief PlatformsContent strategyTechnical validation
  7. Kristina Radonjic The work between the work Digital strategyMarketing
  8. Guanglun Wu Choosing the right tech stack Technical validationPlatformsDigital strategy
  9. Barry Cumberlidge Security deep dive Technical validationContent strategyDigital strategy
  10. David Lowbridge Startups are prototypes Digital strategyBrand automation
  11. Tara Heal Shapeshifting the Future UX & UIMarketing
  12. Tom Small The theme is the guardrail Brand automationPlatforms
  13. Barry Cumberlidge Your biggest asset in an RFP, your website SEOContent strategyDigital strategyMarketing
  14. Michael Gunner Cache Components: the right content at the right time PlatformsTechnical validationContent strategy
  15. David Lowbridge From static frames to a creative operating system Brand automationUX & UI
  16. Tom Small We build by leaving things out PlatformsDigital strategyUX & UI
  17. Michael Gunner Standardise the foundations, not the brand experience PlatformsBrand automation
  18. Charlie Clarke Letting type move Motion designUX & UI
  19. Andy Purbrick Putting video back where it belongs PlatformsTechnical validation
  20. Mike Leonard The cache that doubled as a coordinator PlatformsTechnical validation
  21. Andy Purbrick We test the revenue path Technical validationDigital strategy
  22. Mike Leonard Two months in Three.js, we started over Motion designTechnical validation
  23. Rhona Mackay The form we actually trust PlatformsTechnical validation
  24. Andy Purbrick The testbed nobody will see PlatformsTechnical validation
  25. Andy Purbrick Twenty-four modules, one wrapper PlatformsContent strategy
  26. Andy Purbrick We haven’t missed a Thursday in 33 weeks Content strategyMarketing

Standardise the foundations, not the brand experience

Michael Gunner 3 min read Platforms Brand automation

Detailed work at scale comes down to one judgement: which parts of a project are worth building fresh for every brand, and which should be solved once and reused everywhere.

A visual comparison between "Core functionality" and "Brand expression" in a digital context
Shared functionality on one side, brand expression on the other

Engineering teams have plenty of frameworks and platforms to draw on when they’re building distinctive brand experiences for clients. For years, developers have leant on libraries like Bootstrap to scaffold quickly and avoid repeating the same groundwork on every project. These frameworks earn their place. They speed delivery up and help teams hit deadlines.

But efficiency can’t come at the cost of a distinctive brand experience. How a business shows up online matters more than it used to, and standing out is hard when you’re one of millions. Heavily opinionated frameworks make that harder still. They’re difficult to break out of, and they push their own visual conventions onto whatever you build, diluting the very identity you set out to create. You know a Bootstrap site because it looks like one.

At ON we work the other way round. We give our engineers a set of internal tools for the parts every project needs anyway - data fetching, code structure, CMS integration, localisation, marketing scripts, search. With those handled, the team spends its time where projects actually differ: the brand.

A collage of various different website screenshots
The brand-specific parts that make each site its own

Those tools don’t sit still. The whole team contributes to them and sharpens them, project after project, each round of feedback making the next delivery a little more dependable. By the time a feature ships through them, it’s been proven in real work, not bolted on and hoped for.

Both sides matter. But while brand expression needs a bespoke approach, most of the technical groundwork stays much the same from one project to the next. That’s how it should be. People expect search and localisation to behave the way they do everywhere else.

And the benefit isn’t only the engineers’. A foundation the design team can trust is what gives them room to be ambitious. When nobody has to wonder whether the groundwork will hold, our designers can push a brand harder and reach for the idea that’s tougher to pull off, trusting the engineering underneath to carry it. The stronger the foundation, the bolder the work we can build on it.

So we standardise what benefits from it, and keep our energy for the part that never should be standardised: making each brand feel like itself.

The client gets both at once: the efficiency of a foundation that has already proven itself, passed on to them, and a brand that stands apart because that’s where our time actually went. They never have to choose between a site that simply works and one that’s unmistakably theirs. Strong foundations let us deliver both, every time. That’s what great client work takes.