Jimenez Julien, the builder who keeps InspectBay honest to the bay

Why I built an inspection tool for repair shops

I did not grow up in a service bay. I got here the long way, by building small software for small operators and then sitting in their businesses long enough to understand where the day actually breaks. In automotive repair the break is almost always the same place: the moment between the technician finding something and the customer agreeing to fix it. Everything upstream of that moment is skilled labor. Everything downstream of it is billable. The moment itself, historically, was a phone call and a hope.

The first shop that let me shadow a full week was a four bay independent with two ASE certified techs and one advisor working a counter, a phone and a parts line at the same time. I counted the approval calls. I watched a tech pull a wheel, find a rotor worn past spec, write it on a carbon copy sheet in handwriting nobody else could read, and then wait forty minutes for a decision that never came before lunch. The car sat in the air. The tech went and did an oil change on somebody else's ticket. Nothing about that was a technology problem in the abstract. It was a very specific problem: the customer could not see what the technician was looking at.

InspectBay came out of that week. The design rule I set for myself is that the tech does not get a new job. He gets a camera that is already inside the inspection line, three grade buttons big enough to hit with a glove on, and a numeric field for the measurement he was going to write down anyway. The service advisor gets the red lines sorted to the top and a link to send. The customer gets a photo he can zoom into and a single decision per line. Everything else in the product exists to protect those three jobs from getting complicated.

What I learned about this trade, more than anything, is that shop owners are exhausted by software promises. They have been sold management systems that took six weeks to configure and a marketing dashboard nobody opened twice. So I hold the product to an unglamorous standard: a shop should be running real inspections the same day it signs up, and a flat rate technician should be able to see the payoff in his own numbers inside two weeks. If a feature cannot pass those two tests, it does not ship.

I work with operators the same way every quarter. I run process reviews with a rotating group of owners and advisors across the United States, from single lift shops to five location groups. I ask for the tickets that went badly, not the ones that went well. When a shop tells me the follow up queue is generating more work than the front counter can schedule, that is a product decision waiting to be made, and it usually shows up in the app within a release or two.

What I am accountable for is narrow and specific. I own the roadmap, the words on this website, the pricing, and the promise that your inspection history belongs to your shop and is exportable whenever you ask for it. If something in the product wastes a technician's time, that is my mistake to fix, and the email address at the bottom of this page comes to me.

Experience and expertise

• Software for small operators since 2016. Tools built for businesses where the owner is also the person answering the phone, which means every screen has to survive being used while distracted.
• Field research inside repair shops. Multi day observation in independent shops across several US regions, timing approval cycles, counting callbacks and reading actual repair orders line by line.
• Inspection process design. Templates built with lead technicians for brake, suspension, fluid, tire, battery and under hood checks, tuned so a full multi point inspection finishes in four to seven minutes.
• Customer facing communication. Wording, ordering and severity language tested against real customers, because a report that reads like an accusation gets declined no matter how good the photo is.
• Publishing and product operations at MLJ, SASU. The company that publishes InspectBay and is responsible for its hosting, its billing and its data commitments.

How this product is built and maintained

InspectBay ships in small, frequent releases rather than large annual versions, and every release note is written in plain language a service advisor can read in under a minute. New features start as a problem described by a named shop, not as a line on a competitive matrix. Before anything reaches production it is tested on a phone with a cracked screen and a weak signal, because that is the real hardware in a service bay.

Editorially, every number on this website comes from aggregated shop data or from measured field work, and it gets restated or removed when it stops being true. Testimonials are published with the person's real name, role, business and city, and with their permission. No claim about approval rates, repair order values or recovered work appears here unless it can be traced to something we actually measured.

On the data side, the commitment is short: your shop owns its inspections, photos and customer records, exports are available on request without a support ticket, and nothing is sold or handed to a parts vendor. Security work is boring on purpose, with encrypted transport, encrypted storage and access limited to the people who need it to support you.

Contact the author

If you run a shop and something here does not match what you see at your counter, tell me. I read the mail myself and I would rather hear the hard version. Write to jimenezjulien42@gmail.com, or reach me on any of the profiles below.

• jimenezjulien.com, the personal site and project index
• X, @mljjulien, product notes and build updates
• LinkedIn, Jimenez Julien, professional background
• Facebook, Julien Jimenez
• Instagram, julienjimenez.mlj