1. Consultation – 30 minutes, free
You tell us what you want to achieve: which process to support, who will use it, what does not work today. We tell you what is realistic – including when custom software is not the right answer.
2. Written proposal
After the conversation we send in writing what we will build, with which technology, how long it takes and what it costs. You see exactly what you are committing to before you sign anything.
3. Development in increments
We do not work towards one big handover. Development runs in increments, and you get a test environment along the way where you can try the finished parts. That way you do not find out at the end that you pictured something differently, and your feedback still makes it in on time.
4. Launch and after
At launch we migrate the data that is needed and schedule the switch so work does not stop in the meantime. After that, operation and further development can stay with us if you wish – most of our clients have worked with us this way for years.
What to prepare for the consultation
You do not need a finished specification. It is enough if you can roughly answer these:
- what problem the software solves, and how you handle it today,
- who will use it, and on what: in a browser, on a phone, on a desktop,
- which existing systems it has to connect to,
- whether there is a deadline to meet.
What does the price depend on?
Mainly on the scope: how many processes and roles it has to handle, how many platforms it has to run on, and how many existing systems it connects to. A small internal tool and a multi-platform product differ by an order of magnitude – which is why we always give a written, concrete proposal.
Who owns the code, and what if you switch later?
The source code belongs to the client, and we sign a non-disclosure agreement on request. If you later continue with another team, we hand over the code and what is needed to run it.