Seamless is a security requirement

Every industrial company has a system nobody uses.

It was bought for good reasons. It solves a real problem. And somewhere between the procurement decision and the shop floor, it became one more thing standing between a technician and the end of their shift — so people worked around it, filled it in on Friday from memory, or quietly stopped.

We have all seen it. And it is why we think the most important word in what we build is not secure, or intelligent, or even useful. It is seamless.

That sounds like a design preference. It is not. It is the condition everything else depends on.

Nothing works if it is not used

The argument for capturing operational knowledge is straightforward: the expertise that makes a site run well is trapped in individual heads, and it should belong to the organisation.

But none of that happens in a system nobody opens. There is no knowledge base without capture. No collaborative advantage without knowledge. No safer, faster onboarding, and nothing of your own to teach the machines that will eventually work alongside your people.

Adoption is the gate every other benefit sits behind. And adoption is not won in a procurement meeting — it is won or lost in the first week, by whether the person wearing the device finds their day better or worse.

So the bar is not "acceptable". If a technician would not choose it, it does not matter what it can do.

What seamless actually means

The word gets used by everyone, so it is worth being concrete about what we hold ourselves to.

Two seconds to start. That is the whole interaction cost. You put it on and begin working. Two seconds invested at the start of a job, against hours saved later — by you or by whoever does this next.

Nothing afterwards. No form, no write-up, no logging what you did once you have finished doing it. The capture is the record. For most technicians this is the part that sells it, because it removes something they already dislike rather than adding something new.

It works for you while you work. This is the part people do not expect. Because the system is already there, with your hands busy and your phone in your pocket, you can simply say what you need: make a report of this. Send a message to the site engineer about the worn bearing. Remind me to check this fitting next week. Log the part number I just read out. Things that would otherwise wait until you are back at a desk — and often never happen at all — are done by the time you walk away.

That is the difference between a system that observes you and one that works for you. Only one of those gets worn voluntarily.

You stay in control, effortlessly. A work day is not only work. Colleagues talk about the weekend, about family, about things that have nothing to do with the job — and that should stay exactly as it is. Pausing audio takes a moment. So does saying "ignore the last minute" when something has been caught that should not be kept. Recordings are shared by default, because that is how knowledge compounds and how a colleague on the night shift finds an answer without phoning you at home. But making one private is a single instruction, and it stays private.

The important part is not that these controls exist. It is that using them costs nothing and they work every time. Control that takes effort is control nobody uses.

Why this is a security position, not a comfort one

Here is the connection people miss.

A system that is awkward does not simply go unused. It gets routed around. Work gets recorded on personal phones, notes end up in private messages, procedures are shared in whatever channel is convenient. The knowledge does not stop moving — it just moves through paths nobody controls, on devices nobody manages.

Friction does not prevent that. It causes it.

So when we say seamless, we are describing the same property from two directions. The version that gets used is the version that is secure, because it is the only version where sensitive operational knowledge stays inside a system with actual boundaries around it — where the company owns what is captured, where it is not being quietly used to improve anyone else's operation, and where the people who created it can see how it is handled.

Seamless is not the opposite of rigorous. It is what makes rigour real.

Why us

There is a fair question behind all of this: why trust a company with something this close to how your business actually works?

The honest answer is that you should not trust it lightly, and we would not expect you to. What we can tell you is who is building it and what we have built before.

We are three founders. Two of us are mechanical engineers who have spent our careers with field workers and industrial operations — long enough to know what happens to any tool that adds a step to a shift; one of the two also comes from industrial software and knowledge-based engineering, where the whole discipline is capturing how expert work is done and handling that knowledge responsibly. The third is an industrial designer who previously helped build the world's smallest IoT sensors, where being unobtrusive was not a feature but the entire product.

We are Norwegian, with industrial roots, and we have deliberately built the company here. That shapes the standard we hold ourselves to on how people's work is captured and how it is used.

And it shapes our principles, which are short enough to state plainly. Your data is yours. What your people create is never used to improve a competitor's operation. All the value it produces flows back into your organisation. And the system has to take work off the people who use it.

Those are not policies bolted onto a product. They are the reason the product takes the shape it does — because a system that asks people to give up control of what they know, and makes their day harder in exchange, does not deserve to be used. And it would not be.

— Marcus Horn, CEO & Co-founder, dotspot