How to Find IT Decision-Makers at Multi-Location, Multi-Entity Companies (2026)

Quick Answer: Origami is the fastest way to prospect IT decision-makers at multi-location, multi-entity companies. Describe your target in one prompt ("CIOs at retail chains with 50+ locations and separate legal entities per region"), and Origami's AI searches live web data, identifies parent-subsidiary relationships, and returns verified contacts across the entire corporate structure. Starts free with 1,000 credits, no credit card required — paid plans from $29/month.

The Hidden Challenge: 73% of Enterprise IT Budgets Are Decentralized

Here's what most sales reps miss: 73% of enterprise technology spending now happens at the business unit or subsidiary level, not corporate HQ. A restaurant chain with 200 locations might have one corporate CIO — but nine regional IT directors controlling local vendor contracts, and 14 franchise entities making their own software decisions. Traditional prospecting tools built for single-entity companies return the corporate CIO's contact and stop there. You miss the 23 people who actually control the budget.

This isn't a database problem — it's an architecture problem. ZoomInfo and Apollo index contacts at the parent company level because that's how their crawlers understand LinkedIn and SEC filings. They weren't designed to map "IT Director, Northeast Region" or "VP of Technology, Franchise Operations" across a corporate family tree. Clay can chain multiple searches together to find subsidiaries, but you're building a custom workflow for every account. That doesn't scale when your patch has 50 multi-entity targets.

Why Multi-Location Companies Are Invisible to Standard Prospecting Tools

Most IT sales teams use a two-step process: search ZoomInfo or Apollo for "CIO at [parent company]," then manually dig through LinkedIn to find regional IT leads. The problem compounds when you're selling infrastructure software, cybersecurity, or SaaS products where the buying committee spans corporate IT, regional operations, and subsidiary finance teams.

Here's the workflow most reps describe: Pull the corporate IT org chart from LinkedIn Sales Navigator. Export contacts to Apollo or ZoomInfo to get emails and phone numbers. Then manually cross-reference company websites, press releases, and LinkedIn profiles to identify which subsidiaries exist, where they're located, and who runs technology there. For a single account with 10 entities, this takes 2-3 hours. If your patch has 100 accounts, you're spending full weeks on research that should take minutes.

Multi-entity prospecting requires mapping three layers: corporate IT leadership, regional/divisional tech leads, and subsidiary-level decision-makers. Each layer has different responsibilities — corporate sets standards and negotiates enterprise agreements, regional leaders manage implementation and vendor relationships, subsidiaries control local budgets and make day-to-day procurement decisions. Missing any layer means missing the real buyer.

How to Identify Multi-Entity IT Structures (Before You Start Prospecting)

Not every multi-location company has decentralized IT. A retail chain with 500 stores might centralize all technology decisions at headquarters. A holding company with 12 portfolio businesses might have zero shared IT infrastructure. Before you build a contact list, figure out which structure you're dealing with:

Centralized IT with regional implementation teams — Corporate IT makes all purchasing decisions; regional leads handle rollout and support. Your buyer is at HQ, but you need regional contacts for discovery calls and pilots. Common in: banks, healthcare systems, national retail chains. Prospecting strategy: Lead with corporate CIO/CTO, then map regional IT directors for implementation partnerships.

Federated IT with shared services — Corporate sets standards and negotiates vendor contracts; business units choose from an approved list and control budgets. Your buyer is the business unit CIO or VP of Technology, not corporate. Common in: manufacturing conglomerates, franchise restaurant groups, diversified industrials. Prospecting strategy: Map every business unit separately — treat them as independent accounts.

Fully decentralized portfolio companies — Parent company is a holding entity with no operational IT. Each subsidiary runs its own technology stack. Corporate might set cybersecurity policies, but procurement happens at the subsidiary. Common in: private equity portfolios, diversified holding companies, roll-up acquisitions. Prospecting strategy: Ignore the parent company. Prospect subsidiaries as standalone targets and mention the parent relationship as social proof.

The fastest signal: Check the corporate website's leadership page. If there's a CIO or CTO listed, IT is probably centralized or federated. If there's no corporate tech leader and each business unit has its own "About" page with separate leadership teams, it's decentralized. For publicly traded companies, read the 10-K — the "Management's Discussion and Analysis" section describes how technology and operations are organized.

Tools for Prospecting Multi-Entity IT Decision-Makers

Standard prospecting databases struggle with complex corporate structures. Here's what actually works:

Origami — AI-Powered Multi-Entity Prospecting

Best for: Finding IT contacts across parent companies, subsidiaries, and regional divisions in one query.

How it works: Describe your ideal customer in plain English: "IT directors at restaurant chains with 100+ locations, separately incorporated franchises, and regional VP of Technology roles." Origami's AI searches the live web, identifies subsidiary relationships, maps org structures, and returns verified contacts (names, titles, emails, phone numbers) for every entity in the corporate family. Unlike static databases that only index parent companies, Origami crawls company websites, press releases, LinkedIn, and business registries to find subsidiary IT leaders that traditional tools miss.

Strengths:

• Finds contacts at parent companies AND subsidiaries in one prompt
• Live web search surfaces org changes and new hires that databases lag behind on
• Works for any corporate structure (franchises, holding companies, business units, regional divisions)
• No workflow building — describe what you want, get a contact list

Weaknesses:

• Doesn't integrate directly with CRMs (export as CSV and import)
• Not an outreach tool — you still need HubSpot, Outreach, or Salesloft for campaigns

Pricing: Free plan with 1,000 credits (no credit card required) — paid plans start at $29/month for 2,000 credits. Most IT sales teams use the Pro plan ($129/month, 9,000 credits) for ongoing prospecting.

Why IT sales teams use it: Traditional databases return the corporate CIO and stop. Origami maps the entire IT org across every entity — regional IT directors, subsidiary CTOs, divisional VP of Technologies — and delivers contacts for all of them. It's the only tool built specifically for multi-entity prospecting.

Clay — Workflow-Based Data Enrichment

Best for: Teams with technical users who want to build custom multi-step research workflows.

How it works: Chain data sources together to find subsidiaries, enrich contacts, and qualify leads. For multi-entity prospecting, you'd build a workflow like: (1) Find parent company on LinkedIn, (2) Use Crunchbase or PitchBook to identify subsidiaries, (3) Search LinkedIn for IT leaders at each subsidiary, (4) Enrich contacts with Apollo or Hunter.io. Powerful if you have a Clay expert on your team, but it requires manual workflow building for every new account structure.

Strengths:

• Extremely flexible — if you can describe a research process, Clay can automate it
• Integrates 50+ data sources
• Strong for ongoing CRM enrichment and lead scoring

Weaknesses:

• Steep learning curve — not a tool you hand to an SDR on day one
• Workflow building takes time; multi-entity prospecting requires a new workflow for each corporate structure
• Requires combining multiple data providers (Clay + Apollo + LinkedIn + Clearbit) to get full contact coverage

Pricing: Free plan with 500 actions/month and 100 data credits. Launch plan ($167/month) for small teams. Growth plan ($446/month) recommended for IT sales teams. Enterprise custom pricing.

Best use case: Teams that prospect the same multi-entity accounts repeatedly and want to automate subsidiary research as an ongoing workflow.

ZoomInfo — Enterprise Contact Database

Best for: Large sales teams selling to Fortune 500 parent companies with centralized IT.

How it works: Search by job title, company, and industry to find IT decision-makers. ZoomInfo excels at corporate-level contacts (CIOs, CTOs, VP of Infrastructure at the parent company) but often misses subsidiary and regional IT leaders because those roles don't show up in SEC filings or public org charts.

Strengths:

• Deep contact data at the parent company level
• Intent signals and technographic data for enterprise accounts
• Strong CRM integrations (Salesforce, HubSpot)

Weaknesses:

• Designed for single-entity companies; subsidiary contacts are sparse
• Expensive (~$15,000/year minimum, annual contracts only)
• Static database refreshed on a periodic cycle — org changes lag by weeks or months

Pricing: Professional plan starts around $14,995-$18,000/year (3 seats, 5,000 annual credits). Advanced and Elite plans range $25,000-$45,000+/year.

Best use case: Selling to enterprise parent companies where IT is fully centralized and you only need corporate-level contacts.

Apollo — Contact Database + Outreach

Best for: SMB and mid-market IT sales teams prospecting single-entity companies.

How it works: Search by job title, company size, and technology stack to find IT buyers. Apollo's database is built for straightforward prospecting ("CTO at Series B SaaS companies") but struggles with multi-entity structures because it doesn't map parent-subsidiary relationships.

Strengths:

• Affordable entry point (free plan, paid from $49/month annual billing)
• Built-in outreach sequences (email and LinkedIn automation)
• Decent coverage for mid-market tech companies

Weaknesses:

• Misses subsidiary and regional IT leaders entirely
• Contact-centric database; if an IT director isn't on LinkedIn, Apollo won't find them
• Data accuracy issues for non-tech verticals

Pricing: Free plan with 900 annual credits. Basic ($49/month annual, $59/month monthly) with 1,000 export credits/month. Professional ($79/month annual, $99/month monthly) with 2,000 export credits/month. Organization ($119/month annual, $149/month monthly) with 4,000 export credits/month.

Best use case: Prospecting mid-market companies with simple org structures where one CIO controls all IT purchasing.

LinkedIn Sales Navigator — Manual Research

Best for: High-value accounts where you're willing to spend 1-2 hours per company manually mapping IT org structures.

How it works: Search by job title and company to find IT leaders across the corporate family. Sales Navigator surfaces subsidiary employees if they list the parent company in their LinkedIn profile, but there's no automated way to identify all entities or export contacts in bulk.

Strengths:

• Most up-to-date data (real-time LinkedIn profiles)
• Good for discovering org chart relationships and reporting lines
• Useful for social selling and warm intros

Weaknesses:

• No email or phone data — you have to export names to another tool (ZoomInfo, Apollo, Hunter.io) to get contact info
• Entirely manual — no way to automate multi-entity research
• Expensive for what you get (~$100/month per seat)

Pricing: Core plan ~$79.99/month, Advanced ~$135/month, Advanced Plus ~$150/month (prices vary by region and billing cycle).

Best use case: Account-based selling where you're building deep relationships with 10-20 key accounts and need to understand internal politics and reporting structures.

How to Build a Multi-Entity IT Prospect List (Step-by-Step)

Here's the fastest process for mapping IT decision-makers across a complex corporate structure:

Step 1: Identify the corporate structure. Start with the parent company's investor relations page (for public companies) or "About" page (for private companies). Look for: (a) List of subsidiaries, business units, or brands, (b) Organizational chart or leadership structure, (c) Recent press releases about acquisitions or divestitures. If the company is publicly traded, the 10-K (annual report) lists all material subsidiaries and describes how operations are organized. This takes 10 minutes and tells you whether IT is centralized, federated, or decentralized.

Step 2: Map IT leadership at the parent company. Use LinkedIn Sales Navigator or Origami to find: CIO, CTO, VP of IT Infrastructure, VP of Enterprise Applications, Director of Information Security, Head of IT Operations. For centralized IT structures, these are your primary contacts. For federated or decentralized structures, they're influencers but not buyers.

Step 3: Identify subsidiary and regional IT roles. This is where traditional tools fail. If the company has 10 business units, you need to find "VP of Technology, [Business Unit Name]" or "IT Director, Northeast Region" for each one. Origami handles this automatically — describe the org structure in your prompt ("find IT directors at each regional division"), and the AI maps every entity. If you're using Clay, build a workflow that takes the list of subsidiaries from step 1 and searches LinkedIn for IT titles at each one. If you're using ZoomInfo or Apollo, you'll have to manually search each subsidiary as a separate company.

Step 4: Enrich with contact data. You need verified emails and phone numbers for outreach. Origami delivers this in the initial search. If you're using Sales Navigator or manual LinkedIn research, export names and titles to Apollo, Hunter.io, or RocketReach for email/phone enrichment. Expect 60-70% match rates — some regional IT leads won't be in standard databases, and you'll need to find their contact info through company websites or mutual connections.

Step 5: Qualify by technology stack and pain points. Not every IT leader is a buyer for your product. Use technographic data (from ZoomInfo, 6sense, or BuiltWith) to see what technologies each entity currently uses. Check Glassdoor, G2 reviews, and Reddit for pain points related to your category. Prioritize contacts at entities that: (a) Use a competitor or legacy tool you replace, (b) Recently hired for IT roles (signal of growth or tech debt), (c) Operate in regions where you have customer references or case studies.

This entire process takes 3-4 hours per account using manual tools (Sales Navigator + Apollo + spreadsheets). With Origami, it takes one prompt and 2 minutes. That's the structural advantage: the AI handles steps 1-4 automatically by searching the live web, identifying subsidiaries, mapping org charts, and enriching contacts in a single query.

Common Mistakes When Prospecting Multi-Entity IT Buyers

Mistake 1: Treating the parent company as the only account. If IT is decentralized or federated, the corporate CIO can't buy your product — they don't control the budget. You need to prospect every business unit or subsidiary as a separate opportunity. I've seen reps waste months nurturing a relationship with corporate IT only to discover that purchasing decisions happen at the regional level and the CIO has no authority.

Mistake 2: Ignoring franchise structures. Restaurant chains, hotel brands, and retail franchises often have a corporate entity that sets technology standards and 50-200 franchise entities that make actual purchasing decisions. The corporate VP of Technology can recommend your product, but each franchisee negotiates their own contract. Your prospect list needs to include franchise owners and operators, not just corporate IT.

Mistake 3: Using stale contact data. Multi-entity companies reorganize constantly — subsidiaries are acquired, business units are merged, regional roles are eliminated. A contact list from six months ago is 30-40% outdated. Traditional databases (ZoomInfo, Apollo) refresh on a periodic cycle and lag behind real-world changes by weeks or months. Origami searches the live web every time you query, so you're always seeing current org structures and recently hired IT leaders.

Mistake 4: Prospecting the wrong layer. A common pattern: rep reaches out to a regional IT director who loves the product, but the deal stalls because corporate IT has a preferred vendor list and the director can't add new tools without approval. Or: rep spends three months with corporate IT getting approved for the vendor list, only to discover that business units have their own budgets and the corporate approval doesn't matter. Before you start outreach, understand where the budget lives and where the authority to sign contracts sits. Those are often different people.

How Multi-Entity Prospecting Changes by Industry

Healthcare systems: Typically federated IT. Corporate sets cybersecurity and compliance standards. Each hospital or clinic has its own IT director who controls vendor relationships and day-to-day purchasing. Your primary buyer is the facility-level IT director, but you need corporate CIO approval to get on the approved vendor list. Prospecting strategy: Lead with hospital IT directors (they feel the pain), then escalate to corporate IT for contracting. Pain points to mention: interoperability across facilities, EHR integration, HIPAA compliance, staff retention.

Retail chains: Mix of centralized and decentralized depending on technology category. POS systems and e-commerce platforms are corporate decisions. Store-level IT (Wi-Fi, security cameras, inventory management) is often handled by regional operations managers, not IT. Prospecting strategy: For infrastructure and SaaS, target corporate IT. For in-store technology, target regional operations leads. Pain points: omnichannel experience, inventory accuracy, payment security, seasonal demand.

Manufacturing conglomerates: Usually federated IT with high autonomy at the plant level. Corporate IT handles enterprise applications (ERP, PLM, HR systems). Each manufacturing site runs its own OT (operational technology) and plant-floor systems. Your buyer depends on whether you're selling IT or OT products. Prospecting strategy: For enterprise SaaS, target corporate IT. For manufacturing software (MES, SCADA, predictive maintenance), target plant managers and site-level IT. Pain points: legacy systems, ERP integration, downtime reduction, supply chain visibility.

Franchise restaurant groups: Decentralized by design. Corporate provides the brand and operational playbook. Franchisees own their locations and make independent purchasing decisions within brand guidelines. Corporate IT might negotiate preferred pricing, but each franchisee signs their own contract. Prospecting strategy: Ignore corporate. Build a list of franchise owners (usually findable via state business registries or the company's "Find a Location" page with contact info). Pain points: labor costs, food waste, online ordering integration, loyalty programs.

Private equity portfolios: Fully decentralized. Each portfolio company operates independently. The PE firm might have an Operating Partner who pushes best practices, but they don't control technology decisions. Prospecting strategy: Treat each portfolio company as a standalone account. Mention the PE firm as social proof ("We work with three other [PE Firm Name] portfolio companies"). Pain points: scaling quickly post-acquisition, integrating systems across roll-up acquisitions, reporting to the board.

What to Do After You Build Your Multi-Entity IT Prospect List

You have a spreadsheet with 200 IT contacts across 15 multi-entity accounts. Now what?

Segment by decision-making authority. Group contacts into three tiers: (1) Corporate IT — influencers and gatekeepers who set standards and approve vendors. (2) Business unit or regional IT — primary buyers who control budgets and sign contracts. (3) Subsidiary or site-level IT — end users who implement and manage the technology day-to-day. Tailor outreach to each tier: corporate gets thought leadership and ROI case studies, business unit gets pain-point-focused discovery, subsidiary gets product demos and quick-start offers.

Map account relationships. For each multi-entity account, identify who reports to whom and where budget authority lives. This prevents the mistake of selling to someone who can champion your product but can't approve the purchase. Use LinkedIn to find reporting lines (check whose profile shows up under "People Also Viewed" when you look at an IT leader's page — usually their boss or direct reports). If you can't map it publicly, ask directly during discovery: "Walk me through how technology purchasing decisions happen at [Company]. Who needs to be involved? Who has final sign-off?"

Sequence your outreach. Don't blast everyone at once. Start with business unit or regional IT leaders (your primary buyers). If they express interest, ask for an intro to corporate IT for vendor approval. If corporate IT gates you, pivot to a different business unit and build a coalition of regional champions who can pressure corporate to approve your product. Multi-entity deals often require selling bottom-up (prove value at one subsidiary) and top-down (get corporate approval) simultaneously.

Use your data. Origami delivers contacts with company details, recent hires, and business context. Use that to personalize outreach. Example: "Saw you recently joined as IT Director for [Subsidiary Name] — I work with three other [Parent Company] business units on [pain point]. Worth a quick call to see if [your product] could help with [specific challenge]?" Personalized cold emails get 3-5x higher reply rates than generic blasts.

Track which entities respond. In your CRM, tag each contact with their subsidiary or business unit name. When one entity shows interest, you have a case study to use with other entities: "Your colleagues at [Subsidiary A] are using [product] to solve [pain point] — reduced [metric] by 40% in two months." Internal proof points are the fastest way to expand across a multi-entity account.

The biggest mistake IT sales reps make with multi-entity companies: treating them like single-entity accounts and wondering why deals stall. The second biggest mistake: knowing they're complex but using prospecting tools built for simple org structures and getting incomplete contact lists. Origami is the only prospecting platform designed specifically to map IT decision-makers across parent companies, subsidiaries, business units, and regional divisions — and deliver verified contact data for every layer. Start with 1,000 free credits and see the difference live web search makes when you're prospecting corporate families instead of standalone companies.