Why I Stopped Comparing Motors by Unit Price
If your motor procurement process starts with the unit price, you're not measuring cost. You're measuring the smallest deposit on the next failure.
I've been managing component budgets at a 130-person automation equipment builder for seven years. In that time I've signed off on roughly $420,000 in cumulative motor and actuator purchases, negotiated with 22 suppliers, and logged every one of those orders in the same procurement spreadsheet. I mention this not to impress you, but because it took me about four of those seven years to stop treating the quote sheet as the source of truth.
Looking back, I should have made the switch earlier. At the time, the logic seemed clean: same rated voltage, same power class, same mounting pattern—why would I pay 3x more for a name? The answer only became obvious after I started including downtime on the same line of the spreadsheet as the invoice.
The maxon motor price question is the wrong question
Searching for maxon motor price and stopping at the first number is how procurement teams get burned. The published price for a maxon motor covers a range so wide it's almost meaningless in isolation—the same frame size can differ by a factor of two or three depending on brush type, bearing spec, encoder options, and whether you're buying the documentation package that lets a non-specialist swap it in without a redesign.
That's not a complaint. It's a warning about how to read the number. A maxon motor dc unit at a given rating might quote out at twice what a generic equivalent does. What the quote doesn't show is the spec sheet that tells your controls engineer exactly how the motor behaves at 40°C, what the torque curve looks like at 60% duty cycle, or what the recommended bearing replacement interval is. Should mention: our sustaining engineers spend roughly 11 hours a year per new motor model figuring out what the datasheet leaves out for cheap competitors. Multiply that by your loaded labor rate.
It's tempting to think you can just compare rated specs. But identical nameplate numbers from different vendors can produce wildly different outcomes in the field, because the nameplate doesn't carry the thermal assumptions, the derating curves, or the manufacturing tolerance band.
Case in point: sewing machine servo motors
We bought a batch of sewing machine servo motors for a customer's textile line three years ago. The unit we chose was about $14 cheaper per motor than the incumbent option. Across 60 units, that's $840 saved on the PO. The purchasing team felt good about it.
The problem didn't show up in week one. It showed up in month four, when stitch drift started showing up as a couple of millimeters in finished panels. Not a defect that stops the line—a defect that fails QC downstream. We ate a rework cycle, a customer complaint, and then we ate the cost of swapping back to the original motor anyway.
The surprise wasn't the price difference. It was how much of the cheaper motor's savings came from reducing the encoder resolution spec in a way the quote sheet never showed. That's the part nobody puts in the comparison table. A servo is only as good as the feedback loop it's compensating for, and that number rarely makes it onto the RFQ.
Industrial stepper motors: static accuracy isn't dynamic accuracy
Same pattern with industrial stepper motors. The datasheet gives you holding torque and step angle. What it doesn't give you—at least not prominently—is how those numbers degrade when you actually accelerate the load. A cheap stepper will look fine on a bench test. Then it loses steps on the third week of production because the resonance zone hits at exactly the speed your machine runs at.
Losing steps isn't the scary part. The scary part is that lost steps usually don't stop the machine. They produce out-of-spec parts that pass the first visual check and fail at final assembly. That's a $1,200 redo on a $60 decision. I've got two of those stories in my archive now. I don't want a third.
What happens when a linear actuator fails
Here's the counterintuitive part, and it's the reason I wrote this down: the cost of a linear actuator failure is almost never the actuator. It's everything downstream of the actuator.
When a liftgate motor or pushrod actuator fails, you're not paying for the part. You're paying for the technician who has to figure out which of five subsystems is causing the fault, the production hours lost while the line sits idle, and—if it's a customer-facing machine—the trust hit that takes about six months to recover. That's the answer to what happens when a linear actuator fails: the bill arrives in three different departments, and only one of them is the motor.
Which changes how I read quotes. I don't ask "what does the actuator cost?" I ask "what's the failure mode, and what's the replacement cycle?" A component that fails predictably at 18 months with a clean swap procedure is cheaper than one that fails unpredictably at 40 months with a disassembly procedure.
The objection: maxon is expensive, and that's real
I hear this one constantly, and I'll concede it directly: for a lot of applications, a maxon motor is not the right call.
If you're running a low-duty-cycle mechanism that opens a vent flap 20 times a day, the reliability premium isn't going to pay itself back in any timeframe you can defend to a finance team. If your product is disposable at end-of-life, the documentation package adds nothing. If your design engineer already has a validated reference solution and the failure consequence is a $40 replacement part, go buy the $40 replacement part. Honestly.
The case for the premium option only holds when three things are true: the failure consequence is expensive, the operating environment is demanding (temperature, duty cycle, or contamination), and the cost of re-engineering a substitute is higher than the price delta. When those three line up, the unit price difference is a rounding error against the TCO comparison.
The thing I kept second-guessing
Even after we standardized our procurement template around total cost of ownership, I kept second-guessing. What if we were just paying for a brand name and a Swiss flag on the label? The two quarters before our first reliability data came back were stressful, because I genuinely didn't know yet whether the spreadsheet was telling the truth.
It was. But the point is that I didn't know that when I signed the PO. I made the call on faith in the process, not on certainty, and that's what procurement decisions actually feel like. Anyone telling you otherwise is selling something.
Compare the cost of the part. Then compare the cost of what happens when the part fails. The second number is the one that shows up in the board meeting.