We removed the colour amber from our software. Here is why.

Software has a colour it uses to make you anxious, and it is amber. The badge that says fourteen things need you. The banner that says storage is nearly full. The countdown that turns yellow as a renewal date gets close. It works, which is exactly why everyone uses it.

There is no amber in NearSync. Not toned down. Removed.

On its own that is a small decision. But it was the first of a series, and the pattern only shows when they sit side by side. So here are six decisions we took while building NearSync: what we decided, what it looks like in the product, and what it cost us. The costs are the honest part. Anyone can publish a list of values. The bill is what proves you paid for them.

1. No amber, anywhere

In NearSync, something genuinely broken gets a small rose dot. Everything else stays quiet. We allow ourselves exactly one flash of amber in the entire product: a warning toast that appears, says its piece, and dismisses itself. Nothing amber is permitted to sit on your screen and hum at you.

We did not start here. Early dashboards had traffic lights, the way almost every dashboard does. Taking amber out meant redrawing every dashboard, every chart palette and every severity scale around a simpler question: is this fine, or does it need a person. The middle state, the amber state, had to become words instead of a colour, because words can be read calmly and a yellow triangle cannot.

What it cost. Amber is the software industry's pressure lever. It hurries renewals, nudges upgrades, and inflates the feeling that a tool is indispensable. We gave that lever up, and we paid twice: weeks of design rework at the time, and an ongoing price ever since, because we cannot paint a deadline yellow to make you act on it. We think the trade is right. If someone spends eight hours a day inside a screen, that screen should not be allowed to raise their pulse for its own benefit.

2. Leave actually means leave

When leave is approved in NearSync, the person's calls stop ringing and their notifications arrive silently until they are back. Nobody toggles anything and nobody has to remember. The system knows they are away, because the leave request lives in the same system as the phone that would have rung.

What it cost. Every communications product loves the sentence "reach anyone, any time", and we cannot say it. Buyers have asked whether a manager can override the quiet for something urgent, and the answer is no. Not every buyer has liked that answer. It also cost real engineering: leave had to be threaded through the calling stack and every notification rule, weeks of work that shows up on a feature list as nothing at all, because the feature is an absence.

3. Breaks are part of the work

The home screen of NearSync greets you with rings, and one of them is Vitality: did you take your break, did you book focus time, did you speak to a colleague today. It sits beside the rings that track output, at the same size, in the same place, every day.

What it cost. The home screen is the most expensive space in any product, and every department would like a piece of it. We spent a permanent share of it on a measure that no procurement checklist has ever asked for, and to a certain kind of buyer it reads as soft. We kept it anyway. The alternative is a home screen that says the only interesting thing about you is your output, and we do not believe that.

4. Nobody is monitored

There is no screen recording in NearSync, no keystroke counting, no screenshots on a timer. Not switched off by default. Not available. We measure work by what got done: the deals that moved, the invoices that went out, the tickets that closed. The same rule holds inside our own company. We are remote first, nobody watches anybody work, and productivity is the only thing we track.

What it cost. Employee monitoring is a real market with real budgets, sitting directly beside everything we sell, and buyers do ask for it. Each time, we are declining revenue on purpose. There is an engineering cost too, and it points the wrong way round: a screenshot timer is a week of work, while showing output honestly takes a system where the work actually lives. We built the harder one.

5. One price, and nothing held back

Every department in NearSync ships in every plan. Sales, finance, people, projects, support, all of it. The difference between our $25 seat and our $35 seat is AI usage, 2,000 credits against 4,000, where one credit is one question to the AI. That is the whole difference. There is no feature waiting on the higher tier, and when something new ships, it ships to everyone, including the seat paying the minimum.

We decided this after a year of building, at the moment the draft tier sheet was in front of us. Cutting a finished system into rations felt wrong, so we did not do it.

What it cost. The expansion ladder. Most software companies grow their revenue by gating features and selling the gate: the upgrade email, the greyed-out button, the tooltip that says a better plan exists. That machinery reliably prints money, and we walked away from it. Our revenue grows only when a customer adds a person or asks the AI more questions, which means it grows only when they are getting more out of the product. We are fine with that being the only way up.

6. We say the limits out loud

The compliance badges on our own website say "under way". Not a wall of acronyms, the true state, published. The same habit runs through the product: we state what a thing does not do yet before you have to discover it yourself.

What it cost. Tenders. A procurement filter that wants the badge this year drops us before a human reads a word. Sales conversations sometimes open with what is not finished, which no salesperson would choose. We believe the cost runs the other way over time, because the customer who buys from an exact company stays, but we will not pretend the invoice never arrived.

What the six add up to

Read them together and the pattern is hard to miss. Each decision trades a lever that is known to work, urgency colour, constant reachability, monitoring, feature gates, badge walls, for a system we can look at without flinching. Software teaches people what their company thinks of them. It does this every day, in small print, whether anyone intends it or not. We would rather ours said: your attention is yours, your evenings are yours, your break counts, and what you build here is judged by what it does.

The plain version of what we are building is one system for every department of an emerging company, with AI through all of it that asks before it acts. That is the plan. Underneath the plan is the belief this whole post has been circling: the hours someone spends inside a work system are hours of their life, and the system should behave accordingly.

Everyone near, everything in sync.