Approach
From the first conversation to the handover: what happens in each step, what you get to see and what you hold at the end.
The steps of an assignment
-
The first conversation
The first conversation is free and lasts at most one hour. It is about what happens now and what should happen. We ask questions until we can retell your process. Then we write down what we understood and send it to you. If it is wrong, you know before anything is built.
If the assignment is too large to oversee in one conversation, we propose a preliminary study: reading the systems that are there and talking to the people who work with them. The result is a written report, and it is yours, also if you continue with somebody else afterwards.
-
The design and the plan
What gets built is on paper first: which data the system keeps, what happens with every case that deviates, which parts it consists of and what it connects to. If a design already exists, yours or another party's, we read it and say what it lacks.
The plan beside it states what gets built and what is expressly left out. That second list exists because most arguments about software are about something one side thought was included.
It also states what it costs. Every step has a fixed price, settled in advance; we do not work on an hourly basis. A step is invoiced after its delivery, and you pay an invoice within 14 days.
-
Building in steps
We build in short steps. At the end of every step there is something that works, on an environment you can reach yourself. So you see early where your money goes, and you can change your mind before it gets expensive.
Every step comes with a message of a few lines: what is finished, what disappointed, and what the next step is. If something changes in what gets built, we record that change and its cost in writing before we start on it.
-
Testing and going live
What is delivered is tested. Where possible with tests that run by themselves on every change, and always with a round in which you try it yourself. What comes up in that round, we resolve before the software goes into use.
Going live comes with an agreement about the moment, about who is present and about how you get back to the old situation if it goes wrong.
An error you report in writing within three months after delivery, we repair at no cost. That follows from the terms and conditions, articles 48 and 54.
-
Handover
On delivery you receive the source code and the rights to it, and the documentation to run the software: installing, configuring, where the data lives, and how you restore a backup. The measure for that documentation is whether a developer who was not there can carry on with it.
That ends the assignment. We do not take on hosting or maintenance, so who runs the software afterwards is your decision: your own people or a party of your choice. The handover is set up for that.
A first conversation
Write down what happens now and what should happen. That is enough to tell whether this is work we can do something about.