Insightsfrom the studio.

Working frameworks, not theory. AI as mechanism, prototyping for the enterprise, design and engineering as one team, the cost curve most pilots ignore. Written as we ship.

Field notesAI · Design · EngineeringWritten as we ship

Featured this quarter

00 / 08

AI · Thesis

AI as a mechanism, not a feature.

Most enterprise AI is still being built as a widget on a page. The harder, more useful question is what mechanism the AI replaces in the operating model. The features die in production; the mechanisms compound.

6 min readRead the essay →

8 essays

01 / 08

AI · Architecture8 min

Building the AI layer inside an enterprise product.

What we learned shipping the AI Intelligence Layer at Klay Securities. The architecture choices, the compliance constraints, what we'd do differently.

02 / 08

AI · Systems5 min

Closed loops, not static generators.

The structural difference between an AI feature that decays and a mechanism that compounds. What it takes to get the feedback loop right at production scale.

03 / 08

AI · Economics7 min

The cost curve most AI pilots ignore.

Why most enterprise AI doesn't fail at the demo, and what changes when GPU spend, model selection, and eval cost get treated as a system, not an afterthought.

04 / 08

AI · Design10 min

AI inside UX/UI: a complete framework.

A complete framework for using AI inside the design process, from concept to handoff. What works, what wastes time, how to keep the language consistent.

05 / 08

Design · Practice9 min

How to measure design: a working framework.

A working framework for tying design decisions to business metrics. What to track, what to ignore, how to defend design choices in front of the board.

06 / 08

Engineering · Process8 min

Prototyping for the enterprise: speed without sacrifice.

The tools and approaches that hold up at enterprise fidelity. Where rapid prototyping breaks down, and how to push it further without losing rigour.

07 / 08

Engineering · Tools6 min

Framer at production scale, seriously.

When the design tool is also the deployment tool. Where Framer holds up against a custom build, where it doesn't, the patterns that keep it shippable.

08 / 08

Studio · Operating7 min

Why design and engineering shouldn’t be two teams.

The case for collapsing the handoff. What changes when the people drawing the screens and the people shipping the code are the same people.

Start here

Some of our best projects started with a two-line email.

Most of our work starts with a conversation. No deck required.

Start yours