How can a proposal team shorten the deal cycle? Gong's analysis of 7.1 million opportunities found average deal duration stayed flat from 2024 to 2025. The time is lost when deals stall or end with no decision. In this Season 2 episode of The Stargazy Brief, published 19 November 2026, Christina Carter asks a bid leader and a sales leader what proposal teams can do about it.
Kemi Solanke is an award-winning bid and capture strategist. She works as a fractional bid strategist and runs Learn Bids.
Aaron Swanson leads go-to-market at SiftHub.
Track "no decision" as a competitor. Aaron's team measured a win and loss rate against no decision in the same way as against named vendors. He treats it as a sales failure, because the buyer's problem remains. Those deals often return six to twelve months later after a leadership or budget change.
The best RFP is the one that never gets issued. Strong discovery, shared with the proposal team, lets you send a proposal written for that buyer and that problem. Kemi's fastest deal this year followed that route and moved to a statement of work.
Volunteer for the room. Kemi puts her hand up for buyer days, market engagement days and client events, then uses the attendee list to map the competition. First-hand buyer intel makes the response specific.
When a deal stalls, ask what is preventing the buyer from deciding: commercial risk, implementation uncertainty, or an unconvinced finance lead.
Give the buying group one clear, consistent value proposition supported by evidence. A separate message per stakeholder creates confusion.
Every claim needs proof the buyer can check, and it has to match your website and what AI search says about you.
Write for AI evaluators with clear headings, direct answers, consistent terminology and evidence that is easy to locate. Writing for AI does not mean writing like AI.
A maintained content library, named owners for clarifications, and lighter approvals for simple requests all remove waiting time.
Qualify hard. Aaron's team declined an RFP written for a competitor, the buyer called to say no decision had been made, and they went on to win.
About this episode
This episode was recorded as a live panel sponsored by SiftHub. SiftHub is a Stargazy Orbits partner. That relationship has no bearing on the questions asked or on vendor evaluation scoring, which follows the published rubric. stargazy has no commercial relationship with Kemi Solanke or Learn Bids.
Chapter times are approximate and refer to the full recording.
Christina Carter: Hey Stargazers, I have a treat for all of us today. I'm getting a view from a longtime go-to-market sales leader and from a longtime proposal management leader. They're going to talk about something that we really never hear about, and that is how to shorten a proposal deal cycle.
A lot of the time we think this isn't on me, this is on the sales team, it's on the buyer team. What do I have to do with it? But it turns out we have a lot of input on a shortened deal cycle.
Why should you care about a shortened deal cycle? In our industry, as we are trying to be seen as the strategic revenue-driving force that we are, we have to be speaking our sales leaders' language. They care about time to close. Every single pipeline call, every single QBR, time to close is going to come up.
If you want to learn how to do this better, you're going to learn from the best. Kemi and Aaron are going to get into it and give you really specific ideas of what to do. Get out your notebook. Take notes. Let's get into it.
Christina Carter: I want to say a huge thank you to Kemi, a huge thank you to Aaron and SiftHub. I invited Kemi on here because she's amazing. She's an award-winning, experienced bid and capture strategist. I've met her multiple times before. She's on an upcoming podcast, so wait for that. She is going to give us the bid, proposal and capture strategist point of view.
And then we've invited Aaron, who leads go-to-market at SiftHub. To me, that means he's going to be able to give us the sales leadership point of view. So we have two points of view in here.
Aaron, my first question is to you, and that is why deals take so long. We know from Forrester's State of Business Buying 2026 report, which surveyed 18,000 buyers, that a typical purchase involves 13 internal stakeholders plus 9 outside influencers. So the people who are buying from our RFPs are a huge group of people. And yet we found out that 86% of purchases stall at some point.
So the slowdown is not usually us as a salesperson or the sales organization. The issue is usually with the buying team, which has a really tough time making a conclusion about what to purchase. Aaron, that was a really long question. But from the sales side, where do you see deals stall?
Aaron Swanson: Every time I hear the survey data around how many people are involved in deals, the numbers get bigger. A few years ago it was five people, then it was seven, and now we're up to thirteen. It'll probably continue to grow.
We see deals stall usually not within a specific group, but when we're trying to move between groups, between meetings. That team grows during the evaluation, because usually it's one person doing exploration. It gets handed to more people. You have more voices in the room.
If you get enough voices in the room in a formal structure, it's going to end up going to some kind of a competitive bid, probably an RFP with responses. Then that has its own schedule to track. You end up with a lot of, not necessarily conflicting, but interested voices that have to come to some kind of consensus along the way.
So aligning on the steps and the timing continues to get more challenging. I'm going to date myself a little bit, but as we went from perpetual software, where you ship a CD or download something, to SaaS, security requirements grew. Security assessments were non-standard and then they became standard.
Now we're in the world of AI and we're moving past security assessments. Those are almost table stakes. Now we're doing AI security assessments and how that's going to fit into environments. The evaluation process and what's involved continues to evolve.
So it's having awareness of what those steps are, and making sure we have discussions proactively in sales to know what that buying process really looks like. How does that map into the RFP schedule, the response and the evaluation? Then all of us being aware of what those key milestone dates are and tracking through them, so that we stay aligned with the customer and run at the pace they're running at. That keeps everything as tight and quick as possible as the buying process gets more complex over time.
Christina Carter: What I'm hearing is that it's really tough to do, and it's becoming more complicated. So from a sales leadership point of view, this is something you're focusing on even more than before. Kemi, coming to you, when a deal stalls, what can the proposal team do to help get it moving again?
Kemi Solanke: I think one of the biggest mistakes organizations make is assuming that when a deal stalls, the buyer has lost interest. Quite often, that's not the case. The buyer may still be interested, but they haven't reached an internal agreement. Sometimes we forget how many stakeholders are involved from both sides when it comes to a deal.
As bid and proposal people, we're in a unique position because we're working with everybody. We're working across sales, across finance, across operations. We understand the solution. So we're coming from a different angle, and we understand the different concerns the buyers may have, because we've probably been working on the deal from the inception, or even from before the opportunity if we're talking about capture.
So rather than asking what more information the buyer needs, I would be asking what is preventing them from making a decision. Is it commercial risk? Is it uncertainty about implementation? If we're talking about tech, is the finance decision maker unconvinced about the return on investment?
Once we understand the barriers, we can help sales develop targeted evidence, better business cases or responses that address those concerns. The role of the bid team shouldn't end when a proposal is submitted, where we move over to the next deal and the salespeople continue chasing. We should all be working together to help the buyer reach a confident decision.
Christina Carter: I could not agree more. It's tough to get all those people to work together, though. I think that's where buyer stakeholder mapping gets really important. But I'll move on to the next question because we have so much to get through.
My next question is for you, Aaron, and I'm starting once again with a stat. Gong analyzed 7.1 million opportunities, so a lot, and it found in 2026 that the average deal duration stayed the same from 2024 to 2025. So it hasn't gotten longer.
The real problem is probably not that the cycles are getting longer. It's that the deal is stalling or ends in no decision. It's not that you lost to your competitor, it's that they didn't make a decision with anybody. Aaron, does that match what you see in your practical, real-world experience? I would love to hear about it from a sales leadership point of view.
Aaron Swanson: Interestingly enough, we used to spend so much time, and still do, on how we stack up against competitors. Two companies ago, I had a leadership role where we were looking at our competitive positioning, competitive evaluation and win-loss. And we put no decision in as a competitor.
We viewed it specifically as that. It was enough of a loss reason. We couldn't get to consensus, couldn't get to a place where a decision was made that had enough pull to move away from the status quo.
Often those are deals that go away for a little while, because the pain remains. The original problem remains. I do look at it as a sales failure, because we were unable to demonstrate clearly enough how we solve that problem, and that the customer should be willing to make the time and money investment to change.
Often we would see those deals come back six months or a year later. Maybe it was a budget issue that was temporary and hard to overcome. But often it's a leadership change, a personnel change, or something acute happens in the business and they go, "We really have to solve this now." But you have to wait for that.
So I think the sales goal, and the proposal team goal, is to be compelling enough and articulate enough about the problem that the no decisions become a reduced factor overall. It's something we track. As we track competitive win rate against a specific competitor, we ask what our win or loss rate is against no decision.
Christina Carter: I love that, because I think proposal teams can help so much with each piece of that. The data backs up the fact that so many of our buyers are going into these RFPs knowing who they want to win. They're humans, they have biases, they've done their research.
How do you want proposal teams to get involved, especially to help you get into that front-runner position? What have you seen teams do really well? What things, usually outside their job description, do you think they should be doing to support you?
Aaron Swanson: Everything changes so quickly right now on websites, content and strategy. It's gotten easier than ever to produce more and put more out there. So staying on message, with clean content that's compelling, is still an art. It takes time, it takes effort and it takes expertise to produce that. And I think proposal teams have more expertise than anybody in doing that.
So it's staying aligned with sales. If we're not at an RFP yet, what is the right templated content that we should be starting from? Then can we use you to help us customize it with the voice of the customer for this deal, for this problem, so that we're trying to influence that RFP? We're trying to put ourselves into a thought-leader position before that.
I think proposal teams are probably underutilized in how they work on that. Sales teams often try to go it alone at that stage. Only when an RFP rolls in the door do we go, "Now we need help." And maybe it's already too late to get help. We don't know. So getting that assistance earlier, from the people who are really good at articulating those messages, would be hugely beneficial to us.
Christina Carter: Thank you. Kemi, I know you've worked at companies that were in this position before. Now you're a consultant helping companies who are in this position. What would you say to teams working with sales teams who are not using them as well as they could, especially before an RFP comes out?
Kemi Solanke: I think it's a real loss for teams that are divided or highly siloed. It's really important to take a collaborative approach to proposals, because that is the nature of it. You need everybody to input into it. Not only the sales team, to give that customer intelligence, but also marketing and other functions, to help solution the problem you're trying to solve.
If you don't understand the buyer, then you're producing a very vanilla proposal that AI can generate, and that is not going to win the opportunities. So I'm a big advocate of getting involved before the RFP lands, and being involved before you're even qualifying an opportunity in.
That's when you're attending market engagement days, customer buyer days and things like that, where you get so much intel from the buyers themselves. They tell you what their problems are, what their challenges are, and the journey that's brought them to the point where they're looking for a supplier.
If it's only salespeople going there, you're going to get third-hand information relayed to you when you're at your desk trying to storyboard this proposal. Sometimes it's a bit too late, and some things get lost into the ether. So it's really important for sales and proposal teams to be there from the inception.
I've seen a huge difference between responding to a tender where the buyer already knows what they want, and engaging much earlier when they're still defining the problem. You can shape the outcome of what they're asking for, the actual RFP they're putting out there, by having conversations.
Sometimes the conversations you've been having six months before formulate what you're going to put into the proposal as well. Those, for me, are always the strongest proposals. It gives you a stronger opportunity to influence the outcome when you're involved much earlier on, in those meetings with the sales team, absorbing all of that information that you can use to make a more robust, proactive proposal.
So we definitely need to be telling senior leadership and sales leadership that the bid teams need to be involved throughout the whole sales cycle.
Christina Carter: What would you tell a proposal or bid person who isn't a part of those already? What advice would you give them?
Kemi Solanke: Volunteer. In organizations where I was not involved in attending buyer days, supplier days, market engagement days and things like that, I would always put my hand up, because I'm interested to know.
What I would also do quite early on is go through the list of attendees and see what other organizations are there, so that I can formulate the competitive landscape. So I'd be saying it's beneficial, even from an administrative perspective, to have proposal people in those meetings, taking notes and picking up things that maybe the salesperson isn't picking up.
If it's a technical solution, we always think the technical person should be there to ask technical questions and the salesperson should be there. But the proposal person is the person who's going to bring everything together. They have to be in the room.
So I would always say to proposal people, volunteer, even if you're not asked to attend these events or stay behind to schmooze with prospective clients. I always hold my hand up. I'm always the bid representative who comes to the lunch and learn. If there's a subject matter event with key clients after office hours, I will always go along.
The more you build rapport with the buyer, and the more you talk to them about the things they're looking for solutions for, the more you're able to bespoke your writing when it comes to creating these proposals. So I will always advocate for bid and proposal teams to put their hands up and volunteer to be part of the activities the sales team are involved in.
Christina Carter: What I'm hearing is don't be shy. Don't wait for permission. Don't wait until the invite happens. There's data behind this, though. There's a report coming out next week that shows the teams that win the most with RFPs are what we're calling the integrated teams. They are working in lockstep with sales teams before the RFP comes out. So Kemi, you are spot on. The data backs you up.
You talked a little bit about proactive proposals in there. When have you seen proactive proposals shape a deal before a formal process started? And what makes one really effective?
Kemi Solanke: Every process and every deal operates differently. Within IT and tech, for example, there are certain frameworks or marketplaces that buyers can procure from. I've seen that those are the ones with the shorter buying cycle, because you have direct access to them. You're not restrained to be formulaic or to operate through a specific portal. The exchanges are through email, so you have better control over the process.
One of the quickest deals I did this year was when the client said, "Okay, we're interested." The sales team had a series of conversations with them. They had sold a specific solution into them and even negotiated the price.
Unfortunately, there was a change in staffing and management, which meant the deal had to change hands to another salesperson. But what enabled that to be shorter was that I was a consistent person who had been there from inception, who had been brought in on all the meetings and all the conversations. All of those conversations went to form the proposal.
It was a very different process, but it ensured that everything was done very quickly. It was, "Can we have a proposal?" I was able to draft the proposal very quickly because I had been involved in all of the conversations beforehand, and those conversations enabled me to make it as bespoke as possible. Then we were able to pass it through a statement of work type of process, which also made it very quick to get to the money part of the deal.
So that's what I would say. Be proactive. Work with the business development team and the sales team. Be involved in the conversations, because that can shorten the buying life cycle and get you ahead of the proposal.
Christina Carter: When I did a lot of B2B, we would do proactive proposals so we could skip an RFP, which of course shortened the buying cycle. So it works. Exactly what you're saying works. Aaron, how would you want sales and proposal teams to decide to work together on a proactive proposal?
Aaron Swanson: An old saying we've always had in sales is that the best RFP is the one that never gets issued. The reason it doesn't get issued is that you do so well early in the cycle that it becomes almost a sole source, or a smaller audience, where they deem it not necessary to release a formal RFP. I think that indicates you're a really strong fit.
To figure out if you're a strong fit, sales needs to do their job, which is to run effective discovery, understand what the real problem is, and then understand whether we are a match. Are we talking to the right people, the people who are ultimately going to make the buying decision and manage the budget?
Then how do we take everything we learned in discovery? This is one of the things the platform we've built enables: taking all of that knowledge we've gained during the sales cycle and making sure everybody on a team that's going to collaborate on a proactive proposal has it. So we're not sending a stock piece of marketing collateral over to somebody. We're sending a proposal that was written for that specific person, that organization, that problem.
It's tailored to them, so that when they read it, they're like, "Wow, they're talking about me, they're talking about my problem." The reason it sounds like that to them is that we did that discovery and we captured that information well during the cycle.
Then we work jointly as a team, the proposal team and the sales organization, using whatever tools and platforms we have available, to build that proposal in a way that lands with the customer. Hopefully to the point that they go, "This is the right choice for us. We're going to go this way."
That's going to shorten the cycle and reduce the overall effort, because now we're not going out to a formal bid process where we introduce other people, a lot of complexity, unknowns, and probably project delays and decision delays. So capturing that discovery early, collaborating as a team and building something tailored for that customer, in that moment, for the problem they're trying to solve, is how you get in front of that.
Kemi Solanke: I agree with that, Aaron. When you were saying that, I was thinking about one more thing on the other side, which has happened before. There was an RFP that came out and everything about it was written for the incumbent. The tech stack they were asking about was the incumbent's tech stack. The specific examples of experience with the types of organizations they worked with were the incumbent's.
At that point, there's no point in us throwing our hat in the ring, because they've influenced that proposal before it's even come out. There's no point in anybody tendering when it's written for them.
That's why I'm always an advocate of getting ahead with a particular buyer before they're even going to issue anything, because sometimes they have somebody already in mind. For us as bid and proposal people, and for the sales side of things, we've got to listen to the buyer signals as well, and try to build those relationships.
Aaron Swanson: If it does go to bid, you want it to be your language in there. You want it to be your words in that bid, and your influence coming through. And somebody else is going, "I think this was written for the other person."
Kemi Solanke: Exactly.
Christina Carter: I have another question, and it once again starts with data. Gartner found that content relevant to the whole buying group gives three times higher odds of a high-quality deal. The surprising part goes against so much best practice that we learn as proposal professionals: content tailored to individual buyers reduces consensus by 59%.
If you are writing to individual buyers, individual stakeholders who you know are grading and evaluating it, you're probably going to stall the deal and lose to indecision, as opposed to writing to the group as a whole. So Kemi, how do you get your teams to write it to bring the whole group together, rather than please individual stakeholders?
Kemi Solanke: Are you talking about the stakeholders from the buyer side?
Christina Carter: Yes, the buyer side. When they're reviewing. Not writing to them specifically, but as a whole.
Kemi Solanke: That's so important, because each member who's evaluating it has a different concern and a different challenge. They're looking for different things. I've seen this up close. When it gets to a pitching stage, certain panelists light up when you hit on a certain solution they're really interested in. You'll see their faces light up, because you've spoken to the heart of the problem for them.
So it's really important that an inclusive approach is taken when you're drafting proposals, and that you are thinking of each person who's going to be on that panel. The technical questions are answered. You've mitigated any commercial risks. There's a story unfolding there as well.
It's something I'm passionate about advocating: that all the areas are covered when you're bringing all your stories together to formulate this proposal. It is active storytelling, and you've got to have all of those components there. You've got to make sure you're not leaving any stone unturned. Any uncertainties they may have, any risks they may conjure up, you've covered.
That's why solutioning is really important when we do that stakeholder mapping piece and figure out who's going to be in the room and who's pulled this RFP together. You think, who do I need to make sure I've answered all of their questions for? And you cover the evaluation criteria to make sure you're scoring the maximum points as well.
Christina Carter: Aaron, I don't know if you have anything you want to add to that from the sales leadership side.
Aaron Swanson: We have forever been training our sales teams to not be single-threaded in a deal, whether there's going to be an RFP or not. Partly that's because you want a backup in the deal and you want multiple voices. But what you really want is multiple perspectives, so you get a complete picture of the problem, the company, how significant it is and how they envision solving it. That way you're not aligning to a single person's perspective. You're aligning to multiple people's perspectives.
I'll go back again to running good discovery and being in before the RFP, because otherwise you're blind. You need to be there before. Have conversations with multiple people who have different personas or different perspectives in the organization you're selling to.
Then make sure that what you found is communicated not only in the sales team, but across the proposal team who's going to be helping, because they want to help you represent the voice of the customer in the proposal you're sending. So make sure you've got the right conduits in place to give them that voice of the customer. Then the proposal can be tailored not to a single person, but to the entire organization you're sending it to.
Kemi Solanke: I was going to say, sometimes when you're doing your stakeholder mapping and you want to be inclusive of the whole buying committee, what can also unintentionally happen is that it creates confusion, because you have a message for each different stakeholder. So one thing we should be aware of is advocating for one clear, consistent value proposition, supported by evidence, that speaks to the different priorities of those people.
Christina Carter: I hope you listened to that and took notes. If you can get that buyer consensus and put that proof in one story within the proposal, the deals close faster. There's a lot less stalling and a lot less losing to no decision. That is a really important part of getting it to close faster, and it rests on your shoulders as proposal people and capture people, working with the sales team.
One thing I did want to ask you about, Kemi. I won't read out all the numbers anymore, but Forrester did a huge survey and found that we are far less forgiving of claims that don't have proof in them. If you don't prove something, we're not going to forgive you, and we're not going to believe you either.
That stalls deals as well, because usually we'll have a trial period or a pilot period of our service or product, and if it doesn't match up with what's in the proposal, the deal once again stalls or doesn't close. So Kemi, what's your take on this?
Kemi Solanke: I think credibility is everything, and you're building trust. You're building trust from the first conversation you have with the client, before you even start producing proposals. Every discussion is about building trust and backing that with your credibility.
I know every company fudges things a little bit, but you've got to be really careful with that. Ensure that you are backing up claims, that the evidence is there, and that you're using accurate metrics.
Some people get caught out with this. They'll have a case study on their website that says one thing, and then the proposal says another thing. So make sure you're not going to get caught out on whatever you say, and that it's things you can fall back on. You can say, "Look, I have testimonials, we have worked with these people, and this is what happened." Make sure you have stories that are credible.
You've got to be really careful about what types of things you fudge. Make sure that whatever you state to the buyer, you are able to prove and back up with evidence, case studies, testimonials, quotations and stories like that. Once that trust is broken, it's really difficult to get it back.
Christina Carter: Good luck getting that back. But what I've felt in the past is pressure from sales leaders to overpromise. So Aaron, sales leader. If we are getting pressured to overpromise within our proposals, especially now that we are not going to get forgiven for that, what should we do? What's the best way to prove that we shouldn't be doing that?
Aaron Swanson: In the world of AI, people are going to find the answers. They're going to find your content eventually anyway as they research you, because research has gotten easier and easier for them. That proposal is one tool in the overall evaluation that customers are likely doing against you.
So have cohesive messaging. Don't take things too far in a proposal that a customer might debunk without you ever having any idea. Or they might go, "This conflicts," and now you've lost trust. That's a big challenge.
So ensure that you have tools, platforms, or at least knowledge and standard repositories in place that enable that common voice of your business, in your proposals and in how you represent yourself in AI search. I think now we're calling it AEO, like SEO but for AI.
It's making sure the same consistent information is coming up across these different channels that customers are probably going to be evaluating your business through. Whether that's a proposal, going to your website and clicking around, or asking AI to brief them on you as a business and what you do. "Tell me about case studies from that business."
Then as you're building proposals, ensure that when you write a response you're including supporting documentation or supporting links that go back to those sources. Those are the sources they're going to find if they do the research on their own, and it shows that what I'm saying in this proposal aligns with what I'm saying to the world at large. They're going to find the same information in multiple sources.
It's tricky, because there are so many of those things out there. It's a big challenge for proposal writers to keep track of where all those things are and index it constantly. So having appropriate tooling and supporting processes in place to do that is critical. Then the customer sees one cohesive message across the entire business.
Kemi Solanke: When you were saying that, I had a flashback moment. There was a time when we had put that we were thought leaders and that we'd written white papers on sustainability. Then they asked us to send them the links to the things we had.
Aaron Swanson: Uh-huh.
Kemi Solanke: Luckily, it wasn't a lie. We had the links and we had written those. We had been thought leaders in that area. But it goes to show that you've got to back up whatever claim you've made, and you should be able to prove it. I would say evidence reduces uncertainty, and reducing uncertainty is one of the most effective ways to accelerate a buying decision.
Aaron Swanson: Exactly. And if you can do that proactively, as answers are being built for the RFP, if you can go, "Here's the supporting evidence, here's where that source came from," in a way that doesn't take so much time, it adds validity to the proposal. They don't have to go back and ask you for that evidence. It's there.
Christina Carter: We brought up AI and tooling. 94% of businesses are now using AI during their buying process, before they go out to RFP. So what are we doing? Kemi first, then I'll get to Aaron. How should proposal content be structured so it holds up when AI is reading it, grading it and evaluating it?
Kemi Solanke: This is a really important question, because there's been a huge shift in our industry. We're using a lot of tools that are wrapped with AI. A lot of new platforms and products are coming out that look like they want to replace the proposal team. I think it's a new reality. We've got to involve AI to be a lot more productive, but I don't think it means we go away, because you need the human element.
Historically, we've focused on writing proposals that are compelling to human evaluators. Now we also need to consider how AI tools may extract, interpret and summarize our content. So we're going to have to be thinking a lot more about tone.
It will change how we approach the structure. We'll need clearer headings and direct answers. Especially in proposals, where you can sometimes waffle a bit and have a bit of fluff here and there, all of that has to be stripped out. Things like consistent terminology matter. Sometimes at work you start shortening things and doing all kinds of nonsense, so that would probably go out the window. And you're going to have to have evidence that's easy to locate.
So I think it's going to change the way proposal teams write and construct their proposals. If a buyer asks, for example, how we manage information security, the answer should be explicit and supported by the relevant controls and certifications. We shouldn't expect either a human evaluator or an AI tool to search through 10 pages of marketing language to find it.
So we're going to have to be really conscious of how we do this. And I'll say that writing for AI doesn't mean writing like AI. We always have to make sure we have that human insight and that human feel, attached to persuasive storytelling, commercial insight and an understanding of the buyer from our own lived experience, not only from AI scrolling through the internet.
Christina Carter: Aaron, do you have anything to add to that?
Aaron Swanson: Obviously I'm a little biased, because I work for an AI deal orchestration and RFP platform. I could say automation, but for us it's really AI assistance in responding to RFPs. That's what SiftHub really does. I want to address it from two different perspectives.
One is on the buyer side. The buyer's research has moved to AI. They might name the company, or they might say, "Go help me find some companies that solve XYZ problem," and they're going to surface their vendor pool from AI now.
I think in the recent Alphabet earnings release, they talked about search volume starting to go down, because people are moving more search into AI. They're starting to use that as an alternative. And B2B buyers are probably doing that even more, because they want a lot more depth than a search for a basic article is going to give them. They want that content and that analysis: who are the vendors, what are their strengths, what are their weaknesses, what are we seeing. So the buyers are going to arrive a lot more prepared.
And Kemi, to your point, they expect a more tailored response as well. So ensure you're using AI and tooling that can tailor for a different industry. What are people called? What are the different things in the RFP called? Then you're using their terminology in the response, and not generic terminology.
So ensure you have tooling in place that still brings that human element. People are getting much more intelligent about sniffing out AI quickly. When AI has written something, it's formulaic, and you can start to pick it out. When people look at a whole bunch of responses, they notice. I think LinkedIn even has a flag now where you can flag something as AI slop.
I think buyers will flag RFP proposals as AI slop if it's not done well, if there's not a human element to it, if the wording isn't there, or if it feels formulaic.
So make sure you're feeding off of the words the customer said during discovery calls, the tone of the emails that have gone back and forth, what you know about that industry, and what you know about yourself, your own case studies and your own customers. Bring that in, in a tone that matches what they're looking for in the bids they're going to review. I think that's going to set you apart in the future.
So the human element is still going to be there. The tooling has to enable it, because trying to do that manually, at the pace of change we're having with products, literature, case studies and website content, is almost impossible for a person. I think the proposal team will be the puppet master, almost more important than ever, in ensuring that the human tone comes in, even with this really rapid pace of change that AI is going to introduce to the overall process.
Christina Carter: I think that is incredibly true, and I am seeing this across companies. One thing I did want to do is tie this back to how quickly a deal closes. We're seeing that procurement teams are busier than ever. They have more RFPs coming in than they ever have before. So they're using AI to summarize that information and kick people out immediately, and then to score them.
So if you do exactly what Kemi and Aaron said, you're less likely to stall the process or get kicked out, because you can write to both the human and the AI. If you have a 15 million dollar, 15 million pound decision going out, there's no way a human isn't going to be a part of that decision. AI is not going to make that decision for them.
Christina Carter: If a proposal leader or bid leader wants to show sales leadership their team can help close deals faster, what should they start doing?
Kemi Solanke: I think speed starts long before the request arrives. So it's making sure that capture period is happening, whether it's six months before a deal or two years before a deal. They need to be forming a truly collaborative team that's cross-functional, involving all areas of the business, from marketing to finance, from before the RFP lands.
When you're discussing sales strategy and what types of buyers you're going to be going for, the bids and proposals team should be part of that conversation. What deals are being prioritized that year, forecasted deals, all those commercial decisions. Those are the conversations the proposal and bid team should be privy to.
Once they are attuned to those conversations, when the RFP lands, they already have what they need to start. They're not doing that within a deadline. They've pretty much got everything they need.
I think one of the biggest causes of delays in proposal teams is having to recreate information that the organization has already produced multiple times. It does irritate me when some companies want everything produced from scratch. You don't need to do that.
The parts that will be bespoke to the client are one thing. But you have a repository of information for a reason. You have past similar bids. You have a bid library for a reason. You have a proposal library for a reason. Use that, especially from the ones you have won before. Use the content you've already created that has struck a chord with previous buyers. The parts you're going to recreate are the intelligence you've gathered from the conversations you're having about that particular deal.
So focus on having a reliable, maintained content library. That always speeds things up. You'd think that is basic and everyone should have a content library, but not everyone does, and not everybody has a well-structured one. Sometimes, because organizations de-prioritize it, it's a mess, and you spend so much time looking for the metrics and the evidence we talked about.
The second thing I would say is clear ownership within the team. When clarification questions or due diligence requests come in, everyone should know who's responsible, who needs to approve the response and how quickly it needs to be returned. I believe these things can influence shortening that buying cycle.
The third thing would be to distinguish between urgency and importance. Not every request requires the same level of effort or governance. A simple clarification shouldn't take five days because it's going through the same approval process as a multi-million pound commercial commitment.
We've already spoken about AI, but everybody is using it now, and I hope there's no resistance to using technology to help the productivity of the buying cycle. It can help retrieve information from the copious documents that are sent regarding the deal. With human interaction, it can also help draft the responses.
Touching on what we said, although what AI produces can be formulaic, you can have it write in your tone of voice. So it's always a layer on top of your human interaction. Write a draft, refine it, look at it again, review it, refine what AI has produced.
I always tell the teams I've managed: don't ever take something that's come straight out of AI and stick it in a proposal or a tender response. Do not do that. It has to have that human layer of review and iteration involved in it. What AI does is help you get to that first draft quicker. Then you iterate it and add your tone of voice.
I was reviewing a proposal that a particular growth person had written, and as I was reading it, I read it in his voice. It was his voice I was hearing in my head. It sounded like him, the way he wrote it. And he was somebody who knew the buyer inside and out. He knew what they cared about. It was written for them. So tone of voice is really important, but AI can help you do things a lot quicker, so still use it.
For me, the goal is to build a proposal function that's responsive, commercially aware and capable of moving at the speed of the opportunity, but without compromising on quality.
Christina Carter: Absolutely. And I think once you do those things, it's inevitable that the time to close is going to shorten. Aaron, from a sales leader point of view, what would you want your proposal and bid teams helping you to do to close that deal faster?
Aaron Swanson: First I want to highlight one thing I heard from Kemi, which is that content library concept. I think it's like cleaning your house. If you do it every day, there's not much to do and you can keep it pretty clean. But if you let it go a week, it gets unruly, and all of a sudden the task gets substantially harder. Then you look at it going, "Now I have to dedicate a whole bunch of time to it."
This is one of the areas where good tooling has come a long way. There used to be some old ways of managing content libraries that took a lot of work. Now, with information spread across more systems, finding tooling that can help you aggregate that information across all those systems and make sense of it, understanding what's new, what's old, what's been used in the past, what's worked and what's not worked, is critical for building proactive proposals, for RFP responses, even for answering basic questions back to customers. That also drives consistency.
Specifically on how proposal teams can help close deals faster, I think there are two key things. They're almost bookends on the opposite ends of the deal.
One, I think having proposal teams sit in a forecast call or pipeline review call from time to time would be really advantageous. It would help them have more perspective on how sales views deals and what's going on. Or they can call out if they see a gap in the way we're thinking about a deal in the early stages, so we can take it further or in a different direction before we're getting ready to write a proactive proposal or respond to an RFP. So influence the deal a little bit earlier, and help bring another voice to the room.
On the opposite end is making sure we're really effectively doing win-loss analysis. When we won, what did it look like? When we lost, what did it look like? And effective debriefs on RFPs afterward, to review what went well in the process and where we could do better, in terms of the project management, timelines for responses, reactiveness, all of those things.
RFPs used to be issued for weeks or months. I think most companies are now assuming you've got some kind of tooling to help you respond more quickly. As one of those tools at SiftHub, we hold the bar really high for ourselves. If we get an RFP, we believe we should be able to respond to it within days, not weeks.
Usually they're going to be evaluating us as a tool for themselves, so if we're able to respond to an RFP faster, it's proof in the pudding. We responded quickly with a very well-composed response because we're a platform and tooling that enables that.
So thinking early about how to form the deal, helping the sales team form the deal, and doing debriefs on why you won, why you lost, what went well and what didn't, enables you to move more quickly when that RFP hits. Your responses are going to land with that customer when they read them. It's going to sound like it's in their voice. It's going to sound like it's solving the problem they articulated to you.
That end-to-end flow, and using that feedback loop to then move more quickly with the high quality customers expect, is critical. So I would say involving them more in the deal cycle, and doing really thorough debriefs and win-loss, would be the two things. I know you asked for one. I can't do that, so I'm going to give you two.
Christina Carter: That's totally okay. We have really good questions and I do want to get to them. We have the wonderful Chris Renardo. She asked: "I feel the number of stakeholders involved and the complexity of an RFP are inversely proportional to the revenue potential of the deal." So this is for you, Aaron. How can we convince you, a salesperson or sales leader, to push back on resource-intensive RFP processes when the expected deal value is fairly low?
Aaron Swanson: I think deal qualification is as important as ever. Throwing stuff across because you can doesn't necessarily mean that you should. Basic qualification still applies. Are we a fit? Have we had access to an economic buyer? Do we have a champion who's advocating for us? Were we involved before the RFP hit the street or not?
If we don't check any of those boxes and we're still talking about responding, I really want to know why. What is the compelling reason why we should do that?
I do think the temptation is there, as things become more automated, to throw more stuff across because we can. Maybe if you fully automate things, you can do that, and even if you get a five percent hit rate, maybe it's worth it. But it feels like a big distraction to me, and I would need to be convinced that it's worth the effort. Deal qualification is still real. Understanding where you sit in the deal is real.
I have one firsthand experience with this, where we got a cold RFP. This was a few years ago, and I won't name the companies. We read through it and we caught specific language that was obviously tailored to one of our competitors.
So we wrote back and said, "Unfortunately, we reviewed your RFP and it appears it has been written for a competitor of ours. We recognize some of the terminology. We appreciate the opportunity to bid, but we're going to politely decline, because it looks like you've already made your decision and this is a formal procedure to buy that product."
They called us. We had a conversation and they said, "No, no decisions have been made." We said, "Well, we think it's been made for," and we named the vendor we thought it was made for. They said, "Absolutely not. We have not made that decision. We really want you to bid." With that clarification, we said okay. So we did, and we won it.
But I still think if we hadn't had that interrupt in the middle of the process and had that discussion, I'd almost guarantee we wouldn't have won it. So sometimes it's having that check to make sure it's qualified. If it's not, it doesn't always mean you don't bid, but you probably need to do something a little bit different and have a real conversation about how you address it before you do.
Christina Carter: Saying no is so powerful. I can't agree enough. Kemi, this one is for you. This is from Doug: "B2G deals include a lot of 'Yes, we all agree, we are ready to sign and there are no pending actions. Might be next month, maybe.'" We've all been there. These clients are in no rush. Any specific ideas for this scenario?
Kemi Solanke: Unfortunately, it's chase. That's all you can do in that situation. As bid teams, we are well versed in chasing on the portal messaging after the deadline date has passed. "When are we going to find out who this is being awarded to?" They'll say, "We're still evaluating at the moment," or they'll have a reason why things have gone over the timelines they published.
It's part and parcel of what happens sometimes. You have procurements that follow their timelines to a T, and then you have others that roll on and roll on. It could be issues beyond their control.
For example, there was one we had written off. We were like, "What is going on with these people?" It was an NHS trust, and they were not answering us. Every few weeks we would go on the portal and say, "Hi, we want to find out what's happening with this opportunity." And they would say, "We're still reviewing, there are some internal things going on."
We found out there had been a change in governance and in the leadership involved in the original tender. They came back and said, "We really liked your tender, but there have been changes in the budgets. A lot of different things are going on at the moment. We would like to award you something, but we might have to renegotiate and re-discuss what was put out in the original procurement."
So we started having a series of discussions with them, and eventually they awarded us the opportunity. But it was a slightly different scope of work, and it wasn't the same value we had originally bid for.
I guess the moral of that story is that it's not always them dragging things along for no reason. There could be some red tape and internal things they need to overcome to be able to award the contract.
So I would say, as bid and proposal teams, continue chasing the client. What that means is you're in there, at the forefront of their mind. If you let it go and say, "We haven't heard anything, and that's it," you lose that. The person who keeps chasing and keeps reminding them "We're still here" is at the forefront of their mind when they're reading through the proposals.
So do chase, do reach out. But when it comes to government bidding, follow the rules and regulations and do it on the portal. Don't do it through email or any other way. They like having chain records, and they won't even respond to you if it's through any other platform. So stick to the rules, but do keep engaging them.
Christina Carter: Kemi, Aaron, thank you so much for your expertise. I appreciate it so much. Where can people find you, in case they want to talk to Kemi a little bit more or talk to Aaron a little bit more?
Kemi Solanke: Find me on LinkedIn. Kemi Solanke, it comes up as Kemi S, fractional bid strategist. So look me up and add me on LinkedIn. My website is www.learnbids.com. Those are the two avenues.
Aaron Swanson: For myself, LinkedIn, of course, Aaron Swanson. I'm fairly easy to find. Feel free to email me, I'm Aaron at SiftHub.io, and SiftHub.io is our website. Feel free to take a look over there at how we try to help proposal teams automate and make that process more efficient, while still maintaining highly personalized content as we do it.
Christina Carter: I hope you enjoyed that. We really got into so many details from a sales leadership perspective and a proposal leadership perspective. Combine those two, and you have a powerful set of ways that you can help your team shorten the time to close.
And of course, make sure that you tell your sales leader exactly what you're doing, so that you can get the recognition your team deserves. Don't be quiet about it. Be loud about what you're doing to help the sales team be successful, so that they know you are that strategic, revenue-generating force that you are. All right. See you next week.