We are Slytrunk

A team of fans who build like it.

We build the things communities gather around. A brand, a product, a live experience, a moment worth sending to someone. Made together, and held to a standard we set ourselves.


Intelligence

AI made it faster. That was never the interesting part.

We treat it as an instrument. Speed is only interesting for what it makes worth attempting, and the idea that died because it would have taken a year is a different conversation now.

Nothing ships until someone here has had their hands on it. That has not changed and it is not going to.

The bench

Everyone here answers for something specific.

25 people · one shop

Shawn

Leadership· Co-founder · BE

Shawn

Luke

Leadership· Co-founder · FE

Luke

Cory

Leadership· CEO

Cory

Phil

Engineering· FE

Phil

Dave

Leadership· BE/FE

Dave

Clint

Leadership· BE

Clint

Daniela

Product

Daniela

Simon

Engineering· FE/BE

Simon

Andrew

Design

Andrew

Julia

Leadership· Product

Julia

Michael

Engineering· FE

Michael

Niko

Leadership· CCO

Niko

Ben

Leadership· CPO

Ben

Casey

Product

Casey

Cat

Design

Cat

Shah

Engineering· FE

Shah

Philip

Design

Philip

Mark

Product

Mark

Su

Design

Su

Jon

Engineering· BE

Jon

Alex

Engineering· FE

Alex

Aye

Design

Aye

Jeremy

Engineering· FE

Jeremy

Klaus

Engineering· FE

Klaus

Scott

Engineering· FE

Scott


Capabilities

The idea can change. The standard doesn't.

Three groups, one shop. Nobody hands work across a wall here, which is why the list below reads as one engagement rather than three quotes.

Intelligence gets us from idea to running system faster. Nothing ships until someone here has had their hands on it.

01

Product & Strategy

Deciding what is worth building, and then being held to that decision.

  • Market and category analysisWhat the category already does, and the part of it everyone has agreed to tolerate.
  • Audience research and segmentationWho is actually opening this, on what, and at what hour.
  • Product strategy and roadmapShort enough that we can actually keep to it.
  • Journey mapping and testingWatching someone use it before anyone here calls it good.
  • Prototyping and validation sprintsA working answer in weeks, so the argument is about something real.
  • Live-ops and operator toolingThe screens your own team lives in on a match day.

02

Design & Brand

Two colours per surface, and no motion that needs a paragraph next to it.

  • Experience and interaction designA control works when nobody notices they used it.
  • Design systems and guidelinesDone when nobody has to ask a question to use it.
  • Brand identity and architectureWe start by agreeing what the thing will not be.
  • Art directionPhotography, type and field, decided once and held.
  • Motion, 3D, and photographyTimed against a metronome, cut when it is decoration.
  • Physical builds, in venues and in handSomething bolted to a stadium wall has to be right the first time.

03

Engineering

Live data arrives whether or not the build is ready for it, and the schedule does not move.

  • Real-time systems and data pipelinesThe stat on the broadcast is four systems deep and right anyway.
  • Native iOS and AndroidBuilt for the three-year-old handset half the audience is holding.
  • Web and full-stack developmentOne codebase somebody else can still work in next year.
  • CMS architecture and integrationTested by asking a non-engineer to change one word.
  • Performance engineeringTwo and a half seconds, written into the brief rather than raised in the retro.
  • AI-native infrastructureIt writes the boring half. Someone here still signs off on all of it.

Contact

Two things get our attention.

A brief with a real problem in it, or a person who should be sitting at this table. Bring either one.