Why We Built PaddockPro (From the Paddock)

I've spent far too much money on cars. I know it. My other half knows it. The bank definitely knows it.

Track days, racing, modifications, alignment sessions, tyres, fuel, entry fees. It adds up. And somewhere along the way, I realised I was making the same mistakes over and over — not because I wasn't capable of learning, but because I couldn't remember what I'd learned.

PaddockPro exists because I got sick of that feeling. The feeling of arriving at Brands Hatch and having absolutely no idea what setup worked last time. The feeling of someone in the paddock asking "what camber are you running?" and having to half-blag my answer.

I built the tool I wished existed. Here's how.

The Notebook That Didn't Work

Like most track day enthusiasts, I started with a notebook. One of those spiral-bound A5 jobs that sat in the glovebox. The plan was simple: write down the setup after each session, note what worked, review it before the next track day.

The reality was different.

I'd scribble something illegible in the paddock — "front felt good, maybe less rear toe?" — then forget to look at it for six months. By the time I came back to that track, the notebook was either lost, unreadable, or the notes made no sense without context.

I couldn't remember what the weather was like. I couldn't remember if I'd changed the pressures. I couldn't remember whether "good turn-in" was before or after I adjusted the camber.

The Spreadsheet That Never Got Updated

So I made a spreadsheet. Obviously.

Columns for camber, toe, caster, ride height. Rows for each track day. A notes section. Conditional formatting. The works.

I used it exactly twice.

The problem with spreadsheets isn't that they're bad — they're actually great for storing data. The problem is that updating a spreadsheet from your phone in the paddock, with greasy hands and limited signal, is an absolute pain. And if you don't update it immediately, you won't update it at all.

I know because I tried. I've got half-finished spreadsheets going back years. None of them tell me what actually worked.

"What Camber Are You Running?"

This is the moment that really got to me.

I'm at a track day. Nice Caterham next to me in the paddock. We get chatting about setup. He asks what camber I'm running.

I knew — roughly — that I had some negative camber. I'd paid for an alignment a few months back. The guy had said some numbers. I'd nodded along. I'd definitely meant to photograph the printout.

But standing there, being asked a direct question about my own car, I couldn't answer with any confidence. "Minus one point something? I'd have to check."

It wasn't a knowledge problem. It was an ownership problem. I didn't own my setup. I was just… using it.

What If the Alignment Shop Was in My Pocket?

I run a garage with my partner. Not motorsport — regular workshop stuff. MOTs, servicing, diagnostics. But one thing we do is performance alignments. Proper ones. Not just tracking — full geometry setup for track use.

Matt — my partner and the technical brain — can look at a car, hear the intended use, consider the suspension and tyres, and produce alignment settings that transform how it drives. It's part knowledge, part experience, part instinct.

I'd watched him do it for years. I'd said to him a dozen times: "You need to document this. Systematise it. It's all in your head."

His answer was always the same: "You can't. Too many variables."

Then something changed.

It wasn't perfect at first. The early outputs were generic. But we kept refining. Testing. Adjusting. Eventually, even Matt was impressed. The system was producing recommendations he'd be happy to put his name to.

That became the core of PaddockPro — the same alignment intelligence we use in the garage, packaged for enthusiasts who want to understand their own cars.

More Than Just Alignment

The alignment tool was the seed. But once we started building, we realised the real value wasn't just recommendations — it was context.

What if the app remembered your setup history? What if it knew what track you were going to and suggested a starting point based on similar tracks you'd visited? What if it logged the weather automatically so you didn't have to remember?

What if there were checklists so you never forgot wheel torques again?

What if you could log "the car understeers mid-corner" and get specific, structured recommendations based on your setup data — coming soon with the Symptom and Solution Guide.

That's what PaddockPro became. Not just a tool — a proper companion for anyone who cares about their car and wants to actually improve.

What This Is Really About

I'm not trying to make you faster. I mean, you probably will be — better setup, more consistent approach, fewer forgotten checks. But that's not really the point.

The point is ownership.

When someone in the paddock asks what camber you're running, you don't blag it. You pull out your phone, show them your setup sheet, and explain why you chose those numbers for this track in these conditions.

When you come back to a circuit after six months, you don't start from scratch. You have your history. You know what worked. You pick up where you left off.

When the alignment shop asks what you want, you don't say "track use, please" and hope for the best. You show them exactly what you're after and why.

Why I'm Telling You This

Because I think you might be where I was.

You've got a notebook that doesn't get updated. You've got a spreadsheet you made once. You've got setup printouts in the glovebox you haven't looked at in months.

You're spending real money on track days — hundreds or thousands of pounds — and every time you go, you're starting from scratch because the knowledge from last time didn't stick.

That's not a character flaw. That's a systems problem. And I built a system to fix it.

If you're the kind of person who cares about this stuff — who actually wants to understand their car, not just drive it — PaddockPro is for you.

If you're happy with "minus one point something, I'd have to check," that's fine too. But if that answer bothers you the way it bothered me, maybe give it a try.