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.

Hiring managers remember the questions you ask. 8 questions that show you're serious about the role: ➤ "What would success look like in this role in the first 6 months?" - Shows you're focused on delivering value - Sets clear expectations from day one - Demonstrates immediate impact planning ➤ "Could you share more about the team's biggest challenge right now, and how this role would help address it?" - Demonstrates proactive problem-solving mindset - Shows your interest in making an impact - Reveals your solution-oriented approach to problems ➤ "How does this team's work align with the company's 5-year vision?" - Shows strategic thinking - Signals long-term commitment - Demonstrates big-picture understanding ➤ "Can you tell me more about the team's decision-making process for major projects?" - Reveals interest in team dynamics - Shows you're thinking about collaboration - Helps you understand team structure ➤ "What professional development opportunities are available for someone in this role?" - Demonstrates ambition - Shows commitment to growing within the company - Reveals your dedication to continuous learning ➤ "Could you share an example of how constructive feedback is typically delivered within the team?" - Shows emotional intelligence - Highlights interest in team communication - Demonstrates maturity in handling feedback ➤ "How might [recent company announcement/initiative] impact this team's priorities?" - Shows you've done your research - These questions are better than standard questions - Positions you as someone who thinks about business context (Example: "How might the recent expansion into the EMEA market affect this team's product roadmap?") ➤ "What are the next steps in the interview process and what timeline do you anticipate?" - Always ask if it’s not mentioned - Ensures clear follow-up expectations - Gives you an idea on when to send a follow-up email if you haven’t heard back The questions you ask can be just as impactful as the answers you give. Save this post for your next second interview! What questions would you add to this list?  Share below! 👇

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."

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

One cold email isn’t enough. But most follow-ups are just reminders. That’s why they fail. Here’s a better sequence: Email 1 - problem / insight • Lead with a relevant industry shift or pain point. • End with a low-friction CTA. Follow-up 1 - new angle • Instead of “just checking in,” introduce a different benefit. Follow-up 2 – case study or social proof • Show how a similar company solved this issue. Follow-up 3 – final nudge • Make it easy to say yes: “Worth a quick chat, or should I close your file?” The best cold email sequences build momentum. What do you send in follow-ups?

Early in my career at Amazon, I had a manager who was obsessed with EOD reports. Every evening at 5:55 PM: “Status update?” “What did you accomplish today?” “Are you on track?” Meanwhile, I’d been stuck on the same API integration issue for 3 days. The problem wasn’t my productivity. The problem was that no one asked about my blockers. Years later, when I became a manager, I made a radical change: I banned status updates and replaced them with blocker conversations. Instead of “What did you accomplish today?” I started asking: 1/ What’s standing in your way?” 2/ Where are you feeling stuck?” 3/ What resources do you need that you don’t have?” The results were immediate: A team that was perpetually “almost there” suddenly started delivering consistently. Developers who were quiet in meetings began speaking up. Our velocity doubled in one quarter. The counterintuitive truth I learned: Great managers don’t track status—they remove obstacles. When I see managers obsessing over daily status while team members struggle with the same blockers week after week, I know where the real problem lies. Progress doesn’t come from knowing where your team stands. It comes from clearing the path ahead. As a product leader, are you collecting statuses or eliminating blockers?

Is your RAG system a paperweight? It is if it can't handle a simple follow-up question. Building basic RAG is easy. The real challenge is engineering systems that go beyond simple retrieval and actually do more with your data. This is how you build a RAG pipeline that can think, reason, and adapt. Here's how advanced 𝗽𝗿𝗼𝗺𝗽𝘁𝗶𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀 transform your RAG pipeline: 𝗖𝗵𝗮𝗶𝗻 𝗼𝗳 𝗧𝗵𝗼𝘂𝗴𝗵𝘁 (𝗖𝗼𝗧): Instead of jumping to an answer, the model breaks down complex queries into intermediate steps, making the LLM "show its work." 𝗧𝗿𝗲𝗲-𝗼𝗳-𝗧𝗵𝗼𝘂𝗴𝗵𝘁𝘀 (𝗧𝗼𝗧): Takes reasoning further by exploring multiple paths simultaneously. The system generates several potential solutions and evaluates which is most promising. This is how you systematically weigh different pieces of evidence from multiple retrieved documents. 𝗥𝗲𝗔𝗰𝘁 (𝗥𝗲𝗮𝘀𝗼𝗻𝗶𝗻𝗴 + 𝗔𝗰𝘁𝗶𝗻𝗴): This framework lets the system *think* and *act* dynamically. It can reason about what information it needs, act to retrieve it, and then reason again based on what it found. But beyond prompting, you need to fix your retrieval, too. 𝗤𝘂𝗲𝗿𝘆 𝗥𝗲𝘄𝗿𝗶𝘁𝗶𝗻𝗴 & 𝗘𝘅𝗽𝗮𝗻𝘀𝗶𝗼𝗻: Before hitting your vector database, change that vague user question into something your retrieval system can actually work with. This isn't just about synonyms, it's about understanding intent. 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀: Move beyond basic search. Think hybrid search (combining similarity and keyword), metadata filtering, and multi-step retrieval for complex queries. This is where it really gets interesting: 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗥𝗔𝗚. AI agents can reformulate queries on the fly, re-retrieve information if initial results miss the mark, and handle queries requiring multi-step reasoning across multiple documents. Moving from a one-shot solution with no reasoning into an intelligent system that thinks, reasons, and adapts. Ready to go from basic RAG to a reasoning engine? We cover these techniques and more in our ebook on Advanced RAG Pipelines. 𝗗𝗼𝘄𝗻𝗹𝗼𝗮𝗱 𝘆𝗼𝘂𝗿 𝗳𝗿𝗲𝗲 𝗰𝗼𝗽𝘆 𝗵𝗲𝗿𝗲: https://lnkd.in/dita7QCD

CEO: Hey, saw your note — we're cutting Google Ads spend? CMO: Yeah, by -80%. The test confirmed what we suspected. CEO: But hold on… Google was showing 8X ROAS. That’s the best-performing channel we have 😱 CMO: On paper, sure. But when we ran a geo-split test and pulled back spend in key markets, revenue didn’t drop. New customer orders? Flat. Total revenue? Same. Nothing meaningful changed which tells us Google wasn’t driving incremental growth. CEO: So we were paying for sales we would've gotten anyway? CMO: Exactly. A lot of it was branded search - people already looking for us. And here’s the crazy part: when we pulled back Meta in a second hold out test, that’s when revenue dropped. Brand search volume took a hit. Conversions dropped. That was the demand engine. CEO: So Meta was creating demand… and Google was just cleaning it up? CMO: That’s the dynamic here. Meta hunts. Google harvests. The problem is, if you’re only looking at ROAS inside each platform, Google looks like the hero. But when we stepped back and measured total revenue impact, the real growth lever became obvious. CEO: Makes sense. So what’s next? CMO: We shift budget to where it’s actually generating new demand. We’ll keep Google lean. Protect high-intent non-brand searches that are profitable consider cutting brand altogether, but no more over-investing in a PMax black box when we don't know what is retargeting and what is prospecting, CEO: Good call. Thanks for digging into it. If you’re running both Meta and Google, and you haven’t tested which one is actually driving incremental growth - you’re probably spending more than you need to on the wrong channel. The dashboard doesn’t tell the full story. Money in your bank does.

6 Follow Up Templates That Keep Networking Conversations Alive: 1. The Value-First Follow Up Aim to add value to an initiative you know they're working on: "Hi Sarah, saw your company just announced the new product launch. I came across this article on similar launches in your industry. Thought it might spark some ideas for your marketing strategy. Hope the launch prep is going smoothly!" 2. The Specific Question Angle Asking specific questions shows credibility and can get you info you can use to add value: "Hey David, been thinking about our coffee chat last week. You mentioned struggling with team retention in H2. Have you tried implementing "retention interviews" yet? I saw 3 companies in tech reduce turnover by 40% using them, here's a link to that data." 3. The Introduction Offer Networking is hard (as you know!). Offering to make an intro is a great way to add value to two people: "Hi Jessica, following up from our chat. You mentioned needing a UI/UX designer for that new AI feature. My former colleague Anna just went freelance and she's brilliant. She redesigned our entire app in 6 weeks last year. Happy to make an intro if you're still looking!" 4. The Industry Update Hook Leveraging a shift in the market or industry can be a great way to spark a follow up conversation: "Hey Marcus, did you see [Company]'s new Slack-free hours announcement? It directly impacts what we discussed about interrupted work and team output. Could be something worth looking into for your team?" 5. The Achievement Celebration Everyone loves to be recognized for their achievements. Be that person! "Lisa! Just saw you got promoted to VP on LinkedIn. I remember you mentioned being in an interview process when we met for coffee. I know how stressed you were about the interview with the C-Level. Looks like you crushed it! Would love to hear about your new role if you're up for a chat in the next week or two." 6. The Resource Share Sharing resources aligned with your contact's needs is one of the best ways to stay top of mind: "Hi Tom, I know you'd mentioned how much time your sales team was spending on pre-qualification. A connection of mine just shared an AI automation flow that solves for that exact problem. He said it's saved his team 15+ hours per week and led to more sales. I grabbed a copy if you'd like to see it. Just let me know!" —— ➕ Follow Austin Belcak for more 🔵 Ready to land your dream job? Click here to learn more about how we help people land amazing jobs in ~3.5 months with a $44k raise: https://lnkd.in/gdysHr-r

Can you explain what happened here? If you can't, your business may be in BIG trouble. If you work in strategic finance, understanding how to comprehend + explain financial data is not a nice to have...it's a MUST. It doesn't matter whether you are presenting to leadership...the board of directors...or investors. If you don't have a tight grip on your data, you'll be faced with some catastrophic surprises. Let's learn how to interpret + present this by walking through this report together 👇 ➡️ PROFIT & LOSS SUMMARY Your P&L might look decent at first glance... We beat our bottom line net income by 14% 🙌 But a closer look reveals some important details... - Revenue is down 10% ($50K below budget) This is a pretty alarming metric and may mean that your assumptions are too aggressive here. Was it because your conversions rates were lower than expected? Was churn higher than expected? - COGS is actually BETTER than expected by 40% This makes sense...your revenue was lower, so your COGS should also be lower. But there's something more interesting to address here... your gross margin was 80%, compared to your projected 70%. While the variance is favorable it highlights an important question - do you have a strong grip on your unit economics? - Operating expenses are 10% favorable compared to budget. That's good...but why? Which accounts? Was it timing? Was it a change to your plans? - Net Other Income was -$10k compared to your projected +10k. Accounts here typically relate to interest income/expense, depreciation/amortization, and non core business activity. Although $10k may not seem like a lot, it warrants an important analysis This all leads to a $15k favorable net income, which is 14% higher than expected. All done with our analysis? Not quite... We've analyzed the PROFITABILITY of our business, now it's time to analyze our CASH FLOWS ➡️ CASH FLOWS SUMMARY This is where things get puzzling: - Collections are down $70k (78% below target 🤯 ) - Inventory up by $20k over budget - Total cash flows is $35k below budget Woah! We beat earnings but missed our cash flows by 27%?? Believe it or not, this story happens all the time...and it's up to you to see the forest beyond the trees and take action QUICKLY. ➡️ PUTTING IT ALL TOGETHER Your P&L is looking OK, but there are some strong indicators that you don't have a grip on your unit economics, and your revenue projections may be a bit overstated. But the biggest issue by far is your cash flows. You were supposed to collect $90k more than you invoiced this month but instead you only collected $20k. If you have $1m in the bank that may not be too material. But if you have $200k in the bank? Now things get more dangerous. That's why it's CRUCIAL to review this report each and every period - you don't want to be taken by surprise. === How would you interpret these results? What actions would you take? Share your analysis in the comments below 👇