If you sell industrial automation — PLCs, motion control, servos, VFDs, HMIs, sensors, robotics, or the complete line a branch might carry — you already know your prospect list splits in two directions that most data tools refuse to separate.
On one side: integrator shops. Fifteen-person engineering firms that design and build controls panels, program the logic, and commission the cell at the end customer. On the other side: the end-user plant itself — a food processor, a tier-2 automotive stamping shop, a paper mill — where a controls engineer or an automation-capable plant engineer keeps the line running and picks the vendor for the next retrofit.
Most automation reps pitch both audiences with the same email and wonder why neither replies.
They are two different buyers, with two different economic models, two different decision cycles, and two different ways of finding them. This playbook covers who they actually are, what drives each one, and how to build a ranked territory list that separates integrators from end-user plants without trawling LinkedIn for hours.
Who the buyer actually is
Background and career path
Controls and automation buyers reach their desks through electrical engineering, mechanical engineering, or — increasingly common — mechatronics programs. The typical path runs engineering degree → controls engineer at an integrator or plant → senior controls engineer → lead engineer or engineering manager. At integrator shops, the progression continues to principal engineer, project manager, or owner/partner.
Their education is ladder-logic, structured text, PLC architecture, and industrial networking (EtherNet/IP, PROFINET, EtherCAT). They can tell you within 20 seconds whether the Rockwell CompactLogix you are trying to sell will fit the existing architecture, and whether your motion solution will play nicely with the Siemens drive already on the line. They are technically literate buyers — feature-light pitches fall flat, and feature-accurate pitches that miss the economic context fall almost as flat.
The market they operate in is large. Mordor Intelligence puts the global system integrator market near $47 billion in 2025, and the Control System Integrators Association — the trade body for the integrator channel — now counts 500 certified member firms across 35 countries. That is the near-ground; the real universe of controls-and-automation shops in North America runs several times larger once you include non-CSIA members, captive integrators inside OEMs, and the in-house engineering teams at end-user plants.
Title variations
Run a single-title search and you miss two-thirds of the buyer pool. The function — "person who specifies, approves, or influences automation component purchases at this site" — shows up under all of the following:
At end-user plants:
- Controls Engineer / Senior Controls Engineer
- Automation Engineer / Senior Automation Engineer
- Process Control Engineer (common in chemicals, pharma, food)
- Electrical Engineer (when the role doubles as automation)
- Plant Engineer / Plant Engineering Manager
- Maintenance Engineer (at smaller plants where maintenance owns automation)
- E&I Supervisor (electrical and instrumentation, common in heavy process)
At integrator shops:
- President / Owner / Partner (the deciding voice at small integrators under 25 people)
- VP of Engineering
- Engineering Manager / Director of Engineering
- Principal Controls Engineer / Lead Engineer
- Project Manager (influencer, not decider, but the one who will pull your catalog on an active job)
Reporting line and buying authority
The reporting line is different at each side of the channel, and so is the decision timeline.
| Buyer situation | Typical authority on a single project | Decision window |
|---|---|---|
| Controls engineer at a small plant (<200 employees) | Full spec authority up to $25K–$50K per project | 1–6 weeks |
| Controls engineer at a mid-market plant (200–1,000 employees) | Specifies; plant engineering manager signs $50K–$250K | 6–12 weeks |
| Controls engineer at a large plant (1,000+ employees) | Specifies; corporate engineering / approved-vendor list controls brand choice | 12–26 weeks |
| Owner or VP at a small integrator (<25 engineers) | Full authority on every project | 2–8 weeks |
| Engineering manager at a mid-size integrator (25–100 engineers) | Spec authority; president signs large frame agreements | 4–12 weeks |
| Lead engineer at a large integrator (100+ engineers) | Project-level spec; brand decisions escalate to VP of Engineering | 8–16 weeks |
Two practical implications. First, at small integrator shops, you can close a preferred-vendor relationship in a single visit if the owner already knows your catalog. Second, at large end-user plants, the controls engineer is almost never the final brand decision — they are your champion, and your job is to arm them for an internal conversation with corporate engineering or the approved-vendor governance group.
Five pain points that drive every conversation
1. Architecture lock-in and the cost of switching brands
Once a plant or an integrator standardizes on a control platform — Rockwell Logix, Siemens TIA Portal, Beckhoff TwinCAT, Mitsubishi GX Works — the switching cost is not just the hardware. It is the engineer-hours of re-training, the spare-parts inventory at the plant storeroom, the PLC programs that have to be ported, and the site standards documents that reference brand-specific function blocks.
The real acquisition cost of a new PLC platform at a multi-plant manufacturer is typically 5–10x the hardware cost once you include engineering retraining and spare-parts duplication. That is why the controls engineer seems strangely uninterested in your "better specs at a lower price" pitch — they are running the full-cost math in their head, and the answer is almost always "no."
What this means for your pitch: If you are trying to displace an incumbent platform, you are selling a multi-year transition, not a product. The only realistic wins are (a) greenfield projects where no platform is locked in yet, (b) application-specific components that slot into the existing architecture as complements, and (c) integrator firms looking to add a second certification to open up more end-user territory. Target accordingly.
2. Safety compliance and the updated robotics standard
Anyone selling industrial robots, cobots, or robotic-cell components has to understand the regulatory backdrop. The flagship standard — ISO 10218, updated in 2025 into new Part 1 and Part 2 documents — sets the safety requirements for industrial robots and, in Part 2, for integrators of robot systems and cells. Part 2 is the one that matters for your customer: it covers the design, installation, operation, maintenance, and decommissioning of the complete robotic cell, including safeguarding, risk assessment, and operator interfaces.
Integrators carry personal professional liability for the safety design of every cell they build. A shop that is not compliant with the updated 10218-2 does not just face regulatory exposure — it cannot bid on work from risk-averse Fortune 500 end users who write compliance into their purchase specs. Functional safety (IEC 61508 / IEC 62061) and machinery safety (ISO 13849) sit in the same conversation.
What this means for your pitch: If your product is a safety controller, safety light curtain, safety PLC, or any component that sits in the safety circuit, lead with the standard. "Compliant with the updated ISO 10218-2 Part 2" is not a feature bullet — it is the entry ticket to the RFP. If your product does not fit the safety circuit, reference the standard anyway: it tells the integrator you understand their regulatory reality.
3. Project-margin compression at the integrator shop
Integrator economics are brutal. The shop bids a fixed-price project, buys components at distributor net, marks up to an all-in system price, and absorbs every hour of commissioning overrun. A project quoted at 1,200 engineering hours that actually takes 1,500 hours loses 20% of its margin before a single unplanned travel day.
Every integrator principal is watching two numbers: gross margin by project and engineer-utilization rate. A component vendor who saves the integrator 40 engineering hours — through a better library of function blocks, a tighter auto-tuning routine on a servo drive, a commissioning wizard that cuts panel startup time — is contributing to margin in a way the end-user plant never directly feels.
What this means for your pitch: When selling into integrators, lead with engineer-hours-saved, not feature performance. "Our drive auto-tunes in 15 minutes on the panel instead of 4 hours on the floor" translates, at a $175 blended hourly rate, to roughly $675 per drive in project margin recovery. That is the language an integrator owner answers their phone for.
4. Certification and acceptance in safety-critical end markets
Selling automation components into food processing, pharmaceutical, chemical, and water/wastewater applications means your product has to carry the right stamps. The list is long and deal-qualifying: UL 508A for panels, CSA for North American cross-border work, IECEx and Class I Div 1/2 for hazardous locations, 3-A Sanitary for dairy and beverage, NSF for water, and ATEX for European-spec end users. In process control specifically, the ANSI/ISA S88 batch control standard is the engineering language buyers speak.
Missing a certification is not a negotiation — it is a disqualifier. An integrator building a pharma skid cannot specify your motor starter if it does not carry the listings the end customer's engineering standards require.
What this means for your pitch: Know which certifications your product carries and lead with them in the vertical where they matter. Pitching a pharma-bound integrator without mentioning your 3-A and S88-compatibility story is like pitching a residential electrician without mentioning UL. It signals you do not understand the market.
5. Consolidation and the platform rollup
The automation industry is consolidating faster than most reps realize, and the consolidation is changing who the "competitor" actually is. Rockwell Automation has been aggressively rolling integration capability into its own platform — the 2023 acquisition of Clearpath Robotics and OTTO Motors added autonomous mobile robots to a portfolio already including Plex, Fiix, and the Kalypso consulting arm. Siemens completed a $10 billion acquisition of Altair Engineering in 2024–2025, extending its simulation and AI stack into the same sales conversations.
The practical effect on a rep's territory: the integrator channel is not stable. An independent shop that was a Rockwell partner last quarter may be a Siemens partner this quarter; a shop that was certified on two platforms may have been acquired into a parent that mandates one. Component reps who track only the parent brand and not the facility-level certification miss what is actually happening on the floor.
What this means for your pitch: Segment your integrator list by primary platform certification, not by corporate logo. Verify certifications annually — CSIA status and platform alliances change faster than most CRMs update.
Where to find them: the Facilities Finder workflow
The two-audience split is the reason most automation reps spend a frustrating share of their week on LinkedIn. A search for "controls engineer" returns integrator employees and end-user employees in the same list, with no facility context to tell them apart. A search by company name returns the HQ record, not the five regional plants where the controls work actually happens.
Facilities Finder separates the problem cleanly because every record is indexed at the facility level, not the company level. Here is the workflow to build both an integrator list and an end-user list in the same territory.
Step 1: Draw your territory
Open Facilities Finder and draw your territory polygon — by state, by county, by drive-radius from a branch location, or by freehand polygon around a metro. Every subsequent filter will constrain to facilities physically inside that zone, so a shop in Cleveland and a shop in Cincinnati do not end up in the same bucket just because both are in Ohio.
Step 2: Apply ICP filters with natural-language search
Type what you are looking for. "Industrial automation integrators and controls engineering firms in the Great Lakes region" returns integrator shops. "Tier 1 and tier 2 automotive stamping plants with controls engineering teams in Michigan" returns end-user facilities. Our AI extracts products, industries, and intent from your query, then ranks all 600,000+ US industrial facilities by how well they actually match — no NAICS codes to memorize, no industry-bucket guessing, no keyword match against stale company descriptions.
Run the two queries separately. They produce two lists that belong in two outreach sequences.
Step 3: Prioritize by size and fit
Sort by employee count to surface the highest-value accounts first. For integrator prospects, facilities with 25–250 engineers are usually the sweet spot: big enough to have real project volume, small enough that the owner or VP of engineering will take your call. For end-user prospects, filter above 200 employees to exclude sites too small to have dedicated controls headcount.
Apply the role filter to surface controls engineers, automation engineers, electrical engineers, engineering managers, and integrator principals attached to each facility. Every contact is keyed to the physical site, not a corporate switchboard — when you call the number, you are reaching a person who works in that building.
Step 4: Activate the pipeline in the built-in CRM
Tier 1 accounts — the top 50 integrators and top 50 end-user plants — flow directly into the rep's pipeline inside Facilities Finder. No CSV round-trip, no separate CRM to sync into — the territory, the accounts, the contacts, and the deal pipeline all live in the same system. Deals auto-create, and your first outreach sequence can launch against a segmented list the same day you draw the territory.
Outreach angles and templates
Controls buyers are technical and short-patience. The email that lands opens with a credible problem specific to their platform, proves you know the vertical, and asks a single question instead of requesting 30 minutes.
Email template 1: End-user plant, retrofit-timing opener
Subject: [Platform name] retrofit at [Facility name] — question on [component category]
Hi [First name],
I work with controls engineers at [industry] plants on [component category — e.g., motion control, remote I/O, safety relays] retrofits, specifically where the existing [platform] architecture is at end-of-life and a drop-in replacement is on the engineering roadmap.
Most of the plants I talk to are carrying 10–15-year-old [component category] that is fine until a spare fails and lead time is 16 weeks. The replacement decision usually sits with the controls engineer — which is why I am reaching out to you rather than purchasing.
Quick question: is [component category] a live retrofit topic at [Facility name] in the next 12–18 months, or is the installed base still in good shape?
Not pitching anything on this email — just trying to gauge timing before putting specs in front of you.
[Your name] [Title] | [Company] [Phone]
Why this works: It names a specific, credible pain — spare-parts lead times on obsolete components. It acknowledges the buyer's platform reality rather than pitching a rip-and-replace. It asks one qualifying question instead of demanding a meeting.
Email template 2: Integrator shop, project-margin angle
Subject: Engineer-hours on [component category] at [Integrator name]
Hi [First name],
Most of the integrators I work with are watching the same two numbers every week — project margin and engineer-utilization. When we benchmark commissioning time on [component category], shops using our [specific feature, e.g., auto-tuning drives, pre-built faceplate libraries] are coming in 30–40% faster on that portion of the job.
At a blended [$175]/hour rate, that is roughly $5K–$8K in recovered margin per typical project.
I know you are already specified on [competitor platform]. Not asking you to switch — I am asking whether it is worth a 15-minute call to walk through where our [component] has actually slotted in as a second source on specific project types.
[Your name]
Why this works: Speaks to the number the integrator owner actually cares about — project margin. Uses concrete hours-saved math. Respects incumbent platform loyalty. Asks for a defined, low-commitment conversation.
Email template 3: Safety compliance angle (robotics / safety components)
Subject: ISO 10218-2 update — compliance review at [Facility name]
Hi [First name],
The updated ISO 10218-1 and -2 published in 2025 changed a few things for cells commissioned under the older standard. In particular, the Part 2 updates around risk assessment and safeguarding are prompting several of the [industry] integrators and end users we work with to run a compliance review on legacy cells.
I am not a compliance auditor and am not pitching that service. I am reaching out because [component category] retrofits are often the cleanest way to bring an older cell into the updated standard without a ground-up redesign.
Worth a quick call to see where [Facility name] sits on its legacy-cell review cycle?
[Your name]
Why this works: References a real, recent regulatory change the buyer already knows about. Positions your product as the low-disruption fix rather than a full replacement. Names the standard correctly — signals you actually work in this market.
LinkedIn message template
Hi [First name] — I work with [controls engineers / integrator principals] on [component category]. Saw [Integrator name / Facility name] from my [region] territory coverage and wanted to connect. If [platform or vertical] is a current priority, happy to share a couple of project references that line up. No ask.
Character count note: Keep LinkedIn messages under 300 characters for the preview to show the full message. The above runs ~285.
Voicemail script
"Hi [First name], this is [Your name] from [Company]. I work with [controls engineers / integrator principals] in the [region] on [component category] — specifically on [retrofit timing / project-margin math / safety compliance]. I am not calling to pitch anything — I have a quick question about whether [Facility / Integrator name] has a live project in this area before I put specs in front of you. You can reach me at [phone number]. Again, that is [repeat number slowly]. Thanks."
Voicemail notes: Under 30 seconds. State the problem, not the product. Offer a question, not a pitch. Say the phone number twice.
Red flags and disqualifiers
Filter these signals out early to protect pipeline accuracy.
Corporate-approved-vendor-list (AVL) lockout. Large end users — especially Fortune 500 food companies, tier-1 automotive suppliers, and publicly traded chemical processors — maintain corporate AVLs that dictate which PLC platform, drive brand, and safety architecture every plant must use. If your product is not on the AVL, the controls engineer at the plant cannot specify it regardless of technical fit. Ask directly on your first qualifying call: "Is there a corporate engineering standard or AVL on this category, or does your plant have discretion?" If the answer is AVL-controlled and you are not on it, your path runs through corporate engineering at HQ — a different, longer sales motion.
Integrator shop primarily certified on a competing platform. A shop that is 90% Siemens-certified is not going to build a Rockwell-native project for you on spec. Look at the integrator's case-study library and trade show footprint — it tells you more than any conversation about "being open to alternatives." Focus on shops with dual certification, or shops adding a second platform to expand geographic coverage.
Plants in financial distress or parent-level consolidation. A plant idling shifts, running at low OEE, or appearing in parent-company earnings calls as "under strategic review" is not a capex buyer. Automation projects go on ice long before layoffs start. Local press reports of production reductions are a reliable early signal.
Integrator shops under 10 engineers with no project backlog visibility. Very small shops often run off the owner's single-rep relationships. If you are not already on their short list, displacing the incumbent is a relationship play, not a technical play — and relationship plays at that scale do not pencil for most outside reps.
End-user plants with no dedicated controls headcount. A 50-person job shop where maintenance runs the PLCs is not a spec-in-advance buyer. They will buy when something breaks, from whoever their distributor has on the shelf. These accounts belong in a distribution channel, not in your direct outreach sequence.
When to escalate vs. stay at the controls-engineer level
Staying at the controls-engineer or integrator-principal level is the right move for:
- Components below the plant or shop's project-level sign-off threshold
- Greenfield projects inside the current year's engineering roadmap
- Second-source or complement additions to an existing platform
- Initial discovery and technical qualification (always start here)
Escalation to corporate engineering, VP of Engineering, or purchasing is necessary when:
- The deal requires addition to a corporate AVL — at that point, the controls engineer is your champion and the governance owner is corporate
- You are selling the same product across multiple plants under one parent — this becomes a national-account motion
- The project exceeds the plant or shop's discretionary authority
- The integrator shop is evaluating a new platform certification — that decision sits with the owner/president, not the lead engineer
The worst mistake in this vertical is skipping the controls engineer entirely and going to purchasing at HQ. Purchasing will bounce the inquiry to engineering for technical validation — except now the controls engineer has no ownership of the initiative and no reason to champion it. Build the technical credibility at the engineer level first. Escalate only when the deal size or the governance structure requires it.
Find automation integrators and plants in your territory
The core problem is unchanged: your CRM lumps every "manufacturer" into a single industry bucket, your LinkedIn search returns integrator engineers and end-user engineers in the same list with no way to separate them, and your data tool shows one HQ record for a parent company that actually runs 87 plants each with its own controls team. Meanwhile the real universe of automation buyers in any territory is split across two audiences with different economics, different decision cycles, and different outreach angles.
Facilities Finder indexes every facility as its own record — 600,000+ US industrial locations across all 50 states — with controls engineers, automation engineers, plant engineering managers, and integrator principals keyed to the physical site. Type "industrial automation integrators in Ohio" and our AI surfaces integrator shops; type "tier-1 automotive stamping plants in Michigan with controls engineering" and it surfaces end-user facilities. The territory polygon scopes both searches to the geography you actually cover, the role filter pulls the right titles, and tier 1 accounts flow directly into the built-in CRM pipeline — the territory, the accounts, the contacts, and the deals all live in the same system.
25 million+ decision-maker contacts, all keyed to the location where the work actually happens.
Find automation buyers in your territory →
See also: How to Sell Industrial Equipment to Plant Managers: The Field Rep's Playbook · How to Build a Territory List for a New Sales Rep in Under an Hour · Find Every Facility Owned by a Parent Company