Modernise, integrate and run the systems your business depends on

You already run operations on software: an internal platform, a line-of-business application, a set of integrations nobody wants to touch. We bring analysts and engineers who learn how it really works, change it without stopping delivery, and keep it healthy once it is live.

Six ways this usually starts

Most engagements begin with one of these. The last is for when you are not sure.

A legacy system nobody dares touch

It runs the business, everyone who built it has gone, and the last vendor quoted a rewrite.

Modernisation and technical debt. We document what it does, put tests and monitoring around it, and modernise it piece by piece while it keeps running, with the cloud infrastructure to carry whatever replaces it. No big-bang rewrite unless the analysis says so.

Data rekeyed by hand between systems

The ERP, the CRM and three spreadsheets hold four versions of the same customer.

System integration. We connect what you already run so data is entered once and flows, with the validation and error handling that keep it trustworthy.

A process still run on email, phone calls and Excel

A process that grew up in inboxes and spreadsheets, now with fifty people and no source of truth.

Custom software engineering. A line-of-business application built for that exact process, designed with the people who run it daily so they actually adopt it.

Sogetrel: InfraScoutX, field surveys and deployment tracking for a fiber rollout

A system with no owner

The vendor folded or the developer left, and nobody can change production software safely.

Takeover, then run and maintain. We audit the code and the infrastructure, stabilise it, put monitoring in place and take responsibility for it. Built by us or not.

Data you have but cannot act on, and a board asking about AI

Reports assembled by hand every month, and pressure to do something with AI.

AI and data. Reporting and analytics on data you can trust, and applied AI where it pays inside your process: document handling, classification, assistants on your own data. We start by finding where it is worth it, not with a demo.

A decision to make and no clear picture of what you run

Several entities, overlapping systems, and a budget decision waiting on an inventory nobody has.

Audit and business analysis. We map the systems, the processes and the people, on site, and hand you a picture you can decide on, with recommendations you can execute with us or with anyone else.

Artelis: an audit across Luxembourg and Germany, carried out entirely on site

How an engagement runs

Three phases, the same on every engagement.

Understand

We sit with the people who run the process, in your office, and map how the work actually flows.

You getA process map, a prioritised backlog, and an estimate you can take to a budget committee.

Deliver

Two-week sprints, each ending in a working increment you review. The old system keeps running until the new one has earned its place.

You getSoftware you watch grow, and the room to change direction while it is still cheap.

For big projects, we move in.

We work from your office as much as you want: the whole engagement, the key days of each sprint, or every day of an audit. For Artelis, that meant Luxembourg and Germany, on site throughout.

Operate

Monitoring, patching and improvement after go-live, for systems we built and systems we took over.

You getA system that stays current for years, and the engineers who built it answering when something breaks.

What we need from you

The people who do the work, and one decision-maker who can settle what the system must change.
An hour every two weeks for the sprint review, and someone who owns the backlog.
A maintenance agreement once it is live, and a channel to tell us what is slow.

Four ways to work with us

Pick the shape that fits the decision in front of you. Most clients move between them over the years.

Audit and analysis

Fixed duration

A fixed-duration engagement that ends with a deliverable you can act on, with us or with anyone else.

Choose it when: You need to decide before you commit budget.
What you get: A system inventory, a process map, recommendations and an estimate.

ExampleArtelis

Project

Sprint by sprint

A system built, modernised or integrated to a defined outcome, in sprints you steer.

Choose it when: The scope is clear and the outcome matters more than the hours.
What you get: Working software every two weeks, then a system in production.

ExampleSogetrel

Embedded engineers

As long as you need

Our engineers inside your team, in your office, on your rhythm and your tools.

Choose it when: You have the direction and need the hands, or the project is big enough that you want us in the building.
What you get: Engineers who know your system and answer to your priorities.

Run and maintain

Ongoing

Monitoring, patching, improvement and support, for systems we built and systems we did not.

Choose it when: The system is live and you want someone accountable for it.
What you get: A system that stays current and fast, and the engineers who know it when something breaks.

ExampleSogetrel

Two engagements in detail

One built and run, one analysed and decided. Both told through the same three phases.

Software engineering · Run and maintain

InfraScoutX: field surveys and deployment tracking for a fiber rollout

A fiber rollout run by field teams, with surveys to organise and deployment progress to track across the whole operation.

Understand: Business analysis first: how field surveys were run and how deployment progress was tracked, turned into a scoped, prioritised backlog.
Deliver: Twelve months of two-week sprints. Sogetrel reviewed working software every two weeks and reprioritised between sprints.
Operate: In production and maintained by the same team that built it, under a run-and-maintain engagement.

“InfraScoutX let us quickly organize our field surveys and track deployment progress in real time. It made our fiber rollout smoother and far more efficient.”

Rémy Thirion, Sogetrel

Read the case study

Business analysis · Consulting

An audit across two countries

Activities in Luxembourg and in Germany, and a need for one clear picture of the systems and processes on both sides of the border before deciding what to change.

Understand: An audit of the systems, the processes and the people, carried out entirely on site, in Luxembourg and in Germany.
Deliver: Findings and recommendations, written so they can be executed with us or with anyone else.
Decide: The decisions that follow an audit are the client’s. Ours is to make them possible on evidence rather than on a vendor’s pitch.

Questions procurement will ask

The answers we give before a contract, written down.

Something not covered?

We reply within 48 hours on business days.

[email protected] Talk to us

Who owns the code?

You do. Full intellectual property on everything we build, with source code and documentation handed over.

Do you subcontract or offshore?

No. Every engineer is in-house in Dudelange, Luxembourg. The person who scopes your system is the person who builds and maintains it.

Do you work on site?

As much as you want. For the duration of a large project, for the key days of each sprint, or for a full audit, as we did for Artelis in Luxembourg and Germany.

Which languages do you work in?

French, English, German and Luxembourgish. Specifications are written in the language your staff describe the process in.

Can you take over a system you did not build?

Yes. We audit the code and infrastructure, stabilise it, put monitoring in place and maintain it from there.

Do you use AI to build our software?

Yes. Our developers work AI-augmented, so more of their time goes into your process and less into typing. Every line still goes through the engineers who own your system, and the code and its intellectual property are yours.

What happens after we get in touch?

You hear from us within 48 hours. The first conversation is about the business problem, not a technology pitch, and we tell you honestly whether we are the right team. If we are, the next step is the Understand phase: time with the people who do the work, and a scoped backlog and estimate at the end of it.

Building something new instead? The Studio takes a product from business case to launched software, and stays on as the team that runs it.

Discover the Studio

Arthur Junges

Founder & CEO

Tell us which of the six it is

Describe the system, the process or the decision, and we reply within 48 hours with whether we are the right team and what the first step looks like. If it is big, we will come and see it.