We build the systems businesses end up depending on.
Software engineering for systems you have to be able to trust. We are AI-native: we build with AI, and we build the deterministic checks that catch it when it is wrong. The engineering that comes after the prototype.
Most of our work starts with something that already exists.
A dashboard someone built in a week that six teams now open every morning. A spreadsheet that quietly became the system of record. A platform that has outlived the assumptions it was written under.
Those systems are usually not broken. They are just not ready for the number of people now relying on them, or for the data that is now inside them. The work is making them ready: establishing who is allowed to see what, making the numbers agree with the system of record, and building a path off the old thing that does not require a weekend and a prayer.
How we work
We do not ship what we cannot back.
On one platform we removed a set of half-built screens rather than leave them disabled, because a user could fill them in and nothing was saved anywhere. That rule is enforced by a test, not by good intentions.
We make disagreements visible.
When two systems report different numbers, the honest output is an itemised list of the differences, not a single figure that hides them. What we cannot match, we never quietly fold into a total.
We do not guess on your behalf.
A decision that is genuinely yours gets escalated to you with the options laid out, rather than answered by a model. Where a model produces a number, ordinary code checks it before anybody sees it.
We will not quote you a figure we cannot trace.
No uptime number we have not measured, no percentage improvement we cannot show you the arithmetic for. Every number on this site traces to a repository, and you are welcome to ask which one.
Who you work with
A small senior team. The person who scopes your system is the person who builds it. There is no bench behind us and nobody you get handed to after the kick-off call.
The homepage carries five marks under Who we've worked with, and two of them are not clients. Stated plainly, so nothing on this site has to be read charitably:
Arbor Lodging, Aspire and Com-Sec are clients.
Work we were engaged to do and delivered.
Deloitte and MasterClass are past employers.
Win Raguini, Founder & Lead Engineer, was previously a Senior Consultant at Deloitte, and was Founding Engineer and later Director of Engineering at MasterClass, where he helped build and scale apps used by millions of learners. Those are places we worked, not companies that hired WinLabs.
The three of us, with our roles, are on the Team page.
Have something that works, but not something you would trust yet?
Bring the prototype, the spreadsheet the business quietly runs on, or the platform you cannot turn off. Thirty minutes, technical, no deck.