The build practice

Things we built, and then tried to break.

Product and marketing sites, web apps, APIs, and the pipelines that ship them. Every one went through our own offensive practice before it went live, which is the only reason we are willing to put our name on it.

Selected work
Image pending
Client nameWeb app · 2026

One or two sentences on what the problem was and what shipped. Written for someone deciding whether to call, not for a case-study award.

Next.js · TypeScript · Postgres

Image pending
Client nameMarketing site · 2026

One or two sentences on what the problem was and what shipped.

Next.js · Tailwind CSS

Image pending
Client nameAPI · 2025

One or two sentences on what the problem was and what shipped.

Node · Fastify · Redis

Image pending
Client nameDesign system · 2025

One or two sentences on what the problem was and what shipped.

React · Storybook

Image pending
Client nameWeb app · 2025

One or two sentences on what the problem was and what shipped.

Next.js · Prisma

Image pending
Client namePlatform · 2024

One or two sentences on what the problem was and what shipped.

Next.js · Postgres · Stripe

What it is built with

Counted from the projects above rather than picked for a logo wall. We reach for boring, well-understood tools, because the interesting part of a build should be the problem and not the stack.

Next.js4
Postgres2
Fastify1
Node1
Prisma1
React1
Redis1
Storybook1
Stripe1
Tailwind CSS1
TypeScript1

If one of these looks like the thing you need building, say so.