We ask why
No manual explains why a task is done the way it is. Your staff know. That is why we start with the processes and choose the technology afterwards.
What we build with
Angular, Node.js or ASP.NET, with SQL Server or PostgreSQL. Your environment determines the choice, rather than our preferences. The full list is under Technology & Expertise.
A working version every two weeks
Usually, we deliver a working version to your test environment every two weeks. What you see can change the order of priorities. If the total effort stays the same, we do not charge extra for reprioritising within the agreed scope. We discuss any expansion of that scope separately.
Interfaces
REST, file exports, DATEV, SEPA and EDI. We connect to what you already run: accounting, inventory and third-party systems.
Interfaces for people who use them all day
Administrative work means using the same screen a hundred times a day. Keyboard access and information density take priority over appearance. Lists with tens of thousands of results need to filter as quickly in the browser as they did in the desktop client.
Who does what, and when
Regular progress requires time on both sides for coordination and review.
Assessment
- We
- We work through what you have and write down what the system actually does today.
- You
- You give us access to the legacy system and name the users we may interview. How many sessions that takes, we tell you once we have seen the system.
Scoping
- We
- From the analysis we define the work for the next two weeks and take on the product-owner role that would otherwise tie up one of your staff full-time.
- You
- You review the scope before the sprint starts and say what is needed first. Two named contacts from the business side are enough for us.
Sprint
- We
- We build in narrow, complete slices, so a finished function runs from the screen through to the database. Day-to-day contact goes through Teams; on-site sessions as needed.
- You
- Your contacts are available for questions about business requirements. These arise during implementation and cannot always be planned in advance.
Review
- We
- At the end of the two weeks the working version is available in your test environment and we demonstrate what is new.
- You
- You check it against the acceptance criteria agreed beforehand. What you do not accept is not invoiced.
Rollout
- We
- We train your key users so that bringing the remaining staff up to speed stays in house.
- You
- Your key users train their colleagues and report from live operation what does not fit yet.
Day-to-day work can make it difficult to keep agreed review dates. In that case, we reschedule the review. We only invoice once you have reviewed and accepted the work.
We examine the legacy system first and agree with you and your key users which functions to carry forward. The result is a list included in the proposal, so nobody has to guess later what was commissioned.
Understand your situation. Agree the next steps together.
Tell us what works today and what you would like to change. The first conversation is free and without obligation; afterwards, you receive an initial assessment or possible next steps. You incur costs only when you accept a proposal. For a more detailed business and technical assessment, we agree a separate engagement in advance, with a clear scope and limits on time and cost.
Discuss your project