🚀 How to run introductory sales calls?

3 tactics to run introductory sales calls

🤝 Start the conversation with a human touch

• Kick off with a personal moment (e.g. get a quick laugh, share a recent win/fail, call out something sharp about their company or industry, mention mutual connections etc.)

• Introduce everyone and get names, titles, and responsibilities of each person

• Confirm meeting duration and explain the call structure (e.g. discussion, pitch, or hybrid, when to ask questions etc.)

• Ask what success looks like and what they want out of the call

• Look for clues around decision-making (e.g. management style, internal dynamics, who asked questions, etc.)

🗣️ Qualify fit, amplify credibility, quantify value

• Ask 2–3 questions (using words like “goals,” “challenges,” and “plans”) to uncover pain and priorities that qualify fit and reveal case studies that will resonate (e.g., “What is your company trying to achieve with the purchase?”)

• Share knowledge around competitors, industry statistics, and benchmarks to educate, build trust and demonstrate expertise

• Highlight relatable success stories with similar industry, job title, tech stack and pain point (Use founding story or discovery insights if there are no customers stories yet)

• Address objections with customer examples (e.g. “That’s something we hear a lot. X had the same concern and here’s how we addressed it for them.”)

• Shape a compelling use case by quantifying potential ROI and using prospect’s language

⛳ Map the close

• Tailor close strategy based on buyer stage—don’t skip steps

• If urgency and buying signal is high, confirm budget, verify authority, reconfirm needs and clarify timeline:

  • Confirm budget: “How do you typically evaluate tools like this as a team? How much resources and budget do you have set aside?”

  • Verify authority: “Is there anyone else who would need to see the product or needs to be involved in the decision making process?” 

  • Reconfirm needs: Recap pain points and priorities (should be mostly known by now)

  • Clarify timeline: “Have you ever purchased a tool like this before? What was the process like? Any legal or procurement processes that could impact the sales process?”

• If still considering, focus on goals, challenges, and plans. Ask:

  • Goals / Challenges: “If we could help you achieve this goal or overcome this challenge like we have for X and Y, would you want to explore further?”

  • Plans: “Would it make sense to schedule a follow-up to walk through how we can help achieve this goal more confidently?”

• Avoid questions around budget, authority and timing until solution fit is agreed

• End each call by confirming to-dos, locking next meeting, and previewing the agenda

2 traps to avoid

🚨Default to pitching using a deck or demo

• Introductory sales calls are not for selling, but for understanding and building trust

• Default to asking sharp questions that reveal real problems and context

• Pitch and sell only when it is clear to the prospect how the product will benefit them

🚨Treating the demo like a show-and-tell

• Do not demo the whole product or carry the entire sales call with product demos—tailor and only show what solves their problem

• Hold off the demo until all key stakeholders are present (especially for higher priced solutions)

1 tool to leverage

📖 Best practice on running introductory sales calls

• 58% of prospects want pricing upfront; 54% want to understand product early

• Talk 45%, listen 55% of the time

• Leverage tools like fireflies.ai to capture notes

Bonus: 1 trend to spark startup ideas

📈 Authorization is becoming a critical layer in the age of AI agents

• 98% of enterprises plan to scale AI agents, but 96% see them as security risks—80% report incidents like unauthorized access and data leaks

• Traditional perimeter-based and role-based access models fail as agents make autonomous dynamic decisions involving sensitive data

• Authorization must shift from identity verification to contextualizing identity interactions with data assets across time, applications, and sensitivity levels

• Infrastructure that combines identity context with data classification, automated workflows, and adaptive policy engines will be invaluable