Systems for humans.
If you're going to spend your day inside a tool, the least it can do is not drain you.
If you're going to spend your day inside a tool, the least it can do is not drain you.
Four projects at different stages. Each one moves at its own pace and solves a different problem.
We hunt for inefficiencies in the crypto market by cross-reading what happens in options against what happens in spot. When the two sides don't line up, there's usually something worth reading.
Connects suppliers with public-sector organizations actively buying what they sell. Built so you stop scanning government procurement portals by hand.
A project for digital art and playful experimentation. The space in the lab where the main material is the image.
For writing your investment theses as a tree. A root idea at the top, and the concrete positions that branch out from it underneath. When the market moves, you go back and ask whether the thesis still holds, or whether you're just defending a branch.
Function and aesthetics don't have to compete. A system can be powerful without turning hostile to the person using it.
Productivity depends on mood and attention, not only on the features a system ships. The best ERPs on the market are extremely useful for companies and, at the same time, leave their users eight hours a day in front of interfaces that ignore that fact. That friction is where StentorLabs starts.
Building for humans means making things that are beautiful and also work, and respecting the user's intelligence: handing over information so they can decide, instead of pushing them toward a conclusion. We don't use design to manipulate; we use it to avoid mistreating people. A slow, confusing or insecure system mistreats whoever uses it too, so the technical side isn't a separate topic from human experience.
Small team operating from Santiago, Chile. Whatever ships from here is something we would use ourselves.