Question 1

Should we have an app or a web portal?

Accepted Answer

It depends on how your customers work. We recommend the one they will actually use, and we do not build an app for the sake of an app. If customers order from the office, a portal is often enough; if they are on the move, an app makes more sense. We settle that before we build.

Question 2

Can customers see their own agreed price?

Accepted Answer

We build self-service on your own range and your own prices, so every customer sees what applies to them. Agreed prices, discounts and access follow the individual customer, exactly as when they buy through a salesperson.

Question 3

Can customers book times themselves, not just order products?

Accepted Answer

The customer can both order products and book times, in real time and without calling. We build what your customers actually need, whether that is reordering a standing range or a slot in the calendar. What used to take a call during office hours, the customer now handles at nine in the evening.

Question 4

Do we build self-service on top of our ERP, or is it a new system alongside it?

Accepted Answer

We usually build on top of what you have. The portal fetches range, price and stock from your ERP, so the customer sees their own without double maintenance. You are not changing system, you are giving the customer a way in to what already sits behind it.

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.

Customers cannot order, find or book for themselves

The order waits for you to open

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