Services
IT advice, software design and software development. For each: what it is, when you need it and what you receive.
IT advice
You face a choice about a system and do not want to make it on instinct. You are choosing between two packages, you want to know whether what runs today will last for years, or another party has sent a quote you cannot judge.
We read what is there and talk to the people who work with it. You receive a written judgement: what is there now, what it costs to keep it, and where the risk sits in the route you are considering.
No condition is attached that we build something for you afterwards. If the answer is that you should do nothing, that is what it says.
Software design
Before anything is built, what gets built has to be settled. That holds for a new system and just as much for a change to a system that has run for years and whose dependencies nobody can still oversee.
We write out your process, decide which data the system keeps and what happens with every case that deviates. Then we fix the structure: which parts the system consists of, what it connects to and what it expects from those connections.
You receive that design on paper, in language you can read without a developer. It is yours, also if you have another party build it.
Software development
Your process runs on a package that is a near miss, or on a spreadsheet that has grown too large. Then we build the application ourselves: a web application your team works in, a service that processes data in the background, a link between two systems that need the same data, or a migration that has to carry years of data along.
We build in short steps, and at the end of every step there is something that works on an environment you can reach yourself. What is delivered is tested, and a data migration runs first on a copy of the real data.
You receive working software, the source code with the rights as agreed, and the documentation to install it, configure it and restore it.
After delivery
An assignment ends with the handover. We do not take on hosting or maintenance: who runs the software afterwards is your decision, with your own people or a party of your choice.
So the handover is set up for somebody who was not there. We write the software so that another developer can take it over, and the documentation is part of the delivery.
How an assignment runs
From the first conversation to the handover is on the page Approach. If you already know what you need, write to us straight away.