Where are you right now?
Pick whichever one sounds most like your challenge, because that's what decides where we start.
You're building something new
You have hardware that could be talking to something, and nobody in house who speaks both sides.
Or an existing product you want connected, and no idea yet what that costs or how long it takes.
Start with Product Definition
It's built, and it has to go further
You built the platform and the adoption never came.
Installation quality in the field isn't where the market expects it, and the same support calls keep coming back.
Start with a diagnostic
One thing needs solving
Pairing has been unreliable for a year, or the platform is slow enough that people feel it.
Every new feature costs months.
Go straight to build
Not sure which one?
Ask us, and if it turns out to be none of the three we'll say that.
Ask your question
We're an extension of your team
We are a partner when building the products. We work in your technology, on your repositories, at your pace. And we push back when something needs it.
The technology is a decision we make together. You can read our source code, and the IP is yours.
We can build on top of what you already have, legacy included.
You only have engineers in your team? No worries, we can help you with the UX and design part.
Everything we know, in one framework.
We apply this for every layer
AI & Intelligence
It runs on the device itself. A local model, the manuals already sitting on the machine, and an agent that can only ever reach one user's data, never everyone's. For the person holding the product that means an answer in the moment, in their own words, instead of a manual or a support call.
Security & CRA
Splitting the data per user is what makes privacy, GDPR and the CRA manageable, and that split gets decided when the architecture does, which is the only point at which it is cheap.
UX & strategy
Every workflow starts with the end user in mind, which shapes how information gets found, how actions are taken, and where AI fits into the job.
The stack we know best
Yours may well run on something else, and then we work in yours.
Touch
Flutter or KMP as our default, because it proved itself stable in production. Native iOS and Android where that's the better answer.
Web
Nuxt and Vue, for dashboards, back office, and the portals installers, dealers and end users log into.
Backend
.NET as our base, with Python where AI comes in or NodeJS where it fits. That covers cloud architecture, integrations and the data pipelines underneath them.
Connectivity
MQTT from the device to the backend, then REST, GraphQL and WebSockets for anything that has to be live. Also local connectivity like Bluetooth, NFC, WiFi direct, Modbus TCP, Canbus are protocols we master.
Let's start
Product Definition
We make from your idea a plan you can act on: concept, blueprint, roadmap and budget, all of it before a line of production code gets written.
More about product definition
Connected Product Diagnostic
We analyse what you already have and advise on how to make it better. Most firms sell you a technical workshop and a UX workshop, but your product doesn't split that way, so neither do we.
More about diagnostic
Straight to Build
The pairing problem on Android, the platform that slows everything down, the release that takes months, or a redesign that never got done. One scope, agreed up front, at a fixed price.
More about straight to build
Not sure which one you need?
When you describe what's in front of you in a few lines, we can tell you which of the three fits, or if it's none of them.
How others started
A startup with nothing built and a deadline from their investors. We went straight to build.
In the App Store in under 3 months, pre-seed raised.
Read Sumura case
They had built the platform and the adoption was slow. We started by taking apart what was there.
Rebuilt from zero in under a year, from low adoption to daily use.
Read Atlas Copco case
Firmware that had to update on devices with no internet and no 4G. One problem, clearly scoped.
From idea to MVP in 6 months.
Read Locinox case
An Access database holding a field operation together. We started with the operation, not the database.
From 20 to 40 stops per driver, and 40 to 700 employees.
Read Quatra case
Privacy and security get decided when the architecture does
Read our security documentation
The Cyber Resilience Act is coming for nearly every connected product. We've worked under strict regulation for years.
European engineers you can actually talk to, which usually means the person who wrote it is the one who picks up.
71% of European OEMs say privacy and security legislation constrains them. Source: IoT Analytics.
The questions you're going to ask anyway
Do you do the hardware too?
No, and that's a choice. We advise on chips, communication and encryption. We don't design the electronics, and we work with people who do. Hardware design is one of a handful of things we keep outside the house, alongside branding, hosting and first-line support. Ask and we'll tell you who we would bring in.
Why you, and not a local agency?
Most people are looking for someone who has already seen a device fail in a way that makes no sense. Pairing that works perfectly on the bench and then falls apart in somebody's kitchen. A firmware update that has to reach a device with no internet and no 4G, which sounds impossible right up until you've done it.
That's a much shorter list of companies. In Europe, quite short. The distance question comes up a lot and we understand why, but it matters less than people expect. We work across Europe from Belgium and we can be at your site within a day.
Couldn't we just build this ourselves, with AI?
Maybe. We're not going to pretend AI can't write the code. We use it every day and it's genuinely good.
The part that gives us pause is everything the model doesn't know yet about your particular device. Commissioning flows. Bluetooth edge cases. A unit that drops off the network in the field and has to recover on its own, with nobody there to help it. None of that shows up in week one. It shows up around month four, when everything works on a desk and very little works at a customer site.
So build it yourself if you have the people and the time. Some companies do, and it works. What we usually get called about is a different problem: the platform runs, the engineering is solid, and adoption just never really arrived.
Who exactly will be working on this?
A team. An actual one, not a rotating set of profiles. We run three cross-disciplinary teams, each with a strategist, a UX designer, developers and a project manager. You get one of those three, you meet them, and then you keep talking to the same people.
The fair follow-up question is what happens when one of them leaves, because people do leave. That's why we've spent years moving the experience out of individual heads and into how we work. It isn't a perfect answer, but it does mean the project doesn't stall because one person's calendar changed.
Not ready to ask yet?
Fair enough, take whichever of these answers the thing that's still open.
Read it