What we do, explained properly.

01What we do

Telemetry analysis

Most collaborations begin here. Together with your team, we look at the logged data from a race or test day and work out what it is really saying. That includes checking data quality, preparing the channels, and building a structured picture of the car's behavior: braking, corner entry, mid corner balance, traction, straight line performance, and how consistently the driver can reach the car's potential.

The work goes beyond reading overlaid traces. We run the data against vehicle dynamics models and, where the problem demands it, build complex mathematical models of the car and its subsystems. We use a broad set of engineering software for this, with our own RaceQ platform as one of the core tools. The result is a written report with annotated plots, and a debrief where we discuss the findings with your engineers.

Setup direction

Analysis is only useful if it changes what you do next. We translate findings into a concrete, prioritized setup direction: what to change, what to test, and what to investigate further, with the reasoning behind every recommendation. This covers areas such as springs and dampers, geometry, aero balance, and tyre usage. Where the data is not conclusive we say so, and we design the next test to close that gap.

Custom tools

When a team keeps returning to the same question, a tool serves better than a repeated report. We build software around your data and your process: bespoke analysis views, simulation studies, or data pipelines for your logger formats. Custom tools are built on the RaceQ platform, so they inherit the physics core and stay maintained.

02How we work

A typical engagement runs like this:

1. First contact. You describe the car, the series, and the problem you want solved. Confidentiality is standard practice for us; our reference work stays under NDA.
2. Data handover. Before any data moves, we agree on what makes sense: what your logging setup records, which formats you can export, and what we are comfortable working with. Then you send the exports as agreed.
3. Analysis and modeling. We analyze the sessions with our engineering toolset, RaceQ among them, and where needed build mathematical models specific to your car. The modeling spans vehicle dynamics, thermal and mechanical tyre behavior, aerodynamics, and full system analysis.
4. Findings and direction. You receive the report and the setup direction, and we walk through both in a debrief so the reasoning is fully transparent.
5. Iteration. Most value builds over time. Across test days and race events the models are refined for your car, and each new session sharpens the picture.

The same loop scales from a single session review to season long support.

03The software

RaceQ is our own vehicle dynamics and analysis platform, a desktop application built and used in house. It sits at the center of our workflow alongside the wider engineering software we use every day, and it is the base for every custom tool we deliver.

Data

Sessions load from logger exports. Multiple runs can be loaded side by side, aligned by time or distance, and marked for comparison. A preview table shows the raw samples before analysis starts, and a readiness check confirms that the channels a simulation needs are present in the data.

Analysis

Analysis views combine main, secondary, and support graphs with a synchronized track map, numeric tables, and distribution plots. Every logged channel is available alongside derived channels, presets arrange the panels for the task at hand, and a shared cursor keeps every panel on the same moment of the lap.

Simulation

The simulation side runs the car against our vehicle dynamics and tyre models: tyre force envelopes for each corner of the car, grip utilization traces, and a grip heatmap over the track show where performance is available and where it is being left unused.

The screenshots on the main page are taken directly from this software, not from mockups.

04Who we are

RaceQ is a team of engineers with backgrounds in motorsport engineering, mathematical modeling of mechanical systems, aerodynamics, and systems engineering. We came to software from engineering, not the other way around: conventional analysis methods kept limiting how deeply and how quickly we could work, so we built our own.

We work with professional race teams. Our reference work stays under NDA, which we consider a feature of working with us, not a limitation.

We are engineers first. The software is the engine behind the work, built to serve the engineering.