Website Design

zCore Group

Breaking the Federal Playbook

Updated: May 2026

The Insights page on zCore Group's website helped the company win a $5.9M federal contract. During the proposal period, analytics showed a sustained spike in traffic to FMBT-related blog posts. Those posts built credibility with evaluators before the proposal even landed. That outcome traces back to a set of decisions about visual language, content architecture, and what a small digital services firm's website should actually do.

zcoregroup.com - homepage with hero video

The Problem

Federal digital services websites have a visual genre. Navy blue palettes, shield iconography, stock photos of server rooms, advisory boards stacked with retired government officials. The messaging centers on trust and fear: breach statistics, threat landscapes, urgency. It works, in the sense that procurement officers recognize it. But it also makes every company in the space look interchangeable.

zCore Group wanted out of that pattern. They're a small, SDVOSB-certified firm delivering digital services to defense and defense-related healthcare agencies. Their buyers aren't the generation that built those visual conventions. They're younger procurement officers who can tell when a site was built from the same GovCon template as the last five vendors they reviewed.

The brief was clear: bring startup energy into a space that defaults to institutional. The constraint was equally clear: don't alienate the audience in the process.

My Role

I was the sole developer and design engineer. I owned the full scope: design in Figma, development in code, content strategy, CMS implementation, and production deployment. Figma MCP served as the bridge between design and development.

Point of View

Escape the predictable for a small business delivering digital services to federal agency customers. That was the operating principle. Every decision filtered through it. Does this feel like the other sites in this space? If yes, rethink it.

The Work

Visual language: defense tech, not defense establishment

The palette went dark with lime green accents. Not the navy-and-white of traditional GovCon, and not the neon-on-black of consumer cybersecurity. The combination reads as defense tech without borrowing from either convention. It signals the right world while feeling distinct within it.

Hero sections use video loops themed around defense and defense-related healthcare. These set the tone immediately: this is a company that operates in serious domains but presents itself with energy and precision, not gravity and fear.

Dark-field palette with lime green accent system

The map animation

A map component shows zCore team member locations. The craft challenge wasn't the GeoJSON data layer (though that took time). It was landing on the right visual style.

Early iterations used a retro aesthetic reminiscent of 1980s WarGames style digital maps. Glowing grid lines, terminal-green overlays, the whole cold-war-era command center look. It was fun. It also pulled the site toward nostalgia when the brand needed to feel current.

The final version uses a SAR (synthetic aperture radar) style. It reads as operational and technical without being retro. The shift was subtle in description but significant in effect: it moved the map from cool reference to this looks like a tool these people actually use.

Working with the client through that iteration took longer than building the component itself.

Final SAR-style map with team location markers

Content strategy and the CMS pivot

The Insights page started as a standard blog section. It became the most strategically valuable part of the site.

I designed the content strategy and implementation, building a real-time content pipeline so zCore could publish posts timed to contract cycles. The idea was simple: when zCore competes for a contract, relevant expertise should already be visible to anyone researching the company. Blog posts about FMBT and related topics meant that evaluators checking zCore's web presence found substantive thought leadership, not just a capabilities page.

The CMS started with Decap (a Git-based headless CMS). It worked, but the content velocity the strategy demanded outgrew it. I migrated to Sanity, which gave the team the real-time publishing pipeline they needed. That migration is one of the things I'd do differently from the start.

GA4 - Insights page traffic during FMBT contract window

What I Explored and Killed

The early design direction leaned heavily into defense imagery and language. It worked for the cybersecurity audience but created friction for zCore's healthcare-adjacent clients. Defense-related healthcare agencies are still defense, but the visual cues that signal we protect the nation don't translate cleanly to we secure health data for veterans.

Toning down the defense-forward direction opened space for the site to serve both audiences without feeling like a compromise.

How I Worked

Design happened in Figma. Development in React, Tailwind CSS, and Next.js. Figma MCP bridged the two, keeping design decisions connected to implementation. AI assisted with code generation, testing, optimization, and SEO/AEO work. The visual direction, interaction design, content strategy, and architectural decisions were mine.

Impact

The new version of the site has been in production for roughly 8 months. The headline number: zCore won a $5.9M federal contract, and analytics data supports the claim that Insights posts (particularly FMBT-related content) contributed to the win. During the competition period, those posts drove significantly higher traffic than baseline.

Beyond the contract win, the site accomplished what the brief asked for: zCore's web presence looks nothing like the GovCon template. It positions them as a premium partner with startup energy, not a me-too vendor with a different logo.

GA4 - overall traffic and engagement since launch

What I'd Do Differently

Three things.

Start with the CMS. I built the site first and added content infrastructure later. The content strategy turned out to be the most valuable part of the project. If I'd built around Sanity from day one, the pipeline would have been tighter and the client could have started publishing sooner.

Skip Decap entirely. The Git-based CMS model made sense for a developer-centric workflow, but it didn't match how the client's team actually needed to publish. Investing in Sanity (the premium option) earlier would have saved migration effort and given the team better tooling from the start.

Develop the ICP persona earlier. The client discovered their ideal customer profile through the project, which meant revision rounds that could have been avoided with upfront discovery work. I'd push for that persona work in the first week now.

What This Changed for Me

This project shaped how I think about visual language as something market-driven, not just aesthetic. Every industry has what I think of as visual genres: sets of conventions that signal belonging. Those genres aren't static. They shift with market conditions, influenced by market leaders and the design teams at the companies setting the pace.

Positioning a client's website means understanding which genre they're in, where that genre is heading, and whether to work within it or break from it. For zCore, breaking from the genre was the right call. That won't always be true. But the research and client discovery work needed to make that judgment is something I carry into every project now.

Credits

Solo project. zCore Group leadership provided domain expertise, content direction, and iterative feedback on visual direction (particularly the map component).