Selected work

The work should explain the method.

These projects are presented as systems, not trophies. The useful question is what was built, why it was built that way, and what problem the design and engineering were solving.

The Web Maven website
Systems / brand01
The Web Maven

The practice building its own infrastructure: positioning, information architecture, portfolio, service system and the interface that holds it together.

Ayaba Store website
Commerce02
Ayaba Store

WooCommerce, payment integration, mobile checkout and a WhatsApp-assisted buying path.

Crest NG Shop website
Commerce03
Crest NG Shop

A commerce experience shaped around clearer product discovery, trust and purchase decisions.

Dumbiri Cletus website
Authority04
Dumbiri Cletus

An authority-focused personal platform designed to make a person, their work and their ideas easier to understand online.

IHatePDF product interface
Product05
IHatePDF

A lightweight PDF utility product built around getting one thing done quickly, with security and fault tolerance treated as part of the experience.

LWOSOCIA website
Systems06
LWOSOCIA

A structured public-facing web presence designed around information, trust and a clearer path through the organisation.

LWOSOCIA website
Systems07
LWOSOCIA

A structured public-facing web presence designed around information, trust and a clearer path through the organisation.

No theatre

No mystery numbers.

No invented “results”.

When an outcome is measured and approved for publication, it belongs in the case study. Until then, the honest thing is to describe what was actually engineered.

Your project

What are we actually trying to fix?

Bring the problem. We’ll decide whether the answer is a new site, a better funnel, a stronger search layer or something less obvious.

Start a conversation ↗