← back to field notes

One typeface, six pages, no slop.

A short note on type.

We needed a typeface for this site. The shortlist looked like every shortlist: Inter, Geist, Söhne, GT America, Neue Haas, JetBrains Mono. We rejected all of them.

Why

Every one of those typefaces is correct. None of them is ours. Inter in particular is at the point where it functions as the Helvetica of 2026 — well-drawn, ubiquitous, and completely invisible. If you use Inter, your site looks like every other AI-tooling, dev-tools, indie-SaaS landing page from the last three years.

That's not a knock on Inter. It's a knock on using Inter when you're trying to look like a studio that has a point of view.

What we landed on

Inter Tight for display — a tighter, more characterful cousin of Inter that the slop machine hasn't quite saturated yet. It has the same readability advantages without the "I downloaded the first font that came up in npm" energy.

Inter for body. Yes, the same Inter. The body is where ubiquity stops being a problem and starts being an asset — readers don't notice body type, they notice when it fails.

JetBrains Mono for code, captions, and the small status-bar mono details that signal "this site was made by people who write code." That last one matters more than people admit. The mono caption is the hi-vis vest of the design world: it tells visitors what kind of place they're in.

The rule we wrote down

One display, one body, one mono. No more. If a section needs more than three weights of one of those, it's the section that needs editing, not the type system.

This rule survives contact with reality about 90% of the time. The other 10% is the price of having a rule.

Got a project that needs all three teams?

One sentence is enough to start. We'll take it from there.

Start a project