A manufacturer's website is a catalog, and a catalog tells you what they make but almost nothing about how they run. Knowing how to research manufacturing companies for sales means going to the records the plant leaves behind: OSHA inspection logs, EPA facility compliance reports, federal contract awards, state economic-development announcements for new lines and expansions, and customs shipment data that names suppliers. Read those and you know the number of plants, what each one makes, whether the process is discrete or continuous, which certifications they hold, and whether the company is growing or consolidating, all before your first call. The careers page fills in the rest: the ERP, the MES, the automation vendors, and where the next hires are going. The checklist below is that reading order. The prompt under it does the reading and separates what it confirmed against a record from what it inferred from the catalog.
What is different about selling into Manufacturing
Manufacturers separate capital from operating spend, and the line your product lands on decides the process. Capex is planned a year ahead, approved by the CFO or the board, and competes with machines. Opex under a threshold belongs to the plant manager or the VP of Operations, and a plant can often buy for itself while corporate buys for all of them. Engineering and operations technology sit apart from IT, with separate budgets and a long-running argument about who owns the data. Mid-market manufacturers are often family-owned or held by private equity, which changes who signs and how fast. Fiscal years vary and the busiest quarter is protected from change. The misread that ends credibility is confusing a contract manufacturer with a brand owner, or a process plant with a discrete one. Ask a job shop about its product roadmap and they know you have never walked a floor.
How to research manufacturing companies for sales: the checklist
Establish what they make and how many plants make it, then pull the federal records for each plant, then read the job posts. Twenty minutes across those settles the type, the footprint, and the stack; the rest of the checklist tells you what to do with them.
You are researching {{company}} ({{company URL}}), a manufacturer, so I can sell {{our product}} to them. Read their products or capabilities page, locations page, certifications page, careers page, and news page, plus the 10-K if they are public.
Produce a one-page brief:
1. What they make and how: discrete or process, to order or to stock, own brand or contract, and the industries served.
2. Footprint: plant count, locations, headquarters, and which sites are hiring.
3. Certifications and regulation: quality standards held and any federal contracting or export-control exposure.
4. Systems: ERP, MES, quality, and automation vendors named anywhere, and any migration underway.
5. Pressure: expansions, layoffs, citations, enforcement actions, supplier changes, or ownership changes.
6. Likely buyer for {{our product}}, whether it is capex or opex for them, and the approval step that will slow the deal.
Tag every line Confirmed (cite the page or record) or Inferred (state the reasoning). Where the site does not say, write 'Not stated' and name the record that would, OSHA, EPA ECHO, USAspending, or a state incentive release. Close with three questions to ask on the first call.
- The products or capabilities page, read for type: discrete or process, make-to-order or make-to-stock, own brand or contract manufacturing, and the customer industries served.
- The locations page and the certifications page: plant count and geography, and which of ISO 9001, AS9100, IATF 16949, ISO 13485, or FDA registration they hold, because each one names a customer industry and a compliance burden.
- The careers page filtered to plant, engineering, and IT roles: job posts naming SAP, Oracle, Epicor, Plex, Infor, or a specific MES or PLC vendor describe the stack, and the plants doing the hiring describe growth.
- OSHA establishment inspection history and the EPA ECHO facility report for each plant: citations, penalties, and permits show which sites are under pressure and what kind.
- For a public company, the 10-K segment reporting, capex line, and backlog. For a private one, state economic-development press releases and local news on expansions, incentives, and layoffs.
- A new plant, line, or expansion announced through a state incentive program: a build-out with a schedule, new hires to train, and every system decision reopened for that site.
- An ERP or MES migration named in job posts: two years of IT attention, and a window where integrations are decided and everything else waits.
- A federal contract award on USAspending, or a new AS9100 or ITAR mention: a compliance and traceability push with a deadline written into the contract.
- OSHA citations or an EPA enforcement action at a specific plant: mandated fixes and a plant manager who needs a measurable improvement fast.
- Reshoring or supplier-change language in news and shipment records: a supply chain being rebuilt, new suppliers to qualify, and a procurement team working overtime.
- What do they make, for whom, and how: discrete or process, to order or to stock, own brand or contract?
- How many plants, where, and which one is the pilot site for anything new?
- What runs the business, ERP, MES, quality system, and the automation layer, and who owns each one, IT or operations?
- Is my product capex or opex for them, and which dollar threshold moves the decision from the plant to corporate?
- Who signs: the plant manager, VP of Operations, VP of Engineering, CFO, or, at a family-owned company, the owner?
- OSHA Establishment Search for inspection and citation history by site, and EPA ECHO for permits, compliance status, and enforcement by facility.
- USAspending.gov and SAM.gov for federal contract awards, registrations, and NAICS codes; the USPTO patent database for where engineering is investing.
- SEC EDGAR for public manufacturers, and state economic-development agency press releases for private-company expansions, incentives, and site selections.
- ImportYeti for US customs shipment records that name overseas suppliers and shipment volume, free to search by company.
Read the job posts before the About page; the About page says 'innovative', the job posts say 'Epicor' and 'Allen-Bradley'.
Run the research on a real account
The checklist is written for a 40-plant public company and a two-plant family business at the same time, and half of it is wrong for each. Let Claude size it from the URL. It reads the capabilities page, the locations page, and the job posts, then returns the checklist sized to this account, with each signal marked as seen, not seen, or unverifiable from public records.
I sell {{our product}} to {{buyer persona}} at manufacturers. I am researching {{company}} ({{company URL}}).
Read their capabilities, locations, certifications, and careers pages, plus anything public you can reach. Tell me first: discrete or process, own brand or contract, how many plants, and whether the company is public, private, family-owned, or held by private equity.
Then rewrite the research checklist below for this account. Remove items that do not apply at this size or type, reorder the rest by relevance to a {{our product}} conversation, and for each signal state whether you saw it, did not see it, or could not check.
Name the person most likely to own the budget for {{our product}}, whether it is capex or opex for them, and the approval step that will slow the deal. Mark everything Confirmed or Inferred.
CHECKLIST:
{{paste the checklist above}}
Research any account with Claude
- Account brief skill →The Claude skill that turns a company URL into a source-grounded first-call brief, plus the account plan template.
- 90-second account brief prompt →The copy-paste prompt version for one account, right now.
- Account brief from a URL, the use case →The full play, with the tool chain that researches every account on the list before the first call.
Frequently asked questions
How do you research manufacturing companies for sales?
Start with the capabilities page to establish the type, discrete or process, brand owner or contract manufacturer, then count plants on the locations page. Pull the OSHA inspection history and the EPA ECHO report for each site, which show where the pressure is. Check USAspending for federal contracts and the state economic-development site for announced expansions. Then read the careers page, where job posts name the ERP, the MES, and the automation vendors. That sequence takes twenty minutes and produces a brief a plant manager will recognize, which the catalog never does.
How do you find out what ERP a manufacturer runs?
Job posts name it. Manufacturers hire analysts and engineers by system, so a listing for an 'SAP PP/QM Analyst', an 'Epicor Kinetic Administrator', or a 'Plex MES Specialist' names the platform and the modules that are live. Case studies on the vendor's site name customers who agreed to be named. Migration projects show up as contract roles a year before go-live. If none of that surfaces anything, the size of the company is a decent prior: under about $50 million in revenue, expect Epicor, Infor, or Plex; above a few hundred million, expect SAP or Oracle.
Does it matter whether a manufacturer is discrete or process?
It changes the vocabulary, the systems, and the buyer. Discrete manufacturers assemble countable things, machines, devices, and parts, and talk in units, bills of material, and work orders. Process manufacturers make batches or continuous flows, chemicals, food, paper, and metals, and talk in recipes, yields, and lots. They run different MES products, answer to different regulators, and staff different roles, so a pitch written for one lands as noise on the other. Read the capabilities page for the words 'assembly' or 'batch' before you write the first email.