Follow-Up Communication Tips

If you’re an AE and still sending “Recap Emails” after discovery calls, let me save you 12 months of frustration: You're making a mistake. You are confusing the buyer. You’re flooding them with everything you heard—but not what they need to do next. It feels helpful. It feels “consultative.” But in reality, it kills momentum. Here’s what I teach my AEs instead: Only one thing matters between first meeting and proposal: Progress. Forget the fluff. The notes. The recap. The follow-up should be this simple: “Great meeting with your team. Looks like there’s strong potential to help. As a next step, we’ll need to do a deeper dive into your environment so we can show you a tailored demo and proposal with implementation details and costs. Let’s schedule that session—it should take about an hour. After that, we’ll be ready to deliver a proposal.” That’s it. No persuasion. No selling. Just forward motion. Why does this work? Because: Buyers don’t read your bullet-pointed essays. They don’t remember action items buried in paragraphs. They don’t need more “convincing” before the demo. They need clarity. Ownership. Urgency. And when you stop treating every meeting like a closing opportunity, you’ll finally start getting to the point that matters: Proposal on the table.

Excellent tips here illustrating how a subtle change in tone can have a massive influence upon how your message is received. 1) Acknowledge Delays with Gratitude "Sorry for the late reply…" "Thank you for your patience." 2) Respond Thoughtfully, Not Reactively "This is wrong." "I see your point. Have you considered [trying alternative]?" "Thank you for sharing this—I appreciate your insights." 3) Use Subject Lines That Get to the Point "Update" "Project X: Status Update & Next Steps" 4) Set the Tone with Your First Line "Hey, quick question…" "Hi [Name], I appreciate you. I wanted to ask about…" 5) Show Appreciation, Not Acknowledgment "Noted." "Thank you for sharing this—I appreciate your insights." 6) Frame Feedback Positively "This isn’t good enough." "This is a great start. Let’s refine [specific area] further." 7) Lead with Confidence "Maybe you could take a look…" "We need [specific task] completed by [specific date]." 8) Clarify Priorities Instead of Overloading "We need to do this ASAP!" "Let’s prioritize [specific task] first to meet our deadline." 9) Make Requests Easy to Process "Can you take a look at this?" "Can you review this and share your feedback by [date]?" 10) Be Clear About Next Steps "Let’s figure it out later." "Next steps: I’ll handle X, and you confirm Y by [deadline]." 11) Follow Up with Purpose, Not Pressure "Just checking in again!" "I wanted to follow up on this. Do you need any additional details from me?" 12) Avoid Passive-Aggressive Language "As I mentioned before…" "Just bringing this back in case it got missed."

Most change initiatives don't fail because of the change that's happening, they fail because of how the change is communicated. I've watched brilliant restructurings collapse and transformative acquisitions unravel… Not because the plan was flawed, but because leaders were more focused on explaining the "what" and "why" than on how they were addressing the fears and concerns of the people on their team. People don't resist change because they don't understand it. They resist because they haven't been given a compelling story about their role in it. This is where the Venture Scape framework becomes invaluable. The framework maps your team's journey through five distinct stages of change: The Dream - When you envision something better and need to spark belief The Leap - When you commit to action and need to build confidence The Fight - When you face resistance and need to inspire bravery The Climb - When progress feels slow and you need to fuel endurance The Arrival - When you achieve success and need to honor the journey The key is knowing exactly where your team is in this journey and tailoring your communication accordingly. If you're announcing a merger during the Leap stage, don't deliver a message about endurance. Your team needs a moment of commitment–stories and symbols that anchor them in the decision and clarify the values that remain unchanged. You can’t know where your team is on this spectrum without talking to them. Don’t just guess. Have real conversations. Listen to their specific concerns. Then craft messages that speak directly to those fears while calling on their courage. Your job isn't just to announce change, but to walk beside your team and help your team understand what role they play in the story at each stage. #LeadershipCommunication #Illuminate

When I started as a SOC Analyst, I thought the job was all about me, my SIEM, and my alerts. But I quickly realized: Even the best detection is useless if no one understands what I’m saying. If the IT team doesn’t get my request, they won’t isolate the machine. If leadership doesn’t understand the risk, they won’t support action. If developers don’t see the threat, they’ll push vulnerable code again. Here’s how I started building better communication skills — and how it changed everything: 1. Translate Technical to Practical Instead of: “We detected TTPs consistent with MITRE ATT&CK T1059 via base64-encoded PowerShell.” I now say: “We found someone trying to run malicious PowerShell on a user machine. It could lead to ransomware. We blocked it.” Simple. Clear. No jargon. 2. Listen Before You Send I used to send long, technical emails — assuming the other team would read and respond. Now, I ask: “What does the IT team care about?” (Steps to fix) “What does management care about?” (Business risk, cost) Tailoring your message is respect. 3. Speak Their Language For IT: Use system names, impact, urgency For Leadership: Talk risk, reputation, compliance For DevOps: Focus on secure coding and CI/CD integration 4. Document Your Ask Clearly I learned to write tickets or emails like this: What happened What I need from them Deadline or urgency Contact if they have questions This clarity saves time — and builds trust. Final Thought: You don’t just need to detect threats — you need to communicate them. The more clearly you speak, the faster your organization can act. Cybersecurity is a team sport. Communication is your bridge. How do you make sure your messages land across teams? #CyberSecurity #SOCAnalyst #SoftSkills #CrossTeamCommunication #BlueTeam #InfoSec #IncidentResponse #Leadership #DevSecOps #SOCLife #SecurityAwareness #CyberCareers #SpeakToLead

𝗪𝗵𝘆 𝗔𝗜 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝘀 𝗙𝗮𝗶𝗹 𝗮𝘁 𝘁𝗵𝗲 𝗦𝗲𝗰𝗼𝗻𝗱 𝗠𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲 — 𝗡𝗼𝘁 𝘁𝗵𝗲 𝗙𝗶𝗿𝘀𝘁 Most AI products fail not at launch. They fail at Milestone 2 — the moment after the initial “wow” disappears and users start behaving like humans again, not tourists. Here’s the core pattern I see across AI startups : 𝗠𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲 𝟭: “𝗧𝗵𝗶𝘀 𝗶𝘀 𝗰𝗼𝗼𝗹.” Every AI agent, wrapper, or assistant clears this hurdle. Users try it. They get a result. They feel the dopamine rush of “AI magic.” Founders celebrate. Retention graphs look promising for 14–30 days. This is not success. This is novelty. Novelty behaves like a sugar high. It spikes. It always crashes. 𝗠𝗶𝗹𝗲𝘀𝘁𝗼𝗻𝗲 𝟮: “𝗪𝗶𝗹𝗹 𝗜 𝘂𝘀𝗲 𝘁𝗵𝗶𝘀 𝗲𝘃𝗲𝗿𝘆 𝘄𝗲𝗲𝗸?” This is the graveyard. This is where: “AI writing tools” go to die “AI research agents” flatten “AI copilots” get uninstalled “AI dashboards” become ghost towns “AI wrappers” vanish as quickly as they appear 𝗪𝗵𝘆? Because Milestone 2 is no longer about capability. It’s about psychology. It’s driven by: Habits Trust Emotion Reliability expectations Identity (“Does using this make me feel competent?”) Loss aversion (“Will this break if I rely on it?”) Most AI products don’t understand the human they’re serving. They understand the model they’re using. 𝗦𝗼𝗺𝗲 𝗲𝘅𝗮𝗺𝗽𝗹𝗲𝘀 : 1) The “Smart Assistant” that becomes a stranger Milestone 1: It answers your prompt well. Milestone 2: You realize it doesn’t remember context, tone, preferences, or your working style. It feels like starting over every time. AI becomes a chore. Outcome: Churn. 2) The “AI Inbox / Email Agent plugin” that overwhelms Milestone 1: It drafts replies quickly. Milestone 2: You notice: Wrong assumptions Overconfident rewrites Tone mismatches Hallucinated commitments Replies you’d never send Users don’t want speed in communication. They want safety. Outcome: Turned off within 10–14 days. 𝗛𝗲𝗿𝗲’𝘀 𝘁𝗵𝗲 𝗱𝗲𝗲𝗽𝗲𝗿 𝘁𝗿𝘂𝘁𝗵: AI products fail when they cross from novelty → dependency. Dependency requires: Predictability Emotion Behavioral reinforcement Onboarding into a new identity A sense of progress Trust compounding A stable workflow A feeling of “I can’t go back” These are psychological milestones, not technical ones. This is why product architecture matters more in AI than in traditional SaaS. It’s no longer about what the tool can do — it’s about what the user is willing to trust, adopt, and depend on. — 𝗠𝘆 𝟮 𝗰𝗲𝗻𝘁𝘀: If you want your AI products to survive Milestone 2, Go for behavior, not outputs. Solve for needs, not features Design for identity, not actions. Architect for trust, not demos. Most AI products can clear the “magic” bar. Almost none can clear the human bar. That’s where the real work starts for the AI PM!

𝗠𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝘁𝗿𝗲𝗮𝘁 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀 𝗮𝘀 “𝗮𝗳𝘁𝗲𝗿𝘁𝗵𝗼𝘂𝗴𝗵𝘁𝘀.” 𝗕𝗶𝗴 𝗺𝗶𝘀𝘁𝗮𝗸𝗲. Done right, comments are mini-posts that 3X your reach, authority, and engagement. Here are 10 powerful tactics I use (that most people miss): 1️⃣ 𝗧𝗵𝗲 𝟯-𝟮-𝟭 𝗠𝗲𝘁𝗵𝗼𝗱 3 lines adding value 2 lines sharing experience 1 line asking a question → Works like magic for sparking replies. 2️⃣ 𝗣𝗮𝘁𝘁𝗲𝗿𝗻 𝗜𝗻𝘁𝗲𝗿𝗿𝘂𝗽𝘁𝘀 Start with “Actually…” or “Interestingly…” → Instantly stands out in a sea of “Great post!” 3️⃣ 𝗠𝗶𝗰𝗿𝗼-𝗦𝘁𝗼𝗿𝗶𝗲𝘀 𝗪𝗶𝗻 Challenge → Action → Result → Humans respond to stories more than statements. 4️⃣ 𝗧𝗵𝗲 𝟭𝟱-𝗠𝗶𝗻𝘂𝘁𝗲 𝗥𝘂𝗹𝗲 Engage within 15 minutes of a post going live. → LinkedIn boosts early engagement. 5️⃣ 𝗧𝗵𝗲 𝗕𝗿𝗶𝗱𝗴𝗲 𝗠𝗲𝘁𝗵𝗼𝗱 Take the post → link it to your expertise. → Builds thought leadership without hijacking. 6️⃣ 𝗖𝗼𝗺𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗰𝗸𝗶𝗻𝗴 Reply to top comments with insights or questions. → Turns you into part of the conversation, not just a spectator. 7️⃣ 𝗖𝗿𝗲𝗱𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗗𝗮𝘁𝗮 𝗣𝗼𝗶𝗻𝘁𝘀 “This worked 3X better for me” “Got a 227% increase doing this” → Specific > vague. 8️⃣ 𝗔𝗴𝗿𝗲𝗲𝗱 + 𝟭 𝗘𝘅𝘁𝗿𝗮 “Yes, and here’s another angle…” → Shows you’re not just nodding along. 9️⃣ 𝗦𝗺𝗮𝗿𝘁 𝗧𝗮𝗴𝗴𝗶𝗻𝗴 Mention 1–2 relevant experts (never spam). → Expands visibility organically. 🔟 𝗖𝗹𝗼𝘀𝗲 𝗪𝗶𝘁𝗵 𝗮 𝗛𝗼𝗼𝗸 “What’s your take on this?” or “How do you approach this?” → Invites dialogue, not dead ends. 𝗕𝗼𝗻𝘂𝘀 𝗥𝘂𝗹𝗲: If your comment looks like a throwaway… it probably is. Never waste an opportunity to show up with value. 👉 Stop scrolling. Start commenting like a creator. Your next client, opportunity, or collaborator might just find you in the comments.

I was Wrong about Influence. Early in my career, I believed influence in a decision-making meeting was the direct outcome of a strong artifact presented and the ensuing discussion. However, with more leadership experience, I have come to realize that while these are important, there is something far more important at play. Influence, for a given decision, largely happens outside of and before decision-making meetings. Here's my 3 step approach you can follow to maximize your influence: (#3 is often missed yet most important) 1. Obsess over Knowing your Audience Why: Understanding your audience in-depth allows you to tailor your communication, approach and positioning. How: ↳ Research their backgrounds, how they think, what their goals are etc. ↳ Attend other meetings where they are present to learn about their priorities, how they think and what questions they ask. Take note of the topics that energize them or cause concern. ↳ Engage with others who frequently interact with them to gain additional insights. Ask about their preferences, hot buttons, and any subtle cues that could be useful in understanding their perspective. 2. Tailor your Communication Why: This ensures that your message is not just heard but also understood and valued. How: ↳ Seek inspiration from existing artifacts and pickup queues on terminologies, context and background on the give topic. ↳ Reflect on their goals and priorities, and integrate these elements into your communication. For instance, if they prioritize efficiency, highlight how your proposal enhances productivity. ↳Ask yourself "So what?" or "Why should they care" as a litmus test for relatability of your proposal. 3. Pre-socialize for support Why: It allows you to refine your approach, address potential objections, and build a coalition of support (ahead of and during the meeting). How: ↳ Schedule informal discussions or small group meetings with key stakeholders or their team members to discuss your idea(s). A casual coffee or a brief virtual call can be effective. Lead with curiosity vs. an intent to respond. ↳ Ask targeted questions to gather feedback and gauge reactions to your ideas. Examples: What are your initial thoughts on this draft proposal? What challenges do you foresee with this approach? How does this align with our current priorities? ↳ Acknowledge, incorporate and highlight the insights from these pre-meetings into the main meeting, treating them as an integral part of the decision-making process. What would you add? PS: BONUS - Following these steps also expands your understanding of the business and your internal network - both of which make you more effective. --- Follow me, tap the (🔔) Omar Halabieh for daily Leadership and Career posts.

"Let me know if you have any questions." "Happy to discuss further." "Looking forward to your thoughts." Every time you end a follow-up with these wimpy closes, you're asking busy executives to do work they won't do. They're not going to think of questions. They're not going to schedule a follow-up call. They're not going to send you their thoughts. They're going to delete your email and move on with their actual job. The fix is making the next step so easy that a drunk executive could do it. Instead of "let me know if you have questions," embed your calendar link directly in the email. One click to book time. Instead of "happy to discuss further," Create a simple yes/no decision box: "Ready to see the ROI calculation? Yes | No" Instead of hoping they'll respond with their availability, give them three specific time slots to choose from. The most powerful follow-up technique? Use their exact words from your call. When Jessica said she's "bleeding money on software licenses," don't paraphrase it. Quote it exactly. Reference her Thursday board meeting. Add one insight she didn't know. There's nothing more impossible to ignore than hearing your own words reflected back with new value attached. Your generic templates sound like every other vendor they're ghosting. But your personalized follow-ups that reference specific moments from your conversation get responses. Stop making prospects do the work of figuring out next steps. Start making it obvious how they move forward. Every follow-up is life or death for your deal. Most AEs are committing suicide with their own emails. Don’t be like most AEs.

There's a difference between responding quickly and being responsive. I’m convinced quite a few of our colleagues in Sales and CS don't know they're confusing the two. I’ve seen it happen countless times. A customer sends a message. The AE/CSM sees it, feels that familiar pull … “got to get back to them” … and fires off a reply within minutes. And the reply is fine. It's professional. It's fast. It's just not quite right. Not because the AE/CSM gave bad information. But because they answered the question that was asked instead of the question that was meant. The customer said "can we talk about pricing?" and what they actually needed was someone to hear that they're nervous about renewing given their budget constraints. The customer said "we're having trouble with onboarding" and what they actually needed was someone to acknowledge that we dropped the ball somewhere upstream. Speed closed the loop. But it missed the point. Here's my point: the instinct to respond fast is genuinely good. It signals respect. It signals urgency. Your customers notice it and they appreciate it. But the instinct becomes a liability the moment it skips the pause. Not a long pause. Not "I'll get back to you in three days." Just the small moment where you stop and ask yourself: *what does this customer actually need right now?* Not what did they type. What do they need. That pause is the work. Too many AEs/CSMs skip it. So here's what I'd push every CS and Sales professional to build into their practice: 1️⃣ Read it twice before you respond once. Not for typos. For subtext. What is the customer *really* telling you? What's the feeling underneath the question? That second read is where you find it. 2️⃣ Separate speed from responsiveness; they're not the same thing. Being responsive means the customer feels heard, helped, and confident you understand their situation. That can happen in five minutes or five hours. Speed is a proxy. Responsiveness is the real standard. 3️⃣ Ask before you answer when you're not sure. "Before I dig in, may I ask what's driving this?" is not slow. It's not weak. It's the move that separates an AE/CSM who closes tickets from one who actually builds trust. Customers remember the people who asked the right question before giving the answer. The best AEs/CSMs I've seen aren't the fastest. They're the most intentional. They respond with purpose and their customers can feel the difference. That's what responsiveness actually looks like. #CreateTheFuture #CustomerSuccess #Leadership #SalesExcellence #GrowthMindset #AlwaysLearning

One thing 99% of candidates never do after their interview and it costs them the offer every time… They never send a real, impactful follow-up. My student, a complete fresher, was competing against candidates with more experience. After weeks of rejections and silence, he got his YES from a top MNC. Because he did this ONE thing 99% ignore: he sent a follow-up message that showed genuine interest, real value, and absolute intent. Why does this matter? According to LinkedIn’s research, candidates who follow up within 24 hours are 50% more likely to receive a positive response. But almost no one does it well. 👉 Here’s the exact type of follow-up I teach my students to send (that actually works): Subject: Thank you for the opportunity Hi [Interviewer’s Name], Thank you for meeting with me today. Our discussion about [specific project, e.g., Infosys’ new fintech initiatives] made me even more excited about the possibility of joining your team. I wanted to add a quick thought: Given my experience leading my college’s coding club and developing a payments app for over 2,000 users, I believe I can quickly add value to [Company]’s [specific goal or project]. If there are any further steps I can complete or details I can provide, please let me know. Looking forward to the next steps! Best, [Your Name] Why did this work? 1️⃣ It’s specific (mentions a company project or problem). 2️⃣ It ties the candidate’s unique value directly to the company. 3️⃣ It’s proactive and genuine, not “just checking in.” The post-interview silence is where most opportunities die. But also where a single message can reopen the door. 💡 My tips for you: ➡️ Always send a tailored follow-up within 24 hours. ➡ Reference the interview and your own strengths — show you remember, you care, you fit. ➡ Keep it short, real, and focused on THEM (not just you). If you want to turn interviews into offers, don’t just prepare for the questions. Own the moments after you leave the room. #interview #interviewtips #interviewpreparation #careergrowth