The convergence is real and it is not a failure of imagination. Four independent pressures each have blue as their safest answer, and a team making all four decisions sensibly arrives there without ever choosing it.

1. Status colours claim the good hues first. Red is danger, amber is warning, green is success. Those are learned, near-universal, and unavailable. What is left as a brand accent is blue, violet, teal or a warm neutral — and blue is the largest, safest region of what remains.
2. Contrast is easiest in blue. A mid-blue passes contrast against both white and near-black with the least tuning. Yellow, lime and orange need real work in both directions, and the work happens late, under deadline, when the fix is "make it more blue".
3. Trust research gets cited early and literally. Every brand-colour article says blue reads as trustworthy and stable. For a product asking to hold someone's data, that argument wins the meeting.
4. Defaults. Framework and component-library starting themes ship a blue or violet primary. A team that never deliberately changes it has still chosen it, and most teams have more urgent things to change in month one.

This is the colour version of a broader convergence in software interfaces, where shared defaults and shared advice produce shared results. The general case — and what it looks like when generation is automated — is in why AI-built websites all look the same.

Here is the observation that changes what you do about it. Open any product screen — a list, a settings page, an editor — and estimate how much of it is the accent colour. It is a primary button, maybe an active nav item, maybe a link. Call it two percent of the pixels.

The other ninety-odd percent is neutrals: page background, card surfaces, borders, table rows, body text, secondary text, disabled states. That is what someone actually sees when they look at your product, and on most SaaS products it is the *same neutral grey* as everyone else, because the accent was the only decision anybody made.

A neutral pulled a few degrees toward warm sand, cool slate, sage or ink reads as deliberate immediately, costs nothing in contrast, and cannot collide with a status colour because it has almost no saturation. It is the highest-leverage colour decision in a product interface and the one most often skipped.

Palette galleries and generators show five swatches on a white card, which flatters everything. A SaaS palette is judged somewhere much less forgiving: a dense screen, used for hours, by someone who is trying to finish a task and not admire your colours.

• A settings table. Header row, body rows, hover, selected, disabled, and a border between all of them. This needs eight or so distinguishable neutral values and is where a three-grey palette dies.
• A form with an error. Danger text, danger border, danger background, and a still-legible label. Three roles most palettes define as one.
• An empty state. Muted text on a muted surface, which is the pairing least likely to have been checked.
• Eight hours. A saturated accent that is delightful in a screenshot is fatiguing as a permanent nav highlight. Product colour is judged over a workday, not a glance.
• Dark mode. Increasingly the default for developer-facing products, and not an inversion of your light palette. The measured specifics are in dark mode colour palettes that hold up.

The argument above is only worth as much as the alternatives. These are three complete SaaS-viable palettes with their real hex values, each solving the neutral differently. None of them is a mood board: every role a dense screen needs is present, including the ones that decide whether a table is readable.

1. 1

   Pick the neutral first

   Decide the temperature of your product before its accent: warm (sand, clay, bone), cool (slate, ink, steel), or tinted toward a hue you like. Everything else is easier once this is fixed, and this is the decision people actually perceive.

2. 2

   Build the full neutral ramp

   Around nine steps, spaced perceptually rather than by even hex arithmetic — even arithmetic clusters everything in the middle and leaves the extremes useless. Carry a little of the tint through the whole ramp so it stays coherent.

3. 3

   Reserve the status colours

   Success, warning, danger, info. Fix them before the accent so you know what is taken, and never let a decorative element borrow one.

4. 4

   Choose the accent from what's left

   Now the field is genuinely open, because the neutral is doing the identity work and the accent only has to be distinct from the status set, legible in both modes, and tolerable for eight hours.

5. 5

   Define every role in both modes

   Not a palette — a role list. Background, foreground, card, popover, muted, primary, secondary, destructive, border, input, ring, and their foregrounds. Anything undefined gets invented per screen.

Every year brings a round of "SaaS palette trends" pieces, and they are not useless — they are a reasonable read on what currently signals contemporary. They are a poor basis for a product palette for one structural reason: a trend is by definition what a lot of people are doing at once, so adopting it is a route into convergence rather than out of it. The palette that read as fresh in January is the one three competitors also adopted by June.

The more durable version of the same instinct is to take the *neutral temperature* from what you like and leave the specific hues alone. A warm-neutral product does not date the way a specific accent does, and it is the layer nobody copies because nobody notices it is the thing doing the work.

Product UI is increasingly generated rather than drawn, and a generated screen fills every unspecified value with the model's default — which is the same default every other model has. We sampled 299 public DESIGN.md files, written specifically so a coding agent will follow them: 86% list raw hex values with no semantic role attached, and 54% contain at least one unmeasurable adjective, most often "clean" or "modern".

"Clean and modern" is not an instruction — it is a compliment, and an agent satisfies it with its median idea of clean and modern. Which is blue, on grey, with evenly rounded cards. A palette written as named roles with values in both modes changes that outcome in one file.