Question 1

Is custom not expensive and risky?

Accepted Answer

We build in stages and start with a digital pre-project, so you see the business case and the plan before you commit properly. You can stop after each step, so you are never left holding half a giant project, but something usable that works on its own.

Question 2

How do we start without building everything at once?

Accepted Answer

We begin with a narrow first version, an MVP, that solves the most pressing part first. You put it into use early and see value before the rest is built on. That keeps the risk small and lets us correct course along the way, instead of waiting for one big finished system.

Question 3

What if our process changes after the system is built?

Accepted Answer

We build so the system can change with you, because a process that stands still is rare. Because it is built around how you work, it is also easier to adjust as the way of working develops. You own the code and can build on, either with us or with your own people.

Question 4

Why not just adapt a standard system?

Accepted Answer

If a standard system fits closely enough, we gladly recommend it, because then you should not pay to build from scratch. But when the unique part of your process is exactly what makes you competitive, standard customisations often end up as new workarounds. We have built from scratch for Universal Apps and DTU, where the shelf did not reach.

Question 5

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 6

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 7

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 8

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 9

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 have a process or an idea no finished system supports

Nobody has built a system for what you do

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

App platform lifts sales and loyalty in the auto industry

Frequently asked questions