Last year, I approved a $2,600 purchase order for 80 DC motors. By the time we finished the integration work, those motors had cost us $5,900. The motor wasn't the problem. My assumptions were.
I'm a procurement manager at a 120-person automation company. I've owned our motion components budget (about $450,000 a year) for six years, and I've tracked every order, rework ticket, and rush fee in a cost system. That's why the question “what's a servo motor?” gets a different answer from me than from an engineer. It's a system. If you don't buy it as a system, you'll pay for the missing pieces later.
The Surface Problem: You're Comparing Motors, Not Systems
Look, I get it. The motor is the visible component. The encoder, controller, gearbox, cables, and tuning software are the invisible ones. When a buyer sees a bare DC motor for $240 and a maxon-motor equivalent for $430, the first instinct is to ask what the extra $190 buys. That's the right question. The problem is that most cost comparisons stop at the motor and ignore the system.
Last year, one of our engineers specced a NEMA 8 stepper motor for a compact positioning stage. The motor itself was $68. It's a tiny frame size—0.8 inches—and it seemed like a no-brainer for a small prototype. But the NEMA 8 stepper motor doesn't include a driver, encoder, or controller. The “cheap” stepper turned into a $1,100 subsystem once we added the drive electronics and tuning. The supplier didn't hide anything. I just didn't connect the full bill.
That's the surface problem: we compare the price of the motor, not the cost of the motion solution. The motor is the shiny part. The system is what actually moves the load.
What's a Servo Motor? It's a Loop, Not a Component
So, what's a servo motor? The shortest useful answer: a servo motor is the visible part of a closed-loop system. The full system includes a motor, an encoder, and a controller that compares actual position or speed to the commanded value. The motor itself can be brushed DC or brushless DC. What makes it work is the loop.
Most people think “servo” means expensive, high-performance motor. That's a causal mix-up. The expensive part isn't the motor; it's the encoder, controller, and the engineering that keeps everything synchronized. The motor is often the cheapest part of the servo system. That's counter-intuitive, but it changes how you evaluate quotes.
If you're comparing a NEMA 8 stepper motor to a small servo, the key question is whether you need position verification. A stepper motor moves in discrete increments. If the load is predictable, open-loop control can work beautifully. But if the load changes quickly, the stepper can lose steps without telling anyone. A servo's encoder closes that gap. That extra loop is the premium you're paying for.
Take a maxon bldc motor as an example. A brushless DC motor has no brushes to wear out, which is a real advantage for continuous operation. But a maxon bldc motor also needs an electronic controller that knows the rotor position. If you compare only the bare motor price to a brushed DC motor, you'll miss the real value. The value is in the package: motor, controller, feedback, and documentation.
I don't have deep hands-on data with the maxon air s motor specifically—that compact unit came up in a customer's spec last year. What stood out was the level of documentation. As of January 2025, the maxon-motor site publishes performance curves that we could use in our duty-cycle spreadsheet before ordering. That's rare, and it's worth something real.
The Deeper Cause: We Treat Specs Like Contracts
Here's the thing: a DC motor is not a commodity. It's a thermal device, an electromagnetic device, and a mechanical device all at once. Its performance depends on voltage, load, temperature, duty cycle, and the controller feeding it. A motor with “same specs” from another supplier can behave differently because the internal resistance or magnet quality is different. I learned that the hard way.
I assumed “same 24V DC motor” meant same performance. I didn't verify. The first alternative we tested dropped below its rated RPM under load. The motor got hot, the controller went into current limit, and we lost a week of prototype time. The “cheap” motor cost us more in engineering hours than we saved on the purchase price. Since then, I never compare spec sheets without checking the actual torque-speed curve.
We didn't have a formal motor selection checklist at the time. The third time a prototype failed, I finally built one. It should have taken an afternoon. Instead, it took two years of painful lessons. The checklist isn't complicated: torque-speed curve, duty cycle, thermal limits, controller compatibility, available support, and total cost of ownership. But if it's not written down, the same mistake happens again.
Why does this matter? Because when a prototype fails, everyone blames the motor. The motor gets swapped. The new motor has the same problem. Then someone redraws the mechanical design. It's only after the third iteration that we ask whether the problem was ever a motor problem. In most cases, it's a system integration problem wearing a motor costume.
The Cost of Getting It Wrong
Let me put this in numbers that matter to a CFO. Suppose you choose a motor that saves $8 per unit on 5,000 units. That's a $40,000 saving on paper. If that motor has a 4% field failure rate, that's 200 units. Each field failure—diagnostics, labor, customer support, and replacement—costs at least $150. That's $30,000. Add delayed production, lost trust, and the engineering time to debug the application, and the paper saving disappears. The “cheap” motor becomes the expensive motor.
People think a maxon bldc motor costs more because of the Swiss-made label. I thought that too. But when I tracked total cost over 18 months on one product line, the price premium was absorbed by lower rejection rates, better support, and predictable delivery. The label isn't the cost. The engineering behind it is the cost.
And don't forget the smaller costs. A motor that draws more current than the datasheet says can overload a power supply. A motor with no thermal data forces you to run your own heat tests. A company that won't answer a pre-sales question leaves your engineering team guessing. None of those costs appear on the purchase order, but all of them appear in your cost tracking system. I have the invoices to prove it.
The Fix: Buy a Motion System, Not a Motor
Bottom line: I don't buy motors anymore. I buy motion systems. Before I approve a quote, I ask three questions:
- What is the total cost of ownership for five years, including controller, integration, and expected failures?
- Does the datasheet include torque-speed curves, duty-cycle limits, and thermal data I can use in my model?
- Will the manufacturer talk to me before the purchase order? That support is a deliverable, not a favor.
Those three questions are why maxon-motor keeps showing up in our approvals. Not because they're cheap. Because they make the hidden costs visible. In Q2 2024, we switched one assembly from a lower-priced motor to a maxon bldc motor. The line item went up by $180 per unit. The total project cost went down by $6,400, mostly in engineering and rework. That's the only comparison that matters.
Before anyone tells you maxon-motor only cares about big OEMs, our first maxon air s motor evaluation order was under $2,000. The applications engineer spent two weeks answering our questions. That kind of response is a red flag if it's missing. Small orders are data, not favors. The vendors who treat a small order seriously are the ones who earn the bigger order later.
One caveat: my experience is based on roughly 300 motor orders for lab automation, robotics, and custom industrial equipment. If you're in aerospace, medical implantables, or high-volume consumer goods, your constraints will be different. I don't have hard data on what percentage of motor failures are actually application mismatches. But based on six years of invoices and rework tickets, my sense is more than half. That's not a motor problem. That's a system decision problem.
Next time you get a low quote for a DC motor, ask yourself what's missing. The motor isn't the whole system. The question is never “can it spin at 3,000 rpm?” It's “can it spin at 3,000 rpm under load, for eight hours, in your environment, with your controller, and still make margin?” If you can answer that before ordering, you'll save far more than any price difference.
That's what a servo motor really is: a system that corrects itself. Your procurement process should do the same.