Discovery
We document how the work is done today and describe the target process. Occasionally it turns out that a changed routine solves the problem better than new code.
Building your own system pays off when off-the-shelf products force your people into a way of working that costs more than development would. We cover the whole journey, starting with a conversation about what should become easier day to day and ending with an application that is live, supported and still evolving.
The work is split into self-contained phases, each priced separately. You can stop after any of them and keep everything produced so far.
We document how the work is done today and describe the target process. Occasionally it turns out that a changed routine solves the problem better than new code.
System structure, data model, links to tools such as e-conomic or Business Central, and first sketches of the screens.
Two-week sprints where every demo shows working software rather than a status report.
Scenario and load tests written down so they can be rerun against every new release.
Data transfer, remote user training over Teams and a trial period with close follow-up.
Bug fixes, dependency updates and new features once the system is part of daily operations.
Discovery takes two to four weeks. A first version that people can use for real arrives after roughly three months at the earliest. You receive the detailed plan when discovery is complete.
We walk through the process with the staff who know it best and estimate the gain. This phase is invoiced on its own.
A clickable model of the screens. Changing a prototype takes minutes; changing finished code takes weeks.
Progress is shown as we go, so you can change direction early instead of being surprised at handover.
Trial period, fixes based on user feedback, and handover of documentation, access and rights.
Features added »just in case« eat the budget for version one. A large share of the wishes written into a requirements document up front are never used at all. It is cheaper to launch a lean release, watch how staff actually use it and then build what proves necessary.
You do. Source code and documentation are handed over and the rights are set out in the contract. We treat this as a principle: software that only one supplier can maintain ties a business down for no good reason.
Often it would, and we will tell you so even though it is not in our commercial interest. Bespoke development makes sense when the process really is unusual, or when customising a packaged product would cost more than starting from scratch.
Through fixed-price phases. After discovery the picture is clear, and the first release can always be trimmed by moving items to later. Small changes and further development are billed at DKK 895 per hour, excl. VAT.
Entirely remotely. Workshops run on Teams, demos are shared on screen and the test environment lives in the cloud, so your staff can try the system from home or the office.
Describe the workflow you would like to digitise. We begin with discovery, and sometimes it shows that nothing needs to be built at all.
Thank you for getting in touch
One of our consultants already has it. Expect a reply within the working day; anything urgent goes straight to an engineer.
That city is not on our list. Check the spelling or pick the nearest larger town.