· 9 min read
By the end of this guide, you will have a 5-agent sales intelligence system that takes a prospect name and deal context, researches the prospect's company and key stakeholders, analyzes the competitive landscape specific to this deal, prepares objection-handling strategies, and produces a complete deal intelligence brief. A sales rep receives everything they need to walk into a meeting fully prepared, in minutes instead of hours.
Sales preparation is the highest-leverage activity most reps underinvest in. They know they should research the prospect, understand the competitive dynamics, and anticipate objections. But with 30-50 active opportunities, spending an hour researching each one is not realistic. So most reps skim the prospect's LinkedIn page five minutes before the call and improvise. This agent team eliminates the trade-off between preparation quality and time investment.
You need Claude Code or the Claude Agent SDK configured. For CRM integration (triggering research automatically when a deal reaches a certain stage), the Agent SDK is recommended. You also need the prospect company name, the deal context (what you are selling, the deal stage, and any known stakeholder names), and ideally your company's competitive battle cards or objection-handling guides.
Prepare the following if available: your product's feature comparison matrix against competitors, past win/loss analysis data, customer case studies organized by industry and use case, and any CRM notes from earlier interactions with this prospect.
Mission: Receive the prospect name and deal context, dispatch research tasks to specialist agents, collect and integrate their findings, identify the most important intelligence for this specific deal, and produce the final deal brief.
The Coordinator makes the brief actionable. Raw research is useful; prioritized research is powerful. The Coordinator reads all specialist outputs and determines: what are the three things this rep absolutely must know before the meeting? What is the single biggest risk to the deal? What is the most compelling angle to lead with? These prioritized insights go at the top of the brief.
Prompt guidance: Give the Coordinator the deal stage and context: "This is a first discovery call with the VP of Operations at a 500-person manufacturing company. We were introduced through a mutual connection. The prospect currently uses [Competitor X]. Our goal is to understand their current workflow pain points and establish whether there is a fit." The stage determines what intelligence matters most.
Mission: Build a comprehensive profile of the prospect company including business overview, recent developments, financial health, technology stack, organizational structure, strategic priorities, and any challenges or initiatives relevant to the product being sold.
This agent answers: "What do I need to know about this company?" It investigates the company's size, revenue, growth trajectory, industry position, recent press (acquisitions, layoffs, product launches, leadership changes), technology investments, and stated strategic priorities. It looks for trigger events -- recent changes that create urgency for the problem your product solves.
Prompt guidance: Tell the agent what your product does so it can filter for relevant intelligence. "We sell supply chain visibility software. Prioritize information about the prospect's supply chain operations, vendor relationships, logistics challenges, and any public statements about supply chain strategy." Without this filter, the agent will return a generic company overview that does not help the rep sell.
Mission: Research the key decision-makers and influencers involved in the deal. Build profiles including their role, responsibilities, professional background, public viewpoints, communication style, likely priorities, and potential concerns about a purchase like this.
The Stakeholder Analyst gives the rep a map of who matters and what they care about. For the VP of Operations, it might find that she previously worked at a company that had a failed software implementation, suggesting she will be risk-averse and focused on implementation complexity. For the CFO who will approve the budget, it might find public statements about the company's cost reduction initiative, suggesting ROI framing will resonate more than feature discussions.
Prompt guidance: Specify the depth based on stakeholder importance: "Detailed profiles for the primary decision-maker and the economic buyer. Brief profiles for any additional influencers mentioned in the CRM notes. For each profile, include: professional history, likely priorities based on their role and the company's situation, potential objections, and recommended communication approach."
Mission: Analyze the specific competitive dynamics of this deal. Identify which competitors are likely involved, their strengths and weaknesses relative to this prospect's needs, their likely pricing and positioning, and where your product has defensible advantages.
This agent goes beyond generic battle cards. It analyzes the competition in the context of this specific prospect. If the prospect is a manufacturing company with complex multi-site operations, the Competitive Analyst evaluates each competitor's manufacturing-specific capabilities, not their overall feature set. It identifies where competitors are strong (and therefore where the rep should not compete head-to-head) and where they are weak (where the rep should steer the conversation).
Prompt guidance: Provide your competitive intelligence: battle cards, feature comparison matrices, and win/loss data. Tell the agent which competitors you most frequently encounter in this segment. "In mid-market manufacturing deals, we most commonly compete against [Competitor A] and [Competitor B]. [Competitor A] wins on brand recognition and ecosystem integrations. [Competitor B] wins on price. We win on implementation speed and manufacturing-specific workflows."
Mission: Anticipate the objections this prospect is likely to raise based on their company profile, stakeholder priorities, competitive situation, and deal stage. For each objection, prepare a response strategy with supporting evidence.
The Objection Strategist is the deal's devil's advocate. It reads the Company Researcher's findings and the Stakeholder Analyst's profiles to predict where resistance will come from. If the company recently had a failed software implementation, expect objections about implementation risk. If the CFO is driving cost reduction, expect price objections. If a competitor is entrenched, expect switching cost concerns.
Prompt guidance: Provide your standard objection-handling playbook as a starting point. The agent's job is not to replace it but to customize it for this specific deal. "For the objection 'your competitor is already integrated with our ERP,' the standard response is [X]. Given that this prospect uses SAP and we recently launched our SAP connector, the customized response should lead with the SAP integration and reference the case study from [similar company]."
Sales intelligence benefits from parallel research with a final synthesis phase:
The Competitive Analyst needs the company profile to be effective (it needs to know the prospect's specific situation to assess competitive dynamics), so it runs after the Company Researcher. The Objection Strategist needs everything because objections can come from any angle.
Sales intelligence prompts need to emphasize actionability. The rep does not need a research paper -- they need information they can use in a conversation.
For the Company Researcher: "You are a sales research analyst preparing a prospect briefing. Research the following company and produce a profile focused on information that helps a sales representative have a productive conversation. Include: (1) Company overview -- what they do, their size, and their market position; (2) Recent developments -- anything from the past 6 months that signals change, opportunity, or challenge; (3) Trigger events -- specific developments that create urgency for the problem our product solves; (4) Technology landscape -- what relevant technology they currently use; (5) Strategic priorities -- what the company has publicly stated it is focused on. Do not include generic industry background -- focus on this specific company."
For the Stakeholder Analyst: "You are a sales intelligence analyst building stakeholder profiles. For each person, provide: (1) Role and responsibilities, (2) Professional background including previous companies and roles, (3) Public viewpoints -- quotes, articles, conference talks, social posts that reveal their priorities and perspectives, (4) Likely priorities given their role and the company's current situation, (5) Potential concerns about a purchase like ours, (6) Recommended approach -- how to communicate with this person based on their background and likely priorities. Keep each profile to 200-300 words. Emphasize what is useful in a conversation, not biographical trivia."
For the Competitive Analyst: "You are a competitive intelligence analyst assessing the competitive dynamics of a specific deal. Given the prospect's company profile and needs, analyze: (1) Which competitors are likely involved in this evaluation and why; (2) Each competitor's strongest pitch to this specific prospect; (3) Each competitor's vulnerabilities given this prospect's specific requirements; (4) Where our product has the strongest differentiated advantage for this prospect; (5) Recommended competitive positioning -- what narrative should our rep build to win against each likely competitor."
The final deliverable is structured for rapid consumption -- reps are busy and need to prepare quickly:
For a first discovery call with a mid-market manufacturing company:
Top 3 Things to Know:
Objection Playbook (excerpt):
"We already have a system in place." Acknowledge that [Competitor A] handles basic tracking well. Reframe the conversation around what their current system cannot do: real-time visibility, predictive disruption alerts, and multi-tier supplier monitoring. Reference the case study from [similar manufacturer] who kept their existing system for basic tracking and layered your product on top for advanced visibility, seeing a 23% reduction in supply disruptions within 90 days.
"We just went through a major implementation -- we can not take on another one." This objection is likely personal for the VP of Operations given her experience at [prior company]. Address it directly: "Our implementation is fundamentally different from an ERP rollout. We integrate via API with your existing systems -- no data migration, no workflow disruption. The median time to first value for manufacturing customers our size is 12 business days. I would be happy to connect you with [reference customer] who was in a similar post-implementation situation."
CRM-triggered automation. Configure the Agent SDK to trigger a deal brief automatically when a deal moves to a specific stage (e.g., "Discovery Scheduled"). The brief is waiting in the rep's inbox before they start preparing for the meeting.
Post-meeting debrief. After the meeting, the rep inputs notes about what they learned. The Coordinator updates the brief, the Objection Strategist refines its predictions based on what actually came up, and the Competitive Analyst adjusts its assessment based on new information about who else the prospect is evaluating.
Deal scoring. Add a Deal Scorer agent that reads all the intelligence and assigns a win probability based on factors like competitive dynamics, stakeholder alignment, budget signals, and timeline urgency. This helps sales managers prioritize coaching time on deals where preparation can make the difference.
Account expansion intelligence. Use the same team for existing customers approaching renewal or expansion. Replace the Company Researcher's focus from "prospect research" to "account health" -- analyzing product usage, support history, and expansion signals to prepare for the renewal conversation.