LapLiftSign in

For race teams · Custom builds · Any logger

Your data already knows. Nobody's reading it.

We build custom telemetry dashboards for race teams — your channels, your metrics, your car — on the platform behind LapLift. Send us one session file and we'll show you what we'd build.

Start with one file

Sound familiar?

Your engineer exports to MATLAB or Excel after every session, and the report lands in someone's inbox at midnight.
The insight exists. It's just locked in a static PDF nobody opens trackside.
RaceStudio and i2 do everything — which means one person on the team can drive them and nobody else can.
Your damper, tyre and ECU channels get recorded every session and looked at almost never.

What you get

A dashboard built around your car
Your channel set, your derived metrics, your naming. Not a generic template with your logo on it.
The views your engineer draws by hand
Damper velocity histograms, slip and heat maps over the GPS trace, G-G, stint degradation — whatever your current report has, made interactive.
Usable in the paddock, not just the trailer
Works on a phone between sessions. The person who needs the answer is rarely the person with the laptop.
Built for the whole team
Drivers, crew chief, engineer — separate logins and roles, so people see what's useful to them.
Your data stays yours
Private by default, hosted and backed up. You own your data and your dashboard.

How it works

1Scoping call45 minutes · free
We go through how your data moves today — logger, export, who reads what, and where it stalls.
2Paid discoveryAbout a week
You send one real session file. We ingest it and come back with a working prototype built on your actual data — so you see it running on your car before committing to a build.
3The build4–8 weeks typical
Fixed scope, fixed price, staged payments. You see it at every milestone, not just at the end.
4Season supportAnnual
Hosting, fixes, and new channels as the car changes. A dashboard nobody maintains stops being used by round three.

Why it isn't a from-scratch price

Commissioning race data software from nothing means paying someone to solve the boring half first — file parsing, lap detection, GPS handling, charting, video sync, accounts and sharing. That half already exists here and runs in production for drivers every weekend. What you pay for is the part that's actually yours: your channels, your maths, your views. That's why these builds land in weeks instead of quarters.

A recent build

Formula Drift team

Before: AiM logger to laptop, pull the .xrk, process in MATLAB alongside RaceStudio, produce a static PDF report per event.

After: an interactive dashboard on their full 90-channel data set — GPS traces coloured by damper position, velocity and slip, damper velocity histograms, G-G, and run-by-run tandem comparison. Open on any device, minutes after the run, with no MATLAB step.

What it costs

Three parts, stated up front so nothing arrives as a surprise:

DiscoveryA small fixed fee. You get a working prototype on your own data and a firm quote for the build.
BuildFixed price, fixed scope, staged payments. Anything added later is quoted separately rather than absorbed silently.
Season supportAn annual fee covering hosting, fixes and channel changes. Optional, but a dashboard nobody maintains gets abandoned.

Questions

Which loggers do you work with?

AiM, MoTeC, RaceCapture, RaceBox, RaceChrono, TrackAddict, Track Attack, CircuitStorm, Lap Legend, Dragy and VBOX are already supported. We have added new formats for clients before — if yours isn't on the list, ask.

Do we own what you build?

You own your dashboard and all of your data. We keep the underlying platform, which is exactly why a build costs a fraction of commissioning one from scratch.

Do we have to stop using RaceStudio or i2?

No, and most teams don't. Those stay for deep single-run work. This is for everything else — the fast read after a session, and the people on the team who were never going to open i2.

Can you handle endurance data — multiple drivers and stints in one file?

That's an active area of work right now: splitting one long race file into stints and drivers, then comparing them. If that's your problem, get in touch — you'd be shaping how it gets built.

How much data can you take?

Standard track-day and race sessions are handled today. Very large endurance logs need extra ingest work, which we scope during discovery rather than guess at.

What does it cost?

Case by case — it depends on your channel set, your logger, and how much of what you want is new work rather than something the platform already does. Every build starts with a paid discovery week at a small fixed fee; the build itself is quoted fixed-price after that, once we have seen your real data. Support and hosting are an annual line on top.

Send us one session file.

We'll tell you what we'd build with it — no charge for that conversation.

Start with one file

Or email alex@laplift.app