Why we named it Chamfer

The cut at the edge

In a machine shop, a chamfer is the small angled cut along the edge of a part. It’s usually 45°, and usually less than a millimeter deep. It takes seconds on the lathe. Without it, a freshly cut part has an edge sharp enough to nick the hand that picks it up, and a burr that stops it seating properly in the assembly.

A chamfer also helps a part fit. A sharp corner catches on its way into a bore, while a chamfered one guides itself in. Machinists call that a lead-in.

Nobody buys a part for its chamfer. No good shop ships a part without one.

The edge on internal software

Internal tools have always been built quickly, by the people closest to the work. That’s their strength. The trouble is at the edges, and we saw the cost from both sides: the warehouse lost days waiting on reviews, and security spent its weeks chasing tools that had skipped them. The edges are familiar: the panel that reads production with a shared admin password, the spreadsheet script with nobody’s name on it, the approval that happens in a chat thread and then scrolls away.

AI made building faster again. A working app now takes minutes. It didn’t change the edges. There are simply more parts coming off the line, and more of them reach real users before anyone checks how they’ll be handled.

Finishing is part of making

We started Chamfer on one position: the finishing step belongs inside the tool, not in a review meeting three weeks later. Every app the Bench builds arrives with:

• sign-in through your identity provider

• roles, down to the row and column

• a named approver for each release

• a Logbook entry for every prompt, query and change

None of these is the reason you built the app. All of them are the reason your company can depend on it. The Bench builds the app, and your reviewers still decide whether it ships. We don’t think software should approve itself.

Fast tools for the people doing the work, with the controls a reviewer needs already in place.

That was the first line of our first planning document in 2021. It’s still pinned above the kitchen in our New York office.

Why not a louder name

We tried names about speed and names about safety. The speed names made our security customers nervous. The safety names made everyone else stop reading. A chamfer is neither. It’s a small, deliberate step that makes a sharp thing usable, and that’s the job. We also like that most people have to ask what it means. The question gives us thirty seconds to explain what we do.

Where the argument lives now

Five years on, 1,400 companies build on Chamfer and 38,000 of their apps are in production. Oren and I still disagree about plenty. The difference is that the argument now happens inside the product, every time a builder and a reviewer look at the same diff. That’s the right place for it.

We’re 140 people now, in New York, London and Lisbon, and every new hire spends a day on a customer’s floor in their first month. It’s the best way we know to learn where the edges are.

Nadia Keller and Oren Bassett, co-founders