What results did Nexus achieve?

Nexus outcomes included Inbound Inquiries (+163%), Time on Work Pages (+71%), LCP (Mobile) (0.9s), Referral Conversions (+39%). Nexus now owns a presence as sharp as its output | and the site has become the first artifact in every new business development thread.

What results did Nexus achieve?

Nexus outcomes included Inbound Inquiries (+163%), Time on Work Pages (+71%), LCP (Mobile) (0.9s), Referral Conversions (+39%). Nexus now owns a presence as sharp as its output | and the site has become the first artifact in every new business development thread.

What technologies powered Nexus?

Nexus was built with Next.js, TypeScript, Tailwind CSS, GSAP, Vercel. Full stack details are documented in the case study.

Can ZiyadX take on a project similar to Nexus?

Yes. If you need similar portfolio / agency / web work, explore our Branding & Identity Design service or contact the Mumbai studio to brief a comparable engagement.

Who was Nexus built for?

Nexus was delivered for Nexus Studio (2026) with ZiyadX as art direction · web design · development.

Portfolio / Agency / Web

Nexus

Client

Nexus Studio

Role

Art Direction · Web Design · Development

Year

2026

Context

Overview

A sharp agency portfolio engineered for decisive first impressions | work-forward layout, disciplined type, and motion that punctuates rather than performs.

The Challenge

Prospects were arriving from referrals but leaving without understanding the studio's range or calibre. Case studies lived in decks, not on a surface the studio owned.

Goals

01Make the strongest work visible immediately
02Frame projects with context and outcomes
03Reduce friction from browse to inquiry
04Perform flawlessly on mobile networks

Act II | Process

ResearchtoBuild

Fig. 01 | Research Plate

Research

Reviewed how agency buyers shortlist studios | they scan for hierarchy, proof density, and whether the site itself feels designed. Nexus was losing at step one.

Fig. 02 | Design System

Design

Structured the experience as a publication: index, deep dives, and a concise capability layer. Colour and motion were budgeted sparingly so typography and imagery carried weight.

Fig. 03 | Build Surface

Development

Static-first build with progressive image loading, schema markup for creative work listings, and a CMS that keeps project metadata consistent for SEO.

Fig. 01 | Research Plate

Research

Reviewed how agency buyers shortlist studios | they scan for hierarchy, proof density, and whether the site itself feels designed. Nexus was losing at step one.

Fig. 02 | Design System

Design

Structured the experience as a publication: index, deep dives, and a concise capability layer. Colour and motion were budgeted sparingly so typography and imagery carried weight.

Fig. 03 | Build Surface

Development

Static-first build with progressive image loading, schema markup for creative work listings, and a CMS that keeps project metadata consistent for SEO.

Act III | Proof

ShippedWork

F/01

Work index with category filters

F/02

Case-study pages with outcome metrics

F/03

Services and process overview

F/04

Contact routing by engagement type

F/05

Open Graph–ready project sharing

StackNext.jsTypeScriptTailwind CSSGSAPVercel

Fig. 04 | Solution in Context

We turned the portfolio into the pitch. Prospects arrive pre-qualified because the site already demonstrated the standard they were looking for.

Act IV | Impact

Results

Primary Metric

+163%

Inbound Inquiries

+71%

Time on Work Pages

0.9s

LCP (Mobile)

+39%

Referral Conversions

Key Learnings

Agency portfolios compete on editorial discipline. The studios that look curated get shortlisted; the ones that look templated get scrolled past.

Act V | Exit

Conclusion

Nexus now owns a presence as sharp as its output | and the site has become the first artifact in every new business development thread.

Next Project | 16 / 20Luxury / Fashion / E-commerce

Nexus