Davit Arakelyan
← All work
Case study · Fictional brand concept · 2026

Brenvia Engineering Group

Identity, design system and homepage for a Madrid group that builds, secures and runs IT for regulated companies.

Not a real company. Brenvia, its people, clients and every figure in the mockups are fictional, made for this portfolio concept.

Brenvia case cover: headline, colour chips and the status board over a photo of an engineer patching a server rack
Fig. 01Case cover: the headline, the core colours and the status board in its degraded state, over a photo of an engineer patching a server rack.
Role
Brand identity, UI and interaction design
Scope
Self-initiated concept
Year
2026
Deliverables
Identity, design system, homepage in light and dark, status board, banners
01The problem

A homepage that doesn’t say who answers the phone.

I started by reading a typical Madrid IT consulting group homepage the way a buyer, or a hiring team, would. The same problems kept coming up.

  1. The hero is a stock photo of smiling consultants and a line that could belong to any company.
  2. Section order wanders: sister companies, an essay, services, a training calendar, method, clients, certificates, cases, then a second essay.
  3. Services, sister companies and the in-house product are spread across the page, so nobody sees what the group does and who does it in one place.
  4. There is no single next step: no phone, no incident line, and a contact form that asks for the visitor’s tech stack before their problem.
  5. Trust is thin. Client names sit in body copy, certifications are logos without captions, and the cases have no outcomes.
  6. On a phone the page runs to more than twenty screens, and the cookie banner covers most of the first one.

The brief I set myself: one clear promise, one place that shows the whole group, and proof that the operations side works, shown rather than claimed.

02Identity

Two routes through one tile.

The name is built on “via”, route in Spanish. The mark is a rounded tile, read as a network port or a block of the city grid, cut by two routes that turn at 45 degrees. One route ends in a lime node, the live point on the network.

Brenvia logo sheet with lockups, mark construction and favicon sizes
Fig. 2Logo and mark: lockups on Paper, Ink and Fern, the construction and clear space, and the small sizes down to a browser tab.

The palette is warm Paper and Ink, Fern green for actions, and lime used sparingly as a signal. Familjen Grotesk sets the headlines, Hanken Grotesk the body, and Geist Mono the data: times, figures and status labels.

Brenvia colour swatches and type specimens
Fig. 3Colour and type: the core palette with status colours, and the three families with their roles.
Network line diagram and four documentary photos
Fig. 4Imagery: line diagrams for the network, full-colour documentary photos for people and places.
03Design system

One set of parts for the site and the client portal.

The system sets colour for light and dark, a type scale, spacing, corner radius and a twelve-column grid. Dark mode swaps colour only, so every part keeps its size and rhythm.

Buttons come in four states, plus dark. Inputs, status chips and cards share one radius and one line weight, and status chips always pair colour with an icon and a word.

Brenvia design system sheet
Fig. 5Design system: type scale, space and grid, buttons in every state, inputs, status chips and cards.
04Homepage

What we do, who does it, and proof that it works.

The hero makes one promise, “IT that holds up under pressure”, with the live status board beside it instead of a stock photo. Below it sit four plain facts about the group and a banner from the operations room.

Brenvia homepage hero with status board and operations room photo
Fig. 6Homepage hero at desktop width: the promise, two actions, the status board, the group in figures and the operations room banner. All figures are fictional concept data.

Six practices sit in one explorer, tabs on desktop and an accordion on mobile, and each names the company that delivers it. The four group companies follow, each with a photo of its kind of work, then a four-step method that starts with an audit before any proposal.

Practices explorer, four group company cards and a four-step method
Fig. 7Practices, group companies and the method. Company names and numbers are fictional.
Brenvia homepage on a phone, light
Fig. 8Mobile, light: the promise, the status board and the practices as an accordion.
Brenvia homepage on a phone, dark
Fig. 9Mobile, dark: the same page for night-shift readers.

Regulated sectors come with their outcomes, the ISO certifications sit right next to them, and the contact form asks about the problem first. A direct incident line is listed for any hour.

Insights, contact form and footer in dark mode
Fig. 10Dark mode: insights, contact with the Madrid office, and the footer. Phone numbers and dates are fictional.
05Status board

Three states, written as sentences.

The board is the proof on the homepage and the main view in the client portal. It shows a fictional network of six sites, two cloud regions and a client portal in three states.

  1. Normal: everything reports in and the board stays quiet.
  2. Degraded: the Valencia uplink loses packets, traffic moves to the Sevilla route, and a note says who owns the fix.
  3. Incident, contained: a login attack on the client portal, with the impact stated first: no accounts were accessed.
Status board shown in three states side by side
Fig. 11The board in Normal, Degraded and Incident states. Sites, events and figures are fictional concept data.

Each state has its own icon, word and line style, so it still reads in greyscale. Changes are announced to screen readers without blinking, and the map redraws to fit its space, from the hero down to a phone.

Behaviour rules with the dark and mobile status board
Fig. 12Behaviour rules, and the board in dark mode and on mobile.
06Banners and photography

Real photos in full colour, and the identity at work.

The photos are free-licensed documentary shots of hardware, an operations room, engineers at work and Madrid. They run in full colour, as shot, cropped tight on the subject. The brand colours come from the layout around each photo, not from a filter laid over it.

Two full-colour photos, with do and don’t examples
Fig. 13Photo direction: two frames as shot, what to photograph, and what to avoid.

The banners take the identity outside the website: a section banner for the homepage, a launch banner for an invented report, a portfolio cover and three social posts.

Operations room photo with an ink caption panel
Fig. 14Homepage section banner from the operations room in Madrid.
Campaign banner with a lime button beside a server room photo
Fig. 15Campaign banner for “The 3 a.m. Report”, an invented study, with a launch breakfast on 4 February 2027. The figure is fictional.
Social post with an operations room photo
Fig. 16Social post for the report launch.
Social post with switch ports and a hiring line
Fig. 17Social post for hiring network engineers.
Square social post with the status board
Fig. 18Square post built from the degraded status board.
Portfolio cover with desktop and mobile homepage
Fig. 19Portfolio cover combining the desktop homepage and the dark mobile page.

Photos from Pexels, used under the Pexels License. Photographers are credited in the project files.

07

What I’d test next

  1. Whether buyers trust a live status board on a homepage or read it as decoration. A five-second test against a version with a photo hero would show it.
  2. Whether “IT that holds up under pressure” beats a line that names the services, judged by how many visitors open the practices explorer.
  3. How quickly IT managers find who delivers a given service, on a phone.
  4. Whether the incident line gets real incidents or sales calls, and what that means for where it sits.
  5. How the full-colour photos hold up at small sizes in social feeds, next to brighter posts.
Next project

Tellroom Video Platform

AI video platform concept

View case study →
Tellroom Video Platform cover
Contact

Let’s get in touch.

Open to remote roles. Let’s talk.

davitarakelyan92@gmail.com