How to Define an End-User ICP: Site Conditions, Operating Problem, and Buying Path

Who this guide is for

This guide is for industrial equipment, component, maintenance, retrofit, and service suppliers selling to facilities that operate the solution. It is especially useful where procurement is centralized, projects are contractor-led, or local distributors transact on behalf of the end user.

Contents

1 Define the end-user account correctly 2 Verify application and site conditions 3 Describe the operating problem without assuming intent 4 Map the buying path as an account attribute 5 Apply the SellersGPT End-User Fit Record 6 Illustrative example 7 Common mistakes 8 What this does not mean 9 Common questions 10 Sources and methodology

1. Define the end-user account correctly

For this guide, an end user is the organization or operating unit that uses the product, operates the asset, or receives the direct operational outcome. It may buy directly, through a distributor, under an OEM package, or through a contractor. Record four linked levels:

• legal enterprise and parent;

• operating business unit;

• facility and address;

• application or asset at that facility. Do not attach a plant condition to headquarters. Do not assume every facility owned by the parent performs the same process. The EIA Manufacturing Energy Consumption Survey describes a national sample survey of manufacturing establishments and their energy-related building characteristics, consumption, and expenditure. U.S. Energy Information Administration - About MECS Its establishment focus illustrates why facility conditions matter, while its aggregate statistical outputs do not identify account-level needs.

2. Verify application and site conditions

An end-user record should answer: Area Required question Process What does the facility make, handle, operate, or deliver? Application What job would the offer perform, at which step? Current method What equipment, manual work, workaround, or supplier is used? Environment What physical, safety, quality, integration, and duty conditions apply? Outcome What measurable operating result is required? Installation What access, shutdown, validation, and contractor conditions apply? Support What spares, training, warranty, and response model is required? Use facility pages, technical documents, permits, tenders, current recruitment, public filings, and direct discovery. Store exact evidence, scope, and date. OSHA's Establishment Search documentation explains that its enforcement database can be searched by establishment name and that names are not necessarily unique; it also warns that data can be revised and that open-case status changes. Occupational Safety and Health Administration - Establishment Search Help Such records can help resolve a facility identity or historical activity. They do not prove the current application or buying intent.

intent

Write the condition neutrally: At [facility/process], [verified or inferred condition] may affect [bounded operating outcome]. [Critical evidence] remains Unknown. Keep these states separate:

• Condition: Verified, Inferred, Unknown, or Contradicted.

• Consequence: Verified by the account, analytically plausible, or Unknown.

• Application fit: Pass, Conditional, Fail, or Not assessed.

• Timing: Active change evidence, monitoring signal, or Unknown. A parent-company filing can provide first-party evidence about operations, risk, capital allocation, or strategy. SEC EDGAR makes those filings publicly searchable. U.S. Securities and Exchange Commission - Search Filings Read the reporting entity, segment, period, and wording. A company-level risk is not automatically a facility-level problem. Avoid writing outreach that tells a facility what it is “losing” based on public clues. When evidence is incomplete, ask a precise process question.

4. Map the buying path as an account attribute

Before contact research, define which commercial paths are plausible: 1 Direct purchase: the end-user organization contracts with the supplier. 2 Distributor transaction: the end user selects or accepts the product; a distributor quotes, stocks, or invoices. 3 Contractor-led: a contractor or integrator specifies, packages, installs, or procures. 4 OEM-embedded: the product reaches the site inside another system. 5 Centralized enterprise purchase: facility need is governed by corporate procurement or an approved list. The existence of one route does not exclude another. Record application, project, spend, and region scope. For each route, distinguish who can authorize a technical change from who can place an order. A corporate purchasing team may negotiate terms while the plant owns application acceptance; a distributor may invoice while a contractor specifies; an OEM may package the solution while the end user approves the standard. Recording those functions at account level helps research, but the identities and interactions still require a project-specific buying-group map. Route evidence should carry an effective date. Approved suppliers, framework agreements, contractors, and local distributors change, and one route may apply only to a product family or spend threshold. If the scope cannot be confirmed, preserve the route as a hypothesis and ask a neutral discovery question. SAM.gov describes federal Contract Opportunities as procurement notices from contracting offices, including pre-solicitation, solicitation, award, and sole-source notices. SAM.gov - Contract Opportunities A notice can reveal a buying path and requirement for the named procurement. It should not be generalized to private accounts or future purchases. Do not assign one universal “decision maker.” At this stage, record functions likely involved - operations, engineering, maintenance, quality, safety, procurement, finance, contractor, and executive governance - then validate the actual buying committee in Module 03.

5. Apply the SellersGPT End-User Fit Record

The End-User Fit Record is an original SellersGPT editorial worksheet. Dimension Pass condition Hold or fail condition Facility identity Correct operating site verified Headquarters only or site unresolved Application Required job verified or testable No relevant application Environment Critical conditions compatible Incompatible or critical Unknown Problem relevance Consequence is credible and bounded Generic pain claim only Serviceability Delivery, install, support can be met Critical promise cannot be met Buying route Direct or indirect route is viable Route blocked or unresolved Timing Tracked separately Never inferred from fit Decision labels:

• Go: application, environment, service, and route pass.

• Test: fit is plausible; a bounded critical validation remains.

• Hold: required facility, technical, or route evidence is Unknown.

• Exclude: verified hard-gate failure. A score may compare accounts only after gates pass. Keep Unknown fields visible and do not let company size override an incompatible application.

6. Illustrative example

Illustrative example. The facilities, evidence, counts, and decisions below are fictional. They do not represent customer results, market size, or expected sales. A compressed-air optimization supplier researches 30 manufacturing facilities. Four gates are required: relevant compressed-air application, accessible operating data, service radius, and a viable purchase route. Decision Facilities Reason Go 9 All four gates pass Test 7 Application and service pass; data access needs validation Decision Facilities Reason Hold 8 Buying route or facility evidence Unknown Exclude 6 Incompatible service radius or no relevant application Total 30 Bounded research sample The executable share is 9 / 30 = 30%. The validation queue is 7 / 30 = 23.3%. The team does not combine Go and Test into a claimed 53.3% qualified rate because a critical dependency remains for the Test group. Two Go facilities purchase through contractors rather than directly. They remain end-user ICP fits, but the account plan routes commercial research through the contractor relationship.

7. Common mistakes

Using the parent as the operating facility Attach application and condition evidence to the site where the work occurs. Confusing use with purchase The organization operating the asset may not invoice, specify, install, or approve it. Treating an incident as persistent pain Preserve date and scope. Do not diagnose or exploit sensitive events. Ignoring shutdown and service constraints Installation access, response time, local skills, and spares can be hard gates. Assuming an approved vendor list proves intent Approval can enable a route; it does not show an active requirement. Mixing timing into fit Track active projects and change signals separately from durable account characteristics.

8. What this does not mean

• End-user fit does not prove budget, urgency, authority, or willingness to switch.

• A facility user is not automatically the buyer or payer.

• Public regulatory data does not establish current operational need.

• This guide does not prescribe engineering, safety, procurement, or legal decisions.

• Stakeholder mapping still requires account-specific Buying Committee research.

9. Common questions

Can a facility be an end-user fit when the parent buys centrally? Yes. Preserve the facility as the application record and the parent or central function as part of the buying path. What if a contractor specifies everything? The facility can remain the end user, while the contractor becomes the specification and transaction route. Maintain linked ICP records. Should site size be a criterion? Only when it changes application scale, economics, or serviceability. Use the appropriate site measure rather than parent revenue. How should multiple facilities be handled? Create facility-level application records linked to the enterprise. Do not duplicate company facts or assume a condition across sites.

10. Sources and methodology

Sources 1 U.S. Energy Information Administration - About the Manufacturing Energy Consumption Survey. Used for the official establishment-level scope of MECS and the role of facility characteristics. Accessed August 24, 2026. 2 Occupational Safety and Health Administration - Establishment Search Help. Used for the official scope, name limitations, status, and revision cautions for establishment search. Accessed August 24, 2026. 3 U.S. Securities and Exchange Commission - Search Filings. Used for the official availability and scope of EDGAR company filings. Accessed August 24, 2026. 4 SAM.gov - Contract Opportunities. Used for the official types and scope of federal procurement notices. Accessed August 24, 2026. SellersGPT analysis and framework The End-User Fit Record, four-state problem model, gate logic, and decision labels are SellersGPT editorial tools. The example is fictional and no official source endorses the commercial framework. Update policy Review when cited source scope changes. Revalidate facility identity, application, operating conditions, service boundary, and buying route whenever a site or project changes.