Rethinking
software
transformation.
We are a product house building applications around context, set on foundational truths and prepared for the shapes of tomorrow.
Data entries were built before AI
Every tool you use was designed to file what you typed. A task is a string and a checkbox; a note is a blob of text. That was enough while a human was the one reading it back. It is not enough now. Point an assistant at that stack and it has to guess, and guessing is exactly what makes AI features feel like a toy.
So we are building software that makes the shift. Context is captured typed and joined at the moment something happens, which means there is no cleanup stage, nothing to reconstruct, and no pipeline to maintain. The data is already true. That is the difference between an assistant that talks and one that acts.
These are old standards, held to a new clock
We are in Portugal, where a wall is a few thousand tiles and a pavement a few thousand stones, each one set by hand. Nobody set them quickly. They were set to a standard, by people who expected to be judged on work that would outlast them.
We are keeping the standard and changing the clock. Everything we ship is held to that bar and shipped at a pace the craft never had to move at, because AI removes the part of the work that was only ever slow, not careful. Demanding about the result, impatient about everything else.
Where experiments
become products
Labs is where we experiment. The shortest path we know from a rough idea to something real, in production, carrying the Modus mark of quality. We believe that the final product is only as good as its first ideation.
One standard, applied across industries
We look for fields where an old standard is being carried by a slow process, and rebuild the process without touching the standard.
Every industry we look at has both. There is the part that earned its reputation, the judgement, the craft, the person who is accountable when it goes wrong. Then there is the scaffolding built around that decades ago: the handoffs, the re-keying, the waiting on someone to confirm something that was already true. The second one is not quality. It is habit wearing quality's clothes.
Software ideation is how we tell them apart. We take a process down to what is actually load bearing and rebuild everything else to move at the pace the tools now allow. Leaner, and still held to the bar it was built on.
A place to do your best work
A small team, few blockers, and decisions in hours rather than weeks. Everything about how we operate is on the join page, including what we look for.