Question 1

Do we have to move our pricing logic out of the ERP to do this?

Accepted Answer

No. The price should stay where it is calculated today, otherwise you get two places to keep track of. We fetch it from there and show it to the right customer. Then there is still only one source for the price, and it is the one you maintain yourself.

Question 2

Our prices depend on quantity, agreement and geography. Can that even be shown?

Accepted Answer

That is precisely why it is worth showing. The more factors decide the price, the harder it is to look up by hand, and the more time goes on it. We map the rules in the pre-project and work out which of them can be settled automatically, and which still take a salesperson.

Question 3

Do we dare show prices online when competitors can see them?

Accepted Answer

Agreed prices are shown behind a login, only to the customer they apply to, so they are not out in the open. It is a real concern, and it decides what stands open and what takes a login. We make that decision together, before anything is built.

Question 4

What about the customers who have no agreement?

Accepted Answer

They meet the catalogue price, and that is also an answer. The point is that the customer gets the right number straight away instead of calling for it. If the customer has an agreement, they see their own price; if not, they see the list price and can act on 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.

Every customer of ours has their own prices and agreements

The price exists, but the customer has to ring for it

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

Bygma Proff app: engagement and personal service

Frequently asked questions