Rescue and takeover
The project stalled, the agency left, or the developer who built it is gone. We take the codebase as it is, establish what actually works, and get it moving again.
Typical: a build nobody can run, no documentation, no handover.
Brownfield rescue and legacy modernisation
We take over stuck software, stabilise it, and move it forward.
Two senior engineers. No juniors, no project managers. We inherit whatever stack the last team left behind, in whatever state they left it.
What we do
Three ways this usually starts
Legacy modernisation
The application the business runs on is years old and the people who built it have moved on. We modernise it in place, in steps, without stopping the business.
Typical: an ERP integration, a data pipeline, an internal tool nobody dares touch.
Your technical team
For companies with no CTO and no in-house senior. Architecture, development, infrastructure and maintenance, on a monthly retainer with a fixed number of days.
Usually how a rescue ends, rather than how it starts.
How we work
Diagnostic first. Always.
Nobody can price a codebase they have not read. We do not quote a rescue before we have looked at it, and we do not ask you to commit to the rest before you have the report.
Diagnostic
3 to 5 days, fixed price
We read the code, the infrastructure and the data. You get a written report: what is broken, what is worth keeping, what the next three months cost, and whether we think it is worth doing at all.
Stabilisation
2 to 3 weeks, fixed price
Stop the bleeding. A build that passes, a deploy that works, the failures that wake people up removed, and tests on the paths that carry money.
Forward
Day rate with a weekly cap, or a monthly retainer
Whichever fits. The cap is agreed before we start and we report against it every week. You can stop at the end of any milestone.
Diagnostic from 3,000 EUR
Deducted from the stabilisation fee if you continue with us.
Work
Some of what we have taken on
Clients are described by sector until they have agreed in writing to be named.
European cloud hosting provider
Designed the application framework that made a company-wide move from monolith to microservices possible, then refactored the monoliths onto it. Added a scripting language so non-developer teams could change business rules without an engineer.
Computer vision startup, later acquired by a defence group
Inherited a job queue that could not hold production and took it to production viability, then tuned it to keep GPUs busy across mixed cloud and on-premise hardware. Ran it for three years, including air-gapped deployments.
Automotive training organisation
Moved a legacy ERP onto a new architecture without stopping the business, then built the self-serve API platform that lets external integrators manage their own connectors. Team of two, still running.
Who you get
Both of us. Every time.
There is nobody to hand you off to. The people who read your code are the people who write it.
Raphaël Dantzer
Backend and platform, Nantes
Eight years on production systems and the platforms other engineers build on, across a cloud provider, an AI startup, industrial IoT and B2B SaaS. Author of an open-source Go application framework running in production.
Raphael Sequoya Baum
Full stack and data, Lisbon
Ten years across front end, back end and infrastructure. Enterprise data migrations, ERP replacement, and the infrastructure behind the launch of a coding school.
Tell us what broke.
A short description of the system and what is going wrong is enough to start. If it is not something we should take on, we will say so and tell you who should.
or write to hello@touclur.com