Listen and measure
Before proposing anything we look: existing data, set-up history, a track session if the material is not enough.
1–2 weeksMethod
It holds for a three-week audit and for a three-year programme. The length of each stage changes, the order does not.
The four stages
From listening to handover.
Diagnose
What actually limits the car, ranked by weight. With numbers next to it, not impressions alone.
2–3 weeksIntervene
Changes, simulation, testing. One target at a time and verifiable: if it is not measured, it did not happen.
variesHand over
Documentation, procedures, training. What stays behind once we are gone.
at programme endThe principle
The goal is that you can do the next lap without us.
A consultancy that makes itself indispensable has failed. It has just done it slowly.
Every engagement closes with something that stays: written procedures, correlated models, trained people. That is not generosity, it is how you build a relationship that outlasts a season.
For the same reason we use your tools. A method that only works with our software and our rigs is not transferable: when the engagement ends, so does the benefit.
And for the same reason we write down what did not work. A report that lists only the successes is useless: the tests that failed to deliver are half the information.
Engagement
Four models.
You can start with the first and move up. There is no minimum season commitment.
| Model | When it makes sense | Commitment | What we deliver |
|---|---|---|---|
| Technical audit | There is a problem and nobody knows where it comes from | 2–4 weeks | Report with priorities and proposed work |
| Target project | The target is measurable and agreed in writing | 3–6 months | Verified, documented changes |
| Retained support | You need a technical reference over time | Season or year | Presence to calendar and reporting |
| Technical responsibility | The programme needs leading, not just assisting | 12 months and beyond | Technical direction, with contractual targets |
Questions
How it works in practice.
How do we know whether it is worth calling you?
If the car is doing something you cannot explain with the data you have, yes. If you already know what the problem is and only need execution, probably not: you want a supplier, not a consultant.
We say so on the first call, before any proposal.
Do you take competing engagements?
No, not in the same category and the same championship. Category exclusivity is a standard clause in our contracts.
If a request comes in that conflicts with live work, we say so to the enquirer without naming anyone and decline.
How is the data we give you handled?
NDA before the first file. The data stays yours, does not go into models shared with other clients, and is returned or deleted at the end of the engagement on request.
Specific retention procedures are to be defined in the contract document.
What happens if the target is not reached?
It depends on the model. In a target project the condition is written into the contract along with what happens if it is missed: rebate, extension or early closure.
We would rather discuss it at the start, when it is a clause, than at the end, when it is an argument.
First step
The first call is technical.
There is no salesperson in between. We talk about the car, and at the end we tell you whether we are of any use.