When a replacement has already failed once, we take it on.
We read the code, examine the data and the actual workflows before deciding what belongs in your new system – rather than copying a legacy application one to one.
Leasing and logistics: around ten companies run the systems we maintain, with portfolios from a thousand to more than 80,000 contracts each. A back office we built plans deliveries to more than 4,000 sales points.
Examine first. Then decide.
Understand code and data
We read the legacy source code and look at what the database actually contains, not what it is supposed to contain.
Check workflows with the people who run them
Only the people doing a task daily know why it runs the way it does. Detours are sometimes old workarounds and sometimes the actual process.
Decide together
What stays, what changes and what ends is decided with you and your departments. The result is a list that goes into the quote.
What we agree per project
Terms are set per contract. These four points are the frame we usually work in.
- Invoicing against agreed acceptance, not against the calendar.
- You receive the source code for the components we create and the materials needed to build and deploy them. We identify third-party licensed components and their terms.
- Maintenance with a short notice period and an agreed ceiling on price adjustments.
- Response times matched to how critical your system is, rather than one blanket promise.
There are five of us.
You speak to the people building your system. We develop the core ourselves; for specialist areas, we bring in partners we have worked with for years. Usually, you see a testable version in your test environment every two weeks. We appoint a dedicated contact who stays with the project from the first analysis until after launch. If that person needs to change, we let you know and arrange a proper handover. To help you remain independent, we hand over source code and operating documentation throughout the project. We train your people to keep the system running without us.
Where this comes from
crossVault was founded in 2009; the two founders have worked in software development since 2003, first as DevGroup IT-Services GbR, which merged into the GmbH in 2009. The focus has been leasing and finance ever since: we maintain established systems of that kind under contract and are building vertragWerk, our own web-based solution, out of that work. HydraData, a data pump we published under the MIT licence, came out of the migration projects.
You do not need a finished specification.
For a first conversation it is enough to say which system you run today, which workflows get in the way – and, if there was an earlier attempt, what went wrong with it.
Discuss your project