Built, owned, operated.

A mission-first comparison tool that normalises data from flight manuals and owner reports into a consistent schema, then lets a buyer filter by mission (business travel, family hauler, agricultural use), compare up to five aircraft side-by-side, and model real total-cost-of-ownership with customisable cost variables.

The data layer involved reconciling inconsistent reporting standards across 200+ aircraft from 67 manufacturers: performance figures, fuel burn, range, payload, and cost components. The front-end exposes this through interactive range maps, side-by-side comparison tables, and exportable reports.

The feature set and copy were designed to serve a specific buyer psychology, not just display data. The application migrated from a JavaScript SPA to a server-rendered stack for performance and SEO without losing functionality.

A community platform for fiction authors with three connected surfaces: a publishing layer (short stories linked to external content like purchase pages or trailers), a world-building layer (interlinked entities with graph-structured relationships between worlds, characters, and stories), and a community layer (monthly writing contests with cash prizes and editorial features).

The data model is the interesting part: content entities reference each other bidirectionally, so an author can surface a character across multiple stories, or show readers all the fiction set within a particular world. That kind of relational content structure requires careful schema design to stay performant and queryable.

The application serves a non-technical user base with complex underlying data relationships: the UX challenge was making the graph model feel natural rather than exposing its complexity to authors.