Question 1

What happens when there is no coverage at the address?

Accepted Answer

Then it works anyway. We build for the connection being absent rather than treating it as an exception: the whole registration can be completed offline, and the service behind it acknowledges each piece and keeps going until it has arrived. There is no offline mode the employee has to remember to switch on.

Question 2

Can the app write straight into our ERP?

Accepted Answer

Yes, and we usually put a separate service in between. That guarantees the handover, and the app can be developed further without anybody touching the ERP system itself. At Bygma the registrations go that way into M3.

Question 3

Will our people actually use it?

Accepted Answer

Only if it is faster than what they do now. So we cut the interface down for use under pressure: few choices, large touch areas and no screens that require you to find shelter to read them. We test it with your own people before it is finished, because they know what a working day looks like.

Question 4

Do we need an app, or can a mobile friendly site do the job?

Accepted Answer

Often a mobile friendly site can do it, and then we recommend that, because it is cheaper to build and run. But if the tool is used every day, by people without coverage, and the result has to be trusted, the requirement moves from convenience to robustness. That is the assessment the pre-project settles before anything is built.

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.

Our people in the field cannot use our systems

The paperwork waits until the van is home

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