Skip to content
Blax Blax Group
End-user · UX

We build for the morning user.

The person who chooses a tool and the person who uses it at 8am every workday are usually not the same person. The first signs the contract; the second lives in the software. We optimise for the second.

A wooden desk with a typewriter and a lamp under a window looking onto green trees.
Fabian Wagner, founder of Blax Software

Fabian Wagner, founder of Blax

Published

Who we optimise forThe morning user
For the buyerExactly enough
Pre-launch QAWe watch real users

The split between buyer and user

In B2B software the split is the norm. An IT manager evaluates the system, signs the contract, and goes back to running IT. A warehouse worker, a dispatcher, an accountant, a teacher then spends the next two thousand hours of their working year inside the thing. The buyer's checklist of features is satisfied at signing; the user's daily friction starts on go-live and never ends. A vendor that only optimises for the buyer wins the deal and loses the relationship by year two.

What this changes in our work

Error messages that say what went wrong and what to do, not codes that mean nothing without the manual. Forms that remember their state when the network blinks. Lists that scroll to the row you just edited, not the top. Keyboard shortcuts on the views people use ten times a day. A "do not show this again" that is actually respected. None of those is exotic; all of them are extra work nobody pays for if you decide the buyer is the audience.

How we test for it

Pre-launch QA is not just us clicking through the screens. Where possible, we sit with one of the people who will use the software every morning, and we watch. We do not lead the demo; we open the screen and see what they do. The five minutes where they hover the wrong button, the eight where they miss a status indicator, the second where they realise the search does not include archived items: every one of those is a fix in the next sprint.

Why this is also good business

The user who has to live with the software is the one who will fight for or against your tool when the next contract renewal comes up. The user who says "this thing is the only reason I get my work done by five" is your champion. The user who reaches for a workaround twice a day is your future churn. Building for the morning user is the long-game version of building for the buyer.

Where you can read the work

It shows up in subtle places, not in slogans. The contact form on this site validates as you type, recovers your draft on reload, and tells you exactly which field still needs attention; we built it that way because we would have wanted it on the buyer side of someone else's contact form. Every Blax project gets the same level of attention to the actual using-it part. See the broader process for how that lands in practice.
The buyer's checklist is satisfied at signing. The user's daily friction starts on go-live and never ends. Pick a side.
Why we build for the morning user

More perspectives

Engineering

Why we build WebSocket-first

Guide

PHP 8.2 end of life: move WordPress to PHP 8.4 without the critical error

Guide

Hacked WordPress: the first steps

Guide

What a security check covers, and what it does not

Guide

Website relaunch: when it pays off and how existing URLs keep working

Guide

WooCommerce or Shopify for an Austrian shop

Guide

Accessibility in online shops: what applies since June 2025

Operations

Docker by default, Traefik on top

Operations

Linux everywhere

Business model

Open source by default

Workflow

How we work with AI

Trust

Every minute, with a note

How we engage

Built with startups

Curious how this plays out in practice?

These essays are the why. The how shows up in the projects we ship. Drop us a note and we can talk about your specific case.

Build with us Perspectives