Legacy software, modernized for manufacturers

Contact usPricing

  • Access database replacement
  • Excel and macro replacement
  • Delphi and VB6 migration
  • FoxPro migration
  • AI-built prototypes to production
  • C and C++ to Rust
  • Data migration and reconciliation
  • Gradual switch-over
  • Web and desktop
  • Offline-first sync
  • Role-based access control
  • Reports and exports
  • Documentation and handover

What we modernize.

We replace the software a business has outgrown: legacy desktop systems, spreadsheet-based processes, prototypes built with AI tools. The new application preserves the existing workflows and terminology, so the switch is painless.

The data is migrated in rehearsed runs and reconciled against the source, and the old system stays in operation until each team has switched over.

  1. Old system in daily use
  2. New system built alongside
  3. Rehearsed migrations
  4. Warehouse moves over
  5. Office moves over
  6. Old system archived

A legacy desktop system

Access, FoxPro, Delphi, and VB6 applications that still run the business but have become difficult to change, deploy, and secure.

We rebuild them as web or desktop applications on a modern stack. The workflows stay the same, frequent tasks take fewer steps, and reporting scales with the data.

Spreadsheets that became the system

Shared workbooks, macros, and copies sent by email that a business process has come to depend on, without a single source of truth.

We model the data in a relational database, reimplement the formulas and macros as tested application logic, and keep the structure people already work with.

A prototype built with AI tools

Applications generated with Lovable, Bolt, Cursor, or similar tools, which validate an idea quickly and usually need engineering work before production.

We review the generated code, keep what is sound, and rebuild what production requires: the data model, access control, error handling, tests, and deployment.

Memory-safe modernization

We move C and C++ code to Rust for memory safety and thread safety without giving up performance: the compiler rejects use-after-free and data races, array access is bounds-checked, and the code still compiles to native machine code without a garbage collector.

Memory safety errors account for about 70% of serious security vulnerabilities in large C and C++ codebases.⁠[1][2]

More about memory-safe modernization
C and C++Rust
Memory safetyDepends on reviews and testingEnforced by the compiler
Thread safetyData races are possibleData races do not compile
PerformanceNative codeNative code, no garbage collector

What regulators now expect

EU Cyber Resilience ActRegulation (EU) 2024/2847. Reporting from 11 September 2026, full application from 11 December 2027.

Software and connected devices sold in the EU must ship without known exploitable vulnerabilities, get security updates for their support period, and have actively exploited ones reported within 24 hours. Fines reach €15 million or 2.5% of worldwide turnover.

EU Product Liability DirectiveDirective (EU) 2024/2853. For products placed on the market from 9 December 2026.

Software counts as a product, and its manufacturer is liable for damage caused by a defect, including a security vulnerability left without an update.

EU NIS2 DirectiveDirective (EU) 2022/2555. Applicable since 18 October 2024.

Essential and important entities, from energy and health to manufacturing, must secure their supply chain, including how the software they use is built and how its vulnerabilities are handled.

Back to the Building Blocks (US)Report of the Office of the National Cyber Director, 26 February 2024.

Asks software manufacturers to adopt memory-safe programming languages, to remove whole classes of vulnerabilities instead of fixing them one at a time.

Product Security Bad Practices (US)Joint guidance of CISA and the FBI, January 2025.

New products for critical infrastructure written in C or C++, where a memory-safe language could be used, count as a bad practice, and existing products should have a published memory safety roadmap by 1 January 2026.

Example of what we deliver.

An ERP for liquid cargo operations that replaced spreadsheets and email: inventory, ownership transfers, blending, and transport documents now live in one system. The data was migrated and reconciled before the switch-over, and the desktop application works offline when a terminal loses connectivity.

  • 4ha day no longer spent re-typing terminal paperwork at the office
  • 79%faster to close the month (from two weeks to three days)
Read the case studyAbout the team
ERP for liquid cargo operations — on a laptopERP for liquid cargo operations — on a phoneERP for liquid cargo operations — application screenshotERP for liquid cargo operations — application screenshot

How we work.

  1. 01Understand the old system first

    We study the old system, its data, and the workarounds people rely on before writing code, and prepare the specification ourselves.

  2. 02The best modern tools available

    The language, the database, and the hosting follow from what the workload requires.

  3. 03No overengineering

    The simplest system that runs fast, covers every workflow, and scales.

  4. 04Reliability and performance

    Performance targets and failure handling are part of the architecture from the start, verified by profiling and automated tests.

  5. 05Less consulting, more action

    Whatever stage your product is at, we move it forward with working releases you can use and review.

  6. 06Direct communication

    You talk directly to the engineers writing the code, so questions are answered by the people who know the system.

  7. 07Production-ready

    Monitoring, backups, automated deployment, and documentation are part of the first release.

  8. 08Fair price, no surprises

    A fixed price for the agreed scope.

A first release (MVP) built to the standard of a finished product.

New software is judged against the mature products people already use, so we build the first release as a complete product: every workflow in the agreed scope, together with the admin interface, access control, reports, notifications, and the infrastructure it runs on (automated deployment, backups, monitoring).

The engineers who build the release also agree its scope with you. Common parts start from components we have already tested, so most of the time goes into your workflows, built on an architecture that scales as the business grows.

Rethinking the startup MVP, by Linear

What happens after you write to us.

  1. An engineer replies with first questions. We then discuss the requirements with you, by email, on a call, or in person.
  2. The scope, the milestones with their acceptance criteria, and the price, within a week.
  3. You talk directly to the engineers writing the code and receive daily updates, so decisions and adjustments happen quickly.
  4. You receive the source code, the documentation, and access to everything we set up.
  5. You stay supported well beyond the first release. We maintain, refine, and extend your product as your needs grow, keeping it fast and reliable.

MVP package: the first production release

€9,200Standard price:€11,500−20% founding client offer

6–8 weeks from agreed scope to launch

  • Consultation and project scoping, free
  • UI/UX design
  • Frontend, backend, and integrations
  • Testing, deployment, and documentation
  • Bug-fix guarantee for 3 months after launch
  • Source code and a documented handover
Contact usMore about pricing
What does founding client mean?

After launch, you agree to a short written interview for a case study. We agree what gets published before the project starts.

Terms

EU companies with a VAT number pay exactly this amount (reverse charge).

Questions about this service

Our prototype was built with AI tools. Can you take it over?

Yes. We review the generated code, keep what is sound, and rebuild what production requires: the data model, access control, error handling, tests, and deployment.

Can you replace our spreadsheets without changing how people work?

For the most part. The new system keeps the structure, the steps, and the terms people know, and any change to a workflow is agreed with the people who use it.

Will you need access to the old system?

Yes. We review the workflows, the data, and the integrations, and talk to the people who work with the system. Access and confidentiality are agreed before the review.

Do we lose our data?

No. The data is migrated in rehearsed runs against real exports, and the result is reconciled against the original before the switch.

How much does a replacement cost?

Most replacements start as an MVP package: €11,500 for a defined scope and 6–8 weeks of development (€9,200 as a founding client). Larger systems and complex data migrations receive a separate estimate after free scoping.

Let's talk about your project.

Schedule an online call (optional)