Connect, learn and strategize at Responsive Summit 2023. Also, check out the blog about our rebrand.

THE RFPIO BLOG

Start Responding Like a Pro

The RFPIO blog is full of insights and best practices, giving you the tools you’ll need to streamline your process and respond with confidence.

Build an RFP response database to answer faster & win

Build an RFP response database to answer faster & win

Building an RFP response database centralizes your knowledge and improves future responses. Explore this how-to guide to learn best practices and get started today.


Category: Tag: Knowledge management process

Build an RFP response database to answer faster & win

Build an RFP response database to answer faster & win

When it comes to answering requests for proposals (RFPs), efficiency is essential. Unfortunately, if you’re like many of your peers without an RFP response database, getting proposal answers is likely difficult and tedious.

In fact, you likely spend countless hours looking for previous proposal content or waiting for subject matter experts to rewrite RFP answers from scratch. Consequently, one of the most important skills required for successful proposal management is RFP knowledge management. Indeed, whether you respond to five RFPs per year or 100, finding reliable information quickly saves you and your team time and frustration.

In this post, we’ll explore how to create an RFP answer library by leveraging knowledge management best practices. To start, I’ll share the basics of knowledge management and how they apply to RFP content and proposal management. Next, you’ll learn the steps to build and maintain your own RFP knowledge library. And to conclude, I’ll offer an overview of some of the benefits and value you and your proposal team can expect to receive from applying knowledge management to your RFP response process.

Proposal knowledge management basics

What is knowledge management?

There are dozens of definitions of knowledge management, but Gartner summarizes the term best saying:

“Knowledge management (KM) is a business process that formalizes the management and use of an enterprise’s intellectual assets. KM promotes a collaborative and integrative approach to the creation, capture, organization, access and use of information assets, including the tacit, uncaptured knowledge of people.”

Knowledge management is a relatively new practice among businesses. However, the value of the approach is immediately obvious to anyone who has spent hours searching for information. In fact, according to KMWorld, the cost of looking for information is significant: 

“Knowledge workers spend from 15 to 35 percent of their time searching for information. Searchers are successful in finding what they seek 50 percent of the time or less.”

Companies create massive amounts of data on a daily basis. For example, every customer email exchange, invoice, policy document and sales proposal contains information that is vital to the operation of your business. And without a system to save, organize and find that information again, all potential value disappears.

Indeed, time spent searching for information unsuccessfully or recreating knowledge that already exists represents a significant financial cost to your business. Consequently, the goal of knowledge management is to increase efficiency and productivity by making information readily available to those who need it.

Applying knowledge management to the proposal process

While we all know that every RFP is different, it’s also true that there is a significant overlap in the information requested in most RFPs. Our customers often estimate that 60-80 percent of the questions asked in the RFPs they receive were answered at least once already. So, when applied to the proposal process, knowledge management saves, centralizes and organizes those RFP answers for future use. 

In addition, saving and storing RFP data enables you to uncover customer trends, predict future opportunities and explore how variations of answers perform.

Where to store RFP responses

So, where does all of this proposal content end up? Hopefully, in a searchable, centralized, cloud-based RFP response database. Your business may call this database a request for proposal library, content repository, body of knowledge, RFP answer library, RFP knowledge base or some combination of these terms. Regardless of what you call it, this is where your RFP responses live, from your company boilerplate to your list of competitive advantages.

RFP response database software options

Before you can begin building your proposal content repository, you have to select a solution to host it. There are two primary options: an editable shared document platform (Google Docs, Google Sheets, Sharepoint) or RFP software designed for proposal management. Both options offer a centralized location for real-time collaboration with subject matter experts as they create new RFP answers. In addition, both solutions are searchable and provide options for organizing. However, shared document platforms aren’t designed for knowledge management and will limit the efficiency of your RFP process.

Certainly, there are pros and cons for each option, and selecting the right option for your team will depend on a variety of factors. However, you’ll find the primary differences are capabilities and cost. 

If your organization wants to respond to more RFPs by improving efficiency as part of an RFP strategy, proposal management software delivers a strong return on investment (ROI). On the other hand, with some creativity and patience, you can manually manage your knowledge base in a free shared document platform.

Knowledge management features in Responsive:
  • Real-time SME and stakeholder collaboration
  • Categorization tags and account hierarchies
  • Individual user roles and permissions
  • AI-powered search with filters
  • Fully auditable change tracking
  • Duplicate identification
  • Automatic Content Library review cycles
  • Task management and workflow tools
  • Bulk knowledge import and export

How to create an RFP response database

Gather previous proposal content

The first step of building your knowledge base is to gather RFP question and answer pairs from previously completed proposals. Hopefully, some of this information is already digitized and ready to go. You may be tempted to only use RFPs that you won, however, it is beneficial to include as much data as possible.

Decide how you will organize and tag your data

To make your proposal content truly useful, you have to be able to find it quickly. This is where the organizational piece of knowledge management comes into play. Consider how you would categorize each question and its corresponding answer. Also, consider who should have access to what information.

RFP response software uses tags to catalog important aspects of your information. For example, you may use tags to segment knowledge by the industry it addresses, the region it’s applicable to or the section of the RFP it applies to. In addition, the software enables you to easily create account hierarchies to limit a user’s ability to view and edit sensitive information.

Review, update and refine

Now that you’ve collected and labeled your data, it’s time to review it before uploading it to your RFP response database. Start by locating duplicate questions and answers. Then, decide which version of the answer is your go-to response. Factors to take into account include deciding which answer is part of more winning proposals as well as how recently the answer was written or updated. 

After you’re done removing duplicates, review the question and answer sets. Look for any information that is no longer relevant or needs updates. While reviewing all this information may be tedious, it’s important. Your knowledge base can only deliver value if it’s accurate.

Conduct training

One of the biggest factors that determine the success of RFP knowledge management is buy-in from users. While most RFP response database software is very easy to use, hosting tailored training sessions will save you time in the long run. 

Indeed, your sessions should certainly cover search functionality and how to revise out-of-date content. In addition, your team must establish parameters for when to create new knowledge records and which tags to use. Don’t forget to also update any supporting process documentation to reflect the changes.

Seek feedback and optimize

A successful RFP response database is continually growing, changing and evolving to better serve your organization. Ideally, you will consistently update records and add new information as you encounter new RFP questions. Typically, we recommend setting general review sessions at least twice a year to solicit user feedback, review usage and ensure content consistency.

Benefits of creating an RFP response database

Applying a knowledge management approach to RFP answers delivers benefits and solves several common proposal team challenges. 

Stop wasting time searching for proposal content

We all know the old feeling. The sense of deja vu that comes when you read a question you’re sure you’ve answered before. Then you spend time searching through emails, notes and old RFPs to find it. Eventually, you give up and send the question to the subject matter expert who answered it last time, begging them to write it again.

However, with a well-organized knowledge library, your answers are easy to find. Simply conduct a keyword or question search, pick the best answer, and move on with your life. A recent review on G2 described the impact of their knowledge library saying:

A single content repository, combined with automation and project management tools, makes responding to even the most complex RFPs easier. Having a single storage of RFP-driven work that is tracked and easily referenced makes management happy, and our sales teams know how to engage with the bid & proposals team.

Make life easy for your subject matter experts

Working with subject matter experts isn’t always easy. They’re busy. And, just like you, they’re tired of answering the same questions over and over again. 

With a knowledge library, you can use the catalog of existing RFP responses to complete as much of the questionnaire as possible. Then, send any remaining questions that require input to the SME. As they answer new questions, your knowledge library grows. Subsequently, you can complete more of each RFP on your own.

Improve your proposal team’s consistency

We all know that asking two people the same question will probably result in two very different answers. Likewise, an RFP question that has been asked a dozen times may have a dozen answer variations. 

Luckily, a knowledge library serves as a single source of truth for your proposal team. So you only find the best version of each answer. In addition, proposal managers become more confident that the proposal is accurate.

Decide to bid or not to bid in less time

When considering whether to bid or not to bid on a new RFP opportunity, the time required to respond is always a factor. With an updated knowledge library, you can gauge how much new content is required and how much you can reuse. As your collection of responses grows, you’ll be able to take on more proposals in less time.

Conclusion

For organizations focused on growth, efficiency and productivity are key. Consequently, every minute you spend searching for information or recreating existing work represents wasted resources. And, for proposal managers, the lost time results in missed RFP opportunities.

Luckily, a well-managed RFP response database delivers accurate information to the right person at the right time ⁠— maximizing the value of your time and expertise.

Company wiki: How to decide if it’s right for your business

Company wiki: How to decide if it’s right for your business

A prospect sends over a question and you know you’ve answered it before. You already took time getting the answer just right. Now you either have to dig through old emails and notes, or try to recreate that answer. Either way, you’re wasting time duplicating work.

That’s frustrating from an individual perspective, but consider how many other employees have gone through this exact same process—some for that same question. In a recent analysis, Asana found that employees spend over four hours a week on this kind of duplicate work.

One way to get some of that time back is a company wiki.

What is a Company Wiki?

A company wiki, sometimes called a corporate wiki or business wiki, is a type of software that serves as a central repository of company knowledge. It works much like Wikipedia, the most widely known wiki example, in that anyone in the company can contribute. Employees can add articles as new information arises and questions come up, and can edit the information already there to improve accuracy.

54% of professionals said they spend more time searching for documents and files they need than responding to emails and messages. Wakefield Research

4 Benefits of a Corporate Wiki

1. It saves time.

Every minute an employee spends on a work task is one the company’s paying them for, so efficiency matters. In a survey by Wakefield Research, 54% of professionals said they spend more time searching for documents and files they need than responding to emails and messages. A wiki gives employees a faster way to find the information they need, giving them back time for work that’s more valuable.

2. It makes knowledge creation democratic.

Anyone at the company can add information to the wiki, or update an article to improve accuracy. A wiki isn’t a top-down approach. Information about products, processes, and common customer questions can come directly from the people whose jobs are most connected to that knowledge.

3. It enables knowledge sharing.

Someone in your company has written the best possible response to a common question. That response shouldn’t get lost once they press “send” on an email. A wiki allows you to capture every valuable piece of knowledge someone in the company produces so that others can take advantage of it.

4. It supports employee onboarding.

Finding the right candidates is always a challenge, but harder in 2022 than usual. When you find the right hire, you don’t want to lose them. Yet many companies fail to start the relationship right, with 58% of respondents in a Nintex survey saying they’ve encountered broken onboarding processes. 55% specifically mentioned issues accessing the tools and documents required to do their jobs. A well organized wiki collects the main training materials they need in one place so they can start doing their jobs faster.

How Can Companies Use a Company Wiki?

A company wiki can benefit employees across departments. For the customer support team, it provides a central repository of the best responses to common customer questions and issues. For the sales team, it can be a good place to store up-to-date sales enablement materials that make it easier to close deals. And as already mentioned, it’s a great place to keep the information that new hires need to get up to speed during the training process.

Go Beyond a Company Wiki: Get an Internal Knowledge Base

While a company wiki can offer a lot of benefits, it’s not necessarily the best tool for the job. You can get everything a company wiki offers and then some by investing in an internal knowledge base.

A good internal knowledge base offers:

  • Knowledge management features – Recording knowledge is just one part of the equation, you also need it to be easy for the right people to find when they need it. An internal knowledge base has features to aid in organization and findability, such as tags, collections, custom fields, and advanced search functionality.
  • Official department-specific content – There’s a downside to the democratic nature of wikis. When anyone can edit a page, you could end up with information that’s inaccurate or outdated. With an internal knowledge base you can make sure that all information is pre-approved by the right experts, and also organize it by department so employees can find the right information for their needs.
  • Top-level security features – A knowledge base software that promises high-level security features is one you can use for sensitive content like proprietary knowledge and legal information. And if it offers user permissions, you can make sure employees only have access to the information they need, keeping internal data more secure.
  • Collaboration features – A knowledge base with collaboration features allows you to communicate in the same tool where the information lives. Employees can tag each other and add comments.
  • Broad compatibility – An internal knowledge base that works seamlessly with all your other main tools will be much more useful (and more used). You can easily pull in content you’ve already created, and ensure employees can access knowledge from the tools they already spend their time in, like Slack, Google Chrome, and Microsoft Office.

RFPIO promises all these features to aid in knowledge management, and goes a couple steps further. It uses AI technology to make finding information the moment it’s needed even faster, and makes your proposal team’s lives easier by automating much of the proposal process. Additionally, you can give all frontline responders access to your company’s best knowledge in RFPIO’s Content Library with RFPIO LookUp. Using RFPIO LookUp, they can securely search your Content Library without having to toggle out of their browser or CRM.

All of that adds up to more knowledgeable employees, countless hours saved, and a higher win rate on sales and proposals. To learn more about how to gain those benefits, set up a demo today.

How to clean up your RFP Content Library with a 3-step content audit

How to clean up your RFP Content Library with a 3-step content audit

It’s time to show your RFP content who’s boss. And, yes, a healthy content library does more than just keep you sane. It also streamlines your RFP response process. Note that I say “RFP”, but I really mean any kind of complex questionnaire… RFIs, Security Questionnaires, DDQs, VSAs, you name it.

If you’re already working with RFP automation software like RFPIO, a healthy Content Library means answering 70-80% of your RFP with one click (hello, Auto Respond!).

Even if you haven’t upgraded to RFP automation software yet, refreshing your content library means you can bring relevant content to your fingertips and respond to a vast majority of RFP questions at the drop of a hat.

The good news is that an RFP content audit isn’t nearly as scary as it sounds. Read on to learn how to conduct your content audit in just three steps.

RFP content audit step 1: Complete an ROT analysis

ROT stands for “Redundant, Outdated, and Trivial”. A smooth-running live RFP Content Library only contains the most recent, relevant, and accurate information. That means your job is moving redundant, outdated, and trivial content into an archived folder.

Redundant Content: Duplicate and/or similar content. If you’re using RFPIO, run a duplicate report on questions and answers, and click on “View Similar Content” to find comparable responses.

Outdated Content: Expired or sunset content. Isolate any content not used in the last year (let’s call that “expired content”) using the Advanced Search function in RFPIO. Then, identify content from products, services, and solutions that are no longer relevant (we can call that “sunset content”) using tags and/or product names.

Trivial Content: Deal- or client-specific content. Identity trivial content by searching for specific client names.A step-by-step guide to completing a content audit in RFPIO

RFP Content Audit Step 2: Move content out of your active RFP Content Library

Once you do your analysis, you’ll want to move that content out of your active RFP Content Library.

You have two options:

Option 1: Delete it (scary)

Only delete content that you’re sure you’ll never, ever need again. There’s no turning back from deleted content.

Option 2: Warehouse it (less scary, and my preferred method)

Isolate your content and store it in an RFPIO Archived collection. If you’re not using RFPIO, make sure warehoused content is stored in its own location so it doesn’t get confused with your live content.

You can still access warehoused content. You’re still able to bring it into a live project, update it, and push it back into the active RFP Content Library. If you ever find out you need a piece of content that you’ve archived, you don’t have to start with a blank page.

RFP Content Audit Step 3: Set up owners and review cycles

All content in your RFP Content Library should have an assigned owner. The content owner should be the Subject Matter Expert (SME) who is responsible for the accuracy of the answer.

You should also add a moderator, who is responsible for giving the final “white glove” review. The moderator should apply editorial standards to each answer that comes through, ensuring everything that is pushed to the live RFP Content Library is polished.

How often should you conduct a review cycle?

Well… that depends on the content.

For corporate content, I recommend conducting a review cycle every 90 days. Corporate content refers to any content relating to the company as a whole, like number of employees, revenue, mission statements, etc.

For product content, conduct a review cycle every 6-12 months, or anytime a product release occurs. Product content refers to anything related to specific product features or functionalities that change over time.

As far as evergreen content… you might be surprised to learn it isn’t quite as evergreen as you would imagine. Evergreen content is the core content you use to complete most of your RFPs, and you should still review it once every 12-24 months.How often should you conduct a review cycle? It depends on the content.

A healthy RFP Content Library creates benefits across your entire organization

As you’d expect, a healthy RFP Content Library enables your proposal team to quickly complete RFP responses—answer 70-80% of a proposal with a quick click using “Auto Respond”.

When you can automatically respond to those commonly-seen questions, that means that your team has more time to focus on tailoring each response to your customers’ specific needs.

A healthy RFP Content Library also makes life easier for your SMEs—as I explained in a previous blog, the number one rule of working with SMEs is respecting their time.

When you keep your Content Library impeccably clean, your SMEs don’t need to verify content outside of scheduled review cycles. They’ll have more time to focus on their other job functions, and you’ll have an Content Library full of the most accurate, up-to-date content. Everybody wins

You may think that auditing your RFP content is just a luxury of enterprise companies. I’m here to tell you that anyone and everyone can (and should) regularly audit their content, regardless of whether your team has one person, or 100.

If you’re working with a one- or two-person team, follow the steps above to keep your content fresh. Make sure your SMEs understand which content they’re responsible for, and get in the habit of updating content at the appropriate time.

If you’re a larger team, hire a dedicated content manager whose sole focus is keeping your RFP Content Library healthy.

Show your RFP content (and your RFP response process) who’s in charge

You have the tools to complete a successful RFP content audit. It’s time to put your newfound skills to the test!

If you get stuck along the way, check out my webinar below. I’ve demonstrated my step-by-step process for conducting a content audit in RFPIO.

For those of you not using RFPIO to automate your RFP response process, but want to learn more, schedule a demo! Someone on our team would be more than happy to show you the ins and outs of the platform, and see if RFPIO makes sense for your process.

See how it feels to respond with confidence

Why do 250,000+ users streamline their response process with RFPIO? Schedule a demo to find out.