The daily experience

Nobody uses procurement software for ten minutes.

A buyer works in it from nine to five. So the real questions are simple: Is it easy on the eyes all afternoon? When it says no, does it say what to do? Can you reach the people who built it? Everything on this page is in the product now.

Three palettesLight, dark and a low-strain green. Switch from any screen. Remembered per person.

No default themeUntil you choose, Atlas follows your computer's own setting

Measured, not guessedMain, body and muted text pass WCAG AA contrast in all three

One-way line to usSend a note to the people who build Atlas, from any screen. No ticket, no reply expected.

Three palettes

The same screen, the way your eyes like it.

One button in the corner of every screen. Not buried in admin settings. How your screen looks is your choice, so no administrator sets it for you.

These are the real controls — press one

The Atlas dashboard in the light theme: a navy sidebar beside a white workspace.

Light Navy navigation, white workspace.

One screen, one set of data, captured three times. No mock-ups, no colour filters.

It follows your computer

Atlas has no default theme. Until you choose, it follows your computer's setting. If your computer runs dark, Atlas opens dark on first sign-in.

It is remembered, per person

Your choice is saved in your own browser, not the company account. Each person, on each browser, keeps the palette they chose.

Green returns you where you were

Turn green off and you go back to the theme you had before. Work in dark, try green, and you get dark back. No white flash.

The low-strain palette

Easier on the eyes. Here is exactly why.

A lot is claimed about screen colour and eye health. Here is what this palette does, and what it does not.

What it does

It takes the glare out.

What has real evidence behind it is brightness. A big bright white screen tires the eyes over hours. So does pure white on pure black. This palette sits in between. It gives off about a fifth less light than the white theme, measured on the same screen.

Our first try was only about 1% dimmer. It looked greener but did nothing. That is how we know brightness is what matters.

What it is not

It is not a medical claim.

No screen colour treats anything. If your eyes hurt at the end of the day, the advice is still breaks, distance, blinking and room lighting.

Green helps for a smaller reason. The eye is most sensitive near 555 nm, which is green. So green looks brightest for the least light. That effect is small. The dimming does the real work.

Legibility

A dimmer screen that is still readable.

A darker background makes pale text harder to read. So every text colour changes with its background, and we measure the result. WCAG AA asks for 4.5:1 on body text. These are today's ratios.

Text	Light	Dark	Low-strain green
Primary headings, figures, names	15.6:1	13.9:1	9.7:1
Secondary body copy	7.9:1	8.9:1	6.2:1
Muted labels, hints, timestamps	5.3:1	4.9:1	5.8:1

Each theme's text colours, measured against that theme's panel colour. The AA minimum for normal text is 4.5:1. The muted row matters most, because it fails first on a darker background. An automated check blocks any palette below it on every release.

Your workspace

It should look like your company, not ours.

Upload your logo. It shows in the top bar of every screen and on your sign-in page, beside your company name. Your administrator adds it in your own settings. It is your brand, so you set it.

It sits at the end of the bar, after a thin line. It does not replace our mark. Two companies, one toolbar.

The file is checked properly

Atlas checks what the file really is, not its name or what the browser says. SVG logos are refused. An SVG can carry code, and everyone in your workspace sees the logo.

It is stored with your data

The logo is saved in your workspace's own database. So a restore brings it back too.

Guidance in place

The manual is on the screen that needs it.

"What do I do here?" comes up mid-task. Nobody stops to open a manual.

A panel, not a page

Help for the screen you are on opens beside your work, and closes again. It fits that screen and your role. An approver and a requester on the same page see different help.

Search that reaches everything

One search box at the top. Press / from anywhere. It searches requests, orders, contracts and suppliers at once, so you don't pick a list first.

Written for people who did not buy it

The person raising a request did not choose this software. The help is written for them, in the same words the screens use.

When it says no

A refusal with no reason looks like a broken system.

Most business software just says "invalid input" or shows a blank page. You can't tell a rule from a bug. Atlas has one rule: every refusal says what was wrong, what the limit is, and what to do next. A test fails the build if any page refuses silently.

What you usually get

Invalid file.

Is it the size? The format? Did it even upload? You have to guess.

What Atlas says

That image is 2,480 KB against a 512 KB limit. A logo this large is usually a photograph or a print-resolution export; save it for screen use and it will be a fraction of the size.

The real number, the limit, and what to do. No guessing, and no need to ask us.

It matters most for suppliers. Picture a supplier uploading a 45 MB tender document and getting back no file and no message. Mid-tender, they would think the system lost their bid. That is a dispute, not an annoyance. So a test enforces the rule.

Telling us things

Two buttons, for two different things.

Both are on every screen. One opens a support ticket, with a reference, a status and a person who replies. The other sends us a note. It gets no reply, on purpose.

A ticket feels like a big step. So small ideas, like "sort this list by date", often go unsaid. The note is a lighter way to tell us.

Support

Something is wrong, unclear, or a number looks off. You get a reference. Your screen and version are captured for you. Somebody replies.

Feedback

An idea, an annoyance, or something that works well. It goes straight to the people who build Atlas. No reference and no reply. The form says so before you type.

Every note is read. Notes are a large part of what decides what we build next.