3 Things a CEO Should Ask Their Hardware Team About Tooling
By the CADPreview Team · Series: The Hardware Budget
"The most expensive question in engineering is the one nobody asked."
Your hardware team chose their tools. They probably chose them well, by the standards they were optimising for. The problem is that engineers optimise for technical confidence, not cost efficiency. That is not a criticism. It is a structural fact, and it means the business case for the toolchain rarely gets examined by anyone in a position to challenge it.
These three questions are designed to change that. They do not require you to understand what a Gerber file is. They require your engineers to justify a recurring cost in terms a business should care about.
Question 1: Is this tool fit for purpose, or fit for comfort?
Fit for purpose means the tool's capabilities are genuinely required by the work your team is doing. Fit for comfort means the team knows the tool, trusts it, and would have to invest time to become equally productive in an alternative.
Both are real. Only one of them is a reason to spend money.
The question to ask is specific: which features, that a free or lower-cost tool cannot provide, does your team actively use in the work they are doing right now?
If the answer is "we are designing a miniature computer where every signal on the board is operating at the absolute limits of physics," that is a real answer. The tool is earning its cost. If the answer is schematic capture, board layout, and generating files for the manufacturer, that workflow runs on KiCad. KiCad is free, open source, and produces outputs that manufacturers cannot distinguish from those generated by tools costing thousands of pounds per seat per year.
Most hardware products do not push limits that justify premium tooling. Comfort is not a business reason to spend money. Purpose is.
Question 2: What problem does the free alternative actually fail to solve?
Do not ask whether your engineers have looked at free tools. That question is too easy to dismiss. Ask for the specific failure: what did you try to do, and what exactly did it not do?
Open source tools like KiCad exist because engineers needed to solve real problems and built the solution themselves. That is a fundamentally different incentive from a commercial product team building toward a revenue target. Features exist because they were needed, not because they belong on a feature matrix. The genuine gaps are real, but they are specific. If your engineer can name them precisely, that is a legitimate justification. If the answer is vague, "it is not as polished" or "it would take time to learn," you are not looking at a tool problem. You are looking at a familiarity preference, and that is a different conversation entirely.
Question 3: Is the tool incapable, or is the engineer unfamiliar with the alternative?
This is the one no engineer will volunteer about themselves, which is precisely why it needs to come from you.
"KiCad cannot do what we need" can mean two very different things. It can mean the tool genuinely lacks a capability the work requires. It can also mean the engineer has not used KiCad recently, or at all, and is not confident they could be productive in it. Both answers sound identical from the outside.
The distinction matters because the solutions are completely different. A genuine capability gap justifies a licence cost. A familiarity gap justifies a training investment, which is almost always cheaper, and produces an engineer with broader skills who is less dependent on a single vendor's ecosystem.
The Honest Summary
A tool should be justified by what the work demands, not by what the team already knows. Fit for purpose engineering applies to the products you build. It applies equally to the tools you use to build them.
And one question worth keeping for the next renewal: what happens to this investment if the engineer who chose it leaves?
CADPreview is a web-based viewer for KiCad projects hosted on GitHub. Connect your repo once, share a link, and your whole team sees the current design in a browser, without installing anything.