Most companies begin with a business plan.
Mecka began with a broken car.
Getting that car on the road was not just about engines and frames. It exposed how projects stall because information gets lost, handoffs break and small human mistakes create oversized delays.
Those lessons formed Mecka's DNA.
The origin story (with greasy hands)
Part 1: Pictures Lie
In 2010, Robin was ready for a new car.
He had been driving a 2004 WRX and was ready for an upgrade to something with more power. He picked the one he wanted. The “big brother” of the WRX which is the WRX STI. Larger engine, heavy-duty transmission, better steering and way more fun to drive.
Robin was on the quest for a deal. And found his dream car online. A 2008 Subaru WRX STI that was involved in a car crash. All he had was online pictures, but it looked like a getting it back on the road was a manageable project.
When the car arrived, it was technically drivable off the trailer, but barely—the front end twisted, the rear shifted, the frame bent from two separate impacts. It looked less like a performance machine and more like a cautionary tale.
Now the full story could be seen: the previous driver had lost control, hit a wall or guardrail hard enough to shift the entire engine and front structure, then spun and hit again—this time pushing the rear out of alignment too. The car’s “middle” was fine, but both ends had moved. That meant real framework before anything else could be trusted.
Mecka Lesson #1: Scrutiny (The Reality Check)
Don’t trust the "glossy" view. Robin bought a car that looked manageable in photos, only to find a ton of problems in person. In the parts world, a spreadsheet might look clean at a glance, but the truth is in the details. We build Mecka to provide the Scrutiny needed to uncover the ground truth immediately, so you aren’t caught off guard by "bent frames" in your data.
Part 2: The teardown: “Let’s fix Humpty Dumpty”
Robin wasn’t a mechanic—this was his entry point. With some friends who are mechanics, they started dismantling what they could: bolts off, components off, pieces organized as best as they knew how. Robin got a first-hand appreciation for how challenging (and frankly artistic) the work can be when you’re operating in tiny spaces with tight tolerances.
The first “real” step was frame repair, so Robin brought the car to a body shop and explained the project. They agreed to take it on—but he learned a painful truth about discovery-based work: every time the shop found something new that required ordering parts, the car effectively went to the back of the queue. Touch it, discover a broken piece, order parts, wait… and when parts arrived, wait again until it bubbled back up.
The result: the STI sat at the body shop for almost a year and a half. Weeks would pass. A month and a half would vanish because one more part was needed. It was a slow, stop-and-go progress—exactly the kind that drains momentum from any project.
Worse, not every delay was “mechanical.” Robin also experienced the simplest kind of failure: ordering parts by phone, only to find out later that the order hadn’t actually been placed—because it was the end of the day, or someone hung up, or got pulled into something else – and never finished the work.
Mecka Lesson #2: Streamline (Reduce the Clicks)
Every extra step is a place for progress to stall. In the rebuild, a missed phone call cost weeks. In Mecka, we obsess over reducing the "clicks" required to move a task forward. Fewer steps mean fewer places to drop the baton.
Part 3: Reassembly from a “bucket of bolts”
Once the frame was fixed and everything was aligned, it was time for the next step. Reuniting the now straightened frame, with the engine sitting on a crate, using a literal bucket of bolts.
When the car was taken apart, there was no assembly plans. That means the various loose parts had no labels. Just a disorganized bucket-of-bolts.
One mechanic looked at the mess and sighed, “Buddy, what are you bringing me?”
Reassembly meant detective work—figuring out what goes where—on top of the already tough job of putting Humpty Dumpty back together again.
Mecka Lesson #3: Structure (Label the Bolts)
Unlabeled bolts are the physical version of unstructured data. Structure is what makes scale possible. Whether it’s organizing task ownership or mapping complex parts data, we ensure every "bolt" is labeled so you aren’t playing detective when it’s time to reassemble.
Part 4: Standards Matter (aka The Sensors, The Limp Mode and the Clock Spring)
After the car was reassembled—new parts purchased, crash systems addressed (airbag sensors, airbags for the steering wheel, a new clock spring, and more)—the next step was inspection and certification.
One rule in particular hit hard: for certification, used crash sensors weren’t accepted. That meant Robin had to sell the used sensors he’d bought and replace them with full-cost dealership parts.
Even with the pricy parts, the STI would drop into limp mode—an intentionally limited-power state designed to let you get off the road safely (not drive home). This became a three-month troubleshooting stretch centered on one deceptively small component: the clock spring (the part behind the steering wheel that maintains electrical connections as the wheel turns).
Even with new OEM Subaru parts—twice—brand-new parts failed. It took three replacements to fix the issue. It was a reminder that even the best standards can still be implemented incorrectly.
Mecka Lesson #4: Standards (The Language of Precision)
Just as Robin had to meet strict provincial safety standards for sensors and frame alignment, the parts industry relies on ACES and PIES. We don't just treat these as "requirements"—we treat them as the foundation that allows your business to talk to the "big boys" of the industry.
Part 5: The job isn’t done until the paperwork is finished
When it was time to bring the car in for certification, it wasn’t “just bring the car.” Robin had to bring proof: receipts, paperwork, printed documents, and a full before-and-after trail. He assembled a binder that included photos of the crashed car, photos during repairs, and photos after—evidence that the work was done and done properly.
That binder represented a 3.5-year endeavor—so it wasn’t a small thing to pull together. The first time through, inspectors flagged remaining items to address. Even more fixes needed, then reinspection, and after about a day and a half the car finally got the green light. Then it could be registered and driven again.
Mecka Lesson #5: Stability (The Foundation of Trust)
The 3.5-year "binder" of receipts and photos proved the work was done right. In Mecka, audit trails and documentation aren’t just overhead; they provide the Stability your business needs. Documentation is how trust is built with your customers and your team.
The Better Way
By the time the STI finally roared to life in 2013, three and a half years had passed.
The rebuild made one thing painfully clear: projects don’t derail only because they’re complex. They derail because a process can be fragile. A part order that doesn’t get placed, a form that gets stuck in someone’s inbox, a task that’s “basically done” but not actually completed—those tiny slips create big delays.
Mecka’s philosophy is to remove as many failure points as possible: automate the handoffs, make the next action obvious, and reduce the workflow to the minimum number of steps. When the right next step is a single clear action, it’s easier to keep momentum—and easier to know when something truly hasn’t been done.
There are specific lessons learned. The same “label the bolts” problem exists in the parts industry at massive scale. Data arrives in all kind of ways, including spreadsheets and emails. It is often inconsistent, incomplete, and hard to trust.
Rebuilding a crashed car taught Robin what building any serious system teaches you sooner or later: the work is rarely “just the work.” It’s the waiting, the handoffs, the missing context, the standards, the proofs, the exceptions—and the human moments where something small doesn’t get completed and everything downstream slows down.
The STI story comes down to five concepts:
- Scrutiny (The Reality Check) – Don’t trust the “glossy” view and get caught off guard by “bent frames” in your data.
- Streamline (Reduce the Clicks) – Fewer steps means fewer chances for a project to get delayed.
- Structure (Label the Bolts) – Scale is only possible when you are organised.
- Standards (The Language of Precision) – The foundation that lets any sized business compete.
- Stability (The Foundation of Trust) – Prove that all work is done correctly builds relationships.
Mecka wasn’t born in a boardroom. It was born in the grease of a garage, in the frustration of a year-long wait, and in that disorganized bucket of bolts. Robin spent those years living the pain of his future customers so that, one day, they wouldn’t have to.
Today, the STI is more than a car. It’s a reminder that even when things are shifted, bent, and broken, if you have the right tools and enough heart, you can build something that changes everything.
