Book a call

Case study · our own site

The one we cannot
hide behind.

Every other build on this page belongs to a client. This one is ours, which means it is the only one where we had nobody to blame and nothing to hide behind.

Agency siteHand codedLive
JTL Growth, live site screenshot
01

The requirement

JTL Growth was a new brand, so nothing was broken. The requirement was harder than a fix: the site had to be proof.

It had to serve Philippine founders and clients in the US and Europe from the first day, without reading as though it were written for one and translated for the other.

It had to carry no pricing, because the work is scoped rather than listed.

And it had to be built the way we build for clients. A site selling hand built systems cannot itself be dragged together in a page builder.

02

What we built

Hand written HTML, CSS and JavaScript, served straight from a repository. No framework, no builder, no template. Every page is a file you can read.

A live background rendered in WebGL that draws the actual memory of our AI workforce as a field of points and threads, sanitised so nothing readable ever leaves the building.

A page for each offer rather than one long scroll, so a visitor arrives at the thing they searched for.

Two automated gates that run before anything ships: one checks structure, copy rules, motion and accessibility, the other checks that every link on the site resolves and that nothing claims to be clickable without being clickable.

03

What it does now

The domain went from purchase to live HTTPS in a single night.

A push reaches the live site in about the time it takes to read this sentence, and both gates must be green before it does.

The site has been rebuilt several times since launch. Each version is in the history, which is the point: we ship, then we improve in public.

The trap worth knowing

A three dimensional background will quietly steal the visitor’s scroll. The camera control library we used captures the mouse wheel by default, so the page stopped scrolling wherever the background was visible, which was everywhere. The fix was to disable the control entirely and drive the camera from scroll position instead, so the background follows the reader rather than fighting them. On a phone the whole scene is skipped: a megabyte of graphics library is not worth it on mobile data.

Your turn

We build the same way
for clients.

Real systems, shipped, with the same standards you just read. Thirty minutes, no pitch.