Warm software, on purpose

Internal tools have a reputation for being ugly, and most of them earn it. The logic goes: no one’s choosing to buy it, so why make it pleasant? We think that’s exactly backwards. The people stuck using a tool every day deserve more care than the people who see it once in a demo.

A few principles

Warmth isn’t decoration. It comes from a handful of choices we make on every build.

• No pure white, no pure black. Backgrounds are warm paper; text is warm ink. The screen stops feeling like a spreadsheet and starts feeling like a place.
• One confident accent, used sparingly. A single clay tone for the thing that matters most on a screen. When everything is highlighted, nothing is.
• Empty states that explain. A blank screen should tell you what will appear here and how to make it appear — not leave you guessing.
• Calm motion. Things fade and settle; nothing bounces for attention. The interface respects that you’re trying to get work done.

Why it pays off

Warm software gets used. People open it without dread, find what they need, and trust what it tells them — and a tool that’s trusted is a tool that actually changes how a team works. The warmth is the point, not the polish on top of it.