AS/400 Users List
Use AS/400 Technographic Data to distinguish accounts where integration, migration, modernization, security, services, or adjacent software can create an opening. When working with AS/400, what the data must support should determine what the data contains. Campaigns aimed at AS/400 become easier to prioritize when enterprise technology, product footprint, use context, and related investment signals are defined before contacts are selected.
Get Free AS/400 Sample
Target verified decision-makers using AS/400.
What Makes One AS/400 Record More Valuable Than Another
The best audience is not the largest one; it is the one with the fewest unexplained records. Treat AS/400 as a commercial landscape with different operating situations. When enterprise technology, product footprint, use context, and related investment signals are considered together, the audience becomes easier to prioritize for technology-stack improvement, with the AS/400 market definition kept in view. That is why an AS/400 Users Email List should be treated as an AS/400 qualification asset, not as a static directory.
Request a AS/400 User SampleAvailable AS/400 Data Fields & Targeting Signals
Technology & Product Criteria
6 CRITERIACompany & Firmographics
6 ATTRIBUTESDecision-Maker Intelligence
6 CONTACT FIELDSTerritory & Geographic Data
6 LOCATION FIELDSCommercial Uses for a Focused AS/400 Audience
| Buyer Type | Objective | Campaign Use |
|---|---|---|
| Cybersecurity vendors | Build an AS/400 prospect set where AS/400 adoption is interpreted through technology exposure, security architecture, compliance needs, and security leadership. | Map CIO with the other people who influence the environment, then use the audience for account planning, technical outreach, competitive displacement, or expansion. |
| Cloud and infrastructure companies | Develop accounts in the AS/400 market by combining AS/400 technology footprint with hosting model, workload profile, migration signals, and infrastructure ownership. | Use the account context to approach IT Director with a relevant technology hypothesis, then extend the list to other stakeholders if the buying path requires it. |
| Recruitment firms | Separate routine AS/400 usage from commercial fit by looking at AS/400 implementation plus platform skills, team growth, hiring signals, and technical leadership. | Give sales a reason for contact by connecting Applications Manager to the platform context; use the records for consultations, demos, modernization conversations, partner programs, or recruitment, with the AS/400 market definition kept in view. |
| Data and AI vendors | For AS/400, evaluate technographic targeting alongside data flows, analytics environment, platform dependencies, and data leadership so the campaign can prioritize stronger-fit accounts. | Reach CIO and adjacent stakeholders with outreach tied to the account's technology environment; activate the data for prospecting, demos, integration, migration, services, or pipeline development; this is applied specifically to AS/400. |
Choose the AS/400 Segments That Fit Your Campaign
Companies using AS/400
Accounts showing
Contacts at AS/400
AS/400 accounts
AS/400 customers
AS/400 Installed Base records
The AS/400 database can be organized in multiple views for different teams. For AS/400, sales may prioritize account fit, marketing may use role and segment rules, while research or recruiting can rely on another combination of enterprise technology, product footprint, use context, and related investment signals.
Some buyers ask for an AS/400 Users Email List; others start with an AS/400 Customers List or the AS/400 Installed Base. For AS/400, those labels can coexist on the page because the underlying data can be organized around account, platform, and stakeholder views.
Choose the Audience You Want to Reach
Explore related decision-maker contacts, specialized lists, and technology databases.
Sample AS/400 Users Database Preview
Preview 10 verified sample records showcasing our 21+ intelligence data fields with masked contact records.
| # | First Name | Last Name | Full Name | Verified Email | Direct Phone | Fax Number | Job Function | Job Title | Company Name | Industry | SIC Code | NAICS Code | Company Size | Revenue Size | Address | City | State | Zip Code | Country | LinkedIn Business | LinkedIn Profile |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | John | Lin | John Lin | j.l****n@inec***.com | +1 (600) ***-9758 | +1 (600) ***-9759 | Information Technology | Lead DevOps Architect | Lin Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
250–1,000 Employees | $25M – $100M | 500 W 2nd St, Ste 1900 | Austin | TX | 78701 | United States | Company Page | Profile Page |
| 2 | Amanda | Montgomery | Amanda Montgomery | a.m****y@ontg***.com | +1 (637) ***-9881 | +1 (637) ***-9882 | Cloud Operations | Head of Engineering | Montgomery Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
100–250 Employees | $10M – $25M | 333 S Hope St, Ste 1200 | Los Angeles | CA | 90071 | United States | Company Page | Profile Page |
| 3 | Matthew | Ainsworth | Matthew Ainsworth | m.a****h@insw***.com | +1 (674) ***-1005 | +1 (674) ***-1006 | Engineering & DevOps | Database Administrator | Ainsworth Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
1,000–5,000 Employees | $100M – $250M | 1201 3rd Ave, Ste 2200 | Seattle | WA | 98101 | United States | Company Page | Profile Page |
| 4 | Elizabeth | Vanderbilt | Elizabeth Vanderbilt | e.v****t@ande***.com | +1 (711) ***-1128 | +1 (711) ***-1129 | Software Architecture | VP of Cloud Infrastructure | Vanderbilt Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
100–250 Employees | $10M – $25M | 1450 Brickell Ave, Ste 1800 | Miami | FL | 33131 | United States | Company Page | Profile Page |
| 5 | Gary | Vance | Gary Vance | g.v****e@ance***.com | +1 (748) ***-1251 | +1 (748) ***-1252 | Security & Compliance | Enterprise Software Architect | Vance Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
250–1,000 Employees | $25M – $100M | 1000 Main St, Ste 1800 | Houston | TX | 77002 | United States | Company Page | Profile Page |
| 6 | Brittany | Carlisle | Brittany Carlisle | b.c****e@arli***.com | +1 (785) ***-1374 | +1 (785) ***-1375 | Information Technology | IT Infrastructure Manager | Carlisle Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
1,000–5,000 Employees | $100M – $250M | 1717 Main St, Ste 2400 | Dallas | TX | 75201 | United States | Company Page | Profile Page |
| 7 | Frank | Davenport | Frank Davenport | f.d****t@aven***.com | +1 (822) ***-1497 | +1 (822) ***-1498 | Cloud Operations | Chief Technology Officer | Davenport Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
250–1,000 Employees | $25M – $100M | 100 Federal St, Fl 28 | Boston | MA | 02110 | United States | Company Page | Profile Page |
| 8 | Ann | Yates | Ann Yates | a.y****s@ates***.com | +1 (859) ***-1620 | +1 (859) ***-1621 | Engineering & DevOps | Director of Information Security | Yates Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
100–250 Employees | $10M – $25M | 350 5th Ave, Fl 45 | New York | NY | 10001 | United States | Company Page | Profile Page |
| 9 | Robert | Bennett | Robert Bennett | r.b****t@enne***.com | +1 (896) ***-1743 | +1 (896) ***-1744 | Software Architecture | VP of Product Management | Bennett Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
1,000–5,000 Employees | $100M – $250M | 100 N 7th Ave, Ste 400 | Phoenix | AZ | 85004 | United States | Company Page | Profile Page |
| 10 | Jennifer | Barrett | Jennifer Barrett | j.b****t@arre***.com | +1 (233) ***-1866 | +1 (233) ***-1867 | Security & Compliance | Chief Information Officer | Barrett Technologies LLC | Technology - As400 Ecosystem | 7371 |
541511 |
100–250 Employees | $10M – $25M | 1735 Market St, Fl 18 | Philadelphia | PA | 19103 | United States | Company Page | Profile Page |
How the AS/400 Users List Is Built
Select your primary objective to route directly to our core data solutions for AS/400.
Discuss My Sales CampaignFrame the request around the business problem, not simply the number of AS/400 records required.
Map that problem to data criteria such as enterprise technology, product footprint, use context, and related investment signals and the fields needed to act on them so the final AS/400 dataset matches the brief.
Validate the logic with a reviewable sample before committing to the full audience for the AS/400 market.
Once approved, prepare the database for the intended campaign with the agreed segmentation and field set so the final AS/400 dataset matches the brief.
Start with a Smaller AS/400 Sample
Request a focused sample built around your AS/400 criteria and inspect the records before committing to the full audience.
Frequently Asked Questions About AS/400 Targeting
AS/400 Technographic Data describes the account's relationship with AS/400, including product or platform signals, deployment context, related tools, and other environment indicators where available. For AS/400, those signals can be used to qualify accounts for technology-stack improvement.
For B2B use, an AS/400 Users Email List connects the AS/400 account layer with relevant professional contacts. The list becomes more useful when enterprise technology, product footprint, and use context are applied instead of treating every AS/400 organization the same.
Think of an AS/400 Customers List as the account view of the market. It can show the companies that fit the AS/400 criteria and then add stakeholders, firmographics, related technologies, or sales signals.
Yes. TargetNXT can build a list of companies using AS/400 and segment those accounts by industry, size, location, product context, related technologies, and buyer roles. Sample AS/400 records can be reviewed before the list is scaled.
The AS/400 Installed Base can reveal accounts where the current environment creates integration, migration, modernization, security, support, staffing, or replacement opportunities. Pairing that context with stakeholder data helps sales decide where to start, with the AS/400 market definition kept in view.
Account, technology, and contact fields can all be included in an AS/400 Users Database, such as buying signals, deployment context, department, edition or environment, related technologies, industry, and revenue. For AS/400, the buyer can narrow the schema to the information needed for technology-stack improvement.
An AS/400 Customer Database adds account-specific technology and stakeholder context to the firmographic layer. Compared with a general company database, it is designed around organizations where AS/400 is part of the sales hypothesis.