Why we do what we do

When people ask what we do, the usual answer is "we build AI platforms." That is accurate, and it tells you nothing about why we exist. Here is the thinking behind Intric, and why it shapes what we build.

It starts with an observation. Giving an organisation access to AI is now the easy part. A secure assistant can be bought, a model connected, and staff given access in an afternoon. Access on its own changes nothing. A person with a new tool often still does the job the old way. A team with a new way of working does it differently on Monday.

Where the time goes

Picture an organisation with 300 caseworkers. Each one saves five minutes a day thanks to a good assistant. That sounds modest, but it adds up to 1,500 minutes, or about 25 hours, every single day. On paper, that is a big win.

Now look at the queue. If a case still takes three weeks to reach a decision, where did those hours go? Usually into small pieces nobody measures: an extra check, an email chain that was not needed, a handover that takes a week because nobody knows who owns the next step. The time burned off somewhere in the process.

Saved time matters only for what it becomes: shorter queues, clearer records, fewer unnecessary handovers, more room for judgement. If we cannot show that in the work, we have shown nothing, however many users we have.

Change starts close to the work

The person doing the job usually sees the problem first. A caseworker notices a step that serves no purpose. A planning team knows exactly where a handover costs a week. An operations group knows which information always goes missing when something breaks at three in the morning.

That knowledge is valuable and fragile at the same time. It lives in a person, a pilot, a spreadsheet, a script, or a department that never gets around to making the practice durable. When the person changes jobs, the pilot ends, or the supplier project closes, the knowledge leaves with them.

Intric is built for exactly this gap. We want local knowledge to become institutional capability: something the organisation can own, govern, measure, change, and reuse.

Some will say this sounds like consulting in new packaging, and they have a point. We have not always avoided that trap, and we will get things wrong again. Our aim is still clear. The institution keeps ownership. We build with the operation, because the operation knows the exceptions and the judgement calls, and it knows the difference between a polished demo and something people can actually use on a bad day.

Sovereignty is the ability to act

Sovereignty is easy to reduce to a question of server location. That question matters, and security and procurement teams are right to ask it. For us, it is where the conversation begins, not where it ends.

A system is not really sovereign if the institution cannot see what happened inside it, cannot change the procedure, cannot move away from the supplier, or cannot keep the work running when conditions shift. Uptime, failover and dependencies decide whether a municipality, a university, or a defence unit can keep doing its job.

So we mean something practical by the word. Sovereignty is the ability to keep acting under your own authority.

A home for new ways of working

I like the image of a pilot as a tent. It is a good place to try something out. Anyone who plans to stay for years needs a house. New ways of working are the same. They need a stable form: security, responsibility, records, measurement, and room to change. Without that, they stay in tent mode, and once the tent is packed away, nobody remembers how it was pitched.

That is the reason we do not see the platform as the goal. It exists so new work has somewhere to live, a place that outlasts the pilot, the project, the supplier, and the local champion.

What we promise

We build it together. We run it. You own it.

We build it together because the work cannot be understood from the outside. We run it because institutions need environments that work as well on a Tuesday in February as on a Wednesday in October. You own it because institutional capability should never depend on a supplier's goodwill.

Why this matters

People in public institutions usually want to do the right thing. They are glad to share their best tricks when they have time, a sense of safety, and someone willing to listen. What they rarely do is hand over something they know how to do without knowing who will look after it next. Keeping it to themselves is a reasonable reaction to how institutions work.

Our job is to make sharing easier while control stays where it is. The pattern travels. The data stays home.

So the next time someone in another department faces the same problem, they should not have to start from zero.

David Wallén

CEO, Intric