How Nektar Automates Buying Committee Engagement
How Nektar Automates Buying Committee Engagement RevOps 11 min Updated: August 4, 2026 Salesforce’s data model has three objects relevant to a buying committee: Account, Contact, and Opportunity Contact Role. A Contact is a person. An OCR is a static label, “Decision Maker,” “Influencer”, attached to an Opportunity. That’s the entire model. It was built to store contacts. It was never built to map a buying group, and that distinction is architectural, not semantic. The average enterprise deal involves 6 to 10 decision participants. The average CRM opportunity has one or two OCRs. A rep who wants to log a third has to remember to create it, assign a role, and keep it current by hand. In practice, almost nobody does this consistently, and the gap between what’s actually happening in a deal and what’s recorded in Salesforce quietly compounds. Get our latest insights into your inbox Why This Gap Exists, and Why It’s Getting Worse An OCR captures a label at a single point in time. It doesn’t track whether that person is engaging, disengaging, newly arrived, or gone. A contact tagged “Champion” who stopped responding three weeks ago looks identical in Salesforce to one who replied yesterday. The label exists. The signal behind it doesn’t. Every system that reads CRM data inherits this blind spot: forecasting models, ABM platforms, customer success tools, attribution engines, and increasingly, AI agents. When a human reads an incomplete CRM record, they can sense-check it, ask a follow-up question, or lean on institutional memory. When an AI agent reads the same record, it takes it at face value. If Salesforce shows one contact on a deal, the agent plans around one contact. Salesforce’s own April 2026 Headless 360 initiative made every core Salesforce capability available as an API, specifically so agents can read, write, and execute workflows without a human opening a browser first. That’s a real shift in what an incomplete buying group actually costs. It used to produce a slightly-off report a manager could catch. Now it can produce a wrong decision made by software, at a speed nobody catches in time. What Breaks Across the Business When Buying Groups Go Unmapped The gap above doesn’t create one problem. It creates a different failure in every function that touches CRM data. In sales, a rep who inherits an account from a departing colleague gets three logged contacts on a key opportunity when the real buying group was nine. Months of relationship context, who the real blocker was, which VP had a back-channel, evaporate the moment the previous rep leaves. A closed-lost re-engagement trigger fires on the one contact still in the system, while the five or six other people who actually shaped that decision were never captured at all. In sales leadership and forecasting, a CRO’s mandate to “multithread every deal above $200K” has no way to be measured, since there’s no data showing whether a labeled “Executive Sponsor” has attended a meeting in the last month or gone quiet. Forecast models score deals on the activity they can see, which typically represents a fraction of what’s actually happening in the account. In marketing, a VIP re-engagement campaign gets built from CRM contacts that cover maybe one or two people per account, while the procurement lead and technical evaluator who actually shaped the original decision never make it onto the list. A prospect’s CFO can attend a webinar six weeks before close and never show up in an attribution report, because nobody added them as an OCR. In customer success, a champion leaves for a new role three months before renewal, and the team discovers there’s no fallback relationship, because nobody ever recorded who else in the account cared about the outcome. QBR invites go to the two or three operational contacts CS already knows, while the executives who cared about strategic outcomes were never mapped in the first place. In RevOps, a meaningful share of the team’s time goes to chasing and cleaning contact data that was incomplete by design from the start, since adding more contacts manually doesn’t solve a problem that’s actually about missing engagement context, not missing names. How Nektar Automates Buying Group Engagement Nektar’s approach starts from a different premise than “get reps to log more contacts.” The data already exists, it’s in the emails, the calendar invites, and the meeting attendee lists generated by normal sales activity every day. What’s missing is the layer that captures it, structures it, attributes it to the right opportunity, and writes it into Salesforce automatically. Four capabilities do this end to end: 1. Automated Opportunity Contact Role Creation Nektar automatically identifies stakeholders from real email and meeting activity and creates the corresponding Opportunity Contact Role, with no rep input required. Every relevant person gets documented and correctly associated with the opportunity as the relationship develops, not just the one or two contacts a rep remembered to add manually. Why it matters: Eliminates the manual entry that made OCR data unreliable in the first place, keeps contact roles accurate and consistent rather than dependent on rep memory, and gives sales and RevOps leadership a real, current view of who’s actually involved in a deal. 2. Conditional OCR Contact roles get created based on specific, predefined conditions your team actually cares about, not a one-size-fits-all rule. Different sales teams or business units can tailor exactly when and how a contact role gets assigned. Why it matters: Adapts to your specific sales process rather than forcing a generic structure onto it, keeps contact-role creation focused on genuinely relevant people rather than every name that appears in an inbox, and scales to complex sales environments with large, varied buying committees. 3. Intelligent Meeting Tagging Meetings get automatically tagged with relevant context, using AI to identify key details and associate them with the right contacts and opportunities, closing the gap between what happened in a meeting and what’s actually recorded about it. Why it matters: Surfaces real insight into what a meeting actually











