We build pace.
Outlier Speed Co. has built iRacing setups since 2020. We're a small group of builders and drivers who treat setup work like the engineering it is — not like content.
The short version.
How Outlier started, what's changed since, what hasn't.
Outlier started in 2020 with one builder, one car, and one shared Google Drive. The model hasn't changed much. We still build setups for the races we actually run — Monday qualifying, Tuesday open practice, Wednesday fixed, the whole week.
The first year was three builders trading files on Discord. The second year added a road racer who could read damper traces faster than the rest of us could open the file. Year three we started getting requests from drivers we'd never met, which is when the subscription model showed up.
Today there are six builders and a small group of house drivers spread across NASCAR, road, and short track. New setups drop every Monday morning. The schedule has been on time for forty-eight consecutive weeks.
What's different from year one is the bar. Every build runs through a telemetry baseline before the file gets shipped — comparison runs against a clean lap, damper histogram, tire-temperature spread across a green-flag stint. We don't ship setups the builder won't drive themselves.
What hasn't changed: nobody who works on Outlier setups is a content creator first. There's no YouTube algorithm chasing what we build. The setups exist because we wanted them for our own races. The shop happened second.
That's the whole story. Six years in, the brief is the same as week one: build the file you'd be relieved to load before a real race.
Three things, written down.
The shop runs on these. If a build breaks any of them, it doesn't ship.
Telemetry first.
Every build starts with a baseline run, not a hunch. We compare against a clean reference lap, look at the damper histogram, watch tire temps across a full stint. The setup that ships is the one the trace says is faster, not the one that felt right after two laps on cold rubber.
Built by drivers.
Every builder on the team is also a driver. If a builder won't load the file into their own race that week, it isn't finished. That single rule kills more "almost there" setups than any review process we tried before it.
No filler weeks.
If the iRacing schedule lands on a track we can't build with confidence inside the week, we say so in the drop notes. Nobody gets a recycled file with the track name swapped. Forty-eight straight weeks on time, zero filler — that's the bar.
Builders & drivers.
Six builders across the disciplines, three house drivers on the running roster.
Builder 2.
BUILDER·NASCAR NEXT GENBuilder 3.
BUILDER·TRUCKSBuilder 4.
BUILDER·SHORT TRACKBuilder 5.
BUILDER·XFINITY / B OPENBuilder 6.
BUILDER·ROAD / GTPDriver 1.
DRIVER·COKE SERIESDriver 2.
DRIVER·SHORT TRACKDriver 3.
DRIVER·ROADHow a setup gets built.
From schedule pull on Wednesday to Monday-morning drop. No corners cut.
Schedule pull.
The iRacing schedule for next week is pulled Wednesday morning. A builder is assigned to each track based on discipline. If a track is borderline, it gets flagged before any work starts so we can either build it right or pass on it.
Telemetry baseline.
A clean baseline lap is recorded and the build runs against it. Iterative testing — small changes, single variables — over a full green-flag stint. The builder takes notes on what each change did and why the next one is the next one.
Second pair of hands.
A second builder loads the file and drives it without the first builder's notes. They write their own notes. If the two notes don't agree, the file goes back. If they do, the setup is locked.
Monday morning.
The setup ships Monday with the builder's notes — what we tuned, what to feel for, where the lap time lives. Available to subscribers and individual buyers at the same time. No early access, no staggered drops.
Two ways in.
We bring on new builders when we need them and new house drivers when the roster has room. Applications stay open between rounds.
Drive for Outlier.
House drivers run on Outlier setups in iRacing series we cover. You bring the laps, we bring the file. Applications are reviewed in batches — typically once per season change.
Build for Outlier.
Builders work on weekly drops in one or two disciplines. Telemetry analysis isn't optional — you'll spend at least as much time in a trace viewer as the sim itself. Pay scales with output and tenure.