Measure Twice, Cut Once
My father told me to learn a trade. Twenty-five-plus years in the security industry taught me that every trade teaches the same lesson in a different accent — and that lesson is why Design Right AI exists.
My father had one piece of career advice for me: learn a trade.
I grew up in a suburb of Cleveland, Ohio. Steel town. In a place like that, a kid doesn't lack for tools or for things that need fixing, so I learned by doing. Plumbing because a pipe leaked. Carpentry because something needed to be built. Welding. Electrical. Nobody called it an education, but that's what it was.
Later, at a vocational school, I studied electronics down at the component level — resistors, capacitors, the actual physics of a circuit — and something shifted. For the first time I understood why the things I'd been fixing worked, not just how to fix them. That difference, between knowing the steps and knowing the reason, turns out to be the whole story.
Every trade teaches the same lesson
Then life happened. I had a family to raise, so I went out into the field and spent the next 25-plus years in the security industry: selling it, engineering it, running the teams that designed it.
All those trades made me a jack of all trades, master of none. For a long time I heard that as a limitation. I don't anymore. Because every trade teaches the same lesson in a different accent.
The plumber learns it when a fitting is a quarter-inch off and the whole run comes back out. The carpenter learns it when a stud is cut short. The welder learns it when a joint that looked fine fails under load. The electrician learns it when the box goes in before the layout is done.
The expensive mistakes happen at the beginning, and they don't show up until the end.
Measure twice, cut once.
The person they sent in afterward
Here's the part of the story that doesn't fit on an About page.
For a lot of those years, I was the technician who got sent in after everyone else. The one dispatched to fix what somebody forgot, what somebody didn't know how to do, what was never in the scope to begin with. I can name a dozen projects where the client never actually got the technology they paid for — systems never programmed correctly, devices never installed, staff never trained — because the job was always "hurry up, get it done, on to the next one."
It wasn't that anyone set out to shortchange the customer. It's that the incentives all pointed one way: chase the next sale, and let the last one bleed. And when that goes on long enough, the bleed becomes an acceptance. Attrition becomes a norm. The client quietly leaves in three years, and everyone acts surprised.
My counter to that never changed, on any job, in any trade: do the careful, unglamorous work at the start, and keep the customer you already have. One in hand is worth two in the bush.
Why this became software
The security industry has spent forty years recreating the same building over and over. Somebody walks the site. Somebody redraws it in a survey app, or a manufacturer's tool, or by hand. Somebody re-enters it into an estimate. Somebody rewrites the estimate into a proposal. And months later, somebody tries to reconstruct all of it in the as-builts.
Every one of those steps is a fresh cut from a measurement that was taken once, under pressure, and copied by people who weren't there. It's the stud cut short. It's the box set before the layout. The mistake is made at the beginning and paid for at the end — usually by the technician who gets sent in afterward, and by the client who wonders why the system never quite worked.
Meanwhile, the decisions that actually matter in this business are measurements. How far is the target from the camera? How far is the vehicle from the reader when the gate needs to open? How high is the keypad off the floor? Those aren't opinions. They're numbers, and they decide whether the system works.
In the latter part of my career I did something my father probably didn't picture when he told me to learn a trade: I built a software company. But I didn't leave the trades behind. I applied them. Design Right AI captures the building as it actually is — one honest measurement — and makes it the single source of truth. The design flows from it. The takeoff, the estimate, the bill of materials, the labor hours, the proposal: all downstream from one good measurement instead of five redrawn guesses.
The tools this industry already uses aren't wrong. They were just never handed a measurement to start from.
The only rule we have
Measure twice, cut once isn't a slogan around here; it's a work ethic. It means the person who does the careful work at the start earns the right to a good result at the end. It's how this country's buildings got wired and its bridges got built, and it's how we build software.
It's also why you'll see us say "human-confirmed" and "honest measurement" instead of quoting numbers we can't back up. A polished fake is still a fake. An honest gap you can see is worth more than a claim you can't check — on a drawing, in an estimate, or on a website.
If you catch us doing otherwise, tell us. That's not a platitude. It's the job.
— Dan Kozich, Founder, Design Right AI