UpLate Garage is a blog, a knowledge hub, and — soon — an app, all built around one habit: documenting a project build honestly, to the minute and the dollar. No rounded-up hours. No "about three grand." The real numbers, because the real numbers are the interesting part.
Someone at a meet asked how much I'd spent on my MY99 Subaru WRX. I gave the number every builder gives: "ahh, about ten grand?" — and realised on the drive home I had no idea if that was true. Not within five grand, honestly. The receipts were in three different inboxes, a shoebox, and my memory, which is the least reliable of the three.
Worse was the hours. I'd told myself the rear subframe refresh took "a weekend." It took four. The seized bolts alone ate most of a Saturday, and I'd quietly deleted that from the story because it didn't fit the version where I'm good at this.
That's the thing every build thread does: it remembers the install and forgets the wrestling. The result is a hobby that lies to you about itself — about what it costs, how long it takes, and where your time actually goes. I didn't want a prettier version of my build. I wanted the true one.
So I started logging it properly. The blog is where the logs live. The app is the tool I wished I'd had on day one. This site is both.
Anyone can put "authenticity" in a footer. The difference is whether the thing is actually built to make lying hard. Mine is. Here's what that means in practice — these aren't slogans, they're rules the app and the blog both obey:
Time the timer measured is logged. Time I'm backfilling from memory is estimated, and it's labelled, stored, and shown separately — never blended into one flattering total. A guess wearing the same font as a measurement is the original sin.
Parts bolted to the car, parts-plus-overheads, and what it actually cost me including tools — three different questions with three different answers. Mashing them into a single "build cost" is how every garage budget deceives its owner.
Diagnosing a fault and fighting a seized bolt is work on the car, logged against the system it belongs to — not quietly dropped because it doesn't make the highlight reel. "How long did it take" includes the parts that hurt.
If I've never touched the electronics, that area sits at zero — and the site shows it at zero. Empty isn't a gap to hide; it's a true statement about where the build's attention has gone.
I'm not a company. I'm one person who builds project cars after work and writes down what happens. Right now that's a MY99 WRX living in a single-car garage that's always a bit too cold.
Everything on this site — the logs, the guides, the app in development — comes from my own builds. When a guide says a job took an hour and ten, that's because I timed it on my car, not because it sounded about right. When I don't know something, the post says so.
Being solo is the point, not an apology. There's no brand voice between you and the person who actually did the work. If something here is wrong, it's wrong because I got it wrong — and I'd rather you tell me than I pretend otherwise.
I'd rather tell you exactly where this stands than imply it's further along than it is. This is the honest state of things:
No launch-date theatre, no "revolutionary platform" language. A blog that works today and an app being built carefully. That's the whole pitch.
Don't take my word for the honesty thing — go read a build log and check the numbers add up. That's the best way to know if this is for you.