Joint ventures in the federal contracting space tend to produce one of two outcomes: the larger partner's brand absorbs the smaller one, or the two brands get mashed together into an awkward portmanteau with a split-color palette. "ClearCore" was already a portmanteau combining "Clarity" and "Core" from the parent companies. The name was a given. Everything else was open.

zCore Group runs a dark-field visual language: dark backgrounds, lime green accents, tight typography. Clarity Innovations leans lighter, more corporate, more conventional. Pulling colors from both would have produced exactly the kind of forced brand fusion that reads as "two companies pretending to be one." Earlier explorations centered on typography and stronger use of images taken from the parent companies. That direction was killed because it did not convey a new business entity.

I chose not to inherit either palette. Instead, I built a new visual system from a reference point outside both companies: the engineering notebook.

The graph paper background is the foundational design decision. It references the engineering field notebooks that have been standard issue in defense and aerospace since the Cold War. Faint cyan gridlines on white, with the slight texture of technical documentation. The motif signals precision and methodical thinking without borrowing from either parent brand.

The isometric cube in the hero section carries the same logic. It is built from translucent geometric planes with a green core element, suggesting depth, structure, and the idea of something solid at the center of a transparent system. The logo animates on load using Framer Motion, the cube assembling itself from its component planes.

The color palette landed on cyan and white with dark navy for the footer and CTA sections. Cyan reads as technical without being cold. It sits comfortably in the defense tech space without looking like a cybersecurity firm (that was zCore's territory) or a generic consultancy (Clarity's risk).

The site needed to do one job well: support capability briefing requests from DoD contracting officers and program managers. Every section funnels toward that action.

The information architecture runs: hero with value proposition, a capabilities carousel (Web & Portal Development, Cloud-Native Modernization, Data & Analytics, DevSecOps & Compliance, Applied AI, Workflow Automation), featured case studies with metrics, a trust bar of agency logos (Navy, DHS, VA, ECMA, Bespin, Cloud One), and a footer with contact paths.

The capabilities section uses a tabbed layout: vertical nav on the left, detail panel on the right with the graph paper motif continuing into the background. Each capability panel includes a description and an "Explore capability" link. The interaction keeps the user oriented without forcing separate page loads.

I designed in Figma, prototyped the logo animation in Jitter, then built the production site in VS Code. The stack is React, TypeScript, Tailwind CSS, and Vite, with Framer Motion handling the logo and page transitions.

The briefing request modal is the primary conversion mechanism: Name, Email, Phone, Agency/Organization, Timeline, Problem Categories, Desired Outcome, and Security Constraints. The form was designed specifically for how federal program managers think about intake: mission-first, timeline-aware, security-conscious.

All design decisions were mine. The content strategy, visual direction, interaction patterns, and front-end implementation were solo work.

The JV still fell into the portmanteau trap with the name itself: "ClearCore" combining "Clarity" and "zCore." With more time and leverage in the engagement, a stronger brand development process could have pushed for a name that stood fully on its own. That was out of scope for this project. The visual identity had to do the work of making a portmanteau name feel like it belonged to a real, distinct entity.

The site is live at clearcore.digital. As of June 2026, it pulls 1.66k unique visitors per month. The site supports the JV's active pursuit of DoD software development contracts and has been used in proposal responses as proof of digital presence and SDVOSB certification.