<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Content &amp; Resources — Ascender Community</title>
        <link>https://forcemanagement.vanillacommunities.com/</link>
        <pubDate>Sat, 06 Jun 2026 07:47:08 +0000</pubDate>
        <language>en</language>
            <description>Content &amp; Resources — Ascender Community</description>
    <atom:link href="https://forcemanagement.vanillacommunities.com/categories/explore/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Your Tech Stack Is Getting Smarter — Are You Keeping Up?</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/909/your-tech-stack-is-getting-smarter-are-you-keeping-up</link>
        <pubDate>Wed, 25 Mar 2026 14:14:22 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">909@/discussions</guid>
        <description><![CDATA[<p>The modern sales tech stack isn’t static anymore. With AI layered into everything from call recording to forecasting to account research, the tools your company provides are evolving faster than most sellers realize. The gap today isn’t between teams that <em>have</em> technology and those that don’t — it’s between sellers who actively use it to sharpen their execution and those who fall back on old habits.</p><p>Top performers treat the tech stack as a competitive advantage. They use AI to prep for calls, capture insights, validate MEDDICC elements, and keep deals moving with precision. They don’t rely on memory or scattered notes. They let the tools do the heavy lifting so they can focus on thinking, questioning, and leading conversations.</p><p>If you’re not staying current with how your tools are evolving, you’re not just missing features — you’re missing efficiency, clarity, and coaching opportunities that your competitors may already be using.</p><p>Five things to do after reading this:</p><ol><li>Block 30 minutes this week to explore one tool you already have but underuse. Focus specifically on new AI-driven features that help with call summaries, deal insights, or next-step recommendations.</li><li>Use your conversation intelligence platform after every key call. Review how you handled discovery, what questions landed, and where you missed opportunities to go deeper.</li><li>Turn your CRM into a real-time deal strategy tool. Document Decision Process steps, stakeholder roles, and Paper Process milestones so you can manage deals proactively instead of reactively.</li><li>Ask your manager or a top performer how they are using the tech stack differently. Don’t assume you’re using tools the “right” way — learn how the best sellers are leveraging them.</li><li>Use AI tools to prepare before calls. Generate account insights, potential risks, and tailored questions so you show up more informed and more relevant every time.</li></ol><p>Technology won’t replace strong sellers, but it will amplify disciplined ones. The sellers who treat their tech stack as part of their daily workflow — not an afterthought — are the ones creating separation in today’s market.</p>]]>
        </description>
    </item>
    <item>
        <title>Follow Up Emails That Move Deals Forward</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/908/follow-up-emails-that-move-deals-forward</link>
        <pubDate>Wed, 25 Mar 2026 13:50:35 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">908@/discussions</guid>
        <description><![CDATA[<p>I used to treat follow up emails as a recap.</p><p>“Thanks for your time. Here’s what we covered. Let us know if you have questions.”</p><p>Technically correct. Completely ineffective.</p><p>Over time, I realized that the follow up email is not just a summary. It is a chance to reinforce value, confirm alignment, and guide what happens next. In a lot of deals, it is the only thing the broader buying group will actually read.</p><p>As a solutions engineer, I partner closely with sales on these. Sometimes I draft them. Sometimes I review them. Sometimes I just make sure we are being intentional about what we send.</p><p>The best follow ups are not long. They are clear, specific, and tied to what the customer cares about.</p><p>Here are the habits that have made the biggest difference for me.</p><h3 data-id="1-i-anchor-everything-to-their-problem">1. I Anchor Everything to Their Problem</h3><p>The first thing I try to do is bring the email back to why the conversation happened in the first place.</p><p>Not what we showed. Not how the product works.</p><p>Why it matters.</p><p>If the customer said they are struggling with onboarding new reps, I reference that directly. If they are dealing with inconsistent data, I call that out.</p><p>This reminds them that the conversation was about solving their problem, not just showing a product.</p><h3 data-id="2-i-reflect-their-words-not-mine">2. I Reflect Their Words, Not Mine</h3><p>One thing I have learned is that customers trust their own language more than yours.</p><p>If they described a challenge in a specific way, I reuse that language in the follow up. It shows that I was listening and it makes the message feel more relevant.</p><p>Instead of saying:<br />
“We help improve efficiency”</p><p>I will say:<br />
“You mentioned your team is spending too much time manually updating reports”</p><p>That level of specificity stands out.</p><h3 data-id="3-i-keep-it-short-but-structured">3. I Keep It Short but Structured</h3><p>Long emails do not get read.</p><p>I try to keep follow ups tight and easy to scan. Usually three parts:</p><ul><li>What we heard</li><li>What we showed and why it matters</li><li>What happens next</li></ul><p>No paragraphs that go on forever. No unnecessary detail. Just enough to reinforce the conversation and move things forward.</p><h3 data-id="4-i-make-the-next-step-clear-and-easy">4. I Make the Next Step Clear and Easy</h3><p>A follow up without a clear next step is just a summary.</p><p>I always try to include something concrete:</p><ul><li>A proposed meeting time</li><li>A specific action they agreed to</li><li>A question that requires a response</li></ul><p>Something like:<br />
“Based on our conversation, the next step would be to connect with your operations team. Does Tuesday or Thursday work?”</p><p>Clarity reduces friction. The easier it is to respond, the more likely they will.</p><h3 data-id="5-i-use-the-email-to-align-the-broader-team">5. I Use the Email to Align the Broader Team</h3><p>Not everyone is on every call.</p><p>A good follow up helps your champion share the story internally. That means writing it in a way that someone else can read and understand quickly.</p><p>I avoid internal jargon. I avoid over explaining the product. I focus on outcomes and impact.</p><p>If the email can be forwarded without explanation, it is doing its job.</p><h3 data-id="a-simple-template-i-use">A Simple Template I Use</h3><p></p><p>Hi [Name],</p><p>Thanks again for the time today.</p><p>You mentioned that [specific challenge in their words]. We focused on how you could [specific outcome tied to that challenge], especially around [key area discussed].</p><p>During the demo, we showed how you can:</p><ul><li>[Outcome 1 tied to their problem]</li><li>[Outcome 2 tied to their problem]</li></ul><p>Based on our conversation, it sounds like the next step would be [clear next step]. Does [specific time or option] work on your end?</p><p>Let me know if there is anyone else who should be included.</p><p>Thanks,<br />
[Your Name]</p><p></p><p>Follow up emails are simple, but they are not easy.</p><p>They require you to think clearly about what actually mattered in the conversation. They force you to prioritize what the customer cares about over what you want to say.</p><p>The good news is that when you get them right, they do a lot of work for you. They reinforce value, create alignment, and keep momentum going without another meeting.</p><p>That is time well spent.</p>]]>
        </description>
    </item>
    <item>
        <title>The Discipline Behind Trap-Setting Questions</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/906/the-discipline-behind-trap-setting-questions</link>
        <pubDate>Mon, 16 Mar 2026 12:17:45 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">906@/discussions</guid>
        <description><![CDATA[<p>Trap-setting questions are one of the most misunderstood skills in selling. Many sellers hear the phrase and assume it means trying to catch a prospect in a mistake or create a “gotcha” moment. That’s not the goal. When done well, trap-setting questions do something very different — they allow the customer to articulate the conditions that make your solution the better choice.</p><p>In other words, the trap is not for the customer. It’s for the competition.</p><p>Great trap questions are difficult to master because they require preparation, patience, and discipline in the conversation. The structure is simple: open the topic, set the trap by helping the buyer define what matters, and close the trap by confirming the implication. If done correctly, the buyer arrives at the conclusion themselves.</p><p>For example, instead of saying your solution is easier to implement, you might ask how important implementation time is to their business, what happens if it takes longer than expected, and how they plan to evaluate vendors on that factor. When the buyer defines the criteria, competitors who can’t meet that bar naturally fall behind.</p><p>The key is tone and intent. If the question feels manipulative, it breaks trust. If it feels like thoughtful exploration of the buyer’s priorities, it builds credibility.</p><p>Four things to do after reading this:</p><ol><li>Identify two competitive strengths your solution consistently has. Build trap questions around those areas by asking buyers how they plan to evaluate that capability.</li><li>Practice the three-step structure in discovery: open the topic, ask the defining question, then confirm the implication. For example: introduce the topic, ask how they evaluate it, and confirm what happens if a vendor falls short.</li><li>Write down three trap questions before your next discovery call. Preparation matters. The best sellers rarely improvise these in the moment.</li><li>After your call, review whether the customer defined the criteria themselves. If you were the one explaining why it mattered, you likely closed the trap too early.</li></ol><p>Trap questions work best when the buyer owns the logic. When they define what success looks like, the conversation stops being about convincing them and starts becoming about whether other vendors can keep up.</p>]]>
        </description>
    </item>
    <item>
        <title>Team Prep Before the Call</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/904/team-prep-before-the-call</link>
        <pubDate>Mon, 16 Mar 2026 12:15:55 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">904@/discussions</guid>
        <description><![CDATA[<p>Some of the most important work I do as a solutions engineer happens before the customer ever joins the meeting.</p><p>The pre-call with the salesperson is where we align on the situation, pressure test the plan, and make sure we are walking into the conversation with purpose. When that step gets skipped or rushed, it almost always shows up during the customer call.</p><p>I have worked with a lot of excellent salespeople over the years, and the best ones treat the pre-call as a strategy session, not a calendar obligation. They know that a little preparation upfront can completely change the quality of the conversation.</p><p>At the same time, I do not expect salespeople to show up with everything figured out. Part of my role is to ask the right questions so we are both clear on what we are walking into.</p><p>Here are a few habits that make those pre-call conversations productive.</p><h3 data-id="1-i-always-start-with-the-goal-of-the-call">1. I Always Start With the Goal of the Call</h3><p>The first thing I ask is simple.</p><p>“What does a successful call look like to you?”</p><p>Not the agenda. Not the product we plan to show. The outcome.</p><p>Do we want agreement on the problem? Do we want to secure a deeper technical session? Are we trying to validate whether the deal is even real?</p><p>If we cannot clearly articulate the goal of the call, the conversation will drift. When both the salesperson and I are aligned on the outcome, it becomes much easier to decide what we show, what we skip, and how we manage time.</p><p>The best salespeople usually answer this question quickly and confidently.</p><h3 data-id="2-i-ask-what-we-already-know-about-the-problem">2. I Ask What We Already Know About the Problem</h3><p>Experienced sellers usually come in with a good understanding of the customer’s situation. My job is to make sure I fully understand it too.</p><p>I will ask things like:</p><ul><li>What is the problem they are trying to solve?</li><li>How is it affecting the business today?</li><li>What have they already tried?</li></ul><p>This helps me shape how I frame the demo or technical conversation. If I understand the pain clearly, I can connect what I show directly to their reality.</p><p>Good salespeople usually have a story here. They are not just saying the customer is “interested.” They can explain why the conversation started in the first place.</p><h3 data-id="3-i-ask-who-will-be-in-the-room">3. I Ask Who Will Be in the Room</h3><p>This question changes how I approach almost everything.</p><p>If the audience is mostly operators, I may go deeper into workflow. If there is a technical evaluator, I may spend more time on architecture. If a senior leader is attending, I may simplify and focus on business impact.</p><p>The best salespeople come into the pre-call already knowing who will attend and what role they play in the decision.</p><p>If that information is unclear, we talk about how to handle it gracefully once the call begins.</p><h3 data-id="4-i-clarify-what-i-should-not-do">4. I Clarify What I Should Not Do</h3><p>This one is underrated.</p><p>Sometimes there are landmines in a deal. Maybe the customer had a bad experience with a competitor. Maybe pricing conversations are sensitive right now. Maybe there is internal politics we need to be aware of.</p><p>I always ask if there is anything I should avoid or handle carefully.</p><p>Experienced salespeople are usually very helpful here. They will say something like, “Let’s avoid going deep into X today” or “This person is skeptical, so we should address Y early.”</p><p>Those insights can completely change how I structure the conversation.</p><h3 data-id="5-i-ask-how-we-want-to-divide-the-conversation">5. I Ask How We Want to Divide the Conversation</h3><p>The last thing we align on is who will lead different parts of the call.</p><p>Some salespeople prefer to run the meeting and pull me in for specific sections. Others like me to lead the product discussion while they manage the broader conversation.</p><p>Neither approach is right or wrong. What matters is that we agree ahead of time.</p><p>The worst situation is when both of us assume the other person is going to take the lead.</p><p>After doing this for a while, you start to develop rhythm with the salespeople you work with. The best partnerships feel almost effortless during the call because the preparation work already happened.</p><p>A strong pre-call is not about perfection. It is about alignment.</p><p>When the salesperson and the solutions engineer walk into the conversation with the same understanding of the situation, the call feels focused, confident, and purposeful. And from the customer’s perspective, that coordination builds trust quickly.</p>]]>
        </description>
    </item>
    <item>
        <title>Discovery doesn’t end just because the deal&#39;s moving forward</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/903/discovery-doesn-t-end-just-because-the-deals-moving-forward</link>
        <pubDate>Wed, 11 Mar 2026 00:42:45 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">903@/discussions</guid>
        <description><![CDATA[<p>One of the habits I have built over time as a solutions engineer is this simple idea. Discovery never really stops.</p><p>That does not mean I am constantly peppering a customer with discovery questions late in a deal cycle. By the time we are deep into evaluation, a lot of the foundational discovery should already be known. We should understand the problem, the stakeholders, the desired outcomes, and the risks of doing nothing.</p><p>But deals are living things. New people join. Priorities shift. Internal politics surface. Technical concerns appear that were not visible earlier.</p><p>When those things happen, I give myself permission to pause and treat the moment like discovery again.</p><p>That pause has saved several deals for me over the years.</p><p>It is easy to get locked into execution mode late in a cycle. You are preparing demos, aligning security reviews, answering technical questions, and trying to keep momentum going. When something unexpected shows up, the instinct is often to push through it instead of stepping back.</p><p>I have learned that pushing through is usually the wrong move.</p><p>Here are a few ways I keep discovery alive without turning every conversation back into an interrogation.</p><h3 data-id="1-i-watch-for-signals-that-something-changed">1. I Watch for Signals That Something Changed</h3><p>Late stage discovery usually starts with noticing a signal.</p><p>A new stakeholder shows up and asks basic questions. A champion suddenly becomes less responsive. A technical objection appears that was not mentioned before.</p><p>Those are clues.</p><p>Instead of immediately defending the solution, I slow down and ask questions that help me understand what changed.</p><p>For example:<br />
“What prompted that concern?”<br />
“Is this something your team has run into before?”<br />
“Who else is thinking about this internally?”</p><p>These are not early stage discovery questions. They are situational discovery questions that help me recalibrate the deal.</p><h3 data-id="2-i-reconfirm-the-original-problem">2. I Reconfirm the Original Problem</h3><p>Deals can drift.</p><p>Weeks into a process, conversations can become dominated by features, integrations, or procurement details. The original problem that started the evaluation can fade into the background.</p><p>When I sense that happening, I bring the conversation back to the starting point.</p><p>I might say something like:<br />
“Earlier in the process you mentioned that your team was struggling with X. Is that still the biggest priority?”</p><p>This does two things. It keeps the deal grounded in business value and it gives the customer a chance to tell me if priorities have changed.</p><h3 data-id="3-i-treat-new-stakeholders-like-a-discovery-moment">3. I Treat New Stakeholders Like a Discovery Moment</h3><p>Late stage deals almost always involve new voices. A finance leader, a security reviewer, a VP who wants to understand the decision.</p><p>I do not assume those people share the same context as the original champion.</p><p>When a new stakeholder joins, I reset slightly. I ask them how they view the problem and what matters most to them in the decision.</p><p>Not a full discovery session, but enough to understand their perspective.</p><p>Too many deals stall because a new stakeholder never actually bought into the original problem.</p><h3 data-id="4-i-ask-clarifying-questions-when-objections-appear">4. I Ask Clarifying Questions When Objections Appear</h3><p>Technical sellers often jump straight into solving objections.</p><p>I try to resist that.</p><p>If someone raises a concern, my first move is usually to understand the context behind it.</p><p>Questions like:<br />
“What specifically makes that a concern for your team?”<br />
“Have you run into this issue with other vendors?”<br />
“What would a comfortable solution look like?”</p><p>Those answers often reveal that the objection is not exactly what it seemed on the surface.</p><h3 data-id="5-i-create-small-moments-to-revalidate-alignment">5. I Create Small Moments to Revalidate Alignment</h3><p>Every few calls, especially in longer deals, I take a moment to check alignment.</p><p>I might say:<br />
“Just to make sure we are still on track, does this evaluation still feel aligned with what your team needs to solve?”</p><p>That question sounds simple, but it invites honesty.</p><p>If something has shifted internally, this gives the customer space to say it.</p><p>Discovery is often taught as the early phase of a sales cycle. In reality, it is more like a thread that runs through the entire deal.</p><p>You do the heavy lifting early. But you stay curious enough to revisit it when the situation calls for it.</p><p>For me, the key is balance. I do not want to drag a late stage deal backward with unnecessary questions. But I also do not want to miss the moment when the deal quietly changes.</p><p>Good solutions engineers stay technically sharp. Great ones stay curious all the way to the finish line.</p>]]>
        </description>
    </item>
    <item>
        <title>Your Pipeline Is a Strategy Document, Not Just a List of Deals</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/902/your-pipeline-is-a-strategy-document-not-just-a-list-of-deals</link>
        <pubDate>Wed, 11 Mar 2026 00:39:05 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">902@/discussions</guid>
        <description><![CDATA[<p>Most sellers look at their pipeline as a list of opportunities. Leadership looks at it as a forecast. But the best sellers treat their pipeline as a strategy document — a real-time reflection of where deals stand, what risks exist, and where to focus their time.</p><p>In today’s sales environment, pipeline quality matters more than pipeline size. Buyers are cautious, decision processes are longer, and deals that look healthy can stall quickly if key elements are missing. That’s why disciplined pipeline assessment is one of the most important habits a seller can develop.</p><p>Assessing pipeline isn’t about optimism. It’s about clarity. If you know where your deals truly stand, you can spend your time advancing the ones that can move and repairing the ones that are at risk.</p><p>Four things to do after reading this:</p><ol><li><strong>Score your top deals using clear criteria.</strong> Look at whether you have confirmed business impact, access to a real decision maker, a defined buying process, and a realistic timeline. If any of those are unclear, the deal is riskier than it appears.</li><li><strong>Identify stalled opportunities.</strong> Review deals that have not moved stages or had meaningful engagement in the last 30 days. Decide whether to re-engage with a clear next step or remove them from your working pipeline.</li><li><strong>Validate the next customer action in every deal.</strong> A healthy opportunity always has a defined next meeting, deliverable, or milestone owned by both sides. If the next step is vague, the deal will drift.</li><li><strong>Prioritize deals that have momentum.</strong> Instead of spreading time evenly across every opportunity, focus your effort where customer urgency, stakeholder engagement, and decision clarity already exist.</li></ol><p>A strong pipeline isn’t about having the most opportunities. It’s about knowing which opportunities are real, which are risky, and where your effort will make the biggest difference. The sellers who win consistently don’t just build pipeline — they inspect it and manage it with discipline.</p>]]>
        </description>
    </item>
    <item>
        <title>People want to help, but need to know what you want</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/900/people-want-to-help-but-need-to-know-what-you-want</link>
        <pubDate>Wed, 04 Mar 2026 17:14:50 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">900@/discussions</guid>
        <description><![CDATA[<p>For a long time, I assumed that if I worked hard enough, people would just “notice.”</p><p>They would see my effort. They would recognize my ambition. They would connect the dots and think I'm ready for more.</p><p>That is not how it works.</p><p>Most managers are busy. Most peers are focused on their own goals. And most leaders are not mind readers. I learned that if I want help moving toward something in my career, I have to say it clearly.</p><p>People generally want to help. They like opening doors. They like mentoring. They like making introductions. But they cannot help you move toward something they do not know you want.</p><p>Over the past few years, I have gotten much more intentional about sharing my career intentions. Not in a dramatic way. Not in a way that sounds entitled. Just clearly and consistently.</p><p>Here is how I approach it.</p><h3 data-id="1-i-get-specific-about-what-i-actually-want">1. I Get Specific About What I Actually Want</h3><p>Saying “I want to grow” is meaningless.</p><p>Grow into what?</p><p>Do you want to manage people? Move into enterprise sales? Become a solutions leader? Lead enablement? Take on a bigger territory?</p><p>Before I talk to anyone else, I force myself to write it down. What role am I aiming toward? What skills do I need? What gaps do I have?</p><p>Clarity makes the conversation productive. Vague ambition just creates vague encouragement.</p><h3 data-id="2-i-tell-my-manager-directly-and-early">2. I Tell My Manager Directly and Early</h3><p>I do not wait for annual reviews.</p><p>When I have a sense of where I want to head, I schedule time with my manager and say something simple and direct.</p><p>“I want to work toward an enterprise role.”<br />
“I am interested in leadership in the next few years.”<br />
“I would like to be considered for bigger strategic accounts.”</p><p>Then I ask, “What would I need to demonstrate for you to feel confident recommending me?”</p><p>That question changes everything. It turns the conversation from dreaming into a performance plan.</p><h3 data-id="3-i-share-my-intentions-with-peers-too">3. I Share My Intentions with Peers Too</h3><p>This part is underrated.</p><p>Your peers hear about opportunities before you do. They get pulled into projects. They are asked for referrals. They are invited into conversations.</p><p>If they know what you are aiming for, they can pull you in.</p><p>I have had peers say, “Hey, you mentioned wanting more exposure to executive calls. Do you want to join this one?” That only happens if they know your goals.</p><p>This is not about competition. It is about alignment. The more people who understand where you are headed, the more likely someone connects you to the right opportunity.</p><h3 data-id="4-i-ask-for-targeted-exposure-not-promotions">4. I Ask for Targeted Exposure, Not Promotions</h3><p>Instead of saying, “I want the next job,” I ask for experiences that build toward it.</p><p>If I want to move upmarket, I ask to shadow complex deal strategy sessions. If I want leadership, I ask to mentor new hires. If I want cross functional visibility, I volunteer for internal projects.</p><p>This does two things. It builds credibility and it reduces risk for decision makers. They can see me operating at the next level before giving me the title.</p><p>People are much more willing to support growth when it feels earned and observable.</p><h3 data-id="5-i-revisit-the-conversation-regularly">5. I Revisit the Conversation Regularly</h3><p>Career conversations are not one and done.</p><p>I check back in. I ask for feedback on progress. I ask if priorities have shifted. I ask what else I should be working on.</p><p>That follow up signals seriousness. It shows that I am not just casually interested. I am committed.</p><p>It also keeps me accountable. If I said I wanted to grow into something but I am not putting in the work, that becomes obvious quickly.</p><p>Here is the truth. Silence does not equal strategy.</p><p>If you are quietly hoping someone notices your potential, you are leaving your career to chance. When you articulate your intentions, you invite people into your growth.</p><p>Most leaders want to develop talent. Most peers are happy to help. But they need direction.</p><p>If you know where you want to go, say it out loud. You might be surprised how many doors start to open once people understand what you are walking toward.</p>]]>
        </description>
    </item>
    <item>
        <title>Your Tech Stack is Your Advantage</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/899/your-tech-stack-is-your-advantage</link>
        <pubDate>Wed, 04 Mar 2026 17:10:31 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">899@/discussions</guid>
        <description><![CDATA[<p>Most sales teams today have more technology than ever. Conversation intelligence. CRM dashboards. Mutual action plan tools. Forecasting platforms. Internal collaboration channels. The irony is that the reps who win the most are rarely the ones asking for more tools. They are the ones who squeeze value out of the tools already sitting in front of them.</p><p>Technology is not there to impress leadership. It is there to sharpen your execution. If you are not using it to capture talking points, track Decision Process steps, validate MEDDICC elements, and coach yourself between deal reviews, you are leaving leverage on the table.</p><p>In this environment, deals stall quietly. Stakeholders disappear. Paper Processes drag. The reps who stay in control use their tools to reduce guesswork. They document in real time. They review their own calls. They enter deal reviews prepared with data instead of opinions.</p><p>Five things to do after reading this:</p><ol><li>Start reviewing one recorded call per week on your own. Specifically listen for how you handled Metrics, Decision Criteria, and next steps. Write down one improvement and apply it to your next call.</li><li>Use your CRM as a deal command center, not an admin chore. Fully document Decision Process steps, timeline, approvals required, and procurement milestones. If someone asked you to walk through the Paper Process today, you should not hesitate.</li><li>Build a simple deal summary template in your notes tool. After every key call, capture business pain, quantified impact, stakeholders involved, and risks. Share that summary with your manager before pipeline reviews.</li><li>Use mutual action plan software or even a shared document to keep deals on track. Confirm dates, owners, and dependencies with the customer. Technology only works if it is visible to both sides.</li><li>Invite your manager to coach you inside the tools. Instead of vague feedback, ask them to comment directly on a recorded call or in your deal notes. Make it easy for them to help you.</li></ol><p>Technology does not close deals. But disciplined use of technology creates clarity. And clarity creates momentum. If you treat your tools as a performance system instead of an obligation, you will separate yourself from the reps who are still relying on memory and optimism.</p>]]>
        </description>
    </item>
    <item>
        <title>It shouldn&#39;t sound ALL good.</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/897/it-shouldnt-sound-all-good</link>
        <pubDate>Wed, 25 Feb 2026 18:21:18 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">897@/discussions</guid>
        <description><![CDATA[<p>When I leave a call and the prospect says, “This looks great.” “We love it.” “This is exactly what we need.” I don’t relax, but I instead get curious and cautious.</p><p>Not because I enjoy being skeptical. Not because I assume the worst. But because in real buying cycles, meaningful change usually creates friction. It raises concerns. It surfaces risk. If I am not hearing any of that, I have learned the hard way that something might be hiding under the surface.</p><p>Early in my career, I equated positive feedback with deal health. If the customer smiled and complimented the solution, I mentally moved the deal forward. Then weeks later, it would stall. Or go dark. Or end with “We decided to stay with our current approach.”</p><p>Now, when I only hear good things, I slow down and scrutinize the feedback more carefully.</p><p>Here is how I approach it.</p><h3 data-id="1-i-separate-politeness-from-commitment">1. I Separate Politeness from Commitment</h3><p>People are polite. Especially in professional settings.</p><p>“This is really impressive” does not mean “We are going to buy.”</p><p>So I ask myself, what did they actually commit to? Did they agree to a next step with a date on the calendar? Did they introduce me to an economic buyer? Did they share internal hurdles?</p><p>If the feedback is positive but there are no concrete commitments attached, I treat it as neutral, not strong.</p><p>One simple habit that helps is asking, “What specifically resonated with you?” If they cannot articulate impact in their own words, the praise may be surface level.</p><h3 data-id="2-i-look-for-the-missing-objection">2. I Look for the Missing Objection</h3><p>Every real purchase has risk.</p><p>Budget risk. Career risk. Implementation risk. Political risk.</p><p>If none of those come up, I assume I have not earned enough trust yet.</p><p>Instead of celebrating smooth calls, I will follow up with questions like:<br />
“What concerns would someone else on your team raise about this?”<br />
“If this were to get stuck internally, where would it get stuck?”<br />
“What would make this a no?”</p><p>Those questions often unlock the real conversation. And I would much rather deal with a tough objection now than a silent no later.</p><h3 data-id="3-i-reevaluate-my-discovery">3. I Reevaluate My Discovery</h3><p>When feedback is overly positive, I revisit my notes.</p><p>Did I really uncover pain? Or did I stay high level? Did they quantify the problem? Did we tie the solution to a measurable outcome?</p><p>If I cannot clearly explain the business impact in their language, I know the deal is not as strong as it sounds.</p><p>Positive reactions to a demo are easy to get. Agreement around a defined business problem is harder and more important.</p><h3 data-id="4-i-validate-urgency-not-just-interest">4. I Validate Urgency, Not Just Interest</h3><p>Interest feels good. Urgency closes deals.</p><p>So I ask direct questions about priority:<br />
“Where does this rank compared to your other initiatives this quarter?”<br />
“What happens if you do nothing?”<br />
“Why now?”</p><p>If the answers are vague, the deal is likely not real yet. I do not push aggressively, but I do push for clarity. Clear urgency creates momentum. General enthusiasm does not.</p><h3 data-id="5-i-pressure-test-internally-before-i-forecast">5. I Pressure Test Internally Before I Forecast</h3><p>Before I move a deal forward in my pipeline, I challenge it myself.</p><p>If I had to argue why this deal will not close, what would I say? Is there a clear champion? Is there budget identified? Do I know the decision process? Has anyone pushed back meaningfully?</p><p>If the only signal I have is positive sentiment, I downgrade my confidence.</p><p>It is easy to be optimistic when people are complimenting your work. It is harder to be disciplined and look for evidence.</p><p>Over time, I have learned that healthy deals feel a little uncomfortable. They involve tough questions. They force both sides to think. They surface concerns that need to be worked through.</p><p>If I am only hearing good things, I assume I still have work to do. We need to uncover the real objections in conversation and discover them before a deal quietly slips away.</p>]]>
        </description>
    </item>
    <item>
        <title>Share your wins and teach others</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/896/share-your-wins-and-teach-others</link>
        <pubDate>Wed, 25 Feb 2026 18:18:48 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">896@/discussions</guid>
        <description><![CDATA[<p>A lot of sellers are quietly proud. They close a complex deal, navigate procurement, multithread a tough account, get real Economic Buyer access, and then move straight to the next opportunity. No post, internal recap, or breakdown of what actually worked. It's not that you don't want to share what you've learned or that you're being modest, but it's easy to move on to the next thing. We're trained to do it!</p><p>Sharing wins publicly is not about ego. It’s about leverage. When you explain how you quantified Metrics, how you mapped the Decision Process, or how you got ahead of the Paper Process before legal slowed things down, you’re giving your team a blueprint. You’re also reinforcing your own credibility internally and externally.</p><p>The sellers who consistently grow their careers do two things well: they execute and they communicate. Sharing wins positions you as someone who understands the craft. It shows pattern recognition. It builds trust with leadership. And externally, it builds brand equity with prospects who are watching how you operate.</p><p>The key is this: share the process, not just the outcome.</p><p>Four things you can do to take action:</p><ol><li>Post one internal win recap this month. Focus on what worked operationally. Explain how you gained Economic Buyer access, how you confirmed the Decision Criteria, or how you managed the Paper Process timeline. Keep it instructional, not celebratory.</li><li>Create a simple win template for yourself. Include the problem, the Metrics, the turning point in the deal, and one lesson learned. Use it consistently so sharing becomes a habit, not a production.</li><li>Tag your cross-functional partners. Call out your SE, your manager, legal, or customer success. That shifts the tone from bragging to recognition and builds political capital.</li><li>Share one external LinkedIn post per quarter that focuses on customer impact. Talk about the business outcome achieved, not the contract value. Make it about the customer’s success, not your quota.</li></ol><p>Silence doesn’t equal humility. It often equals missed opportunity. When you share wins thoughtfully, you help your team improve, you reinforce disciplined selling behaviors, and you quietly build your reputation as someone who knows how to win the right way.</p>]]>
        </description>
    </item>
    <item>
        <title>How and why I roleplay</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/892/how-and-why-i-roleplay</link>
        <pubDate>Tue, 17 Feb 2026 23:29:04 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">892@/discussions</guid>
        <description><![CDATA[<p>Now that I’m back in a quota-carrying role, I’ve made roleplay a regular part of my prep. Not as a box to check. Not as a team exercise that goes nowhere. But as a deliberate way to sharpen conversations before they matter.</p><p>The difference between average and excellent performance in sales is rarely knowledge. It’s execution under pressure. Roleplay is where I pressure-test that execution.</p><p>Here’s how I approach it.</p><h3 data-id="1-i-never-wing-a-roleplay-i-set-a-clear-scenario">1. I Never “Wing” a Roleplay — I Set a Clear Scenario</h3><p>Bad roleplay sounds like this:</p><blockquote><div><p>“Okay, pretend I’m the customer.”</p></div></blockquote><p>Good roleplay starts with context:</p><ul><li>What stage is the deal in?</li><li>Who is on the call?</li><li>What objection is likely coming?</li><li>What outcome are we trying to drive?</li></ul><p>If I’m preparing for a CFO call, I’ll define:</p><ul><li>They’re skeptical about budget.</li><li>They’ve been burned by a vendor before.</li><li>They have 20 minutes.</li><li>The goal is agreement on evaluation criteria.</li></ul><p>Clarity makes the roleplay real. Without structure, it turns into generic back-and-forth that doesn’t translate to real conversations.</p><h3 data-id="2-i-roleplay-the-hardest-part-not-the-easiest-part">2. I Roleplay the Hardest Part — Not the Easiest Part</h3><p>It’s tempting to practice the polished demo section.</p><p>That’s not where deals break.</p><p>I focus on:</p><ul><li>The first 3 minutes of the call</li><li>The pricing conversation</li><li>The objection I’m hoping doesn’t come up</li><li>The close</li></ul><p>If something makes me slightly uncomfortable to rehearse, that’s probably what I need to practice.</p><p>Comfort doesn’t need rehearsal. Pressure does.</p><h3 data-id="3-i-ask-for-brutally-specific-feedback">3. I Ask for Brutally Specific Feedback</h3><p>After roleplay, I don’t ask:</p><blockquote><div><p>“How was that?”</p></div></blockquote><p>I ask:</p><ul><li>Where did I lose confidence?</li><li>What sounded unclear?</li><li>Did I actually answer the objection?</li><li>Where did I talk too long?</li></ul><p>And I want specifics. Not “that was good.” Not “maybe tighten that up.” Specific language feedback.</p><p>This is especially important when roleplaying with sales partners. If we’re going to sharpen together, we have to be honest with each other.</p><h3 data-id="4-i-use-ai-to-stress-test-objections">4. I Use AI to Stress-Test Objections</h3><p>AI has become one of my favorite roleplay partners.</p><p>I’ll prompt it with:</p><ul><li>The persona (CFO, VP Sales, IT Director)</li><li>The context of the deal</li><li>The likely concerns</li><li>The tone (skeptical, rushed, aggressive)</li></ul><p>Then I ask it to:</p><ul><li>Push back hard</li><li>Interrupt</li><li>Challenge assumptions</li><li>Ask follow-up questions</li></ul><p>What I like about AI is that it doesn’t get tired of being difficult. I can run the same objection five different ways until my answer becomes natural instead of memorized.</p><p>But here’s the key: I don’t memorize AI-generated responses. I use it to refine my own thinking. If I can’t explain something in my own words, I’m not ready.</p><h3 data-id="5-i-record-myself-and-watch-it-back">5. I Record Myself and Watch It Back</h3><p>This is the uncomfortable one.</p><p>Occasionally, I record my side of the roleplay. Not for perfection — for awareness.</p><p>I look for:</p><ul><li>Rambling</li><li>Filler language</li><li>Defensive tone</li><li>Over-explaining</li><li>Missed pauses</li></ul><p>The camera doesn’t lie. Neither does playback.</p><p>Most of us think we’re clearer than we are. Watching yourself once will change how you communicate permanently.</p><p>Roleplay isn’t about pretending. It’s about preparing.</p><p>Customers don’t care how knowledgeable you are. They care how you respond in the moment. They care how you handle tension. They care whether you can think clearly when challenged.</p><p>That clarity doesn’t magically appear in a live call.</p><p>It’s built in practice.</p><p>If you’re carrying a quota and not roleplaying — especially the uncomfortable parts — you’re choosing to rehearse in front of the customer.</p><p>I’d rather do the hard work beforehand.</p>]]>
        </description>
    </item>
    <item>
        <title>Are Your Sales Goals Still Real or Just Written Down?</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/890/are-your-sales-goals-still-real-or-just-written-down</link>
        <pubDate>Tue, 17 Feb 2026 22:52:26 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">890@/discussions</guid>
        <description><![CDATA[<p>At the start of the year, most of us set ambitious goals. Presidents Club. Pipeline coverage. New logo count. Better MEDDICC discipline. Stronger access to Economic Buyers. Cleaner forecasts. Then the year gets loud. Deals slip. Priorities shift. A reorg happens. The market tightens. And suddenly we’re running hard without asking a simple question:</p><p>Are my daily actions still aligned with the goals I said mattered?</p><p>Checking in on your goals isn’t about motivation. It’s about math and behavior. In today’s sales environment, the sellers who win are the ones who recalibrate early — not the ones who hope Q4 saves them.</p><p>If you committed to hitting a revenue number, building pipeline, or tightening qualification standards, now is the time to pressure test it. Not emotionally. Operationally.</p><p>Four things to do after reading this:</p><ol><li>Recalculate your path to goal using real numbers. If your quota is $1.2M and you’ve closed $350K, what must close in the remaining months? What pipeline coverage do you need assuming your actual win rate — not the optimistic one? Write it out.</li><li>Audit your top 15 deals for true MEDDICC depth. Specifically validate Metrics, Economic Buyer access, and Decision Process clarity. If you can’t clearly articulate the Paper Process and procurement path, your forecast is inflated.</li><li>Track leading indicators for 30 days. Instead of obsessing over revenue, measure daily behaviors: new meetings booked, discovery depth, multithreading, access to power. Club-level results are built on controllable inputs.</li><li>Identify one goal you need to adjust — either up or down — and reset it publicly with your manager. Stubbornly holding onto an outdated plan is not discipline. Smart recalibration is.</li></ol><p>Goals are not New Year’s resolutions. They are operating targets. The sellers who consistently win don’t wait until the end of the year to see if it worked. They check the dashboard, adjust the steering wheel, and keep driving with intention.</p>]]>
        </description>
    </item>
    <item>
        <title>Settling in at a new organization without pretending I have everything figured out.</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/888/settling-in-at-a-new-organization-without-pretending-i-have-everything-figured-out</link>
        <pubDate>Wed, 11 Feb 2026 18:05:28 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">888@/discussions</guid>
        <description><![CDATA[<p>Starting at a new organization is humbling. New acronyms. New systems. New personalities. New expectations. And if you’re in a revenue carrying roll, there's a new quota.</p><p>I recently stepped into a new role, and while it’s exciting, I’ve been very intentional about how I’m settling in. I don’t want to rush the process. I also don’t want to drift for six months claiming I’m “still onboarding.”</p><p>There’s a balance between learning the ropes and earning trust. Here’s what I’ve been doing to get grounded and build allies early.</p><h3 data-id="1-schedule-30-45-minute-working-1-1s-not-intro-chats">1. Schedule 30–45 Minute “Working” 1:1s, Not Intro Chats</h3><p>Early on, it’s easy to have surface-level intro calls. I’ve tried to turn most of mine into working sessions.</p><p>Instead of:</p><blockquote><div><p>“Tell me about your role.”</p></div></blockquote><p>I ask:</p><ul><li>What are the biggest blockers you’re facing this quarter?</li><li>Where does my role intersect with yours?</li><li>What does “great” look like from your side?</li></ul><p>Then I follow up by actually doing something helpful. Whether it’s sharing notes, offering context, or helping move a deal forward, I want the interaction to produce value — not just familiarity.</p><p>Allies are built through contribution, not conversation.</p><h3 data-id="2-learn-the-informal-power-structure">2. Learn the Informal Power Structure</h3><p>Org charts don’t tell the full story.</p><p>In every company, there are people who:</p><ul><li>Influence decisions behind the scenes</li><li>Know how things <em>really</em> get done</li><li>Carry trust across teams</li></ul><p>I’m paying attention to who others defer to in meetings. Who gets asked for validation? Who calms tension?</p><p>Building alignment with those individuals early makes navigating the organization far easier.</p><h3 data-id="3-document-what-you-re-learning-so-you-don-t-ask-the-same-question-twice">3. Document What You’re Learning (So You Don’t Ask the Same Question Twice)</h3><p>Nothing erodes credibility faster than asking the same question repeatedly.</p><p>I keep a running document:</p><ul><li>Key terminology</li><li>Internal processes</li><li>Stakeholder preferences</li><li>Political nuances</li><li>What has worked (and what hasn’t) historically</li></ul><p>This does two things:</p><ol><li>It accelerates my ramp.</li><li>It shows respect for people’s time.</li></ol><p>If I do ask a follow-up question, it’s more refined and thoughtful.</p><h3 data-id="4-volunteer-for-small-visible-wins">4. Volunteer for Small, Visible Wins</h3><p>In a new role, you don’t need to own the biggest initiative immediately. You need to build trust.</p><p>I’ve been intentionally looking for:</p><ul><li>A deal I can support</li><li>A process I can improve slightly</li><li>A piece of messaging I can tighten up</li><li>A prep call I can help sharpen</li></ul><p>Small wins compound. They show competence without overpromising.</p><h3 data-id="5-be-transparent-about-what-you-don-t-know">5. Be Transparent About What You Don’t Know</h3><p>There’s pressure to show up polished. I’ve tried to resist that.</p><p>When I don’t know something, I say it clearly:</p><blockquote><div><p>“I’m still learning how we approach that here.”</p></div></blockquote><p>Then I ask:</p><ul><li>How have you handled it historically?</li><li>What’s worked best?</li><li>Where have we struggled?</li></ul><p>People are far more willing to help someone who is honest than someone pretending to have instant mastery.</p><h3 data-id="6-align-with-leadership-on-what-success-looks-like-in-90-days">6. Align With Leadership on What Success Looks Like in 90 Days</h3><p>Early ambiguity creates long-term frustration.</p><p>I’ve had direct conversations about:</p><ul><li>What results matter most in my first quarter</li><li>What behaviors leadership values</li><li>Where they expect me to challenge the status quo — and where they don’t</li></ul><p>Clarity removes unnecessary anxiety. It also keeps me focused on impact, not activity.</p><p>Settling into a new organization isn’t about impressing everyone immediately. It’s about building credibility deliberately.</p><p>You don’t need to dominate your first 30 days. You need to:</p><ul><li>Listen well</li><li>Add value consistently</li><li>Build trust intentionally</li><li>Learn faster than you talk</li></ul><p>That’s how you turn “new person energy” into long-term influence.</p><p>And if you’re in a new role right now, remember that ramping well is a skill. Treat it like one.</p>]]>
        </description>
    </item>
    <item>
        <title>Presidents Club Is Built in the Margins: What Top Sellers Do Differently</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/886/presidents-club-is-built-in-the-margins-what-top-sellers-do-differently</link>
        <pubDate>Wed, 11 Feb 2026 18:01:45 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">886@/discussions</guid>
        <description><![CDATA[<p>Every year, Presidents Club looks glamorous from the outside. The trip. The recognition. The leaderboard. But when you talk to the sellers who consistently earn it, you hear something different. It’s not luck. It’s not one monster deal. It’s disciplined execution in the day-to-day — especially in today’s environment where scrutiny is high, budgets are tighter, and the Paper Process can quietly derail momentum.</p><p>The sellers who make Club aren’t just charismatic closers. They are operators. They qualify hard. They work high. They manage MEDDICC rigorously. They don’t let deals drift. And they don’t treat the Paper Process as an administrative afterthought — they treat it as a strategic milestone.</p><p>In this environment, Presidents Club isn’t won in December. It’s built in Q1 pipeline discipline, Q2 access to Economic Buyers, Q3 close plan precision, and Q4 execution. It’s built in how you handle every forecast call, every discovery, and every “we just need legal to review.”</p><p>The difference between good and elite often shows up in three places: qualification depth, access to power, and control of the close. Elite sellers know that if the Metrics are vague, if the Economic Buyer is distant, if the Decision Process is fuzzy, and if the Paper Process is undefined, they’re not on track for Club — no matter how optimistic the champion sounds.</p><p>Four things to do after reading this:</p><ol><li>Audit your top 10 deals for true MEDDPICC depth. Specifically confirm Economic Buyer access, quantified Metrics, defined Decision Process, and documented Paper Process steps. If it’s not written down, assume it’s not real.</li><li>Build a 90-day pipeline floor. Presidents Club sellers don’t rely on late-quarter heroics. Identify how much pipeline you need entering each quarter and protect it weekly.</li><li>Create a close plan for every deal forecasted this quarter. Include internal approvals, procurement steps, legal review timelines, and resource alignment. Share it with your champion and validate it.</li><li>Block weekly “deal hygiene” time on your calendar. Use it to advance access, confirm next steps, and remove friction from the Paper Process before it becomes a fire drill.</li></ol><p>Presidents Club is rarely about one big swing. It’s about disciplined, repeatable execution. The sellers who treat their business like a system — not a series of lucky breaks — are the ones booking their travel early.</p>]]>
        </description>
    </item>
    <item>
        <title>How I’m Using AI for Call Research Without Letting It Think for Me</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/881/how-i-m-using-ai-for-call-research-without-letting-it-think-for-me</link>
        <pubDate>Wed, 04 Feb 2026 17:15:25 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">881@/discussions</guid>
        <description><![CDATA[<p>AI has become a constant topic in sales conversations and I have it pretty well baked into my workflow. I didn’t want shortcuts that made me lazy, and I definitely didn’t want to show up to calls sounding like I copied and pasted a summary I didn’t fully understand.</p><p>What I’ve landed on is this: AI is incredibly useful for call research <em>if</em> you’re disciplined about how you use it. I don’t use it to replace preparation or judgment. I use it to speed up the parts of research that slow me down, so I can spend more time actually thinking.</p><p>Here’s how I’m using AI today to prepare for calls and how I make sure I’m still doing the critical thinking myself.</p><h3 data-id="1-use-ai-to-get-context-fast-not-conclusions"><strong>1. Use AI to Get Context Fast, Not Conclusions</strong></h3><p>Before a call, I’ll often ask AI to summarize:</p><ul><li>The company’s business model</li><li>Their target customers</li><li>Recent news or announcements</li><li>Industry trends they’re likely facing</li></ul><p>The key is what I <em>don’t</em> ask for: opinions or strategies.</p><p>AI gives me a fast baseline so I’m not starting from zero. From there, I decide what matters. I highlight what seems relevant and discard what doesn’t. The thinking still happens in my head — AI just clears the runway.</p><h3 data-id="2-ask-ai-to-help-identify-possible-pains-then-validate-them-yourself"><strong>2. Ask AI to Help Identify </strong><em><strong>Possible</strong></em><strong> Pains — Then Validate Them Yourself</strong></h3><p>I’ll sometimes ask AI:</p><blockquote><div><p>“Based on this company and their industry, what challenges might they be facing?”</p></div></blockquote><p>I treat the output as a hypothesis list, not truth.</p><p>From there, I cross-check:</p><ul><li>Do these align with what the salesperson heard?</li><li>Do they match what similar customers have said?</li><li>Do they connect to why the prospect took the meeting?</li></ul><p>This helps me walk into calls with sharper questions, not premature answers.</p><h3 data-id="3-turn-research-into-better-questions-not-better-slides"><strong>3. Turn Research Into Better Questions, Not Better Slides</strong></h3><p>One mistake I see is people using AI to script what they’re going to say.</p><p>Instead, I use it to sharpen the questions I plan to ask.</p><p>For example:</p><ul><li>“What questions would a CFO ask about this initiative?”</li><li>“What risks might a technical leader worry about here?”</li></ul><p>I’ll take those prompts and rewrite them in my own voice. If I can’t explain the question naturally, I don’t use it. The goal is curiosity, not performance.</p><h3 data-id="4-use-ai-to-map-stakeholders-then-plan-the-conversation-yourself"><strong>4. Use AI to Map Stakeholders — Then Plan the Conversation Yourself</strong></h3><p>AI can help identify likely stakeholders involved in a deal:</p><ul><li>Economic buyers</li><li>Technical influencers</li><li>Operational users</li></ul><p>That’s useful context. But deciding <em>who to focus on in this call</em> is still a human judgment.</p><p>I use AI to avoid blind spots, then I prioritize based on deal stage, politics, and what the salesperson already knows. AI gives me coverage; I decide direction.</p><h3 data-id="5-sanity-check-your-prep-don-t-outsource-it"><strong>5. Sanity-Check Your Prep, Don’t Outsource It</strong></h3><p>One of my favorite uses of AI is asking:</p><blockquote><div><p>“What am I missing in my preparation for this type of call?”</p></div></blockquote><p>This often surfaces things I forgot to consider, not things I should blindly adopt.</p><p>If I can’t explain why something matters to the customer, it doesn’t make it into the meeting. AI helps me stress-test my prep, not replace it.</p><p>The biggest mistake sellers make with AI is letting it think <em>for</em> them instead of thinking <em>with</em> them.</p><p>Customers can tell when you understand their world and they can tell when you don’t. AI won’t save you in that moment. Your judgment will.</p><p>Used correctly, AI doesn’t make you less thoughtful. It gives you more time to be thoughtful where it actually matters: in the conversation, in the questions you ask, and in how you respond in real time.</p><p>That’s where the great calls are won.</p>]]>
        </description>
    </item>
    <item>
        <title>Why the Paper Process Deserves Your Attention Earlier</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/879/why-the-paper-process-deserves-your-attention-earlier</link>
        <pubDate>Tue, 03 Feb 2026 19:59:19 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">879@/discussions</guid>
        <description><![CDATA[<p>In today’s selling environment, deals are scrutinized more heavily than ever. Procurement and legal teams are involved earlier, reviews take longer, and internal approvals are tighter. That makes the Paper Process a frontline selling issue — not a backend task.</p><p>Sellers who wait until the end to understand paperwork requirements often lose momentum, credibility, or forecast accuracy. Sellers who surface it early can set expectations, sequence activity correctly, and protect their time.</p><p>The Paper Process is also one of the clearest signals of deal health. If it’s vague, undefined, or constantly shifting, that’s risk worth addressing immediately.</p><p><strong>Three things to do after reading this:</strong></p><ol><li>Review your active deals and flag any without a confirmed Paper Process.</li><li>Add Paper Process milestones to your deal plan or CRM notes.</li><li>Loop in internal resources early once you understand what’s required.</li></ol><p>Great sellers don’t scramble at the finish line. They plan for it.</p>]]>
        </description>
    </item>
    <item>
        <title>The Pre-Call Is Where the Call Is Won or Lost</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/870/the-pre-call-is-where-the-call-is-won-or-lost</link>
        <pubDate>Wed, 28 Jan 2026 15:52:35 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">870@/discussions</guid>
        <description><![CDATA[<p>For a long time, I thought my job started when the meeting started.</p><p>Show up prepared. Know the product. Answer questions. Run a clean demo.</p><p>What I’ve learned—sometimes the hard way—is that the real work happens <em>before</em> the call ever begins. The pre-call is where alignment is built, mistakes are avoided, and trust with the salesperson is either strengthened or quietly eroded.</p><p>As I’ve spent more time partnering closely with sales teams, I’ve realized that working well with salespeople isn’t a “nice to have” skill. It’s essential to success. If we’re not aligned before the meeting, the prospect feels it immediately—even if they can’t quite name why.</p><p>Here’s how I’ve been getting more intentional with salespeople in the pre-call, and what’s made the biggest difference.</p><h3 data-id="1-get-clear-on-the-real-reason-for-the-meeting"><strong>1. Get Clear on the </strong><em><strong>Real</strong></em><strong> Reason for the Meeting</strong></h3><p>The calendar invite is never enough.</p><p>Before every call, I ask the salesperson one simple question:</p><blockquote><div><p>“Why did they agree to take this meeting?”</p></div></blockquote><p>Not the official reason. The real one.</p><p>Was it curiosity? Pressure from a boss? A specific pain? A bad experience with a competitor?</p><p>If we don’t align on this, the call risks becoming a generic walkthrough instead of a targeted conversation. The better we understand the prospect’s motivation, the easier it is to keep the meeting focused and relevant.</p><h3 data-id="2-align-on-roles-out-loud"><strong>2. Align on Roles—Out Loud</strong></h3><p>Assumptions kill good calls.</p><p>I now make it a point to clearly align on:</p><ul><li>Who is opening the call</li><li>Who is driving which sections</li><li>Who is listening for what</li></ul><p>This doesn’t need to be formal, but it does need to be explicit. When sales and technical partners step on each other—or leave gaps—the prospect notices. Clear roles create confidence and flow.</p><h3 data-id="3-decide-what-not-to-show"><strong>3. Decide What </strong><em><strong>Not</strong></em><strong> to Show</strong></h3><p>One of the biggest mistakes I see is trying to show too much.</p><p>In the pre-call, I ask:</p><blockquote><div><p>“If we can only show one or two things, what actually matters?”</p></div></blockquote><p>Then we cut the rest.</p><p>This forces discipline and ensures the call is anchored to value, not features. The pre-call is the time to make hard decisions about scope—so the live meeting doesn’t drift.</p><h3 data-id="4-pressure-test-the-narrative-together"><strong>4. Pressure-Test the Narrative Together</strong></h3><p>Before the call, I walk through the story with the salesperson:</p><ul><li>What problem are we solving?</li><li>Why does it matter now?</li><li>What should the prospect believe by the end of the call?</li></ul><p>If the story doesn’t make sense internally, it won’t land externally. These conversations surface gaps early—before they become awkward moments in front of the customer.</p><h3 data-id="5-define-success-before-the-call-starts"><strong>5. Define Success </strong><em><strong>Before</strong></em><strong> the Call Starts</strong></h3><p>At the end of the pre-call, I ask:</p><blockquote><div><p>“How will we know this was a good meeting?”</p></div></blockquote><p>Not “did we get a next step,” but:</p><ul><li>What clarity should the prospect have?</li><li>What question should be answered?</li><li>What risk should be reduced?</li></ul><p>When success is clearly defined ahead of time, the call becomes easier to navigate—and easier to close intentionally.</p><p>The biggest shift for me has been this: I no longer view pre-calls as logistics. I view them as strategy.</p><p>When salespeople feel like you’re invested <em>before</em> the meeting, trust builds quickly. When you show up aligned, intentional, and focused, the prospect feels that confidence immediately.</p><p>Great calls don’t happen by accident. They’re built together, before anyone ever says hello.</p>]]>
        </description>
    </item>
    <item>
        <title>Decision Process Is How You Protect Your Time</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/869/decision-process-is-how-you-protect-your-time</link>
        <pubDate>Wed, 28 Jan 2026 15:50:47 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">869@/discussions</guid>
        <description><![CDATA[<p>In today’s selling environment, time is your most limited resource. Deals that lack a clear Decision Process drain pipeline, forecasting accuracy, and mental energy. If you don’t know how a deal gets done, you don’t know if it deserves your focus.</p><p>Strong sellers use the Decision Process as a qualification tool. They ask early, listen carefully, and revisit often. They don’t accept vague answers, and they don’t move forward without understanding what “yes” actually requires.</p><p>Clarity here doesn’t just help you close — it helps you prioritize. When you know the real steps and timeline, you can plan your activity, engage the right stakeholders, and avoid end-of-quarter surprises.</p><p><strong>Three things to do after reading this:</strong></p><ol><li>Review your top five deals and flag any where the Decision Process is unclear.</li><li>Schedule a conversation specifically to validate approvals, timeline, and sequence.</li><li>Remove or de-prioritize deals that don’t have a confirmed Decision Process.</li></ol><p>The best sellers don’t chase activity — they chase clarity. Decision Process is one of the fastest ways to get it.</p>]]>
        </description>
    </item>
    <item>
        <title>Discipline Beats Heroics</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/862/discipline-beats-heroics</link>
        <pubDate>Wed, 21 Jan 2026 16:52:25 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">862@/discussions</guid>
        <description><![CDATA[<p>In today’s environment, closing is rarely clean. Deals face more scrutiny, approvals take longer, and competitive threats appear late. Sellers who rely on end-of-quarter heroics are often the ones surprised by slips.</p><p>Strong closing strategies today are scenario-based. Sellers anticipate obstacles, align internal resources early, and manage the approval process intentionally. They don’t wait for problems — they plan for them.</p><p>This environment rewards sellers who treat closing like a process, not an event. A clear close plan, fast response to customer concerns, and early post-sale alignment all signal credibility to buyers who are more risk-aware than ever.</p><p><strong>Three things to do next:</strong></p><ol><li>Map the customer’s internal approval process and confirm it with your buyer.</li><li>Identify one likely obstacle to closing and plan your response now.</li><li>Align internal teams early so post-sale readiness doesn’t delay signature.</li></ol><p>The sellers who win today aren’t louder or more aggressive — they’re more prepared.</p>]]>
        </description>
    </item>
    <item>
        <title>Making sure I give the client what they asked for.</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/859/making-sure-i-give-the-client-what-they-asked-for</link>
        <pubDate>Tue, 20 Jan 2026 22:36:18 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">859@/discussions</guid>
        <description><![CDATA[<p>For a long time, I thought I was good at running calls. I had an agenda. I covered my talking points. I advanced the deal. And on paper, things were moving.</p><p>But lately, I’ve realized something uncomfortable: it’s incredibly easy to leave a call feeling successful <em>without ever confirming whether the prospect got what they needed.</em></p><p>In sales, we’re trained to drive outcomes—next steps, demos, validations, timelines. And those things matter. But they don’t matter nearly as much as whether the prospect walks away thinking, <em>“That was worth my time.”</em></p><p>I’ve been working hard to communicate with more intention at the <strong>end</strong> of calls—specifically around whether or not we actually accomplished what the prospect was hoping to see. Because the truth is, if we miss that moment, we risk building momentum on our terms instead of theirs.</p><p>Here are five very real, actionable changes I’ve been making to ensure I’m closing calls the right way.</p><h3 data-id="1-restate-the-prospect-s-goal-before-you-ask-anything-else"><strong>1. Restate the Prospect’s Goal Before You Ask Anything Else</strong></h3><p>Before jumping to next steps, I now pause and say something like:</p><blockquote><div><p>“When we started this call, you said you wanted to understand X and see how we might help with Y.”</p></div></blockquote><p>This does two things:</p><ul><li>It shows I was listening.</li><li>It anchors the conversation back to <em>their</em> expectations, not mine.</li></ul><p>If I can’t clearly articulate their goal, that’s a signal I didn’t truly understand it.</p><h3 data-id="2-ask-the-one-question-most-sellers-skip"><strong>2. Ask the One Question Most Sellers Skip</strong></h3><p>After restating the goal, I ask directly:</p><blockquote><div><p>“Did we accomplish what you were hoping to get out of today?”</p></div></blockquote><p>This question can feel uncomfortable. But discomfort is better than assumption.</p><p>Sometimes the answer is yes. Sometimes it’s “mostly.” And sometimes it’s no—and that’s incredibly valuable information while you’re still on the call.</p><h3 data-id="3-listen-without-defending-or-over-explaining"><strong>3. Listen Without Defending or Over-Explaining</strong></h3><p>When a prospect says they didn’t quite get what they hoped for, the instinct is to explain, justify, or rush to fix it.</p><p>I’m learning to resist that.</p><p>Instead, I ask:</p><blockquote><div><p>“What feels like it’s still missing?”</p></div></blockquote><p>That pause—without defensiveness—builds trust. It shows you care more about their outcome than your performance.</p><h3 data-id="4-separate-their-success-from-your-next-step"><strong>4. Separate </strong><em><strong>Their</strong></em><strong> Success From </strong><em><strong>Your</strong></em><strong> Next Step</strong></h3><p>One of the biggest shifts I’ve made is mentally separating:</p><ul><li>“Did the prospect get value?”<br />
from</li><li>“Did I move the deal forward?”</li></ul><p>Those two things aren’t always the same, and that’s okay.</p><p>If the prospect’s goal wasn’t met, the next step shouldn’t be forced. It should be adjusted. When you align next steps to <em>their</em> gap instead of <em>your</em> timeline, deals actually move faster in the long run.</p><h3 data-id="5-end-the-call-by-reflecting-value-back-to-them"><strong>5. End the Call by Reflecting Value Back to Them</strong></h3><p>Before wrapping up, I summarize the call from <em>their</em> perspective:</p><ul><li>“You came in wanting clarity on X—here’s what we covered.”</li><li>“You were unsure about Y—here’s where we landed.”</li></ul><p>This reinforces that the call was about them, not the product, not the pitch, not the process.</p><p>Here’s the hard truth: it’s easy to leave calls feeling productive. It’s much harder to ensure they were meaningful.</p><p>But the sellers who win long-term are the ones who consistently check in—not just on progress, but on satisfaction.</p><p>The question I’m trying to ask myself more often is simple:<br /><strong>“If I were in their seat, would I feel like this was time well spent?”</strong></p><p>If you can confidently answer yes, out loud, with the prospect, you’re doing something right.</p>]]>
        </description>
    </item>
    <item>
        <title>Communicating With Intention During Demos</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/858/communicating-with-intention-during-demos</link>
        <pubDate>Wed, 14 Jan 2026 17:47:35 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">858@/discussions</guid>
        <description><![CDATA[<p>Over the last few months, I’ve been taking a hard look at how I run demos. Not because something was “broken,” but because I realized something uncomfortable: it’s incredibly easy to show a lot of impressive things and still miss the mark with a customer.</p><p>I’ve seen it in my own demos and in coaching others. We move quickly. We show features. We answer questions. We click through workflows. And then we end the call wondering why the customer didn’t feel the impact we thought they would.</p><p>The issue usually isn’t <em>what</em> we showed. It’s that we didn’t explain <em>why</em> it mattered.</p><p>In a demo, every detail is a choice. Every screen, every click, every data point either reinforces the customer’s problem—or it distracts from it. When we don’t communicate with intention, we ask the customer to do the work of connecting the dots themselves. And most won’t.</p><p>Here are five very real changes I’ve been making to ensure every demo moment has a purpose.</p><h3 data-id="1-start-the-demo-by-defining-the-why-out-loud"><strong>1. Start the Demo by Defining the “Why” Out Loud</strong></h3><p>Before I share my screen, I now take 30–60 seconds to frame the demo:</p><blockquote><div><p>“Today, I’m going to show you three things. Each one ties directly to the challenge you mentioned around X.”</p></div></blockquote><p>This does two things:</p><ul><li>It sets expectations.</li><li>It gives the customer a lens to evaluate what they’re seeing.</li></ul><p>If the customer doesn’t know <em>why</em> you’re showing something, they’re just watching—not engaging.</p><h3 data-id="2-narrate-the-importance-not-the-clicks"><strong>2. Narrate the Importance, Not the Clicks</strong></h3><p>It’s tempting to explain <em>how</em> something works. Buttons, menus, workflows. But customers don’t buy how—it’s assumed.</p><p>Instead, I focus on narrating <strong>why the behavior matters</strong>:</p><ul><li>“I’m clicking here because this removes manual steps your team does today.”</li><li>“This view matters because it gives your leadership real-time visibility without exporting data.”</li></ul><p>Every click gets a sentence that ties it back to value. If I can’t explain why a step matters, it probably doesn’t belong in the demo.</p><h3 data-id="3-pause-and-validate-after-each-key-moment"><strong>3. Pause and Validate After Each Key Moment</strong></h3><p>One mistake I made early in my career was plowing through demos without stopping. Now, after every major concept, I pause and ask a simple question:</p><blockquote><div><p>“Does this solve what you described earlier?”</p></div></blockquote><p>This keeps the demo interactive and confirms alignment. It also gives the customer permission to say, “Not quite,” before we go too far down the wrong path.</p><h3 data-id="4-be-ruthless-about-what-you-don-t-show"><strong>4. Be Ruthless About What You </strong><em><strong>Don’t</strong></em><strong> Show</strong></h3><p>More is not better in a demo. Clarity is.</p><p>I’ve started removing sections of demos that are “nice to have” but not tied to the customer’s stated pain. Even if they’re impressive. Even if I love showing them.</p><p>If a feature doesn’t reinforce the customer’s goal, it dilutes the story. Intentional demos are shorter, sharper, and more effective.</p><h3 data-id="5-end-by-reconnecting-every-detail-to-the-original-problem"><strong>5. End by Reconnecting Every Detail to the Original Problem</strong></h3><p>At the end of the demo, I recap—not with features, but with outcomes:</p><ul><li>“You said X was slowing your team down—this is how we addressed that.”</li><li>“You were worried about Y—here’s what removes that risk.”</li></ul><p>This closes the loop and reinforces that nothing was shown randomly. Everything had a reason.</p><p>Demos aren’t product tours. They’re value conversations. And when we communicate with intention, customers feel it. They lean in. They ask better questions. They see themselves in the solution.</p><p>The challenge I’ve given myself—and now my team—is simple: <strong>if you can’t explain why you’re showing something, don’t show it.</strong></p>]]>
        </description>
    </item>
    <item>
        <title>The Courage to Ask Up</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/854/the-courage-to-ask-up</link>
        <pubDate>Wed, 14 Jan 2026 17:26:18 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">854@/discussions</guid>
        <description><![CDATA[<p>Deals are more complex, budgets are tighter, and cycles are longer. That means you can’t afford to stay low in an account. To change deal momentum, you need to work higher and create urgency with people who actually have the authority to prioritize your solution. It takes courage, but the payoff is worth it.</p><p>Three things you can do today:</p><ol><li>In your next deal review, ask yourself: “If I had to get executive sponsorship tomorrow, who would I target and what would I say?”</li><li>Don’t wait for your champion to introduce you. Ask them directly to set up a conversation with leadership and explain why it matters.</li><li>Track how often you’re having VP+ conversations across your pipeline. Make it a personal metric of success.</li></ol><p>The environment isn’t forgiving to sellers who stay comfortable. Work higher, ask harder questions, and you’ll find your deals gaining new energy.</p>]]>
        </description>
    </item>
    <item>
        <title>Treat SKO Like a Strategic Reset, Not a Pep Rally</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/849/treat-sko-like-a-strategic-reset-not-a-pep-rally</link>
        <pubDate>Wed, 07 Jan 2026 16:09:24 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">849@/discussions</guid>
        <description><![CDATA[<p>In today’s selling environment, SKO isn’t just a kickoff — it’s a strategic reset. Buying cycles are longer, scrutiny is higher, and sellers can’t afford to leave value on the table by showing up unprepared.</p><p>The sellers who benefit most from SKO already know where they’re stuck. They arrive with questions about territory, accounts, and execution. That preparation turns SKO from a passive experience into a problem-solving moment.</p><p>Three things you can do:</p><ol><li>Review your territory and identify where deals stalled last year before attending SKO.</li><li>Bring one execution challenge you want clarity on — not just inspiration.</li><li>Leave SKO with a written 30-day action plan tied to real accounts.</li></ol><p>When you approach SKO intentionally, it becomes less about hype and more about direction. That clarity is what sets strong sellers apart as the year gets underway.</p>]]>
        </description>
    </item>
    <item>
        <title>Starting the New Year With a Blank Slate</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/848/starting-the-new-year-with-a-blank-slate</link>
        <pubDate>Wed, 07 Jan 2026 16:08:09 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">848@/discussions</guid>
        <description><![CDATA[<p>There’s something both exciting and intimidating about the start of a new year, especially when you carry a number. The pipeline resets. The leaderboard clears. Last year’s wins don’t count, and neither do last year’s misses.</p><p>This year feels even more personal for me. I’ve accepted a new role, and I’m back in a quota-carrying seat myself. That shift has forced me to confront something I’ve coached others on for years: the only way to start strong is to treat the new year like a true blank slate. I'm still looking at how I can help motivate the team around me, but I'm no longer the main leader to whom everyone turns.</p><p>When you carry a quota, it’s easy to drag the emotional baggage of the previous year into January. Things like slipped deals, customers that went dark, expectations you didn’t meet. But none of that helps you execute today.</p><p>Here are five very real things I’m doing to reset my mindset and dig into the new year with clarity and purpose.</p><h3 data-id="1-leave-last-year-where-it-belongs"><strong>1. Leave Last Year Where It Belongs</strong></h3><p>This is just so important.</p><p>Before I opened my CRM this year, I spent time writing down what I learned last year. I wrote down what worked, what didn’t, and what I want to change. I wrote down the things that I needed to leave behind, but didn't want to forget. Then I closed the notebook.</p><p>The goal isn’t to forget the past; it’s to extract the lessons and move on. Carrying emotional weight into a new year doesn’t make you more disciplined and it can make you hesitant.</p><p>A blank slate means giving yourself permission to operate without guilt or regret.</p><h3 data-id="2-rebuild-your-pipeline-like-it-s-day-one"><strong>2. Rebuild Your Pipeline Like It’s Day One</strong></h3><p>When I re-entered a quota-carrying role, I resisted the urge to obsess over what was already in the funnel. Instead, I asked myself:</p><blockquote><div><p>“If I were starting from zero, how would I build momentum?”</p></div></blockquote><p>That meant focusing on activities I control:</p><ul><li>High-quality discovery conversations</li><li>Reconnecting with old relationships</li><li>Sharpening my point of view</li></ul><p>Strong pipelines are built, not inherited. Treating the year like a clean start keeps you focused on inputs, not panic.</p><h3 data-id="3-relearn-the-product-through-the-customer-s-eyes"><strong>3. Relearn the Product Through the Customer’s Eyes</strong></h3><p>Instead of just reading release notes, I’ve been listening to customer calls, reviewing deal notes, and asking, “Why does this matter to them?” I'm in my new role, so this is very important to me, right now.</p><p>When you carry a quota, clarity beats confidence. You don’t need to know everything. You need to know what moves deals forward.</p><h3 data-id="4-reset-what-winning-looks-like-daily"><strong>4. Reset What “Winning” Looks Like Daily</strong></h3><p>Big annual numbers can feel overwhelming in January. So I break them down aggressively.</p><p>Winning today might mean:</p><ul><li>Booking one meaningful meeting</li><li>Advancing one deal</li><li>Getting clarity on one account</li></ul><p>Momentum doesn’t come from staring at the quota. It comes from consistent, purposeful execution.</p><h3 data-id="5-approach-the-year-with-curiosity-not-pressure"><strong>5. Approach the Year With Curiosity, Not Pressure</strong></h3><p>Pressure narrows thinking. Curiosity expands it.</p><p>In this new role, I’m asking more questions—of customers, teammates, and myself. Curiosity helps me adapt faster, learn quicker, and stay energized.</p><p></p><p>A blank slate isn’t about proving something. It’s about discovering what’s possible.</p><p>Carrying a quota resets us all to the same starting line. Titles don’t matter. History doesn’t matter. What matters is how intentionally we show up.</p><p>This year, I’m choosing clarity over noise, curiosity over pressure, and progress over perfection.</p><p>If you’re starting this year with a number to hit, my challenge to you is simple: treat it like a blank slate and act like it’s your first shot all over again.</p>]]>
        </description>
    </item>
    <item>
        <title>Doing the small things that prevent big problems</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/841/doing-the-small-things-that-prevent-big-problems</link>
        <pubDate>Wed, 17 Dec 2025 16:23:27 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">841@/discussions</guid>
        <description><![CDATA[<p>The day-to-day sales environment at year-end is chaotic. Buyers go dark. Internal deadlines stack up. Everyone wants certainty where there isn’t much. In this reality, small execution details make a huge difference for Ops.</p><p>Incomplete close plans, missing paperwork, or unclear next steps don’t just slow deals — they create extra work for teams already running hot. The sellers who stand out in December aren’t the loudest; they’re the most prepared.</p><p>This is about professionalism as much as performance. Clean execution now earns trust that carries into next year.</p><p>Three things you can do this week:</p><ol><li>Confirm close dates and next steps with customers in writing, then reflect them accurately in the CRM.</li><li>Double-check legal, procurement, and approval requirements before Ops has to chase you.</li><li>Flag risk early instead of waiting until a deal “suddenly” slips.</li></ol><p>Year-end is stressful enough without surprises. When you operate with clarity and urgency, you help Ops close the books with confidence — and you position yourself as someone leadership can rely on when it matters most.</p>]]>
        </description>
    </item>
    <item>
        <title>The Perfect Holiday Gift You Can Give Ops</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/839/the-perfect-holiday-gift-you-can-give-ops</link>
        <pubDate>Wed, 17 Dec 2025 16:21:03 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">839@/discussions</guid>
        <description><![CDATA[<p>As the year winds down, everyone feels the pressure — especially Sales Ops. Forecast calls get tighter, scrutiny goes up, and gaps in deal clarity become painfully visible. This is where MEDDICC stops being a checkbox and becomes a service to the entire organization.</p><p>When Metrics are vague, Economic Buyers are assumed, or Decision Criteria live only in your head, Ops has to guess. That guesswork shows up as re-forecasting, last-minute deal slips, and uncomfortable end-of-year conversations. A well-documented MEDDICC deal gives Ops confidence in what’s real and what isn’t.</p><p>The stronger your MEDDICC discipline, the fewer “Can you clarify this?” messages you’ll get in December. And more importantly, the more credibility you build heading into next year.</p><p>Three things you can do this week:</p><ol><li>Review your top 5 deals and update every MEDDICC field with customer-validated information, not assumptions.</li><li>Call out MEDDICC gaps proactively in forecast conversations instead of hoping they won’t matter.</li><li>Add a short MEDDICC summary note in the CRM that Ops can quickly reference without digging.</li></ol><p>Closing out the year isn’t just about landing deals — it’s about landing them cleanly. MEDDICC is one of the simplest ways to reduce friction, build trust with Ops, and start next year with a pipeline everyone believes in.</p>]]>
        </description>
    </item>
    <item>
        <title>Why Sales Engineers Need to Anticipate Customer Needs (and How to Do It)</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/838/why-sales-engineers-need-to-anticipate-customer-needs-and-how-to-do-it</link>
        <pubDate>Wed, 10 Dec 2025 17:44:09 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">838@/discussions</guid>
        <description><![CDATA[<p>One thing I’ve been talking about a lot lately—both with my team and with sales leadership—is how critical it is for Solutions Engineers to <strong>stay two steps ahead of both the customer and the salesperson</strong>.</p><p>In today’s sales environment, customers expect more than a good demo. They expect partnership. They expect insight. They expect someone who understands not just what they <em>asked for</em> but what they’re <em>going to need</em> as the deal evolves.</p><p>The best SEs—especially in complex revenue cycles—don’t wait to be told what to do. They anticipate. They prepare. They intentionally make the sales team stronger by showing up ready to create clarity and momentum.</p><p>Here are five real, practical ways SEs can think proactively and help their sales teams win more often and with less chaos:</p><h3 data-id="1-pre-read-everything-before-the-customer-call"><strong>1. Pre-Read Everything Before the Customer Call</strong></h3><p>This sounds simple, but you’d be amazed how often it’s skipped.<br />
Before a customer call, SEs should read:</p><ul><li>Previous call notes</li><li>The customer’s website</li><li>Their product pages</li><li>Recent press or funding announcements</li><li>Any internal chatter about the account</li></ul><p>Don’t wait for the AE to “brief you.” You’re a partner, not an assistant.</p><p>A prepared SE brings confidence, direction, and better questions. And customers feel that difference immediately.</p><h3 data-id="2-build-a-running-list-of-likely-needs-based-on-the-customer-s-role"><strong>2. Build a Running List of ‘Likely Needs’ Based on the Customer’s Role</strong></h3><p>Different stakeholders tend to follow predictable patterns of interest and concern.<br />
For example:</p><ul><li><strong>A VP of Sales</strong> usually wants clarity on productivity and forecasting.</li><li><strong>Ops leaders</strong> want system stability, integrations, and data cleanliness.</li><li><strong>IT</strong> wants security, scalability, and ease of management.</li></ul><p>Before each conversation, SEs should pre-build a set of insights or talking points tailored to the roles expected in the call.</p><p>Proactive SEs don’t wait for questions—they answer the ones the customer <em>will</em> ask.</p><h3 data-id="3-bring-if-this-then-that-options-to-every-deal-review"><strong>3. Bring ‘If This, Then That’ Options to Every Deal Review</strong></h3><p>AEs frequently get hit with curveballs mid-deal: budget cuts, new stakeholders, shifting priorities.</p><p>The SE’s value skyrockets when they come prepared with scenario planning, like:</p><ul><li>“If they push back on integration complexity, here’s our lightweight path.”</li><li>“If procurement gets involved, here’s the security doc we’ll need.”</li><li>“If they bring in the CFO, here’s the ROI frame that will resonate.”</li></ul><p>Prepared SEs reduce deal friction before it surfaces.</p><h3 data-id="4-give-the-ae-inside-information-they-didn-t-ask-for"><strong>4. Give the AE Inside Information They Didn’t Ask For</strong></h3><p>There are moments where the AE doesn’t know what they need next—but the SE does.</p><p>Examples:</p><ul><li>Offering a technical validation checklist <em>before</em> the customer asks for next steps</li><li>Highlighting a potential risk based on something subtle in the call</li><li>Flagging a capability gap early so the positioning stays clean</li></ul><p>This is where SEs shift from “demo resource” to “strategic operator.”</p><h3 data-id="5-end-every-call-with-clear-recommendations-not-just-recaps"><strong>5. End Every Call with Clear Recommendations, Not Just Recaps</strong></h3><p>Too many SEs say, “Let me know what you need next.”</p><p>Proactive SEs say:</p><blockquote><div><p>“Based on what we heard today, here are the next three steps I recommend we take…”</p></div></blockquote><p>When SEs offer direction instead of waiting for it, deals accelerate. Salespeople appreciate it. Customers trust it. And momentum stays intact.</p><p></p><p><strong>At the end of the day, great sales teams win because they operate as a unit.</strong><br />
And the best SEs don’t just react—they anticipate. They see around corners. They prepare the path before anyone else recognizes there’s a turn ahead.</p><p>If you’re an SE reading this: your technical knowledge matters, but your ability to proactively guide the deal matters <em>more.</em></p><p>If you’re a salesperson: give your SEs the space to anticipate, contribute, and lead. You’ll close more deals—and you’ll close them with a lot less stress.</p>]]>
        </description>
    </item>
    <item>
        <title>Preparing for SKO Like a Pro</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/834/preparing-for-sko-like-a-pro</link>
        <pubDate>Wed, 10 Dec 2025 17:17:41 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">834@/discussions</guid>
        <description><![CDATA[<p>The sellers succeeding today aren’t waiting for SKO to “kick off the year.” They’re preparing in advance so SKO becomes an accelerant, not a reset button. With budgets tightening and buying committees expanding, you need every SKO session to tie directly to your territory, your accounts, and your plan.</p><p>If you walk into SKO without clarity on where your pipeline will come from, you’ll walk out with inspiration but no execution. If you walk in prepared, every workshop becomes a force multiplier that helps you refine strategy with precision.</p><p><strong>Three actionable things to do:</strong></p><ol><li><strong>Review your territory plan</strong> before SKO and bring specific questions to validate your assumptions.</li><li><strong>Reassess your top accounts</strong> with a focus on new stakeholders, org changes, and fresh initiatives for next year.</li><li><strong>Identify 5 whitespace opportunities</strong> and use SKO sessions to refine your approach to them.</li></ol><p>SKO is where strategy meets execution. If you invest time upfront, the event becomes the catalyst that fuels your Q1 momentum and sets you up for a stronger year.</p>]]>
        </description>
    </item>
    <item>
        <title>Helping Your Sales Teams Use Their Solutions Engineers the Right Way</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/830/helping-your-sales-teams-use-their-solutions-engineers-the-right-way</link>
        <pubDate>Wed, 03 Dec 2025 16:45:08 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Ben Fleishman</dc:creator>
        <guid isPermaLink="false">830@/discussions</guid>
        <description><![CDATA[<p>One thing I’ve learned across multiple teams and multiple companies is this: the partnership between Sales and Solutions Engineering can be a competitive advantage—or an underutilized asset. Rarely anything in between.</p><p>When the relationship is aligned, intentional, and structured, deals move faster, customers feel supported, technical risks get surfaced early, and the team shows up as a unified front. When it’s not aligned, you get confusion, gaps in communication, last-minute scrambles, mismatched expectations, and frustration on both sides.</p><p>Recently, I’ve been spending a lot of time helping my teams understand <em>when and how</em> to pull their SEs into deals. The SE role is incredibly powerful, but only if you use it deliberately—and not as a last-minute rescue button.</p><p>Here are five real, practical ways sales teams can get the most out of their SE partners (and ultimately win more deals with less friction).</p><h3 data-id="1-bring-your-se-in-early-not-just-when-things-get-technical"><strong>1. Bring Your SE in Early—Not Just When Things Get Technical</strong></h3><p>This is the #1 mistake I see. Sellers assume “I’ll bring in my SE when the customer needs to see a demo.” That’s too late.</p><p>A great SE can:</p><ul><li>Help shape early discovery</li><li>Identify technical implications of business pain</li><li>Spot risks before they explode</li><li>Help you ask better questions</li></ul><p><strong>Action:</strong> Invite your SE to planning sessions for any deal that <em>might</em> become meaningful. A 10-minute async brief early on is better than a 2-hour emergency call later.</p><h3 data-id="2-send-context-before-every-call-not-after"><strong>2. Send Context Before Every Call—Not After</strong></h3><p>Your SE shouldn’t have to guess why a meeting exists. They also shouldn’t have to chase you for information.</p><p>At minimum, send this before every customer call:</p><ul><li>Objective of the meeting</li><li>What you want the SE to own or observe</li><li>Who is attending (titles + decision roles if known)</li><li>What you already know technically</li><li>What you <em>don’t</em> know yet</li></ul><p>Don’t write a novel. Two clean paragraphs or a bullet list is more than enough.</p><p>This single habit improves call quality immediately.</p><h3 data-id="3-use-your-se-to-validate-pain-not-just-validate-tech"><strong>3. Use Your SE to Validate Pain—Not Just Validate Tech</strong></h3><p>Most teams underutilize their SEs in discovery. Technical sellers hear things differently, notice different friction points, and can often uncover insights the AE wouldn’t hear alone.</p><p>Examples:</p><ul><li>“What’s slowing down your current workflow?”</li><li>“Where does data break or bottleneck today?”</li><li>“How reliable does this process need to be for the business impact to be real?”</li></ul><p><strong>Action:</strong> Let your SE run part of discovery—even 5–7 minutes—to pull out the technical pain that deepens the business problem.</p><h3 data-id="4-co-create-the-demo-strategy-don-t-dump-it-on-the-se"><strong>4. Co-Create the Demo Strategy—Don’t Dump It on the SE</strong></h3><p>A demo is not a presentation. It’s a <strong>narrative that proves value</strong>.</p><p>Your SE shouldn’t be learning the storyline <em>on the call</em>. A well-run demo happens when the AE and SE sit down and decide:</p><ul><li>What value messages to reinforce</li><li>Which capabilities matter and which do not</li><li>Where to pause for customer confirmation</li><li>What objections might come up and who covers what</li></ul><p><strong>Action:</strong> For important demos, schedule a 20–30 minute prep session. It will save you hours in the long run.</p><h3 data-id="5-treat-your-se-like-a-strategic-partner-not-a-task-rabbit"><strong>5. Treat Your SE Like a Strategic Partner—Not a Task Rabbit</strong></h3><p>If your SE only hears:<br />
“Can you build this?”<br />
“Can you show this?”<br />
“Can you handle this part?”</p><p>…you’re missing their biggest value.</p><p>SEs are often closest to:</p><ul><li>Emerging customer patterns</li><li>Product limitations</li><li>Product strengths</li><li>Competitive gaps</li><li>Common objections</li><li>Real implementation pitfalls</li></ul><p>Lean on that. Ask:</p><ul><li>“What do you see happening across deals?”</li><li>“Where do you see technical risk here?”</li><li>“What would you challenge me on in this opportunity?”</li></ul><p>SEs typically have more pattern recognition than anyone else on the team. Use it!</p><p></p><p>Sales and SEs win together when both sides operate with purpose. When you plan together, debrief together, and show up as a unified team, customers feel it—and it changes deals.</p><p>If you’re a seller, you don’t need to be deeply technical. But you <em>do</em> need to know how to use your technical teammates.</p><p>Do these five things consistently, and your partnership with your SE stops being transactional—it becomes a differentiator your competitors can’t match.</p>]]>
        </description>
    </item>
    <item>
        <title>Everyone Owns Their Pipeline</title>
        <link>https://forcemanagement.vanillacommunities.com/discussion/827/everyone-owns-their-pipeline</link>
        <pubDate>Wed, 03 Dec 2025 16:41:19 +0000</pubDate>
        <category>Content &amp; Resources</category>
        <dc:creator>Courtney McCoy</dc:creator>
        <guid isPermaLink="false">827@/discussions</guid>
        <description><![CDATA[<p>In the current selling environment, deals take longer, buying committees are larger, and inbound isn’t what it used to be. That means pipeline creation can’t be delegated. Even top-performing sellers today are going back to basics — researching accounts deeply, building relevant outreach, nurturing stale leads with value, and becoming relentless about creating opportunities.</p><p>Modern buyers want sellers who show up informed and ready. That starts long before the discovery call. Your pipeline is simply a reflection of the effort, discipline, and creativity you put into the early parts of your sales process.</p><p>Three actionable things you can do today:</p><ol><li><strong>Review your entire Q3 and Q4 territory to identify dormant accounts worth re-opening.</strong> Prioritize those with known pain.</li><li><strong>Block 30–60 minutes every day for pure pipeline work.</strong> Protect this time like an executive meeting.</li><li><strong>Use AI to research accounts faster.</strong> Ask for trends, recent financial changes, or role-specific challenges to fuel your outreach.</li></ol><p>If you want predictable performance in the second half of the year, it starts with disciplined pipeline creation now. Every conversation you start today becomes the momentum you rely on tomorrow.</p>]]>
        </description>
    </item>
   </channel>
</rss>
