Giving Socius a brand worth
believing in

I started with research, not concepts. Ran stakeholder interviews across leadership to understand how they saw the brand versus how their clients experienced it. Reviewed site analytics and lead conversion paths to see where the existing identity was costing them. Bounce rates on service pages were high. The visual inconsistency between the website and sales materials was creating friction in the sales cycle.

Then I ran a competitive audit. Mapped how every B2B digital marketing agency in their space presented themselves. The landscape was flooded with the same blue-and-white corporate look. Socius had a strong reputation through word-of-mouth, but their visual identity told a completely different story online.

The biggest risk with any rebrand is that it ships and nobody uses it correctly. So I built the system with adoption in mind from the start. The guidelines document was not an afterthought. It was a core deliverable. Same with the modular components. If the marketing team could not assemble a landing page without calling a designer, the system would fail.

I templated everything: case study layouts, one-pagers, social cards, email headers, and sales decks. Every piece was built to be assembled, not designed from scratch each time. That's what turned a rebrand into something the team could actually own. After launch, marketing built landing pages and sales assembled decks without design in the loop. The system made that possible.

The rebrand was not just a logo and a PDF. I designed and built every page of the new website. 20 core site pages plus all case study and blog templates. I did not use an existing UI kit or framework. I built a modular component system from scratch.

The system used Figma component variants so the team could adjust size and style without breaking anything. Buttons, dropdowns, alerts, navigation bars, footers, column layouts, text-and-image lockups. All built with variants. I also created an icon service tag system that let you swap icons depending on what was needed for hero image overlay graphics.

I explored breakpoints across devices, designed button states for static, hover, and active, and documented a web style guide for the dev team to build from. The dev team shipped the site directly from the style guide without needing to come back for clarification. That's how I know the documentation worked.

The hardest part was not the visual exploration. It was the consolidation. Socius had good people, but different teams had been making visual decisions independently for years. The rebrand was not just a new logo. It was replacing years of uncoordinated decisions with a single, coherent system that everyone would actually use.

Building the component system for the website changed how I approach every project now. I do not design pages. I design the system that generates pages. That shift in thinking carried directly into my design systems work at EverHealth.

The other lesson was about handoffs. The dev team shipped the site from my style guide without needing to come back with questions. That only happened because I documented intent, not just specs. I wrote the reasoning behind spacing decisions, color choices, and interaction patterns. When engineering understands why, they make better decisions on the edge cases you did not anticipate.