Case study

NOVA: showing everything an IT company does, on one board

A technical preview of a software and IT services company's site, built to test whether a business that does twenty different things can be understood in one screen — and whether its inquiry forms can be trusted to hold a request rather than merely send it.

NOVA is an independent technical preview I designed and built to demonstrate this approach end to end. It was not commissioned by a company, its contact details are placeholders until an owner replaces them, and no client or revenue figures are claimed here — what follows is the reasoning and the build.

NOVA homepage on desktop: a dark board of twenty services arranged from 'it broke today' to 'we plan it', across support, infrastructure and software
Live preview · desktop
NOVA homepage on a phone: the service board reflowed into two columns under the headline
Live preview · phone

The problem this tests

IT companies that do software, infrastructure and support at once usually present as a list of nouns nobody can rank. A visitor with a server down and a visitor planning a new system land on the same generic page, and both leave without knowing whether this company is for them.

NOVA was built to test whether the full range can be shown at once without flattening it — and whether the moment a visitor finally writes in can be made durable enough to trust.

One board, one axis

The hero is a board of all twenty services, arranged on a single axis from 'it broke today' to 'we plan it', across three rows — support, infrastructure, software. A visitor finds their situation by urgency first and by discipline second, which is how the need actually presents itself. Hovering one area dims the others; every cell is a link into that area's page.

The board is built from the real service catalogue, not from a hand-written list, so it cannot drift from what the area pages describe.

Forms that hold a request

The commercial and technical inquiry forms do not simulate a send. They validate on the client and again on the server with the same schema, archive the request durably, assign it a reference the visitor can quote, and then try to notify the configured channel — with a fallback if the first one fails.

Each submission carries an idempotency key, so a retry after a dropped connection is recognised rather than duplicated, and repeated abusive traffic is rate-limited. The identity, contact channels and legal data are edited from the admin panel, so nothing invented ships to production by accident.

What the build proves

NOVA runs on a managed relational database with an authenticated back office and an explicit publication policy: the site stays out of search engines until an owner sets a real domain and authorises indexing.

It shows the studio designing information architecture for a wide offer and engineering the intake — the part most service sites treat as a formality — as the reliable system it needs to be.

Want the same thing for a real business?

Tell me what your site has to do. I will review whether the scope fits before proposing a next step.