LinkedIn Post Ideas for Account Executives

The discovery call that saved me from a six-month dead deal. Great fit on paper. ICP company, right size, the buyer was warm, the use case made sense. I was excited. Twenty minutes into discovery, I asked a question I'd been working into my regular discovery flow: "Walk me through the last vendor decision your team made above $50k. How did it actually move through your organization?" Her answer: "Oh, we don't usually decide things at this price point. Anything over $25k goes to our procurement committee, and they only meet once a quarter. We just missed the last one — the next is in November." It was March. A worse version of me would have proceeded. "Great, let's get a champion-buy-in going for November." Six months of follow-up, multiple decks, three more meetings. Maybe a deal in Q4. Maybe not. The better version asked the harder question: "Is your team budgeted for this in November, or are you exploring whether to make a case?" She paused. "Honestly, we're exploring. The budget would need to come from somewhere." So I disqualified. Out loud, to her: "It sounds like the timing isn't right for either of us. I'd rather not have us both invest six months in something that doesn't move forward. Could we set a reminder for August to see if the budget picture has changed?" She was visibly relieved. She thanked me. She referred two of her peers within a month. The lesson: — Disqualifying early is the most under-trained skill in sales. — Buyers respect AEs who respect their time more than the ones who chase. — A clean "not now" preserves the relationship in a way "slow yes" never does. If you're sitting on three deals that have been "close" for four months, audit them with this question: "Walk me through the last vendor decision above [your ACV]. How did it actually move?" The answer tells you whether to keep chasing or stop the bleeding.

I reviewed every lost deal from last year. Sharing the pattern. 14 closed-lost. I tagged each with what I think killed it. Then I had my manager review my tags blind to check my honesty. The distribution: — No budget: 2 — Lost to competitor on price: 1 — Lost to competitor on features: 2 — Champion left: 1 — Internal priority shift: 3 — Never met the economic buyer: 9 Let me say that again. Nine of fourteen losses had one thing in common: I never met the person who would actually sign the contract. I had champions. I had users. I had budget owners. I had IT review. In nine deals, I never sat in a room with the actual decision-maker. Why this kept happening: — My champions said "don't worry about that, I'll handle the executive sign-off." I believed them. — I felt awkward asking my champion to introduce me to their boss. I told myself it would feel pushy. — I assumed if I won the user evaluation, the executive would rubber-stamp it. What I changed this year: 1. I now ask in discovery, every time: "Who else needs to be comfortable with this decision, and when would be the right time for me to meet them?" 2. I treat "no need to meet them" as a red flag, not relief. If my champion is gatekeeping the executive, I'm not in a deal — I'm in a project. 3. I send a pre-meeting Loom to the executive 48 hours before any final meeting. Short. "Here's what I think we're discussing, here's the recommendation, here are the two questions I expect you might have." Forces a real introduction even if a live meeting isn't possible. 4. If I can't get to the economic buyer by the second meeting, I name it openly with my champion: "I'm not sure we have a path to your sponsor. What's our move?" The result, halfway through this year: — Close rate up 12 points. — Average sales cycle DOWN by 19 days. Counter-intuitive but real — confronting the gatekeeper question early kills slow deals, frees time for real ones. If you haven't reviewed your lost deals with one specific question — "did I ever actually meet the economic buyer?" — run the audit this week. One pattern. Nine deals. Steal the lesson, save the year.

Your demo is too good. That's why your deals stall. I'll defend this. I lost twelve months to this mistake. The pattern: I'd run a demo that showed everything. Every feature. Every workflow. Every integration. The prospect would say "this is amazing." Then the deal would stall for six weeks because they had "so much to think about." What I was actually doing: solving every possible objection in 45 minutes. The prospect left with no question urgent enough to keep the conversation moving. The shift my manager forced on me last year: 1. Show 30% of the product, deliberately. Pick the 2-3 capabilities that match the specific use case the prospect described in discovery. Skip the rest. 2. Hold back the best part. If there's a killer feature that everyone reacts to — show 5 seconds of it, then say "we'll go deeper on this in our next conversation. Most teams want to bring [X stakeholder] to that one." 3. End with a real question, not a CTA. "What concerns came up while watching this?" — not "what's next." The concern is the door to the second conversation. What changed: — Demos went from 45 minutes to 28. — Second meetings booked in the same week went from ~40% to ~70%. — Stalls dropped because the prospect left with a reason to keep talking. What's counterintuitive about this: — Showing less builds more conviction in the buyer. They feel curious instead of full. — The killer feature only lands when it's invited, not when it's volunteered. — Demos are the only part of sales where over-delivery hurts you. Most sales training tells you to "wow" prospects. Most prospects don't buy from being wowed. They buy from a path that keeps moving. If your demos consistently get praised and then go quiet, the praise is the problem. Show 30% next time. Hold the rest for the room with the buyer in it.

How I multi-thread a deal without annoying my champion. The exact phrasings I use. Every sales leader asks for it. Most reps fumble it. The mistake: asking your champion to "introduce you to other stakeholders" which sounds like an extraction — and feels like one. The reframe: position multi-threading as a service to your champion, not a request from you. Three scripts that work. 1. Surfacing the executive sponsor. Wrong: "Could you introduce me to your VP?" Right: "Most teams find that if their leadership hasn't been part of an early conversation, the final approval slows down. Would it be useful if I prepared a 15-minute briefing tailored to [VP]'s priorities? You'd join, I'd present, you stay in charge of the relationship." Why it works: gives the champion a reason that benefits them (faster approval). Positions me as supporting them, not bypassing them. 2. Getting the technical evaluator involved. Wrong: "Can I get connected to your IT team?" Right: "In rollouts like this, the technical team usually flags 2-3 questions late in the process if they weren't in early. Want me to send a one-page technical brief you can forward to your IT lead, with an offer of a 20-minute call if helpful? Saves you the work of being the middle person." Why it works: removes friction for the champion. They forward a doc, not a calendar invite. 3. Getting another department's buy-in. Wrong: "Who else needs to weigh in on this?" Right: "Have any other departments been affected by this problem? In cases like yours, we've often found that [marketing/finance/operations] runs into the same pain. Want me to draft a short note you could share with the right person on their team? Sometimes their input strengthens your case internally." Why it works: turns multi-threading into the champion building a stronger internal case for themselves. The pattern across all three: — Reason is for the champion's benefit, not yours. — You do the heavy lifting (briefing, doc, call prep). — The champion stays in control of the relationship. — The other stakeholder is positioned as adding to the case, not auditing it. Results from using these scripts for a year: — Champion friction has gone way down. Almost nobody has said no to one of these framings. — Average stakeholder count per closed deal: up from 2.3 to 4.1. — Stall rate at the executive-sign-off stage: down sharply. If you're hearing "my champion won't open doors," the issue is usually the ask, not the champion. Try one of these phrasings this week.

A prospect ghosted me for five weeks, then signed. Sharing the follow-up that worked. The deal was on track. Demo went well. Pricing conversation was constructive. Champion verbally committed to next steps. Then silence. I did the normal sequence: — Day 3: friendly check-in. No reply. — Day 7: value-add (sent a customer case study). No reply. — Day 14: another check-in. No reply. — Day 21: a "let me know if priorities shifted" note. No reply. At this point most reps either keep nudging or move on. I tried something different. Day 35, I sent a break-up email. Not the soft version. The honest one. The email, verbatim: "Hi [name], I haven't heard back from you in five weeks. That's fine — I know how these things go. I want to respect your time and stop landing in your inbox if this isn't moving. I'll assume you've deprioritized this unless I hear otherwise. If something changes in the next quarter or two, you have my contact. No pressure to reply to this either — silence works as the answer. One thing I genuinely want to say before I close this thread: when we talked about [specific problem they'd described], I thought you were sharper than most people I'd spoken with this year on it. If you ever want to compare notes on it whether or not you're buying anything, I'm always up for that conversation. Thanks for the time you did give me. [my name]" Reply landed within 6 hours. Her message: "This is the most honest email I've ever gotten from a sales rep. We had a re-org and your project got buried. I had no good way back into the conversation. Can we talk Thursday?" We signed the next month. What the email did right: — Released pressure. "Silence works as the answer" removes the obligation that's making the response feel impossible. — Specific, sincere compliment. Not flattery. Acknowledgment of something real. — Offered relationship without the deal. "Compare notes" reopens conversation without forcing commitment. — Short. No PS. No marketing materials attached. No "calendar link in case." What it didn't do: — Didn't apologize for following up. — Didn't ask for anything. — Didn't include a CTA. This works maybe 1 in 5 times. It still beats the "checking in" sequence that works maybe 1 in 50. If you've got prospects who've gone quiet, the break-up email — written honestly — is the highest-leverage follow-up you've got. Use it on the next three. Report back.

My exact mutual action plan template, and when I introduce it. Stealing welcomed. For years I treated mutual action plans (MAPs) as a sales-side artifact — I'd build one in my CRM, share it as a PDF, and watch it die. The buyer never engaged. What changed: introducing it as the buyer's tool, not mine. The template (one shared doc, editable by both sides): --- TITLE: [Buyer Company] + [Our Company] — Path to Decision --- **Decision target date**: [Specific date] **Decision owner on your side**: [Name + Role] **Decision owner on our side**: Me ([name]) **What does "yes" require?** [3-5 bullets — written together: what they need to be true to sign] **What does "no" look like?** [2-3 bullets — what they'd need to see for this to not be a fit] **Workstream A: Technical evaluation** — Owner: [their tech lead], me supporting — Key milestones: [list, with dates] **Workstream B: Business case** — Owner: [their champion] — Key milestones: [list, with dates] **Workstream C: Procurement and legal** — Owner: [their procurement contact] — Key milestones: [list, with dates] **Stakeholders we need to align** [Names, when they get involved, what their role in the decision is] **Risks to the timeline** [Both sides write what could blow this up] **Open questions** [Living section] --- end template --- When I introduce it: NOT in the first meeting. Most reps make this mistake. Introducing a MAP in discovery feels presumptuous to a buyer who hasn't decided to engage seriously. I introduce it after the second substantive meeting — typically post-demo, when both sides have decided this is worth exploring further. The pitch when I share it: "Here's a doc I find useful for keeping us both on track. It's not a contract or a commitment. It's just a working agreement on how we'll evaluate this and what 'done' looks like for both of us. I've filled in what I know. Could you take 15 minutes this week to fill in the rest of it from your side?" Why this works: — I've already started it. Less work for them. — Framed as their tool, not mine. — Asks for collaboration on a discrete task, not a commitment. — The "what does no look like" line is the most important — buyers respect that I want a clean no as much as a yes. What happens after: — Buyers who engage with the doc close at ~70%. — Buyers who don't engage with it (after one follow-up) are almost never going to close. Useful filtering signal. — My forecast accuracy jumped meaningfully once I started using this. Steal the template. The structure matters less than the timing — introducing it post-second-meeting and framing it as the buyer's tool changes everything. If yours isn't being used, it's the timing. Try this.

Five questions buyers wish AEs would stop asking. From actual buyer feedback I've collected. I interviewed 12 buyers — people I'd sold to, people I'd lost to, and a few who'd never bought from me — and asked them the same question: what's the sales rep question that makes you internally roll your eyes? The top five. 1. "What keeps you up at night?" Why it's dead: every buyer has heard it. It signals you've read a sales book but haven't done your homework. Buyers want specific, not generic. What to ask instead: "What's the project on your team's plate right now that you'd happily make disappear if you could?" 2. "How do you make decisions like this internally?" Why it's dead: buyers know you're scoping for the economic buyer. The question signals you don't yet trust them to surface decision-makers. What to ask instead: "Walk me through the last vendor decision your team made above [your ACV]. How did it actually move?" 3. "What's your budget?" Why it's dead: buyers find this question presumptuous early in the relationship. They also know the budget question is about you, not them. What to ask instead: "For projects like this, what range do you typically see internal pricing land in?" Lower-pressure, lets them stay generic if they want. 4. "Is there anything I haven't asked that I should have?" Why it's dead: it puts the burden on the buyer to do your job. Most buyers respond politely but disengage. What to ask instead: "If I were sitting in your seat, what would I want to know next?" Reframes the question as a perspective swap, not a confession of unpreparedness. 5. "Are you the decision-maker?" Why it's dead: it's almost always perceived as condescending, and the answer is often complicated ("sort of"). Either you've shown you understand their structure or you haven't. What to ask instead: nothing, in that exact form. Replace with workflow questions: "How does a recommendation like this typically move through your team toward a final yes?" The pattern across all five: — Generic questions reveal lazy preparation. — Specific, context-rich questions earn buyer respect. — Buyers don't mind hard questions. They mind tired ones. If you find yourself defaulting to any of these on Monday morning's calls, you'll feel the difference immediately by swapping in the alternatives. Buyers are scrolling LinkedIn. They notice which AEs are showing up sharper. Be one of those.

Buyers now research everything before our first call. My discovery had to change. Here's how. The old discovery model: I'd ask 15-20 questions to understand their situation. Pain points, current stack, team size, decision process, timeline. The problem in 2026: by the time a qualified buyer takes a sales call, they've already read 8-12 of our pages, watched 2 product videos, read 3 G2 reviews, and asked their network about us. They know more than they used to. Asking them to re-explain wastes the meeting. What I do now. Before the call: — I research them. Their company news, their LinkedIn activity, our analytics on who from their company has visited which pages. — I draft a 1-page "hypothesis" doc: what I think their situation is, what I think the pain points are, what I think our fit looks like. — I share that doc 24 hours before the call. "Here's what I think I know — let me know what's wrong before we meet." In the call: — Open with: "Based on what you've shared and what I've researched, here's where I think we are. Tell me where I'm wrong." — Spend the first 10 minutes letting them correct my model. Calibration, not interrogation. — Use the rest of the call for the questions only they can answer — internal dynamics, recent shifts, what's actually motivating the timeline. What changed: — Discovery is shorter. 30 minutes instead of 60. Buyers love this. — The questions I do ask are sharper. I'm not gathering information; I'm pressure-testing assumptions. — Conversion to second meeting is up. The pre-share doc proves I've done the work, which builds trust before the call even starts. What I avoid: — Asking "what does your current solution look like?" when their tech stack is public. — Asking "what's prompting you to look now?" when I've watched their pricing page traffic spike. — Asking "who else is involved in this decision?" when LinkedIn shows me three of their colleagues have viewed my profile in the last week. The shift in mindset: — Old: discovery is when buyers tell me what they need. — New: discovery is when I prove I've already done the homework, and buyers correct my model. The buyer who's done their research is not annoyed by the work. They're annoyed by AEs who ignore the work they've done. If your first calls still feel like interrogations, your discovery hasn't caught up to 2026. The pre-share doc + correction-first opening is the easiest fix. Test it on your next three discoveries.

Anatomy of my deal review prep. What I bring to my manager every Friday. Most AEs prepare for deal reviews defensively — anticipating what their manager will ask and rehearsing answers. I learned the hard way that this is the wrong frame. What I do instead: I bring my manager the prep that makes the conversation useful for me, not safe for me. The doc I send 24 hours before every weekly deal review. --- Header: This week's pipeline + asks --- **Top 3 deals — status and what I need** For each deal: — Account, stage, ACV. — What I think is true: "My read is this closes in October." — What I'm worried about: "My champion went quiet 8 days ago after a positive demo. I think there's a stakeholder I haven't met." — What I've already tried: "Sent a value-add yesterday. Drafted a break-up email but haven't sent." — What I want from my manager: "Help me think through whether I should send the break-up or pursue a different angle." **Pipeline health (the honest version)** — Current quarter coverage: [number] — Realistic close estimate based on stage progression: [number] — Gap to quota: [number] — What I think drives the gap (one of: not enough pipeline, low close rate, deals slipping, all three) **One pattern I noticed this week** — Either a recurring objection, a winning move, or something about my own approach that's worth surfacing. **One thing I want feedback on** — Specific. Not "how am I doing." Examples: "My discovery on enterprise deals feels rushed compared to mid-market. Want to listen to one and tell me what you'd change?" --- end of doc --- Why this works: — My manager comes to the review prepared. We don't spend 20 minutes loading her on context. — I lead with my honest assessment. She doesn't have to extract it. — The asks are specific. Coaching gets focused. — The "one pattern" forces me to reflect every week. That habit alone has been the biggest skill driver of the last year. What happened after I adopted this: — My manager started prepping similarly for her reviews with her director. — I got promoted within 9 months. Cited in the conversation: "You manage up better than anyone on my team." — My pipeline forecast accuracy is the best on the team. Not because I'm a better forecaster — because the weekly discipline forces honesty. The meta-lesson: Deal reviews are not for performance theater. They're for getting better. The AE who comes in honest and asks specific questions gets coached. The AE who comes in defensive gets managed. Most AEs spend reps prepping the wrong way. Steal the template above. Watch what changes.

AEs, low-stakes Friday question. What's the strangest reason you ever lost a deal? I'll go. A prospect ghosted after a near-verbal commitment. Three weeks of silence. I finally got him on the phone. His reason: our pricing page had a typo. "Inegrations" instead of "Integrations." Not the contract. The pricing page. He said, and I quote: "I figured if you couldn't get your own website right, I didn't trust you with my data." We lost it. To this day, I don't know if he was joking. I checked the page after the call. He was right — there was a typo. Had been there for months. He was the first prospect to mention it. We fixed it within an hour. Sent him a screenshot. Didn't reopen the deal. The lesson I half-take from it: every detail signals something. The marketing page is part of the sales experience. The lesson I mostly take from it: sometimes deals die for reasons you'll never predict, and the only thing to do is laugh and call the next prospect. Your turn. What's the weirdest loss you've ever taken? Reply with the story. I need to hear that I'm not alone in this.