‍
Services \ Step 1 · Clarify

Where AI can
make a difference \

01

Step 1 · Clarify

We turn your goals into concrete opportunities and give you one clear recommendation, with a basis for the decision that you can stand behind.

Where does it make sense to start with AI? And how do you explain the choice to the board, the executive team or the team? We help you get the groundwork in place, so you can make a decision.

We start with what you want to achieve: lower costs, better service, faster development or something else. Together we assess where AI can help and what it takes in terms of data, systems and people. You get one reasoned recommendation. Also when our advice is to wait.

Five questions we help you answer

  1. Where can AI support our strategy?

    We go through your goals, workflows and data with the people who know the daily work. We look at where AI can save time, improve the service or create new opportunities, and what it takes to get started.

    You get A prioritised list of initiatives for management to decide on.

  2. What do we do first, and what do we leave?

    In 2 to 3 weeks we go from "we need to get started with AI" to a concrete recommendation. We talk to the people who will use the solution, map the starting point and assess the alternatives, including those that need no new development.

    You get One recommendation with reasons, scope and next steps.

  3. Are our systems and data ready?

    We go through your code, architecture and data and assess what can be built on and what needs to be in place first. If a system has become hard to change, we recommend a way forward: gradual modernisation, running in parallel or replacement.

    You get An assessment your own people and your suppliers can work from.

  4. How do our developers get more out of AI?

    In our own development, agents build in tools such as Claude Code and Codex while people describe the tasks, review the code and approve the changes. We help your team adopt the same way of working, with knowledge documented in the code base, automated tests and clear agreements on approval.

    You get A way of working that is set up in your own code base and tried on real tasks together with your team.

  5. How do we manage access, responsibility and risk?

    Who may read which data? What is logged? And who approves changes? We help you settle it and plan a separate layer for access control that your own people are in charge of. That also lets you change model later.

    You get An architecture and a set of rules that you own.

    See how we work with security and guardrails

What an engagement can consist of

Workshop with management

Review of strategy and goals

Interviews with employees and users

Mapping of workflows and data

Review of code and architecture

Assessment of alternatives

Business case

Recommendation and plan for the next steps

A sound basis
for your next decision.

Understand the problem before you choose a solution.

We examine the problem together with you and challenge the assumptions. Our own too.

Get one clear recommendation.

You get our view of where you should start, and why.

Get an honest answer.

Sometimes the best advice is to wait, to buy something ready made or to leave it.

Decisions you can stand behind.

A basis that makes it easier to explain the choice and bring the organisation along.

From our work: Det Danske Spejderkorps

The first step was a small experiment.

Det Danske Spejderkorps, the Danish scout association, wanted to clarify how IT could support scouting before investing in a new architecture. We began with a study among volunteer leaders across the country. The recommendation was to try one idea first: a meeting planner with AI, built in a few days without changing the existing system.

Tell us what you want to achieve.

Then we talk about where AI can make a difference for you, and where it makes sense to begin.

Contact us

"We want to understand the problem before we recommend a solution. So we ask questions, challenge assumptions and give you advice we can stand behind. Also when the advice is not to build."

Mads Hofman, CEO