A strong vendor does not only build screens. They understand how a communication failure, slow data or unclear error can become downtime, rework or manual intervention.
Evaluate industrial experience, not only software experience
Industrial development combines software, operations and plant constraints. Ask whether the team has worked with critical systems, production windows, maintenance teams, shop-floor validation and existing-system communication.
- Have they modernized critical applications without stopping production?
- Do they understand material flow, quality, traceability and support?
- Can they work with plant personnel and IT without losing context?
- Can they document risks and dependencies before proposing technology?
Review integration capability
Many industrial applications fail because integration is underestimated. The vendor should be able to work with PLCs, SQL Server, APIs, RPC, local files, queues, legacy systems and plant-specific rules.
More importantly, they should design what happens when a source does not respond, arrives late or returns invalid data.
Architecture, diagnostics and maintainability
A custom system must be maintainable. Ask how they separate communication, logic, interface, logging and configuration. Also ask how technical decisions are documented and how failures are diagnosed.
If the vendor proposes reusable libraries, structured logging, integration testing and phased deployment, they are likely thinking about operations, not only code delivery.
View modernization service ↗Testing and deployment in real conditions
The key question is: how will it be tested without risking production? A serious vendor should propose representative scenarios, controlled windows, clear owners, acceptance criteria and a rollback plan.
- Dependency assessment.
- Tests with real or representative data.
- Error and recovery validation.
- Phased deployment.
- Post-launch stabilization with support and metrics.
Recommended next step
Before asking for a fixed quote, request a technical assessment. This short phase reveals risks, dependencies and decisions that may change scope, timing and real cost.
Evaluating an industrial software project?
Axyz can help map scope, risks and integrations before development starts.
Frequently asked questions
What matters more: price or industrial experience?
Price matters, but in critical systems industrial experience often reduces risk, downtime and hidden support costs.
Should the vendor understand PLCs?
If the system interacts with equipment, the vendor should understand communication logic, states, errors and validation with control systems.
What should be requested first?
A technical assessment covering dependencies, proposed architecture, risks, tests and deployment plan.