How to Map a Full Buying Committee Before First Contact Using Only Public Data

Most reps multi-thread too late.

They find one director on LinkedIn, launch a cold sequence, get a reply, and only start asking who else is involved after the deal is already live. By then, procurement appears late, security slows things down, a VP says they were never looped in, and the internal champion loses control.

The better move is to map the committee before outreach starts.

This is pure OSINT work. No ZoomInfo. No Demandbase. No org-chart tools. Just free, public sources used in the right order. If you do it well, your first email is not a guess. It is directed at the right role, references the right initiative, and already accounts for the people who can approve, evaluate, or block the deal.

That matters because enterprise purchases are not one-person decisions. Forrester’s 2026 State of Business Buying says buying groups are growing larger and procurement is becoming more influential. In related 2026 Forrester commentary, 73% of purchases involved three or more departments, with an average of 13 people inside the buyer’s organization and nine external influencers. If you only know one name, you are not in the deal. You are in one inbox.

Key takeaway: a rep who spends 30 minutes mapping the committee before first contact will out-prepare every competitor who sends a cold sequence to one name and hopes for the best.

The five buying committee roles to map

Economic buyer controls budget or can release it. In SaaS and tech accounts, this is usually a VP, SVP, GM, CFO, CIO, CISO, CRO, or business unit leader depending on the problem you solve. This person may not run the evaluation, but they can greenlight the spend and tie it to a company priority.

Champion is the operator who feels the pain and will carry your case internally. Common titles are Director, Senior Manager, Head of, or functional lead in the team that lives with the problem daily. Champions are usually measured on workflow, productivity, compliance, pipeline, uptime, or security outcomes.

Technical evaluator checks whether your product will work in the real environment. In SaaS deals this is often an architect, engineering leader, security lead, IT admin, systems lead, or platform owner. They care about integration, deployment effort, access controls, risk, and compatibility.

Procurement or legal enters once the deal is real, but smart reps map them early. Procurement controls process, pricing discipline, and supplier terms. Legal reviews data handling, liability, security terms, and redlines. Common titles include Strategic Sourcing Manager, Procurement Manager, Commercial Counsel, Corporate Counsel, and Legal Operations.

Blocker is the role most reps fail to identify. This is the person whose incentives point the other way: an incumbent tool owner, a security skeptic, a finance gatekeeper, or an adjacent leader protecting headcount, budget, or architecture. They are not always anti-vendor. They are often anti-change.

The public sources that reveal committee structure

• LinkedIn company pages: Start with the company page, then click People and search by function keywords like security, revops, procurement, legal, platform, IT, enterprise applications, or partnerships. Use title patterns: VP, Head, Director, Manager. LinkedIn will not hand you an org chart, but it reliably shows role clusters and reporting layers.
• Job postings: This is the most underused source in sales OSINT. Search the company careers page plus Google queries like site:company.com/careers "reporting to" or site:company.com/careers procurement security operations. Job ads often reveal reporting lines, team ownership, systems in use, internal priorities, and which functions are expanding. If a role says “reporting to the CTO” or “partnering with legal, security, and procurement,” you just found committee clues.
• Press releases and newsroom pages: Executive hire announcements are gold because they spell out who owns what. DocuSign’s June 2024 release announcing Paula Hansen as President and CRO and Sagnik Nandy as CTO says both report to CEO Allan Thygesen, and that Hansen leads sales and partnerships while Nandy leads engineering. That immediately tells you who likely owns budget and who influences technical approval for a category tied to agreement management.
• Earnings call transcripts and investor press releases: These reveal which initiatives the CEO is pushing and which executives are attached to them. If the CEO repeatedly emphasizes AI governance, customer productivity, security, or operational efficiency, you know the buying motion is tied to that initiative. They also name the executives who show up repeatedly in those motions.
• G2 reviews: Reviews often expose team ownership in plain English: “our IT team rolled this out,” “security required it,” “marketing operations uses this daily,” or “legal needed approval.” You are not looking for product sentiment. You are looking for which team owned deployment and who cared enough to review it.
• Company blog and newsroom content: Product launch posts, partner announcements, and customer stories tell you which departments are being targeted internally. If a company writes repeatedly about identity, governance, workflow automation, or cost control, those themes usually map back to real internal owners.

The 30-minute committee mapping workflow

1. Define the likely pain owner. Before touching the account, decide which function should care most about your product. If you sell security software, start with security and IT. If you sell RevOps tooling, start with sales operations, revenue operations, and finance.
2. Pull the top layer from LinkedIn. Open the company page and search People by your function keywords. Capture one executive, one director-level operator, and one technical title. You are building a first-pass spine, not a perfect chart.
3. Search job postings for reporting lines. Use Google and the careers site. Look for phrases like reporting to, partnering cross-functionally with, owning vendor evaluation, or named systems. Job posts tell you who sits next to whom operationally.
4. Read the newsroom for executive ownership. Search the company’s press releases for leadership hires, product launches, and strategic initiatives. Note who is quoted. Quoted executives are almost always the accountable leaders for that initiative.
5. Check investor materials for company priorities. Read the latest earnings release or transcript. Pull one initiative that matters now: efficiency, AI, compliance, margin improvement, customer expansion, platform consolidation. This gives you the business case for outreach.
6. Use G2 to identify user-side ownership. Search reviews for phrases that show deployment ownership: IT rolled it out, legal approved, procurement negotiated, operations administers, security mandated. This helps you predict the champion and evaluator roles.
7. Map each person to a role. Assign names under five columns: economic buyer, champion, technical evaluator, procurement/legal, blocker. You do not need certainty on day one. You need a strong working hypothesis.
8. Write source-backed notes. Next to each name, write the evidence. Example: “CTO — named in press release as leader of engineering” or “Senior Manager, Security Engineering — found via LinkedIn + job post references to security platform work.”
9. Build outreach around the map. Your first message should reference the initiative, the likely pain owner, and the cross-functional impact. Your follow-up should multi-thread into the adjacent roles you already mapped.

A real worked example: mapping DocuSign from public data

DocuSign is a good live example because public sources clearly expose leadership, ownership, and initiative direction.

• Economic buyer: Allan Thygesen, CEO. Source: DocuSign investor press releases. In the company’s June 2025 Q1 FY2026 results, Thygesen said Q1 was important for DocuSign’s long-term transformation and highlighted growth in Intelligent Agreement Management. That signals top-level executive sponsorship and budget alignment around IAM.
• Economic buyer / budget co-owner: Paula Hansen, President and Chief Revenue Officer. Source: DocuSign June 25, 2024 press release announcing new revenue and engineering leadership. The release says Hansen would lead enterprise and commercial sales and partnership teams worldwide, reporting to Thygesen. If your product touches revenue workflows, growth systems, or partner operations, she is squarely in the budget conversation.
• Technical evaluator: Sagnik Nandy, Chief Technology Officer. Source: same June 25, 2024 press release. DocuSign states Nandy leads all aspects of engineering, research, and engineering operations. That is a direct public indicator of who evaluates platform fit, scalability, and technical risk for major technology initiatives.
• Technical evaluator / internal systems owner: Shanthi Iyer, Chief Information Officer. Source: DocuSign newsroom announcement on her CIO appointment. The release says Iyer would drive operational excellence, employee productivity, and ease of doing business, and that she reported to then-COO Scott Olrich. Even though that release is older, it still clearly identifies the CIO lane: internal systems, productivity, and operating infrastructure.
• Champion candidate: a director or senior manager in agreement operations, revenue operations, business systems, or legal operations. Source method: LinkedIn People search plus current roles. Public title patterns at a company like DocuSign point to operator-level owners who would carry the day-to-day case for a new system tied to agreements, workflows, or productivity.
• Procurement/legal: strategic sourcing, procurement, commercial counsel, and legal operations titles. Source method: LinkedIn and careers search. These roles rarely appear in press releases, but they are usually visible publicly and should be added to the map before outreach if the deal will trigger vendor review or data terms.
• Likely blocker: incumbent platform or systems owner in IT, engineering operations, or legal tech. Source method: LinkedIn role clustering plus job postings that mention current systems and cross-functional ownership. If they already own adjacent tooling, they can slow or shape the evaluation.

What makes this useful is not that public data gives you a perfect org chart. It gives you enough to enter the account with a credible point of view:

• CEO is pushing IAM transformation.
• CRO owns revenue-side execution and partnerships.
• CTO owns engineering and technical evaluation.
• CIO owns internal productivity and operational systems.
• Operator-level champions likely sit in the workflows touched by agreements, automation, or compliance.

That is already better than emailing one random director and hoping they forward you.

The reps who win enterprise deals do not wait for discovery to reveal the committee. They walk in with a map, test it fast, and adjust from signal. That is what OSINT gives you: a head start built from public evidence instead of vendor data exhaust.

If you want more breakdowns like this, subscribe to SalesInt’s paid tier. That is where we publish deeper playbooks and account teardowns that show exactly how to turn public data into usable pipeline intelligence every week.