DiVotek case studies and experience
Complex projects
What's behind projects like these
Data migration
In the retail project it mattered to keep not just the products but also their attributes, price variants, reviews, articles and redirects from the old URLs. We define the migration scope before development.
Consistent records
Car availability or stock levels affect both the site and the manager's decisions. You need to decide where the up-to-date data comes from and how it gets updated.
Different people at work
The customer, the manager and the staff member keeping the books work with different parts of the process. Interfaces and access must match their tasks.
Connections between systems
An enquiry, a payment, a document and a status change are parts of one scenario. We design these connections together with the business logic so the team can work in one consistent process.
We build web systems that connect the customer-facing side with the business's internal processes: sales, accounting, documents and the team's work. Here we show the tasks clients bring to us and what changes after launch.
Why the write-ups are anonymized
Some of our projects are under NDA. So we describe the business task, the shape of the solution and the confirmed results without company names, internal data or real interfaces.
The diagrams in the write-ups show how the parts of the system connect in general. One project's results are not a forecast for another business.