About
Written inside a working agency, not a boardroom.
Zawrix started as the system a licensed temporary help agency built to run itself. Every screen in it was built for a shift that had to be filled that morning.
Why it exists
Five systems that had never met.
An applicant arrived by WhatsApp. Their permit sat in somebody's phone. Hours lived in a spreadsheet, got typed into accounting software on Friday, and the invoice was built by hand from a third place. Every seam was somewhere a worker got paid wrong, a client got billed late, or an expired permit went on site.
Nothing on the market did the whole job. The tools that did part of it did not speak to each other, and the ones that claimed to be end-to-end were assembled from acquisitions and behaved like it. So the system was built to run one agency properly, and then built again to run any of them.
That is the entire claim. We are not going to tell you how many thousands of agencies use it or quote a percentage we made up. Ask for the demo and you will be shown the real thing, with real data in it, including the parts that are still rough.
What that actually buys you
The difference between a feature request and a Tuesday.
Software written for an industry from outside it gets the nouns right and the hours wrong. Everything below came from something going wrong in a real week, not from a backlog.
The board is grouped by start time
Not by client, and not alphabetically. At twenty to six the only question is who starts at seven, and every minute spent re-sorting is a minute not spent on the phone.
Blocked people stay on the list
Greyed, with the reason. A coordinator short one person is entitled to know that the only candidate left needs boots — a shorter list is not a more useful one.
Hours have four buckets
Regular, overtime, night and holiday, because they bill at four different numbers and a single total cannot be unpicked in March when a client queries January.
Documents refuse, they do not warn
An expired work authorisation stops a dispatch rather than raising a flag somebody has to notice. The failure mode of a warning is that it is read at 6:05.
The invoice freezes the client
Their details as they were on the day of issue. Renaming a company this March must not quietly alter an invoice sent last January.
Nothing is deleted quietly
Who placed whom, who verified which document, who changed a rate, who opened an account. The day you need that record you need all of it.
How we build
Three commitments, and what they cost us.
We do not build payroll. Remittance and year-end filing is a regulated domain where being 99% right is still a compliance failure. We prepare and export clean figures and hand them to something correct. It costs us a feature on a comparison chart.
We do not invent proof. No customer counts, no testimonials, no certifications we do not hold, no uptime figure. It costs us the part of a homepage everybody else fills with logos.
Isolation is not a feature. It is tested on every change by a suite whose only job is to try to break it. It costs us the speed you get from a single shared table.
Judge it the way we would.
Bring a morning that went badly and see whether this would have caught it.