2019
The studio starts, on the racing line: audits and reviews on GT cars for customer teams. Year to be confirmed.
Studio
Whoever picks up the phone is the person who then looks at your data. It is the only structure we know how to make work.
Who we are
People who worked trackside before they wrote about it.
Technical consultancy is only worth anything if the person doing it has taken those decisions under pressure.
This section needs completing with the directors: composition of the engineering group, professional backgrounds, years active and actual locations. The text below is the structure, not the facts.
RacingSyn started from the idea that the method that works in competition — measure, decide quickly, write down what you decided — is useful outside competition too. It is why the three lines of work sit together: they are the same craft applied to different clients.
We have no sales function. Work arrives from people who have already seen us work, and the first conversation is always technical. That holds while we stay small, and it is a constraint we chose.
Track record
How we got here.
Dates and milestones to be confirmed with the directors before publication.
2021
First season-long race engineering engagements, and the first rebuild of a team's technical structure. To be confirmed.
2023
The one-off line opens: feasibility and engineering of unique cars on an existing base. To be confirmed.
2025
First OEM support programmes, with makers running prototype test campaigns. To be confirmed.
Today
Three lines running in parallel, with a single engineering group across all of them.
A consultancy that makes itself indispensable has failed. It has just done it slowly.
The studio's principle
How we behave
Four rules we do not negotiate.
01
Category exclusivity
We do not work with two teams fighting each other in the same championship. It is a standard clause, not a courtesy.
02
NDA before data
Confidentiality signed before the first file, and before the first technical call if you want it that way.
03
We say no
If the problem is not ours, or if someone is already solving it well, we decline. We say so on the first call.
04
We write down what failed
A report that lists only the successes is useless. Failed tests are half the information.
Contact
If you read this far, write to us.
Car, category and what is wrong will do. An engineer replies.