What can I help you with?
Six disciplines for companies, municipalities and founders. I build all of it myself, from the first sketch to operations.
- AI agents
Which task do you want off your desk?
AI that does a real job. It reads, checks and answers, and asks a person when it matters.
Applications, customer questions, privacy and internal knowledge.
- Automation
Routine work that runs itself.
The routine work runs on its own in the background.
Documents, reports, imports and systems that do not talk to each other.
- Security
Find the holes before someone else does.
Security testing and penetration testing of apps, APIs and AI features. Black, grey or white box.
Companies with systems in production, and founders who built with Lovable, Cursor or Bolt.
- 3D and visualisation
Let people see it before it is built.
Let people see it before it is built.
Renovation, property, interiors and products.
- Apps and websites
From idea to the App Store, and kept running.
From the first sketch to the app in the store, and kept running after.
Founders, companies and the public sector.
- Games and campaigns
Make people want to join in.
Quizzes, rebus walks and live maps that get people involved.
Municipalities, festivals, museums and brands.
Why one person
Most projects need several of these at once.
An app needs a server, the server needs security, and somewhere along the way a task turns up that an agent could take. When the disciplines sit with different suppliers, the handovers are where things go wrong.
I build, automate and test myself. Nothing gets lost between suppliers, and what I learn from looking for holes in other people's systems goes straight into what I build.
When no ready-made solution fits
And what fits in none of the boxes.
Some problems do not belong to one discipline. A home that has to be measured with a phone. Thousands of heritage sites that should become readable texts without a single year being wrong. An AI that must answer correctly about privacy, not just plausibly.
They are rarely solved with something entirely new. The technology usually already exists, and the job is seeing what it can actually do and putting the pieces together in a new way. I start with the problem, not the request, prove the idea at small scale, and say so if there is no clever way.
You do not need to know whether it is called an agent, an automation or an app. Tell me what is hard.
How it works
How we work together.
- 01
You tell me what you want to achieve.
An email or a chat. Half-finished thoughts are fine.
- 02
I reply within a day.
With questions, a first idea of how it could be solved, and an honest answer on whether I am the right person.
- 03
We start small.
Often with one task or one part of the product, so you see it work before we build on it.
- 04
You see everything along the way.
You get to try what is being built the whole way, not just at the end.
- 05
It keeps working.
I stay on after launch, so it is kept up to date and secure.
Common questions.
What does it cost?
It depends on what is being built, what already exists and how much has to work with other systems. After a first conversation you get a concrete proposal, so you know what you are saying yes to before anything starts.
Do we need our own IT department?
No. Most of the people I work with have no developers of their own. I handle the technical side and explain the choices in plain language, so you can make the decisions.
Who is behind this?
Michelle Sæther, CTO and co-founder of Link Utvikling in Bergen, Norway. Projects are delivered through Link Utvikling.
Do you only work in Norway?
No. I am based in Bergen, but I work with clients across Norway and abroad. Most of it can be done online.
What is the problem?
Tell me what you want to achieve, even if it is only half thought through. I reply within a day.