Modernization
We don’t throw it away. We carry it forward.
Taking over existing systems, re-architecture, progressive migration. Strangler pattern, regression test harnesses, data reconciliation. Production keeps running.
Software engineering · France · Worldwide
Your software runs. And nobody wants to touch it.
Every change costs more than the last, and the technical decisions were made by people who have since left. We take it over, make it maintainable, hand it back. No rewrite, no stopping production.
Based in France
The engineering happens in France. The work goes where you are.
Price agreed upfront
Fixed fee on audits. Day rate agreed before we start on longer engagements.
Handover included
Documentation, tests, knowledge transfer. Planned from day one and included in the price.
What we do
Three ways into a system you cannot switch off.
Where a failure costs money the same day.
Data & automation
What no longer keeps up, and what gets redone by hand.
Ingestion pipelines, warehouses, real-time processing, reporting, sized for the volume you actually have. And everything your team redoes by hand every week.
Audit & security
An audit that ends in a costed plan.
Application and infrastructure audits, cloud review, hardening, secret management. You leave with a prioritized, costed remediation plan, short enough to read in one sitting.
Strengthening a team you already have
Your team is there. Delivery is what is stuck.
One more developer does not fix a delivery problem. You need someone to hold the technical line.
- 01
Technical lead
Architecture calls, breaking down the work, code review, and the decision when one has to be made.
- 02
Delivery process
Continuous integration, tests, reviews, incident handling. Measured with the DORA metrics. Progress becomes a number you can check yourself.
- 03
Agile, the useful kind
Scrum, Kanban, or whichever mix fits. I start from what already works here and fix what wastes time. Nobody needs one more ritual.
- 04
Mentoring juniors
Code reviews that explain, pair programming, autonomy built up step by step. It stays in the team after I leave.
The five DORA metrics, published by the research programme of the same name at Google Cloud.
How we work
Four phases. The last one matters as much as the rest.
- 01
Audit
Two to four weeks seeing the system as it really is. Code, data, infrastructure, team, regulation.
- 02
Scope
A written roadmap, broken into increments, costed. Risks named, and what we recommend you don’t do.
- 03
Build
Short, verifiable releases. Nothing gets built inside a black box.
- 04
Hand over
We leave, your team stays. And we stay reachable afterwards.
In production
Two systems that could not be stopped.
At employers we can name.
Blank — Groupe Crédit AgricoleOct 2025 → present
A critical module had to migrate while the banking integrations were running in production. No outage window available.
Migration delivered in six weeks, with no interruption to the banking integrations.
FincomeJun 2024 → Sep 2025
Python financial data pipelines that no longer kept up with the volume, and infrastructure that had to reach SOC 2 standard.
Pipelines that keep up with the volume again, infrastructure that can be rebuilt from code, and the SOC 2 compliance work carried through to the end.
Our products
Three products we run ourselves.
What we learn shipping them goes straight back into client work.
Reporting & data
Glow Reports
Trusted answers in plain language, in minutes.
Your spreadsheets become board-ready reports. Stripe, HubSpot, GA4 and Shopify in one view. Ask in plain English, then click any number to see the rows behind it.
- One source of truth
- Natural-language questions
- Every number traceable
- Shareable PDF reports
30-day free trial
Visit Glow ReportsProspecting
Glauria
Less time on LinkedIn. More time closing.
An AI prospecting agent. It finds the right people the moment they show intent, qualifies them, and books the meeting. It runs on your own machine, in your voice.
- Intent detection
- Automatic qualification
- Matches your voice
- Runs locally
Early access
Visit GlauriaEducation
Transf’R Toi
Careers worth discovering, without the stereotypes.
A free serious game. Students explore eight career worlds and leave with careers they had never considered. Every answer is explained back to them.
- Eight professional worlds
- No grades, no ranking
- Progress across sessions
- Free for schools
Live, free
Visit Transf’R ToiCompared with an IT services firm
They leave with the ownership. We hand it back.
You own the code, the contract says so. The real question comes later. In six months, can your team change this system without calling back the people who built it? An IT services firm has no structural reason to want that answer to be yes. Dependency renews the contract.
| At an IT services firm | At Tari Software | |
|---|---|---|
| Where the knowledge accumulates | In their team, on their tooling, in their heads. It stays there. | In your repository, your tests, your documentation. Available from day one. |
| What gets written down | Documentation arrives at the end, if it was in the contract. | Decisions are written as they are made. Six months later you still know why. |
| The day you want to change something | You call the supplier back, because nobody on your side has the controls. | Your team does it. If they are not ready yet, getting them there is part of the job. |
| At the end | The contract stops, and command of the system leaves with the team. | We leave, command of the system stays. It is the only outcome we are interested in. |
Engagement models
Three ways to work together.
2 to 4 weeks
Fixed-price audit
Fixed scope, fixed price, a written deliverable. The document is yours whether or not we continue together.
3 months and up
Embedded engineer
An engineer embedded in your organization, at a day rate agreed before we start. A verifiable release every two weeks, and the same person from the first day to the last.
6 to 18 months
Build & transfer
We build the system, then transfer it to your in-house team. Hiring support, training and handover included.
Frequently asked
What people ask before signing.
What does an audit cost?
A fixed fee, agreed before we start. The price follows the scope, so the number of applications, the volume of code and the complexity of the infrastructure. You leave with a costed remediation plan that is yours whether or not you continue with us.
Do we have to rewrite everything?
Almost never. A full rewrite is the most expensive option, the riskiest, and the one that fails most often. We isolate what is causing the problem and replace it piece by piece, in production. The rest keeps running.
How many of you are there, and what happens if you are not around?
Tari Software is one engineer. The person reading your code is the person answering your call, from the first day to the last. Nobody junior gets quietly swapped onto the project halfway through.
The rest is handled structurally. You have repository access from day one, documentation moves with the code, the handover is planned from the start. You can take it back in-house whenever you want. And if the work turns out to be more than one engineer can carry, we say so before starting.
What technologies do you work with?
We take over systems we did not write, that is the job. A lot of Python, TypeScript, .NET, Java and PHP. SQL and NoSQL. AWS, GCP, Azure, Kubernetes and on-premise infrastructure. If your stack is not on that list, tell us.
Where is our data hosted?
Wherever you decide. We work from France and we know how to work with European hosting providers when sovereignty is part of the constraints.
Do you work outside France?
Yes. Tari Software is based in France. Engagements run in France and internationally, in French or in English.
Sectors
- Banking & finance
- Cybersecurity
- Healthcare
- Industry
- Education
- Logistics
- Public sector
- Retail
The company
Who you are dealing with.
Tari Software was founded and is run by El Mehdi Benane, a software engineer: six years on banking, cybersecurity and high-volume data systems, and three products in production. He is the one who takes your systems on, and his record is public in detail.
- Legal name
- Tari Software
- Contact
- contact@tarisoftware.com
- Working languages
- French · English
Let’s start by looking at what you already have.
Thirty minutes, no commitment. You leave with an engineer’s read on your situation, whether or not we end up working together.
Email Tari SoftwareOr write directly to contact@tarisoftware.com