Skip to main content
About

Why I built Apex Derby

I run my church's pinewood derby. Apex Derby is the software I wished I'd had the first year.

I didn't set out to be a derby guy

Another dad from the church and I were clearing out the storage room, moving chairs and tables, and found an old wooden derby set in the back. We both remembered how much fun it was as kids. We asked around, the youth were excited, and that was that.

We split the work. The church admin found the families and handled the logistics. He's handy and has the tools, so he took the physical setup and the pit stop on race day. I'm the techy one, so I took the spreadsheet and the schedule. We rent the track from another church, and it came with an automatic timer, so nobody had to build that.

That derby has run for three years now and grown every year. This past year had just under 50 racers, everyone got at least three runs, and the day moved.

The spreadsheet year

Year one ran on a spreadsheet. It mostly worked, and it was ugly. My laptop was cloned to the projector, so the whole room watched me click around and type between heats. The display was a flat grid of numbers, and families hunted for their own name in it. I'm not gifted with graphics.

The real problem was fairness. My lane juggling wasn't good. Some kids ran the same lane every heat. Some families raced each other over and over. A few kids ran three heats in a row and then sat for the rest of the morning. People noticed, and they were right to.

“The whole room watched me click around and type between heats.”
Year one

What I wanted instead

We run a mixed qualifying round and then a single-elimination bracket, split into groups. What I wanted was more variety in who raced whom, and a schedule that sorts the heats properly and keeps them streaming along, one after the other, without me fiddling in a spreadsheet between races.

The lane rotation math was worked out decades ago by people who did it far better than I could have. Their math is impeccable. I borrow it now for single elimination and the other formats, so every heat is built the same careful way whichever format you pick.

The rest followed from race day. Times come straight from the timer, because one of our finals came down to a thousandth of a second and the eye test doesn't work. The display screen shows the room what's up next and who just won, and parents follow their own racer on their phone instead of squinting at my spreadsheet.

This year I ran another church's derby on it, start to finish. The timer fed results to the site live, spectators scanned a QR code in the stands, and I walked around the room watching the laptop from a distance. It was more pressure than my own derby, because those people don't know me. It worked. I still didn't fully relax until the last heat.

The display screen during finals.

Who's behind it

It's one person, me, with a lot of help from AI along the way. I build it, keep it running and read every email. Setting up is free, so you can take your time with it, and you only pay once you're ready to race. If Apex Derby lets you down on race day, I'll refund your event or give you another one free.

If you're interested, please sign up and try the free practice event.

Questions, ideas, or a timer we don't support yet? Email hello@apexderby.com. It comes straight to me.

Running your first one? Start with the race-day planner. Then get enough volunteers. It's the biggest reason our event works.

Free to set up. $50 USD on race day.

How pricing works