← All work2026SportswearPortland

Northmark

Creative technology and launch platform

A trail-running launch that let 40,000 people put their own run inside the campaign — built to survive a traffic spike on a single day.

Client
Northmark Athletic
Year
2026
Sector
Sportswear
Scope
Launch platform, generative tool, campaign
Duration
14 weeks
Team
6 from the studio, 4 client-side

Northmark launches one trail shoe a year and the launch day is the business. Their previous launch site had done its job and then fallen over for 40 minutes at peak, which cost more than the campaign did. We were asked for something more ambitious that failed less.

01 — The problem

One day of traffic, one shot at it

Northmark's audience does not browse — it arrives at 09:00 on launch day, all at once, from a newsletter and three athlete posts. The site has to hold, convert, and be interesting enough to share within the same ten minutes.

The previous launch had treated the spike as an infrastructure problem. It was also a design problem: the page asked the audience to watch, and a watching audience leaves.

02 — The thinking

Give the runner something only they can make

We built Route Plate: upload a run, get it back as a two-ink print in Northmark's campaign colours, ready to share or order as a poster. The shoe launch became the frame around forty thousand personal artefacts.

Crucially the generator runs entirely in the browser. No queue, no server render, no cost per generation — which is also why it did not fall over.

Route Plate — input, separation, output

03 — The making

A static page with one clever island

Everything except the generator is static and served from the edge, so the page itself cannot be overwhelmed. The generator is a single isolated client component that loads after first paint and degrades to a gallery of pre-made plates if the browser cannot support it.

The campaign art direction came out of the tool rather than the other way around: the posters, the film titles and the in-store prints all use the exact generator output, so nothing in the campaign is unachievable by a customer.

Generator output — same engine as the campaign art

04 — The result

It held, and people stayed

Launch day ran without an outage and with a median session far longer than any previous Northmark launch, because the audience had something to do rather than something to watch.

Behind the decisions

What we chose, and what we argued against.

Why in the browser

A server-side generator would have needed a queue on the only day it mattered. Client-side rendering made the expensive feature the cheapest part of the stack.

Why the campaign used generator output

If the posters had been prettier than what a customer could make, the tool would have felt like a toy. Identical output made it feel like access.

The fallback we designed first

We built the no-JavaScript gallery before the generator, so the launch had a floor we were happy to ship even in the worst case.

Selected artefacts

From the work itself.

Outcome

What changed.

40k

Plates generated

In the first 72 hours, all client-side.

0

Minutes of downtime

Against 40 minutes at the previous launch.

1

Interactive component

Everything else ships as static HTML.

We asked for a launch site. They gave our runners a reason to open it twice, and it stayed up while they did.
Dana WhitfieldVP Brand, Northmark Athletic

Credits

Who made it.

Creative direction

Júlia Ferreira

Creative technology

Teo Marchetti, Priya Raman

Campaign

Nadia Brandt, Sam Okonjo

Start a project

Have something like this in front of you?

A 45-minute call with the people who would do the work. If we are not right for it, we will say so and suggest who is.