13 Questions to Ask Industrial Automation Cell Vendors Before You Sign

Thirteen questions separate an automation integrator who will engineer for your constraints from one who will bolt a generic cell onto your floor. They cover engineering depth, project management, application experience, lifecycle support, and business stability. Ask all thirteen of every vendor on your shortlist.

You have identified a need for a custom automation cell or a turnkey robotic system, and you have a shortlist. Now the real work begins.

Choosing the wrong partner for an industrial automation cell is not just a budget problem. It is a long commitment of your team's time and operational attention, and a vendor who overpromises does not simply miss a timeline. They disrupt your production floor, strain your workforce, and leave you with a system that underperforms for years.

The reverse is also true. A strong integrator understands your process, engineers around your actual constraints, and supports the system across its life. You cannot tell which one you are talking to by reading their website. You can tell by asking the right questions before you sign anything.

Below are thirteen questions, organized by what matters most in a high-stakes automation project. For each one, why it matters, what a strong answer sounds like, and what a weak answer sounds like. Our robotic automation page covers the systems these questions apply to.

Category 1: Engineering capabilities

These questions reveal whether a vendor has the technical depth to solve your specific problem.

1. What is your approach to process analysis before you start designing a solution?

Why it matters: Strong integrators do not sell you a robot. They sell you a system that solves a manufacturing problem, and that requires understanding your process first. A vendor who skips this step designs something that works in theory and struggles on your floor.

Strong answer: An upfront discovery phase with on-site visits, process observation, cycle time analysis, and time spent with your engineering and operations teams. They document current state, identify the variables that will affect performance such as part variation, changeovers, and environmental factors, and validate assumptions before design starts.

Weak answer: A quote built from a phone call and a spec sheet, with confidence that they have seen this before. That confidence should concern you.

2. Do you design and build your own custom tooling, or do you rely on off-the-shelf components?

Why it matters: Real production rarely fits catalog solutions. Custom tooling is often the difference between a cell that hits theoretical throughput and one that hits your actual production targets. Vendors without in-house tooling capability hand this off to a subcontractor, which creates quality, timeline, and accountability gaps.

Strong answer: Dedicated mechanical engineering and tooling design in-house, able to design to your part geometry, materials, and cycle time. They can also work with tooling you already own rather than locking you into a single source.

Weak answer: "We source all tooling through our supplier network." That means no direct engineering accountability when a fixture does not perform as specified.

3. Which robot brands do you integrate, and do you hold certifications from those manufacturers?

Why it matters: Manufacturer certifications are not marketing badges. They mean a vendor's engineers have been factory-trained and tested by the robot OEM, which usually means earlier access to technical support, firmware, and escalation when something goes wrong. A vendor who integrates several platforms is also more likely to recommend the right robot for your application rather than the one they are most comfortable selling.

Strong answer: Multiple robot brands integrated, active certifications from the relevant OEMs, and a clear explanation of the tradeoffs between platforms for your specific application. Ask to see current certificates.

Weak answer: One or two brands, and no ability to articulate why one platform fits your application better than another.

4. Do you design and integrate machine vision, and what is your experience with 2D versus 3D?

Why it matters: Machine vision now sits at the center of most advanced cells, handling part identification, inspection, robotic guidance, and traceability. Vendors without vision expertise either exclude it from scope, which limits what your system can do, or subcontract it, which creates an integration gap at the boundary between systems.

Strong answer: Vision engineers in-house, both 2D and 3D integrated, familiarity with lighting technique and deep learning inspection where it applies, and specific vision applications they have commissioned in environments like yours.

Weak answer: "We can add a vision system if you need it." An afterthought answer signals an integration risk.

Category 2: Project management

Automation projects fail more often on project management than on engineering. These questions reveal how a vendor runs a project, not just how they design one.

5. Walk me through your project management methodology from kickoff to commissioning.

Why it matters: A well-run automation project has defined phases, documented deliverables, regular customer touchpoints, and gates that stop the project from advancing until each phase is validated. Without that structure, timelines slip, scope creeps, and the surprises all arrive at commissioning.

Strong answer: A formal phase-gate methodology with named phases such as design review, fabrication, controls, integration, runoff, and installation, each with milestone approval. Certified project managers, transparent risk management, and a stated on-time delivery rate. Industry average sits below 80 percent, so a disciplined integrator should be meaningfully above it.

Weak answer: "We keep you in the loop." Communication language with no structure behind it is a yellow flag.

6. What does your customer acceptance process look like before a system ships?

Why it matters: The factory acceptance test is your last line of defense before the system leaves the vendor's building. It is where you confirm throughput, cycle time, and quality before you are committed to an on-site installation. Vendors who skip a rigorous FAT push their problems onto your floor.

Strong answer: A comprehensive FAT at their facility using your parts or representative samples, documented against agreed acceptance criteria, with your team invited to participate. They do not ship until the system meets spec, and they describe a first-time-yield mindset rather than a plan to fix things at installation.

Weak answer: "We test everything before it ships," with no structured, customer-involved acceptance process behind it.

7. How do you handle scope changes during a project, and can you give an example?

Why it matters: Scope changes happen on every complex automation project. Parts change, volumes shift. What separates a trustworthy partner from a problem is whether those changes are handled transparently with documented cost and schedule impact, or through verbal agreements that become disputes at the end.

Strong answer: A formal change order process. Every change documented in writing, priced before work begins, approved by you. They can walk you through a real example from a past project and how it was managed.

Weak answer: "We are flexible and work things out as we go." Flexibility without process is how cost overruns happen.

Category 3: Industry and application experience

The best integrators have seen your problem before. These questions test whether their experience is actually relevant to your application.

8. What industries do you primarily serve, and do you have experience in mine?

Why it matters: Industry-specific automation carries regulatory requirements, material handling nuances, cleanliness standards, and documentation expectations that differ sharply between sectors. An integrator who has commissioned systems in your industry understands those constraints as engineering decisions, not as general awareness.

Strong answer: Named industries with concrete applications inside them, and an understanding of the specific requirements your sector imposes without needing a tutorial from you. Our industries served page is the equivalent for us.

Weak answer: "We work across all industries." It may be true, and it tells you nothing. Push for specifics.

9. Can you show examples of systems delivered at a similar scale and complexity to ours?

Why it matters: Track record at your scale matters. An integrator who mostly builds small, simple cells may not have the engineering depth, project management rigor, or resource capacity for a complex system. References are how you check the claim.

Strong answer: Several comparable projects described by application type, industry, and measurable outcome such as throughput gain or defect reduction, plus reference customers who will actually take your call.

Weak answer: "We have done thousands of projects," with no specifics and no verifiable references.

Category 4: Post-installation support and lifecycle management

A well-built cell should run reliably for decades. How a vendor supports you after commissioning often matters more than anything that happens before it.

10. What does your post-installation support model look like in the first year and beyond?

Why it matters: This is where vendor relationships usually break down. Some integrators are attentive through the sale and the build, then effectively disappear. Others build the service infrastructure that keeps the system running year after year.

Strong answer: A defined warranty period with response time commitments, structured support agreements covering preventative maintenance and priority emergency response, field service technicians familiar with your specific system rather than just its component brands, and critical spares in stock. Our field service group is built for exactly this.

Weak answer: "We stand behind our work." An assurance with no documented service model is not a plan.

11. How do you approach operator and maintenance training, and what materials do you provide?

Why it matters: A perfectly engineered cell still underperforms if your operators and maintenance staff cannot recover from a fault. Training is frequently the difference between a system that hits its designed throughput and one that runs well below it because nobody knows what to do when it stops.

Strong answer: Structured programs for operators and for maintenance technicians, delivered at commissioning and refreshed later. Documentation that includes process manuals, troubleshooting guides, and preventative maintenance schedules. The goal is a self-sufficient team, not a team dependent on the vendor for routine faults.

Weak answer: "We walk your team through the system at installation." A verbal walkthrough is not a training program.

12. How do you handle modernization and upgrades as technology evolves?

Why it matters: A control platform that was current five years ago may not be supportable now. A vision model trained on last year's parts may need retraining as the part changes. Lifecycle management is real engineering work, and the better integrators address it before it becomes urgent.

Strong answer: Structured modernization programs, periodic system assessments that identify components approaching end of life, and phased upgrade plans that minimize disruption. They can describe actual modernization work they have completed, including legacy control upgrades and robot rebuilds.

Weak answer: "We handle upgrades as needed." Without a proactive program, as needed usually means after a failure.

Category 5: Business stability and partnership philosophy

The last question is about the vendor as an organization, and whether they will be there when you need them.

13. What is your ownership structure, and how long have you been in business?

Why it matters: Automation systems are long-lived assets. A cell you commission this year may be on your floor for twenty years. Vendor instability, whether from financial pressure, an ownership transition, or growth that outruns operational capacity, converts directly into risk on your production floor.

Strong answer: A meaningful operating history, stable ownership, and demonstrated operational continuity. Where there have been ownership changes, they can speak plainly about what it meant for their team, their capabilities, and their commitments to existing customers.

Weak answer: Evasiveness about ownership, history, or scale. These are fair questions for a partner you will rely on for years.

Where do you find qualified automation cell vendors?

Knowing the questions is the first step. Finding the right vendors to ask is the second. These are the channels that produce a usable shortlist.

Ready to ask these questions?

Integrion Automation was founded in 1983 and has built robotic automation solutions from Wauseon, Ohio for more than forty years. Our team has installed more than 1,000 automation systems, including more than 450 robotic integrations, across automotive, life sciences, food and beverage, electronics, and general industrial, with equipment operating in over 20 countries.

What we can tell you directly:

• Engineering. We integrate multiple robot platforms and select the one that fits the application rather than the one we are most comfortable with. We design and manufacture our own Wauseon TubeTech tube end forming equipment in-house, and our machining is done in-house inside our own group, so fixture and tooling revisions during debug do not sit in an outside shop's queue.
• Project management. We run a phase-gate methodology with milestone approvals at each stage. Our on-time delivery rate exceeds 90 percent, against an industry average below 80 percent.
• Support after installation. Full lifecycle field service including preventative maintenance, emergency repair, system modernization, and operator training. We support systems we did not build as well as our own.

We will answer every question on this list, in detail, on the record. If you are earlier than the shortlist stage, start with the readiness signals in this piece on assembly line readiness.

Tell us what you are trying to solve on the contact page and we will tell you exactly how we would approach it.

Frequently asked questions

What drives the cost of a custom automation cell?

Part variation, cycle time, the number of processes inside the fence, and how much integration the cell needs with your existing controls. Two cells doing the same operation can differ substantially in price because one handles a stable part and the other handles a part that moves. To get comparable pricing, give every vendor an identical scope package and require a written exclusion list with the quote.

How long does it take to build an industrial automation cell?

The schedule is set by long-lead components and by how long design review takes on your side, not by build time. Ask for a schedule with named milestones: design freeze, long-lead release, factory acceptance, ship, site acceptance. A vendor who gives one duration and no milestones has not planned the job yet.

Should we buy a standard cell or a custom automation cell?

Standard cells make sense when your process and part are close to what the cell was designed around, since you are buying a proven configuration for less engineering cost. Custom is the answer when part geometry, cycle time, or the interface to existing equipment does not fit a catalog product. An honest vendor will tell you which one you are.

What is the difference between an automation integrator and an equipment OEM?

An OEM sells a machine that does one thing well and expects you to handle everything around it. An integrator designs the system, combines components from multiple manufacturers, writes the controls, and is accountable for the process outcome rather than for one box. If your project needs several technologies to work together, you need an integrator.

How many automation cell vendors should we quote?

Three is usually right. Fewer and you have no way to test whether a quote is reasonable, more and the evaluation effort outruns the value. Send all three the same scope package on the same day and ask all three the same thirteen questions, so the comparison is about their answers rather than their proposal formatting.