Lead UX/UI DesignerResponsive Marketing WebsiteSoftware Development Agency

Beurdev Agency

BEURDEV CO., LTD. · Feb 2024 – Oct 2024
Beurdev agency site rebuild — dark engineering-led marketing site naming the tech stack and publishing package pricing
Executive Summary & Impact
Consistency
Consistency and standards
five pages moved onto one dark system
Real-world
Match between system and the real world
services described by the frameworks a buyer checks
Visibility
Visibility of system status
each process stage labelled with its status

A rebuild of a software agency's own site, designed for a prospect deciding whether the team fits their project before getting in touch. The design gives five pages one visual language, names the frameworks behind each service, and labels the working process by stage. Each decision below is tied to the usability heuristic it serves.

01 / Discovery & Heuristic Gaps

Problem & Usability Gaps

The site being replaced had the right sections, a price list and a package table among them, but it did not read as one company. Read against the heuristics, its five pages used two unrelated looks, so a visitor moving between them could not be sure they were still on the same site; the team was described by role, with no frameworks named, so a technical buyer had to ask what the team builds in; and two of the pages were led by stock illustration that showed nothing of the work.

Two looks
five pages split between a teal and a navy layout
No stack named
the team described by role, with no frameworks listed
Stock imagery
two pages led by illustration rather than the team's work
02 / Architecture & UX System

Design Decisions by Heuristic

01
Consistency and standards
Five Pages, One System
Every page moves onto one dark ground with green accents and a code texture, under the same header and above the same footer. A visitor going from the home page to services, portfolio or contact stays inside one company's site rather than crossing between templates.
02
Match between system and the real world
The Stack, Named in the Buyer's Terms
The tech stack splits into iOS app, front end and back end, and names each framework with its logo: React Native and Flutter; React, Vue.js and Angular; NestJS, Laravel and Django. A prospect with an existing codebase checks compatibility in the vocabulary they already use.
03
Visibility of system status
Each Stage Labelled With Its Status
The working process runs as three cards, Design, Build and Roll Out, tagged Starting, On Progress and Success, with QA and testing named inside the last. A client can see what each stage covers and where a project stands at each point before the work begins.
04
Aesthetic and minimalist design
The Work in Place of Illustration
The stock illustration gives way to screenshots of client projects and photographs of the two founders, and the four packages sit side by side with their inclusions under each price. The space that decoration took now carries what a prospect came to check.
03 / Verification & Evidence

Before & After by Heuristic

HeuristicBeforeAfterChange
ConsistencyTeal pages and navy pagesOne dark system on all five pagesUnified
Real-worldTeam described by roleFrameworks named in three groupsCheckable
VisibilityProcess as a row of arrowsThree stages, each with a statusLabelled
MinimalismStock illustrationClient work and founders' photosFocused

"A prospect choosing a software house runs two checks it can make on the page: is this one serious company, and does it build in what my project needs. The rebuild puts both answers where they can be checked."

— Design rationale · Beurdev Agency
04 / Retrospective

Design Learnings

→

Naming frameworks is stronger than describing capability because it is checkable; a claim a visitor can verify in their own vocabulary carries weight that a general one does not.

→

Consistency across pages is part of credibility: five pages in two looks read as a set of templates, not as one company.

→

For a technical service the visual register is part of the message; illustration that carried no information was quietly saying the wrong thing.