Client
CrossBoundary Group
Role
Lead Design Engineer
Deliverables
Website (Multiwebsite Environment)
Multi-site system for one of the largest sustainable-development investment firms in the Global South.
CrossBoundary invests where capital is hardest to deploy — energy, infrastructure, agriculture, and growth companies across emerging markets. Following their rebrand, the group needed a digital presence that could hold the breadth of the firm under one identity while giving each investment platform (CrossBoundary Group, CrossBoundary Energy, CrossBoundary Advisory, and others) room to speak to its own audience, stage of maturity, and stakeholders.
The brief was twofold: define a digital audience strategy that reflected how the firm actually went to market, and build a multi-website system that translated the new brand into a scalable, long-lived web architecture.
The project was carried out in collaboration with backendforth studio.
The situation
We approached the ecosystem as a single design system with multiple front doors. One visual and editorial language, one underlying component library, but independent sites — each with its own narrative, hierarchy, and audience focus. The work spanned information architecture, content strategy, UI design, design-system build, and end-to-end development across the platform family.
Design and development are both built on a custom-made, scalable component design system — a shared library of tokens, patterns, and UI components that keeps Figma and code in lockstep. It gives every site in the family a consistent visual language while leaving room for each platform's own voice, and gives CrossBoundary's team a foundation they can extend across new platforms and campaigns without losing coherence.
Every page was designed to perform at two levels: as a clear, trust-signalling surface for institutional investors, partners, and governments; and as an editorial environment for the firm's research, reporting, and project storytelling.
My role
Leading design engineer across the multi-site system and bridge between the design team and delivery. On the engineering side, that meant setting frontend architecture, building the shared component library, defining the CMS structure, and owning implementation across every site in the family. On the design side, it meant leading designers in translating brand decisions into reusable patterns, pressure-testing layouts against real content, and keeping design intent intact from Figma to production.
The goal was a system that the client's team could keep extending long after launch, without losing visual coherence, performance, or editorial clarity as the firm grew.
