Education
Learning tools that adapt to the student in front of them, run on modest hardware and keep working when the connection drops.
Artificial intelligence, robotics and devices, built for the places where better technology measurably improves someone's day: classrooms, ecosystems, farmland, homes, and the hours people spend at work.
A teacher has no tool that adapts to a class of forty. A farmer guesses at what the soil needs. A river goes unmonitored until it floods. A building tells nobody it is failing until it fails. An administrator spends the afternoon copying numbers between two systems.
These are engineering problems. They are solvable with tools that already exist, and they are not where most of the industry has been putting its attention.
Trimvic works on them. The test we apply before starting is the same every time: we have to be able to name the person whose day gets measurably better — and afterwards, show whether it did.
The first four are where we think technology is furthest behind what people need. The fifth is the one that funds the others, and it follows the same rule: give someone their hours back.
Learning tools that adapt to the student in front of them, run on modest hardware and keep working when the connection drops.
Air, water and soil measured continuously, at a cost a municipality or a research group can actually afford.
Rugged, repairable devices that stay useful without a signal, priced so a smallholder can reach them.
Buildings and homes that report their own condition, so a fault is known before it becomes a failure.
The repetitive hours inside a company — quoting, invoicing, scheduling, reporting — handed to software, so the day goes back to the work that needs a person.
One team covers all four. That is the point: a device, the intelligence inside it and the software around it stop being three vendors' problems.
We are new, so we cannot point at a decade of case studies. We can tell you exactly how we decide, and let you hold us to it.
Connectivity is a luxury in most of the places we care about. We design offline-first and treat the network as a bonus.
Standard parts and documented designs, so a local technician can open it and fix it. Hardware that dies at the first fault is waste, not help.
We collect the minimum, keep it where it belongs, and never build a business on reselling it. Your data and your IP stay yours.
We agree in advance on the number that would show the work mattered, then report it — including when it disappoints.
So you know what you would be working with.
The year we started. There is no portfolio on this page because there isn't one yet, and we would rather say so than fill the space.
Disciplines in one team: artificial intelligence, robotics, hardware and software.
How long we take to reply, in business days. You will be talking to the people who build.
We are early. What we can offer now is direct access to the people doing the work and a clear account of what we can and cannot do. Projects usually start with a conversation, then one small piece of work with a fixed scope.
A classroom, a field, a river, a building, a process that eats someone's week — if you are responsible for something technology could genuinely improve, write to us. If we are not the right people, we will say so.