Clear Channel Outdoor — Redesign + App Starter

INNOV8 delivered two distinct tracks for Clear Channel Outdoor — one of the largest out-of-home advertising companies in the world — within a single engagement spanning 2023 and 2024.

Track 1: clearchanneloutdoor.com redesign

The public-facing corporate site was rebuilt from a legacy architecture to a modern JamStack approach on Next.js + React (React 17), with Emotion handling component-scoped styling and MUI (Material UI) as the component foundation.

The content layer was migrated to a headless GraphQL CMS, decoupling editorial workflows from the frontend deployment cycle. LunrJS powered the site’s fuzzy search — a client-side full-text search implementation that indexed the site’s content at build time, delivering instant search results without a server round-trip. HubSpot integration handled dynamic contact and inquiry forms, maintaining the marketing team’s existing CRM workflows without requiring a backend endpoint for form submissions.

The redesign drove measurable results post-launch: +22% monthly traffic, +5% leads, and +33% revenue attributed to the improved site performance and updated information architecture.

Track 2: CCO Config Driven React Application Starter

The second track was a force multiplier for Clear Channel Outdoor’s internal engineering teams: a configuration-driven React application starter that could spin up new internal tools without the usual scaffolding overhead.

Built on React 18 + Redux + Emotion + MUI, the Starter encoded the architectural decisions, component patterns, and integrations that every CCO internal application needed — authentication, state management shape, component library wiring, CI/CD hooks — into a single zero-configuration starting point. The first internal application deployed against it went from ground-up development to production in one week by a single developer, a workload that had historically required a multi-developer team over six or more months for comparable applications.

The two-track structure reflected the engagement’s core insight: the public site and the internal tooling ecosystem needed different solutions, but both benefited from the same underlying architectural discipline — consistent component patterns, typed interfaces, and configuration-first thinking over copy-paste flexibility.