Question 1

What cannot be automated?

Accepted Answer

Anything that takes a judgement or a decision stays with your people. The automation takes the repeated part, not the part that needs an assessment. It takes over lookups, data entry and fixed steps, while a person still makes the calls that cannot be reduced to a formula.

Question 2

What happens to the people whose work gets automated?

Accepted Answer

The automation takes the routine, not the people. The hours that used to go on data entry and lookups, your employees spend on customers, sales and the tasks that need a judgement. In practice it usually frees people up for what they are good at, and that is often what makes growth possible without new hands.

Question 3

Do we have to change systems to get things automated?

Accepted Answer

It rarely takes new systems. We build the automation on top of what you already have, and start with the task that fills the most and is most predictable. That way you see the effect in one area before we build further, instead of rearranging the whole operation at once.

Question 4

What does it cost, and how do we get started?

Accepted Answer

You start with a half-hour conversation where we narrow the problem down. If it needs working through properly, we run a digital pre-project: two to three weeks at a fixed price, agreed before anything is set in motion. The fee is offset against the first stage if you build on within 90 days.

Question 5

How long before we feel an effect?

Accepted Answer

The pre-project itself takes two to three weeks and gives you a basis for deciding straight away. If we build, we build in stages, so you often see the first effect within weeks rather than months. We take whatever weighs most first, so the gain arrives early.

Question 6

What if it does not work, can we stop along the way?

Accepted Answer

You can stop after each stage. Because we build in stages, you are never left holding half a giant project, but something usable that works on its own. If a pilot shows the gain is not there, we say so, and then you have not spent a large budget finding out.

Question 7

Do we own the code and our data afterwards?

Accepted Answer

You own the solution we build for you and the data it runs on. If we use our own reusable modules to keep the price down, you get the right to use them, and we say clearly which is which. We document the work, so your own team or another supplier can carry it on.

Question 8

You are a smaller agency, do you fit our size?

Accepted Answer

We work both with large organisations such as Bygma and Nykredit and with smaller companies where one solution moves a lot. We document what we build, so it can be handed over and run without us. If we get busy, we are honest about the timeline rather than promising something we cannot keep.

We are drowning in manual, repetitive work

It is rarely one big job. It is a hundred small ones

How we start, without you committing to anything big

Clarification meeting

Digital pre-project

Development in stages

We decide exactly what is needed together

This is what it looks like once it is solved

Digital driver app streamlines Bygma's delivery processes

Frequently asked questions