Question 1

Are we not giving the product away by showing it?

Accepted Answer

That is the right worry to start with, and the answer is to show enough to create appetite without opening the box. At Geomatic the paid API sits behind a proxy, and the user meets the real data through a few selected filters, not the whole model. Where the line should sit is a business decision, and you make it, not us.

Question 2

How much does a taster have to do before it works?

Accepted Answer

Enough for the customer to see their own case. A generic example convinces nobody, but the customer does not need to see the whole product: they need to see that it applies to them. So we build it around the one question a buyer always asks, instead of showing everything at once.

Question 3

Can you do it without simplifying our model into something wrong?

Accepted Answer

That is the whole job. We build together with the people at your end who own the model, so the tool reflects it rather than becoming a simplification nobody can stand behind. At DTU Management we worked directly with the researchers, precisely to avoid that.

Question 4

Our product needs advice no matter what. Is it wasted then?

Accepted Answer

No, but the purpose shifts. Then the taster should not replace the conversation, it should make it better: the customer arrives prepared and has already understood what you otherwise spend the first half hour on. That is also how we have used it at Nykredit, where the calculations follow the customer in to the adviser.

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 product is complex and hard to explain

The best thing about the product cannot be seen

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

Data-driven segmentation boosts customer engagement

Frequently asked questions