How to Buy Industrial Software Without Getting Burned
A plain-English vendor-selection guide for ops leaders: the questions that surface red flags, what a safe contract looks like, and when to walk away from a demo.
Short answer: most industrial software purchases go sideways for the same three reasons—wrong problem, wrong scope, wrong vendor. A 30-minute audit of the demo and the contract catches almost all of it before the first invoice.
The three failure modes
- Wrong problem — the vendor solves the symptom (“we need a dashboard”) instead of the cause (“we don't trust our inventory numbers”). Dashboards don't fix data quality.
- Wrong scope — the vendor sells a platform when you needed a tool. You now own a $60K seat-license problem for a $6K-of-value job.
- Wrong vendor — the salesperson is sharp, the implementer is a subcontractor, and the product manager ghosts you after launch.
Questions that surface red flags
- “Who will I be working with after we sign?” If the answer is vague, assume it's a subcontractor.
- “What does a real implementation timeline look like for a company our size?” Vague = they don't know.
- “Show me the ugliest customer in your book—the one where it's not perfect.” Vendors who won't show you are hiding something.
- “What happens to my data if I leave?” You want export tooling, not a paragraph from legal.
- “Who owns the code we build together?” Our answer is always “you do.” Ask every vendor.
What a safe contract looks like
- Monthly or quarterly out — no multi-year lock-ins on new relationships.
- Data portability clause — your data exports in a documented format within a named SLA.
- Scoped milestones — payment tied to visible outputs, not calendar time.
- IP ownership named explicitly — don't assume, write it down.
- A cap on scope creep — change orders in writing, approved in writing.
When to walk away from a demo
- Everything is always “on the roadmap.”
- You can't get a straight answer about implementation owner.
- The reference calls all sound scripted.
- The proposal lands with a sense of urgency you didn't create.
CIRQL's posture is deliberate: monthly retainer, you own the code, one team from discovery to delivery. See how we work and ownership FAQ.