Planning, building, looking after it: one team does it all.

Usually once it's clear what is to be built. That includes which other systems the solution has to work with and what we're assuming along the way. We work this out with you and write it down. That becomes the quote, and the quote states the price.

Often that's a good way in. A small, clearly defined project shows both sides how working together goes. Afterwards it's easier to judge whether and how to continue. We can work out in the intro call whether that suits your plans.

Then we usually look at it first. Often what you have can be connected or extended. Whether something new makes more sense depends on what your current solution can do and what you need.

That depends mostly on the scope you have in mind. How quickly content and decisions come from your side also plays a part. A rough idea of the size can usually be discussed in the intro call. Whatever we agree on timing is then set out in the quote.

That depends on the project and the services it needs. We prefer data centres in the EU. Which provider and region come into question is something we discuss with you. What's binding is what the quote and the data processing agreement (DPA) say.

Under Art. 28 GDPR, such an agreement is needed as soon as a service provider processes personal data on your behalf. It has to be in place before the processing begins. It usually comes with an annex describing the technical and organisational measures (TOMs), such as who may access what. Whether your project needs one depends on whether we process personal data for you in it.