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.

Thank you for subscribing.

Something went wrong.

Business proposal example, template, and how-to instructions

Business proposal example, template, and how-to instructions

Before I get into the business proposal example, template, and tips, I need you to remember one thing: You’re Yoda, […]


Business proposal example, template, and how-to instructions

Business proposal example, template, and how-to instructions

Before I get into the business proposal example, template, and tips, I need you to remember one thing: You’re Yoda, not Luke Skywalker:

“Think about Luke Skywalker and Yoda in Star Wars. When Luke meets Yoda, he encounters the perfect guide. Yoda understands Luke’s dilemma and has mastered the skills Luke must develop if he is going to defeat the Death Star.”
Donald Miller

As the writer of a business proposal, you want to come off as the perfect guide. Your goal is to make your prospect look like Luke Skywalker, the hero of the story. The prospect doesn’t care about your product; they care about solving their problem.

What is a business proposal?

Put simply, a business proposal is your solution pitch to a prospect’s business problem. It’s you saying, “I understand your problem. This is what the situation will look like after it’s fixed. Here’s a few ways we can help you fix it. Sign here to get the solution rolling.”

It’s used often, especially if your prospect isn’t the only stakeholder involved in deciding whether or not to buy your solution. In such situations, the business proposal is the document that your prospect will share with those decision-makers. Jeff Bloomfield, sales coach and author of NeuroSelling, says, “They need to know that they are saving money with your solution when compared to the high cost of the problem you are solving.”

As succinctly as possible, you need to tell the story of how your solution will help your prospect look like Luke Skywalker. That’s not much room; the opening scroll in all the Star Wars movies takes up more than two pages.

A business proposal is brief, yet informative and customized to every prospect’s specific problem, even if you only have one solution. Remember this is about their needs rather than your features. To put it another way, it’s the photo negative of a brochure or website.

How to write a business proposal

Arguably the most important step when writing a business proposal takes place before any writing begins: Confirm interest in your solution. Odds of winning deals from unsolicited business proposals are multi-state lottery-level. Any effective business proposal starts with a conversation.

When you understand objectives and have a solution, then you can begin writing. If after identifying the prospect’s pain points you believe that your solution isn’t strong enough, then keep digging for the pain points where you can excel. Sometimes you have to push to get the right objectives to make sure there’s enough pain to justify your solution.

Timing is essential because a business proposal needs to be educated and comprehensive. Too early and it’s going to land on deaf ears. Too late and either someone else solved the problem or you’re perceived as not caring enough to make it a priority.

As soon as you’ve identified pains, objectives, and how to position your solution as the ideal, then gather the following content:

  • Logos (yours and prospect’s)
  • Pricing options
  • Scope of work collateral you can link to from the business proposal

Now you just have to complete the business proposal template. These business proposal best practices will help.

8 business proposal best practices

  1. Take advantage of “title” real estate. As my esteemed colleague Keith Norrie explains in his expert advice on executive summaries, the title is too good of a setup opportunity to pass up. Use an action verb to surface the primary problem that you’re proposing to fix with your solution. The following power-verb examples will perk up stakeholders’ ears: increasing, reducing, accelerating, improving, streamlining, monetizing… Check out the business proposal example to see how I framed the solution in the proposal.
  2. Agree on 3-5 objectives with the prospect’s champion during your initial calls. These objectives will be based on pains that your prospect wants to overcome.
  3. Explain how your solution will enable these objectives. This isn’t an opportunity for you to list product features—most of which the prospect won’t care about. It’s where you tie solutions to problems. For example: “RFPIO’s AI-enabled Answer Library will reduce XYZ Company’s time spent responding to repetitive questions from 1,200 hours to 720 hours or fewer annually for an equal number of submitted RFPs.”
  4. Give multiple pricing options as a checkable list. Avoid line-item detail. Explain the difference between each option. For example, “This one allows you to scale…this one gets you to the end of the year…this one is best for small businesses…”
  5. Provide a high-level scope of work specific to the prospect’s need. Link out to data sheets or websites for more information.
  6. Include a call to action, preferably a signature request. At the very least, schedule a call to review next steps.
  7. Review the proposal with the prospect over the phone or through video conferencing. If possible, try to get the person you’re really building the proposal for (the decision-making stakeholder in the shadows behind the prospect champion) to join the review. If you can’t schedule a review, then record a Vidyard of you walking through the business proposal that can be shared with stakeholders.
  8. Be careful of jargon. Every industry has its unique terminology, but be wary of using jargon for jargon’s sake. With only two pages, you don’t have any room to waste on hollow language that doesn’t address the prospect’s specific problem.

Download your business proposal template & business proposal example

Here are the business proposal template and the business proposal example. When you’re ready to write your own business proposal, make a copy of the template. Then, delete all the instructions as you complete the sections. That way you don’t accidentally fire off a document complete with my tips and tricks. Also, if you build your business proposals from Salesforce, then these tips on Salesforce Proposal Builder will be a big help.

I hope you find the template and example helpful. Remember, the decision-making stakeholder (likely an executive) will be reviewing multiple proposals. They should be able to look at yours and identify that it’s comprehensive and customized for them. They’ll sniff out cookie-cutter treatments immediately and will sideline them while they look for something unique, like yours.

Be confident. This isn’t a shot in the dark. The prospect needs to solve this issue. Your business proposal will illustrate how you’ve thought through their problems.

Bid & Proposal Conference Denver: Key Takeaways

Bid & Proposal Conference Denver: Key Takeaways

We just returned from 3 jam-packed days in Denver, Colorado—and we’re still buzzing from all the excitement. There’s just something so special about having real conversations with people in person. Although, remembering how to talk to people was definitely a bit of a learning curve.

In short, APMP’s 2021 Bid and Proposal Conference in Denver was great. It was held at the Gaylord Rockies—an absolutely gigantic hotel outside of Denver, complete with a waterpark. If anything, nobody was complaining about not getting their steps in.

I’d also like to call out what a good job APMP did with COVID precautions. Attendees could order a COVID test to come to your house right before the conference. And everyone needed to submit a health screening form and get their temperature taken before the day’s activities began.

Learning and growing

BPC did not lack in informative sessions. With more than 40 sessions over three days, we definitely left with far greater insights than we came with. Here were a few of our faves:

How to use FBI hostage techniques to get what you want from other people

This session was a huge hit—to the point that people had to stand in the back in order to sit in.

And the speakers, Adele Cehrs and Chip Massey, made some brilliant parallels between the job of an FBI agent and the job of a proposal professional.

When an FBI is in a hostage negotiation, they need to connect with the fugitive. So they approach the situation from the fugitive’s point of view. A good FBI agent will say: “I know what you’re going through. You’re looking over their shoulder, thinking something’s going to happen, you can’t trust anyone… You know you’re going to be brought in eventually. I’m here to help.”

If you looked at things from an FBI agent’s point of view, they’d just say, “Listen, I need to bring you in. So come on.” That’s not very convincing.

Proposal professionals are doing the same thing. They’re understanding the situation from the buyer’s perspective. What is their pain? Why are they seeking the solution? How can you help?

These are all questions a good proposal manager will ask themselves.

Bid Responsibility: Effectively Partnering with the Sales Team

The CEO of Patri, Josh Ellars, started off this presentation with this slide.

After this slide was shown, I imagine everyone in the audience mentally said, “Looks about right.”

A stark difference in headcount isn’t the only thing that’s disconnected between bid and proposal teams. In this presentation, Josh explained what else is missing—and what you can do about it.

Exploring the Future of Response Management

In this session, RFPIO’s very own CEO sat down with the President of APMP, Rick Harris for a “power half hour” coffee. They talked about everything under the sun, including where response management came from, where it’s going, and how the relationship between AI and humans will continue to evolve.

This was a well-attended session that saw lots of audience participation where people were able to interact with Ganesh. It was a really fun session to watch!

Managing the Changing Landscape of Response Management

Change is hard, but necessary. Because the risk of staying the same is much greater than the risk of accepting change.

In this session, Angela Earl, VP of Global Marketing at RFPIO, talked about how response management has changed over time—especially over the last few years.

At the same time, buyer’s expectations are changing. Buyers expect providers to know who they are, what interactions they’ve had, and where they are in the decision-making process. Prospects want to be heard, not herded.

Networking and reconnecting

BPC Denver was absolutely a chance for everyone to regrease those socializing wheels, dust off your electric magenta blazer, and get back out into the world of interacting with people in real life.

Luckily, APMP made networking and reconnecting easy. Here are some of the activities we enjoyed:

Regi-ception

We kicked off the conference with a “Registration + Reception” combo. This helped jumpstart everyone’s socializing skills and get everyone excited for the days ahead. RFPIO sponsored

THE TARA

“TARA” stands for “The Art of Reconnecting Annually”. And APMP did not disappoint. They had a ton of great food (the truffle mac n cheese was my personal fave), a VW bus photo booth, cornhole, ladder ball, and shuffleboard. It was a lot of fun!

RFPIO Booth

To honor the weirdness of the last year and a half, we were giving out some fun, practical SWAG at our booth—hand sanitizer and notebooks.

We also had a lot of fun with a photo booth! Anyone who took a photo at our booth would be entered into our raffle to win a $100 Amazon gift card. We only had four lucky winners, but a lot of wonderful entries!

On Day 2, I felt like everyone could use a bit of a pick me up… so I hyped up the music a bit. And it worked like a charm. As soon as I put on “We Will Rock You” by Queen, a group of people started stomp-stomp-clapping. And to honor their impromptu-ness, Angela, our VP of Global Marketing, gave them all impromptu raffle tickets!

Chapter of the Year: APMP India

Finally, I want to give a shout out to APMP India for winning Chapter of the Year award! This award honors the APMP chapter that demonstrates excellence in chapter sustenance and development through support of APMP initiatives.

Nice work, APMP India! 🎉

Looking forward

After all the fun we had at BPC Denver, we immediately checked when BPC 2022 would be. It’s already scheduled for May 22-25, 2022 in Dallas.

If you’re interested in more APMP events, make sure to register for their upcoming webinar, “How Proposal Teams Can Drive Sales Productivity and Improve Outcomes.” Register for the webinar here.

Also, make sure to sign up for updates about RISE UP 2022! It will be a fully virtual event, happening February 16-17, 2021.

How to write a winning RFP executive summary—er, briefing (with template)

How to write a winning RFP executive summary—er, briefing (with template)

Executives don’t want to be summarized. They want to be briefed, which is what your executive summary needs to do. While common terminology is “executive summary,” approaching it as an executive briefing will put you in the proper persuasive mindset.

It all tracks back to Dr. Tom Sant. Know him? If you prepare proposals or briefings to make your sales living, then Dr. Sant’s subject matter expertise needs to be in your toolbox.

He’s written a few books, one of which is Persuasive Business Proposals. I highly recommend it, and not just because I used to work with Dr. Sant at one of the companies he founded. Its value is in how he ties proposal writing to the psychology of how humans make decisions. It’s a master class in how to use persuasive language in sales when building proposals and their executive summaries.

For the sake of this article—and to help keep us focused on the executive summary—I want to focus on one of Dr. Sant’s most helpful guidelines, which goes by the acronym NOSE.

  • Needs: Spell out your understanding of the prospect’s problems.
  • Outcomes: Confirm the results they anticipate when their problems are solved.
  • Solution: Recommend how you can solve the problem.
  • Evidence: Illustrate how you’ve solved similar problems in the past and who else trusts you to solve such problems.

According to Dr. Sant, by organizing your executive summary to align with NOSE, you’ll address three questions that executives want answered while being briefed:

  1. Are we getting what we need?
  2. Is it really worth the investment of resources and time?
  3. Can they really deliver?

Many salespeople make the mistake of focusing more on “summary” than “executive.” Summaries tend to not provide answers. They’re more like glorified tables of contents for the larger proposal.

Create the executive summary with the understanding that it’s likely the only part of a proposal that executive-level decision-makers will review. You have to elicit the desired response from a proposal without including everything that goes into a proposal. No doubt it’s a top-flight challenge in persuasion, but it’s the hurdle your executive summary has to leap.

Executives want to see that you understand their needs and desired outcomes, their pains and wants. Seeing this level of understanding articulated in the executive summary helps relieve any anxiety they may have as check writers. Many executives just want the briefing to overcome their fear of making the wrong decision or selecting the wrong vendor, which can be a career-damaging move.

5 more tips for writing an executive summary that packs a punch

There are heaps of tips written in-line in the template. It’s a template with instructions, like one of those fresh dinner boxes you can have delivered that has all the groceries and the recipe you need to make a meal, but without all the surprise prep work that no one ever mentions (“Wait, I still have to marinate this meat and chop all these veggies?”).

In fact, there’s so many tips that I didn’t have room for these four, so I’m dropping them in here:

  1. Create a title using a dynamic verb: Sadly, the most popular title for an executive summary is “Proposal for Prospect Company.” Use the title as an opportunity to capture the executive’s attention. “Increasing lead-generation…,” or “Visualizing revenue forecasting…,” or “Streamlining cloud storage…” or whatever it is that your solution is going to do for them.
  2. Use the recipient’s actual name whenever possible: It makes recipients feel important and personally attended to when they see their name on the front page.
  3. Aim for a 3:1 ratio of recipient company name versus your company name: Make the document feel customized to them, not you.
  4. Show how well you understand your prospect’s needs: Sales or business development representatives should provide this information either from experience or from a formal discovery phase that needs to happen prior to your building a proposal with an executive summary. List only 3-5. Six and beyond are dismissed by the brain as trivia, and are almost never read.
  5. Make sure your key functionalities match your prospects’s desired business outcomes: If they don’t, it’s probably not a good fit.

Executive summary template: Use it or reference it, whichever works best for you

I could tell you *how* to write an executive summary until the cows come home. But, if you’re anything like me, things don’t really click until you see these best practices put into action.

That’s why I pulled together an executive summary template based on Dr. Sant’s NOSE. Replace the in-line instructions with recommended content and you’ll end up with an executive summary that’s bound to impress. Or, at the very least, that’s bound to address executive-level strategic concerns about your proposal. Download the full template here.

Pro-Tip: When you’re ready to write your own executive summary, make a copy of the template. Then, delete all the comments. That way you don’t accidentally fire off a document complete with my tips and tricks.

Create effective executive summaries consistently

Some of us around here at RFPIO are prone to saying, “A proposal on its own is not likely to win a deal, but it can certainly lose it.” The same can be said for an executive summary.

Remember that executives buy a solution for different reasons than a production team (sales, marketing, IT, etc.) wants to use it. Executive teams have strategic goals while production teams have daily workflow improvement goals. In RFPIO’s case, while prospect executives may want to increase sales pipelines, sales and proposal teams just want time back for sanity.

I hope you find this template and walkthrough helpful. It’s been my experience that very few organizations or individuals get any training on writing executive summaries. Hence, on the sales side, there can be a lot of inconsistency across the organization when it comes to executive summary approaches. With RFPIO’s ability to work from templates for executive summaries and proposals, uploading this template can help establish a consistent foundation for executive briefing creation moving forward.

To learn more about RFPIO and functions such as Salesforce Proposal Builder, schedule a demo today.

What is an RFP?

What is an RFP?

RFP stands for request for proposal, but it’s so much more than that. It’s a plea for help, a clue to problems that need solved, and an opportunity to build pipeline. This article will take you from asking, “What is an RFP?” to knowing how to use RFPs to drive revenue in less than 1,500 words. Buckle up.

First, an assumption: If you came here because you want to know what an RFP is, then I’m guessing that a high-value target has decided to issue an RFP to find a solution to a problem you feel strongly about solving. When that target finally understands that you’re the answer to their problem, then you’ll pick up a sizable chunk of business. Now you just have to play the RFP game.

(Just in case you’re here because you want to know how to issue an RFP, check out this article instead.)

What is an RFP opportunity?

There are essentially two types of RFP opportunities: solicited and unsolicited. Solicited means that you’re invited to play the game. Unsolicited means you have to crash the game. You have a better chance to win when you’re invited.

That reminds me. There’s a fair bit of jargon in the RFP world. Here’s a short glossary of some common terms you’ll encounter often, including in this article:

  • RFP issuer: The organization that sends out the RFP. They have a problem, and they’re willing to pay someone to solve it, within certain parameters.
  • RFP responder: You.
  • RFP response: How you answer the RFP.
  • RFP proposal: Your response to the RFP.
  • RFP Q&As: Most RFPs present a number of questions that responders must answer. This section makes up the lion’s share of your proposal.
  • RFP win: You were selected by the issuer to solve their problem.
  • RFP loss: Happens to the best of us.

Back to more on “What is an RFP opportunity?”…While you can still win an RFP if you submit an unsolicited response, the odds are against you and you need to take an honest look at whether or not it’s worth it to respond.

RFP responses are not easy, even when you’re invited to partake. If you’re lucky enough to be alerted to an RFP on the day it’s issued, then you’re likely looking at a 3-6 week window to compose your response. Rarely are you so lucky. Sometimes it’s brought in with notice of a week or less, putting you on a tight deadline. The number of hours you’ll have to commit to building a proposal during that time will be determined by, among other things, team participation, content relevance and access, and how much you have to rely on manual processes to complete the response.

Now that you understand what an RFP is and the opportunity it presents, you need to put yourself on a path to respond only to those RFPs that you can realistically win. If this is one of your first RFP responses, then it could be a rabbit hole of unknown depths. Insert a go/no-go milestone before you go ask Alice. It involves asking yourself the following five questions:

  1. What was your level of involvement prior to the RFP being issued?
  2. Is your solution a fit (now, not at some squishy date in the future after you’ve had a chance to adapt it to what the problem calls for)?
  3. Does your price match the RFP issuer’s budget?
  4. Will winning the RFP be a strategic fit for your organization?
  5. Do you have bandwidth (to complete a competitive proposal, not to deliver your solution)?

As part of the RFP response process, you should have an opportunity to ask the questions necessary to fill in the gaps for your go/no-go milestone. Best-case scenario? Your sales team has already laid the groundwork for all of this with the issuer and it’s just a matter of taking their learnings and making them actionable.

It’s a “go.” Now what?

It’s a process deal. Doesn’t that take the pressure off?

I won’t get into the nitty gritty of the RFP process here (you can do so here if you’re ready to start now), but I will touch on the value of efficiency. Even if this is your first RFP, you’ll want to go into it as prepared as possible to save you and your team some pain and give your organization its best shot at winning.

Break down your efficiency goals into three main categories: project management, content management, and proposal quality. Before you start checking boxes under these categories, you need a team. Part of that team has likely already formed. The salesperson at the tip of the spear will be your subject matter expert (SME) for issuer-related questions and perspectives. The rest of the team will come together based on your review of the RFP. What questions need answered? Who has the answers? Who has the design and technical chops to build the proposal?

After you identify potential team members, dig into their availability and try to build a schedule to complete the response by deadline, preferably before deadline to give yourself some buffer. Then schedule a kickoff meeting with all team members to get their buy-in to process details for the following:

  • Project management: You’ll be the lead for collaboration, assigning tasks, and driving the schedule.
  • Content management: You’ll need content creators, content reviewers, and a storage system for a content library (if you’re gathering all this valuable info for an RFP, you’ll want to save it for repurposing; even if this will be your only RFP response of the year, the info will be useful for business proposals, answering prospect and customer questions, and training new hires).
  • Proposal quality: Answering RFP Q&As won’t be enough. You need to personalize the proposal to make it stand out.

Remember, the issuer is using the RFP process to identify its optimal vendor. They’re inciting competition, so you need to play to win. Second prize doesn’t even get a set of steak knives.

Beef up your sales pipeline

Now that you’ve discovered RFPs and the opportunities they can offer, you may want to evaluate how they can help you achieve your sales goals. 69% of B2B salespeople do not have enough leads in their pipeline to meet quota. Pursuing RFPs can build up pipelines fast: Globally, $11 trillion of revenue is won through competitive proposal processes (i.e., RFPs) every year.

Obviously, you’re not going to win every RFP. We found the average win rate to be 45%. However, RFP opportunities can cost as much as 5X more than traditional sales opportunities, which makes your process and your sales tech stack your best friends when it comes to response efficiency.

Automate to dominate

The optimized sales technology stack is a hot point of conversation these days. With so many software solutions, it’s easy for sales teams to overspend on solutions they barely use. A recent Harvard Business Review article cites a survey where 62% of B2B companies were not satisfied with their sales technology return on investment. It also found that:

“The winning companies in our analysis were 1.4 times more likely to fully deploy sales technology tools and 1.9 times more likely to fully integrate them…By taking the time to embed these technologies properly into its sales processes, the [SaaS] company was able to increase revenue growth by 200 basis points within a few weeks.”

RFP automation offers a massive competitive advantage for responders. It saves time, improves proposal quality, and helps companies create their best work by activating their company knowledge. Companies with RFP-specific technology responded to 43% more RFPs in 2020 than those without a designated RFP tool. “With RFPIO, I would say we have increased our win rate by 15%,” said Grégory Saive, IBA global director of sales support and tender management,

But it has to be the right RFP automation technology for your sales tech stack. It has to be able to manage your entire response process — from building proactive proposals to answering prospect and customer questions on the fly and responding to questionnaires — while integrating seamlessly with the other applications you rely on, such as your CRM, communication, and cloud storage solutions.

What’s next? Demo.

We started with “What is an RFP?” and made it all the way through to the value of RFP automation. Once you win one, you’re going to want to win more. Since I’m almost at my promised 1,500-word cap, I’ll wrap it up with a tip on your next step: Schedule a demo. It’s the fastest and easiest way to find out if RFP automation is right for you. Even if it’s not, you’ll get some valuable response tips from our process experts.

How RFPIO celebrated Hispanic Heritage Month

How RFPIO celebrated Hispanic Heritage Month

Hispanic Heritage Month is a period from September 15 to October 15 in the United States for recognizing the contributions and influence of Hispanic Americans to the history, culture, and achievements of the United States.

It started way back in 1968 under President Lyndon Johnson and was officially signed into law in 1988.

This year, the RFPIO team celebrated Hispanic Heritage Month in our own way, through cocktail making, pot painting, and a bit of trivia.

How RFPIO celebrated Hispanic Heritage Month

Our Hispanic Heritage Month Event was special for two reasons. First, because we were able to celebrate Hispanic culture. Second, it was our first company event since RFPIO acquired RFP360! It was great bringing the two teams together under one virtual roof and getting to know each other a bit better.

We gave everyone the option to do two different activities: Cocktail Making and Terracotta Pot Painting

Cocktail Making 🍹

For this one, we invited the great Robert Damian Scout to help us become cocktail-making pros. He showed us how to craft a couple of amazing classic cocktails made famous by a man named Don Javier Delgado Corona. He’s an absolute legend in the Hispanic community AND the bartender community worldwide. If you’re looking for a good story, look him up. You won’t be disappointed.

In the class, Robert showed us out to make two classic cocktails: La Paloma and Batanga.

Here are the recipes:

La Paloma
2 oz blanco Tequila (preferably Patron Silver)
½ oz fresh lime juice
1 oz fresh grapefruit juice
¼ oz r squirt of agave nectar (simple syrup works too)
Club soda
Pinch of salt
Tajin or chili salt (optional)
If you’re not a fan of tequila, a grapefruit shandy or beer also works great!

Batanga
2 oz blanco Tequila (preferably Patron Silver)
¾ oz fresh lime juice
4-5oz of Coke (preferably Mexican Coke)
Salt
One whole lime

Tools:
Shaker tin of any sort (anything with a removable and tight lid will work)
Cocktail Strainer (you can also use your hands)
One sharp knife, big enough to stir into your glass
Preferably a “collins” glass, but any pint-like glass will work

Terracotta Pot Painting 🎨

For this activity, we sent anyone a kit with a few mini terracotta pots and some paint pens.

We kicked off the event by exploring the virtual art exhibit hosted by the Smithsonian museum, Our America: The Latino Presence in American Art.

At this exhibit, we learned about how the civil rights movement of the 1960s and 1970s galvanized Latino artists across the United States, who began creating new images of their communities and examined bicultural experiences. Until recently, this art was not considered part of “American” art—the exhibit at the Smithsonian attempts to change this.

We’d encourage you to explore the exhibit on your own here. It will run until March 2022.

After we learned a bit about the history of Latino art in the United States, we learned more about the significance of pottery in Latin America, but Mexico specifically, and how native indigenous pottery was influenced by Spanish techniques. And then… we took that inspiration and painted our very own masterpieces!

Each participant received two terracotta pots and 4 paint pens… and then we got to work. Here’s a sampling of our collective genius:

Hispanic Heritage Trivia 🤓

We finished off our event with some trivia!

Here are some of the questions we asked. See if you could get them right! (Scroll to the bottom of the blog for answers).

Why does Hispanic Heritage Month start on September 15th?

  1. September signifies the start of Fall in many Latin American countries
  2. It’s Pancho Villa’s birthday
  3. It marks the day many Latin American countries gained independence

When was the first time Hispanic Heritage Week (now Hispanic heritage Month) was celebrated in the US?

  1. 1988
  2. 1968
  3. 1990
  4. 1978

How large was the self-described U.S. Hispanic population as of 2019?

  1. 132 million
  2. 50.5 million
  3. 27.8 million
  4. 60.6 million

How many states had a population of more than 1 million Hispanic residents as of 2019?

  1. 8
  2. 10
  3. 12
  4. 14

According to a 2018 census estimate, the U.S. Hispanic population will reach this size by 2060.

  1. 81.2 million
  2. 91.8 million
  3. 111.2 million
  4. 124 million

What’s the largest city in Latin America by population?

  1. São Paulo
  2. Mexico City
  3. Lima
  4. Bogotá

What’s the highest waterfall in South America?

  1. Iguazu Falls
  2. Tugela Falls
  3. Gocta Waterfall
  4. Angel Falls

Which South American country do the Easter Islands in the Pacific Ocean belong to?

  1. Uruguay
  2. Paraguay
  3. Argentina
  4. Chile

All for a good cause

While drinking and painting are good fun, there was a greater purpose behind our shenanigans.

All participants were encouraged to donate money to Voto Latino, a grassroots political organization focused on educating and empowering a new generation of Latinx voters, as well as creating a more robust and inclusive democracy. We set out with a stretch goal to raise $1,000—and we surpassed that number!

As of October 8, we have $1,175 raised. The fundraiser will be open until the end of Hispanic Heritage Month on October 15. If you haven’t donated yet, but would like to, please visit our GoFundMe page.

If this sounds like fun… we’re hiring

At RFPIO, we like to have fun. If you also like to have fun, you’ll fit right in.

We’re hiring in pretty much every department. Check out our most current job listings here. If something catches your eye, please apply! We can’t wait to meet you.

Answers to trivia questions:
C. It marks the day many Latin American countries gained independence
B. 1968
D. 60.6 million
C. 12
C. 111.2
A. São Paulo
D. Angel Falls
D. Chile

To learn more…

Here are some resources you can check out.

Podcasts: 

MexiCan

A Latinx culture podcast about Mexican and Mexican-American history, folklore, traditions, and art. 

Anything for Selena

Marcia Garcia was 9 years old when Selena was murdered. 25 years later, she’s on a quest to understand what it means to love, mourn, and remember Selena. 

Code Switch

A podcast that tackles the subject of race with empathy and humor, exploring how race affects every part of society. 

Reading:  

Book: The Motorcycle Diaries: Notes on a Latin American Journey, by Ernesto Che Guevara

Book: The Brief Wondrous Life of Oscar Wao, by Junot Diaz

Article: Dia de los Muertos

Watch

Documentary: Latino Vote: Dispatches from the Battleground

Documentary: Underwater Dreams

TV Show: Gentefied

Documentary: Discovering Colombia

10 ways RFPIO customers can strengthen security

10 ways RFPIO customers can strengthen security

$3.92 million. That’s the global average cost of a data breach in 2019, according to Ponemon Institute.

So it’s no wonder that companies invest heavily in cybersecurity. In the five years between 2017 and 2021, global spending on cybersecurity products is slated to exceed $1 trillion—and this trend is only expected to continue on its upward trajectory.

If you’re storing company information in RFPIO to streamline your RFP responses, I have good news: RFPIO has state-of-the-art security controls to protect your data. Even so, there are still extra things you can do to further protect your information.

Here are 10 things you can do to further strengthen security in RFPIO:

1. Use SSO: A Sweet Security Option

SSO stands for Single Sign-On, but it is also a super sweet security option. RFPIO uses the most widely accepted industry standard, SAML 2.0.

With SSO, RFPIO users use the credentials they already have to sign in. That means they don’t have to remember (yet another) separate user ID and password—and Admins don’t have to take on the responsibility of managing user credentials.

SSO isn’t just convenient. It’s also more secure. When you use SSO, passwords aren’t stored in the browser and there’s a lower risk of a lost or forgotten password. This prevents security gaps that hackers will exploit to gain unauthorized access to the application.

Additionally, SSO allows Admins to manage user activities in real-time, which gives you the extra visibility you need for a tightly run security program.

2. Automate user management with SCIM

SCIM stands for System for Cross-Domain Identity Management. Luckily, it is not as complicated as the 13-syllable name would have you believe.

In a nutshell, SCIM simplifies user management. If SCIM is enabled, users can be added or deleted automatically. It’s as easy as that.

On the one hand, SCIM makes life much easier for Admins. No more manually adding and deleting user accounts.

But it’s also important from a security perspective. With SCIM, user accounts are automatically deleted as soon as employees leave your organization, which means employees won’t have access to sensitive company information after they’ve left.

SCIM happens through SSO and is supported by OneLogin and Microsoft Azure. If your identity provider supports it, I highly recommend implementing SCIM—both for the added convenience and peace of mind.

3. In lieu of SSO, use 2-factor authentication

If your organization doesn’t use SSO, I would recommend you set up 2-factor authentication as an additional layer of security.

If you’ve ever had a code sent to your email or phone, that’s 2-factor authentication. After a user enters their username and password, 2-factor authentication prompts users to enter a valid key or code.

2-factor authentication prevents an unauthorized person from accessing data. Even if a cyber attacker learns the login credentials, they will not be able to access the code for 2-factor authentication.

RFPIO supports 2-factor authentication through Google Authenticator and Duo Mobile.

4. Control access with User Roles

With User Roles (default) and Custom Roles (customized), you can define what users can see and do, and ensure users only have access to the data that’s relevant to them. This is key for security. When you reduce the number of people with access to sensitive data, you minimize the risk of leaks.

RFPIO’s out-of-the-box user roles include Super Admin, Admin, Manager, Team Member, and Project Requester. With Custom Roles (available as an add-on, or included with enterprise package), you can create your own roles that make sense for your organization For example, Content Owner, Reseller Partner, or Project Contributor, but really it can be whatever you want. The world of custom roles is your oyster.

Read our Help Center article to learn more about specific permission levels for the out-of-the-box user roles (RFPIO customers only).

5. Control visibility with collections

Collections is another, more granular way to control access to sensitive data.

While User Roles controls access to projects and organization settings, Collections controls access to content.

When you assign a piece of content to a collection, you can restrict visibility to that collection, either by a user group level (e.g. the sales team) or on an individual level. You can get as granular as you’d like.

For example, you may choose to have a “security” collection and restrict visibility to just the InfoSec team. Or maybe you want a “financials” collection, and want to restrict access to just the finance team and upper management. Here’s a blog with more detail on using collections to organize your content (or scroll to the bottom to watch the webinar).

6. Get really granular with permissions

If you want to get really in the weeds with visibility, you can set privacy settings at the individual object level (e.g. a Q&A pair). Rather than assigning it to a collection, you can set privacy settings to control who can view or edit a specific piece of content.
If there’s a Q&A pair you really only want upper management to have access to, you can do that.

You can also adjust view and edit permissions. For example, maybe there’s a question about a product feature that you really only want the product team to be able to edit, but still want to give your marketing team access to view.

7. Keep up with your audits

With RFPIO, all activities are tracked and logged at different levels (e.g. project level, content level).

Every so often, I’d recommend pulling the Activity Report, which monitors all user activity within the application—including permission changes, user creation, and user deactivation.

For example, if you notice an individual user’s permissions have been changed to have broader access to data that may not be relevant to their role. In response, you can reach out to the person who made the change for more information—and, if necessary, reverse their permission levels to a level more appropriate to their role.

You can also pull the User Login Activity Report. This log includes information about:

  • Who accessed the account,
  • When it was accessed,
  • Where it was accessed (e.g. IP address), and
  • How they logged in (e.g. SSO, username + password, etc.)

Using the User Login Activity Report, Admins can see if the user logged in at odd hours, like on the weekend or very late at night. This could be an indication of unauthorized access that could lead to a data breach.

8. Set up “session timeout”

Avoid the risk of internal attacks by setting up session timeouts that automatically log you out of the application. This is most relevant for organizations working in an office setting.

Here’s the scenario: The VP of Sales leaves their desk for a meeting. Scooby-Doo walks over to the VP of Sales’ desk and downloads a bunch of sensitive financial information from RFPIO, and uses it to wreak havoc. Classic Scooby move.

To prevent this kind of situation from happening, you should set up “session timeout”. The default timeout is 20 minutes, but you can adjust according to your needs.

9. Bring Your Own Key (BYOK)

Set up an extra layer of security with BYOK. RFPIO already encrypts data with our own mechanism, but if you want that added boost… you should consider BYOK.

Basically, BYOK gives you the ability to provide your own encryption key to protect your data—on top of the encryption that RFPIO already uses. This is an added measure for fighting unauthorized access to data.

If you’re an RFPIO customer, learn more about BYOK in the Help Center.

10. Securely share information via Linked Companies

Share company information with partners (e.g. resellers) in such a way that they can only view and use it—but don’t have edit access. This essentially transforms your RFPIO Answer Library into an internal knowledge base that your reseller partners can use to respond to RFPs or answer any other questions that may come up during the sales cycle.

You can set this up using Linked Companies. Learn more about how to set up and use Linked Companies in the Help Center (RFPIO customers only).

What is RFx? Do the math for sales and procurement.

What is RFx? Do the math for sales and procurement.

What is RFx? In this case, it’s proof that Mrs. Vickers, my pre-algebra teacher, was right. She assured me that algebra would come in handy in my adult life. It only took 35-ish years, but it turns out Mrs. Vickers’s crystal ball wasn’t so foggy after all.

Back to the original question: What is RFx? It’s the shorthand for your “Request for” category of procurement and sales processes and documents. Solve for x.

  • RF(Proposal)
  • RF(Information)
  • RF(Quote)
  • RF(Application)
  • RF(Bid)

Explanations and definitions of these are insightfully encapsulated here (processes) and here (glossary). However, if you want an overview of how you can use any of these RFx varieties for your business — either in procurement or business development, then you’re in the right place.

Using RFx for procurement

If you use RFx for procurement, then you’re the issuer creating the RFx. Typically, you’ll submit requests in the following order:

  1. RFI
  2. RFP
  3. RFQ

Ultimately, you want to play your RFx cards to select an ideal vendor using strategic sourcing. The RFI will be high level, probing to see if a problem can be solved. It will help narrow down providers to whom you’ll want to submit the RFP, which will be much more detailed and a heavier lift for you to evaluate.

Your RFP will ask for in-depth problem analysis, what it will take to solve the problem, how a vendor proposes they’ll solve the problem, proof of solving similar problems in the past, and, possibly, an estimate on cost. It may also inform responders how responses will be evaluated (e.g. cost = 35%, experience & performance = 35%, response quality 30%), budget expectations, and timing details.

From your pool of RFP responses, you’ll submit an RFQ to one or two providers to finalize your costs. At this point you know the exact product or service that you want so you request a price quote for that specific solution.

“RFB” is also known as “invitation to bid.” While this terminology does appear in the U.S., it may be more common internationally, where issuers post “tenders,” and responders submit “bids” in response to those tenders.

RFAs are associated with government agencies and nonprofit organizations. Funding has already been set aside for a specific requirement and now agencies or organizations are seeking recipients of funding. Agencies want to solve a very specific problem, such as building the capacity for drinking water systems. Nonprofit organizations have grant money available and seek applications to distribute the grant, such as for placing veterinarians in underserved areas.

Using RFx for business development

For the 69% of salespeople who do not have enough leads in their pipeline, RFx opportunities are an opportunity to drive revenue. When you use RFx for business development, then you are the RFx responder. Response teams require expertise from multiple areas, including sales, product development, product marketing, finance, contracts, and more, depending on the product or service you sell. It’s up to you to respond appropriately in an attempt to put your product or service at the top of the list for RFx issuers.

If you’re lucky, then you have a unified content repository of some sort to reference for your responses. Many sales professionals still work from personal content libraries they’ve amassed on their own, which is problematic for brand management and onboarding new employees. If you’re even luckier, then you represent one of the 43% of organizations using RFP-specific software, which helps automate response processes.

Responding to an RFI will get your foot in the door. Hopefully, it’s something you do regularly and doesn’t take up a lot of bandwidth, for you or any other response team members. This will be early on in the sales process, possibly too early to even count toward your pipeline. When an RFx is not certain of gaining revenue, then you want to minimize resources spent on responding.

However, once you’re selected to respond to an RFP, you can add prospective revenue to your pipeline. This will also be the largest investment as far as resources that you’ll commit to responding to an RFx.

The RFP is your opportunity to lay all your cards on the table. Show the issuer what you can do, how you can do it, and why you can do it better than anyone else. Expect to be evaluated on your experience, your price tag, and the quality of your response. By evaluation, I mean you’ll be measured against all other responders in as much of an apples-to-apples comparison as the issuer can comprise based on the complexity of the response.

The RFQ will be the final deal number, if it wasn’t already requested in the RFP. It will highlight the solution you’re providing within the issuer’s budget. If your solution comes standard with additional functionality beyond the scope of what the issuer originally requested (e.g., integrations with other software, free training, or VIP support), the RFQ is a great opportunity to call that out.

What is RFx automation?

RFx automation reduces the manual processes required to issue and respond to any RFx. For issuing, RFx automation streamlines how requests are created and organizes the evaluation process for you. For responding, RFx automation uses artificial intelligence to Auto Respond to any RFx based on content in your Answer Library. Organizations that use RFP-specific software are not only able to respond to 43% more RFPs than those without a designated RFP tool, they’re able to turn around each response 40% faster.

RFx response automation can also extend to responding to security questionnaires, due diligence questionnaires (DDQs), scopes of work, and whatever else you may be requested to respond to in your sales or client support lifecycles. The functionality can also serve you well for proactive proposals, where you need to deliver a proposal or presentation even though one wasn’t specifically requested. This is common in business proposals when a prospect wants something in writing to share with management or the C-suite to build a business case for adding your solution.

Whether you want to use RFx for procurement or business development, if you’re going to do it for the long term, then RFx automation will be a boon to your workflow, morale, and bottom line. The math works out. Mrs. Vickers says so. Learn more about AI-enabled RFx management by scheduling a demo.

Guide to a great RFP response process

Guide to a great RFP response process

If you’re reading this, then you’ve already contemplated why you need a request for proposal (RFP) response process. Something hasn’t been going right. Too much time being spent on responding? Poor quality proposals? Lack of wins? Or maybe you’re a new proposal manager, or you’re trying to provide proposal manager-level leadership as a sales or marketing manager. The point is that now you know why you need an RFP response process, so where do you get started?

I’m going to lay it all out for you, but first…

How do you respond to an RFP?

Depending on your industry, an RFP may contain several hundred questions and ask you to gather dozens of documents, certificates, and other content that validates your product as a solution to the issuer’s problem. You’ll have to compose a response that addresses all the questions and content requirements, which may require you to reach out to multiple people in your organization for help. Oh, and of course there’s a deadline. And it’s never far enough in the future for you to feel comfortable about hitting it.

Your response will be reviewed and compared to responses from your competitors. The quality of your response will determine whether or not your organization moves forward in the sales process. As many an RFP pro can attest, you can’t win a deal solely on the basis of an RFP, but you can certainly lose one.

RFPs can be painful without a process. Evaluating what’s required, searching for content, tracking down subject matter experts (SMEs) to help, and composing a high-quality proposal takes time, most of which will be wasted if you take an ad-hoc approach. Your process does not have to be extensive, but it does have to exist.

What is an RFP response process?

An RFP response process is an efficient workflow that clarifies roles, responsibilities, and timelines to help an organization meet the issuer’s deadline. A great RFP response process is practiced by an entire team. RFP contributors come together to build the process, and they follow it consistently.

When to create an RFP response process

I touched on some scenarios in the opening paragraph, but here are a few more red flags that might indicate you need to create an RFP response process:

  1. A new proposal manager is taking over the process. Whether they are taking over an existing process or implementing one for the first time, this is an excellent opportunity for a proposal manager to make an early impact.
  2. The current “process” just isn’t working. This can range from being tired of responding to RFPs in an ad-hoc fashion, to recognizing the current proposal process is broken or cannot scale, to realizing that AI-enabled software help is out there and it’s time to implement.
  3. Merging organizations with separate RFP response processes. Rare is the occasion when two companies come together and proceed in lockstep through their first RFP as a merged entity. If you’re going to try to cherry pick the best of both processes, then you might as well scrape the lot and build anew. The good news is that your combined experience will accelerate decision-making.
  4. New markets or new products. What may have worked in the past with familiar markets and established products may fall flat with audiences that don’t recognize your company or product. This is a prime opportunity to get back to basics and modernize a process that may have grown stale anyway.

Set goals for your RFP response process

Start by identifying what you want to achieve. Only then can you draw a blueprint that you can follow to get there. I recommend including these three objectives in your initial goal-setting:

  1. Decrease response time: The pain of too much time spent on responding is likely what got you here in the first place. Drop this metric in as one of your primary markers for success. If you do it right, you can decrease response time by up to 40% or more. The right process will make you more nimble.
  2. Improve response quality: Some, if not all, of that time you save with a new RFP response process can be re-invested in your responses. Instead of scrambling to find answers or begging for reviews, you’re spending the time customizing a proposal to better position your solution for the win.
  3. Increase shortlist rate: This will take a few responses before you see any results. More shortlists means that you’re receiving greater consideration. Eventually, an uptick in this metric will correlate to an uptick in win rates, too.

Further out, you can look at goals for win rate, content development, and increasing the number of RFPs you respond to every year.

12 RFP process steps for efficient RFP responses

Start with this RFP process checklist. Plan on at least a month of work to get the process going. The status and volume of your existing content will be the major determining factor in how quickly you’ll see results.

  1. Identify key stakeholders: Who are they? What is their contribution? What is their role (e.g. proposal development/management, subject matter expertise, strategy, review, etc.)?
  2. Figure out the average timeline. Government RFPs tend to have longer lead times but more requirements. Private sector RFPs are generally quicker but may not be as complex. Knowing this will help you construct your response calendar. For example, if you have an average of two weeks then reviews won’t be extensive, or you may have to respond with a generic proposal instead of a custom version.
  3. Identify other metrics that will determine whether or not you pursue the opportunity.
  4. ROI: Is it worth committing resources to the effort?
  5. Strategic positioning: Is your solution truly the right fit for the issuer’s problem?
  6. Pricing: Does the estimated budget align with your pricing?
  7. Existing relationships: If you’re an unknown entity, then you have a steeper hill to climb to get shortlisted.
  8. Locate content and evaluate how easy or difficult it will be to access it. Dollars to donuts that this will be your biggest headache.
  9. Select the optimal channels for collaboration. Email? Slack? Teams? You’ll need to include all of your identified stakeholders. Then you’ll need to create a strategy of how to collaborate. Include everyone in everything (and risk early onset of project fatigue)? Customize communications for every action item (and add a hefty amount of work to the project lead while risking losing touch with some stakeholders)? Quick tip: Break away from a linear process; people can work on multiple pieces simultaneously.
  10. Get buy-in from everyone. For a process to be effective, it needs to be followed. Bring in executive sponsors from the get-go, and start selling efficiency benefits to SMEs pronto. Relationship building within your organization will be just as important as the business development relationships your salespeople are cultivating.
  11. Consider whether software can help. Software helps you have a clearly defined process. Software itself enforces the process, with the help of the administrator. It also centralizes content, makes it searchable, and automates part of the response process, all of which will simplify creating the process in the first place.
  12. Should you hire a proposal manager? This is a professional role that brings value to the RFP process. It’s a combination of project management, proposal development, and relationship-building expertise earned from extensive response experience. Otherwise, someone is going to have to multi-task with their other responsibilities to lead the RFP response.
 benchmark-blog-report

The 2021 Benchmark Report: Proposal Management

Learn about the state of proposal management, and see what teams need to do to be successful in 2021

Read the report

A template: The ideal RFP response process flowchart

As soon as you have your ducks in a row, you can go about building your proposal process in the flowchart below.

RFP Response Process and Steps

8 key RFP process steps:

  1. Qualify RFP: Insert a go/no-go evaluation at the beginning of the RFP response process. Sales will be the loudest voice, but proposal teams, SMEs, and executive sponsors will need to weigh in to evaluate risk, timing, and strategic fit.
  2. Kick-off project: Provide clarity and accountability to the full response management team, including strategic objectives that everyone can work toward.
  3. 1st response: Make an initial response pass based on reusable content. This step is much faster with RFP software.
  4. 2nd response: Tap into resources for new questions, and assign segments that require customization to respective SMEs.
  5. Review & revise: Conduct internal reviews to ensure a high-quality proposal. Link review requests to specific purposes (i.e., Are strategic objectives met? Are responses accurate and high quality? Did we fully answer the question?)
  6. Submit: Deliver polished RFP with reviewed supporting materials. Follow up to confirm receipt. Keep internal stakeholders abreast of progress.
  7. Save & audit: Save finalized responses in a centralized location and commit to regular content audits.
  8. Post-mortem: Winning doesn’t always mean content was perfect. Losing doesn’t mean it was a bad response. Evaluate what worked and what didn’t.

Strengthen your RFP response process with RFP software

I touched on some of the benefits in the above checklist. But there is a lot more than management of process and content. Integration with other applications in your sales tech stack, the ability to work from custom response templates, Auto Respond functionality, and streamlined collaboration are just some of the highlights.

The happiest teams we know find that RFPIO features make it easier to stick to a consistent RFP response process. Imagine being able to assign reviewers sequentially to ensure the proposal is polished with the highest quality responses for each section. You can do it from a single interface, communicate with responsible SMEs, and establish clear timing of every task for everyone to see.

You can certainly respond to RFPs without software, assuming you have a rock-solid approach that hums along without any inefficiencies. But if you want to go from moving the needle to burying it, then combine a strong process with RFP response software.

Still not sure where to start? Demos are always great launching pads. Schedule one for you and your RFP response stakeholders today!

4.5 reasons I (a sales pro) love Autograph e-signature

4.5 reasons I (a sales pro) love Autograph e-signature

As a sales professional, when I’m closing a deal I don’t want anything getting in the way. The closer I get to a win, the more I get nervous about two things: delays and relying on others. E-signature functionality has been a huge help to minimizing both.

On the delay side, if there’s always been one holdup that makes me question my closing skills more than any other, it’s waiting for a signature. Back in the paper days of yore, it was even worse. Fax machines were already gathering dust by the time I started my sales career in 2007. At that time, we had progressed to a print-fill out-scan-email process that was annoying enough for me, especially for complex contracts that required multiple signatures and initials. Inevitably, a client would miss an initial blank or two and I’d have to chase them down for it. Then I’d have to merge multiple documents to make a complete, legally binding signed contract.

I once had a client on a $150K deal sign one page of a contract but forget to sign another. While waiting for that second signature, other stakeholders entered the picture, held up the deal, and eventually it died…all because I didn’t have e-signature capability.

On the relying-on-others side, this isn’t a selfish play. On the contrary, I depend on my pre-sales, marketing, operations, product development, and customer support teams to help me do my job every day. This play is about streamlining the approval process: I seek to remove as many barriers as possible to simplify what prospects need to do to sign off on a contract. The less I have to rely on them to print, scan, and email, the faster I can get my signatures.

When e-signature hit the scene a few years ago, it was a game changer. Adoption was slow at first, but it’s picked up big time over the last year. The pandemic has helped, in a sense, because the accelerated digital transformation everywhere has increased usage and familiarity with e-signature functionality.

Now that RFPIO has integrated e-signature capabilities across the user experience for all customers, I’ve fallen in love with it all over again. Known as Autograph, there are 4.5 reasons why, as an account executive sales professional, it’s changing the way I work, for the better.

#1 I move faster

Yeah. I know. I was just complaining about delays. Well, I can be the cause of those delays, too. Even prior to Autograph, I wasted cycles toggling back and forth between my e-signature app and whatever I was using to build proposals and contracts (usually either PowerPoint, Word, or PDF).

With Autograph e-signature, I now have capabilities embedded in the same system I’m using to create proposals and contracts, which means no more toggling. From RFPIO I can create the document, add signature requests, send it out, and save the signed version all in the same application. From the moment I have verbal assent on a deal, I can spin up a proposal or contract in a matter of minutes.

The big bonus with it being in RFPIO is that everyone in the organization can have access at no extra costs.* And I’m not just saying that because I happen to work for the app creator. RFPIO’s unlimited user licenses means everyone can have access, and it’s now included as a standard feature.* In addition to not needing to toggle to and fro with your e-signature app, you don’t have to pay for it, either.

#2 I’m more efficient

It’s about more than just working fast. It’s also about having more control over the whole sales lifecycle. Like any other sales professional, I have a quota or goal that I aim to achieve every month, quarter, and year. Autograph enhances the control I was already gaining with RFPIOs other features. Now I can add e-signature to my ability to manage documents, create content, access answers in near real time, and collaborate with my teammates in sales enablement and proposal development.

One of the greatest efficiencies is with contracts that need signatures from multiple parties. With Autograph, I can set a signing order, include personalized private messages to each signer, set a deadline, and prompt reminder emails. Signers will be invited via email to review the document and add their signatures and initials.

#3 I have more visibility

No deal exists in a vacuum. Quota calls, and I need to keep an active pipeline. There’s a fine line between managing multiple deals and spreading yourself too thin. At any one time, I may have two or three contracts out for signatures. The most important deal is always the one I’m currently working, so it was frustrating and distracting to have to keep tabs on contracts that were awaiting signatures on other deals.

Autograph has a dashboard that helps me track all my contracts, including timestamps, what’s been signed, who still needs to respond to the signing order, and all other actions taken with the document. The dashboard is my window into an organized record of all my signed documents, all of which are also stored in RFPIO and only accessible by me. There is no limit to how many documents I save, and no one else can see the documents without my permission.

#4 I minimize my tech stack

Don’t get me wrong. I love my technology. The fact that I can do what I do from almost anywhere still sometimes astonishes me. But like the inevitable course of a TikTok challenge going too far, there can be too much of a good thing.

I’m of the school of productivity through simplicity and taking the straight line from point A to point B. In the face of Nancy Nardin’s overwhelming 2021 SalesTech Vendor Landscape, I’m seeking to consolidate for more efficiency, automation, and of course, ROI. RFPIO has my back: First, by introducing Autograph on top of another new product this year, RFPIO® LookUp; second, by integrating with other applications I already have in my sales stack. From Salesforce to Microsoft Teams to Google Chrome, I have my sales tech stack dialed in for optimal productivity.

#4.5 Get more colleagues involved

This is only 4.5 because, while the byproduct is still something I love, it also comes with the luxury of working for the company that built Autograph: We all use it already. For you, the benefit is that Autograph exposes RFPIO to other users in your organization who may not have experienced it yet. If you’ve been trying to get any engineers or finance team members—maybe even other sales teams—in your organization to start using RFPIO because it’ll make your life easier, then Autograph is the perfect lure.

I’m one of many who love it

Beyond the sales benefits, I’m hearing a lot of love for Autograph from customers on proposal, human resources, and operations teams. Proposal managers are turning around proposal components such as cover letters, legal documents, NDAs, and disclosures faster than ever. HR is incorporating Autograph into onboarding to make the process easier for administrators and new hires. Operational subject matter experts are realizing efficiencies in utilizing Autograph for vendor/supplier agreement contract management.

Autograph is a no-brainer. Free and ready to go if you’re a current RFPIO customer.* Why not try it? Log in. Navigate to Autograph on the left. Upload a doc. Set a signing order. Send it externally or internally. NEXT!

Request a demo and ask to see how Autograph works, or check out a cool GIF demo of Autograph in action. If you’re already an RFPIO customer, view our Help Center article for detailed instructions on using Autograph.

*The inclusion of the free Autograph tool depends on your RFPIO package. If you currently don’t have Autograph, but want it, please reach out to your Account Manager.

Knowledge management best practices

Knowledge management best practices

Albert Einstein said, “The pursuit of knowledge is more valuable than its possession.” With all due respect to Einstein, phooey. At least in terms of knowledge management as we know it today. To capture data and information, impart it with knowledge, and derive wisdom is the “quantum theory” of doing business these days: It’s the fabric of systems and processes behind every data-driven decision, from sales to content strategy to product development.

Underlying the somewhat mystical element of how it all comes together to make every company unique is a knowledge management system, the development and implementation of which can be overwhelming. Where do you start? What’s the best fit for your company? How do you manage change? How will end users react? And, of course, the Big Bang whopper: Will it work?

I’ll answer the last one first: Yes. As far as the other concerns, these knowledge management best practices will help. It’s important to always remember that the reason you need effective knowledge management is to develop your organization’s single source of truth. It’s the only way to be sure that everyone in the organization is always presenting the right information and telling the same story.

Knowledge management best practices

1. Determine the right fit for your company

There are two popular solutions common to knowledge management: corporate wikis and internal knowledge bases.

Corporate wikis are a bit like the wild west. Anyone can add, delete, or edit content. They’re dynamite for increasing employee engagement but lacking in reliability and measurement. If you just want to build a searchable warehouse and have confidence in all your contributors, then corporate wikis may be all that you need.

Internal knowledge bases are dynamic content repositories built on software with knowledge management processes, collaboration tools, and a user experience baked in. They’re designed to capture, curate, and share knowledge efficiently and effectively. One of the biggest differences between them and wikis is that content creation and editing is reserved for specialists who can be trusted. They also function within the parameters of a content strategy, which can be as fluid as necessary for organizations to remain agile and nimble.

To learn more about both options and why we recommend internal knowledge bases, check out “Corporate wiki vs internal knowledge base: Which is better?”

2. Basic is better

One of the reasons we recommend internal knowledge bases is because the user experience should be built to streamline the complexities that tend to result in failed knowledge management initiatives. Application developers should be automating processes of capturing, curating, and sharing knowledge while adding features that actually improve the daily workflow for end users. In other words, the application helps them be more productive or more effective or more efficient. Or, best of all, all three!

Keep the “basic is better” mantra in mind while rolling out a knowledge management system too. Prioritize departments in need and introduce the system to one department at a time. Gradually expand as you dial in training, word of mouth circulates about how great the system is, and you have success stories to share with new departments and executive sponsors.

3. Measure improvements

The functional value of knowledge management will rapidly become apparent to end users in how they’re able to execute their responsibilities. They’ll be able to build better proposals faster, respond to prospects and customers with greater accuracy in near real time, and gain contextual insight into all the content relevant to their role.

The strategic value of knowledge management is that you’re able to show the value of the system to your leadership team in such a way that they can trust your reporting accuracy. Numbers don’t lie, but you need measurement capabilities to get the numbers. Plus, it makes it easier to measure ROI. You have to communicate the value of your single source of truth.

Internal knowledge base software easily allows you to measure success post-implementation. I’ll call out three of my favorite RFPIO reports that help illustrate its strategic value:

  • Answer Library Insights Report: This dashboard connects you to insights on your Answer Library, including content moderation and usage, content owners, and content moderators.
  • Answer Library Timeline: More of a tool than a report, this allows you to proactively set SME schedules so content auditing responsibilities are parsed out manageably instead of piling on hundreds of questions at the end of the year. From a reporting standpoint, it shows leadership how SME time is being used more efficiently.
  • Answer Library Search Terms Report: Which terms are end users searching but receiving zero results for? This report delivers instant insight into which content you need to develop to meet user—and ultimately prospect and customer—needs.

Schedule monthly Answer Library health reports with team leaders. Roll those up into quarterly reports to show the value of your knowledge management solution to your c-suite.

4. Make the knowledge diverse

If knowledge is not accessible and usable at scale, then it’s probably not worth managing. Sales teams need content to answer tough prospect questions in near real time and build personalized presentations. Proposal teams need on-demand knowledge to answer questionnaires and build engaging proposals. Support teams need access to knowledge from wherever they’re working without toggling between applications to improve the customer experience.

All of this can only happen with open access to the knowledge management system. That’s why RFPIO provides unlimited user licenses, so everyone who can benefit from knowledge can also access knowledge. Technical, product development, sales, marketing, legal, security…all of this content has value and will strengthen your knowledge management. The right system will help you restrict access to sensitive content that may include private, confidential, or proprietary information.

Sorry, Albert, I meant no offense

Back to Einstein. In all fairness, knowledge management systems didn’t exist in his day. We can do a lot more with knowledge than what was possible 80 years ago (we can actually do a lot more with knowledge than we could one year ago), so I meant no disrespect by my opening “phooey.” Perhaps another Einstein quote suits knowledge management best practices more aptly: “Out of clutter, find simplicity. From discord, find harmony. In the middle of difficulty, lies opportunity.”

To learn more about how to apply knowledge management best practices in your organization with the help of RFPIO, schedule a demo today! Check out my on-demand webinar for tips on Building a Solid Content Foundation.

Corporate wiki vs internal knowledge base: Which is better?

Corporate wiki vs internal knowledge base: Which is better?

Wikipedia is the primary resource hosts Jason Bateman, Sean Hayes, and Will Arnett cite in their podcast, Smartless, when interviewing a veritable who’s who in entertainment, sports, and journalism. It’s a must-listen podcast, IMHO, but not because the hosts actually rely on Wikipedia as their source. The use of Wikipedia is an inside joke because one or more of them usually knows their “surprise” guest quite well. As a result, the interviews are funny, insightful, and loaded with personal anecdotes and nostalgia.

What would happen to Smartless if Jason Bateman decided to forego podcasting for more directing opportunities? Could Sean and Will fall back on a wiki or internal knowledge base where Jason had the opportunity to upload his insight into interviews with Erin Gray, Ricky Schroeder, or Alfonso Ribeiro? (Try a reference that’s timelier than “Silver Spoons,” RD.) How about interviews with Laura Linney, Jason Sudeikis, or Rachel McAdams? Comparatively, they’d fall flat without Bateman’s personal knowledge and relationship with those guests.

In the real world, where we all do business with people who haven’t starred in a movie, sitcom, or Netflix series in the past 40 years, falling flat due to ineffective knowledge sharing means not meeting customer expectations, not having answers to prospect questions fast enough, or giving wrong or outdated answers in proposals. It’s costly and embarrassing. It’s also avoidable.

Businesses looking for knowledge sharing tools often end up deciding between two options: corporate wikis or internal knowledge base software. While they may seem similar, they’re actually quite different. In this blog, we’ll break down the differences between company wikis and internal knowledge base software to determine which is the best for your business.

Why is knowledge sharing so important?

In 2020, Forrester asked more than 3,000 sales reps about their main roadblocks to productivity. Finding content or information was at the top of the list. And a McKinsey study found that knowledge workers spend 20% of their time searching for internal information or tracking down colleagues who can help with specific tasks. Time equals money, and IDC estimates that an enterprise of 1,000 knowledge workers wastes $5.7 million annually searching for information that is never found.

One more bit of bad news (I’ll end on a high note. Promise.): Knowledge workers are quitting. They are not immune to “The Great Resignation” of the pandemic. According to the New Yorker, “Many well-compensated but burnt-out knowledge workers have long felt that their internal ledger books were out of balance: they worked long hours, they made good money, they had lots of stuff, they were exhausted, and, above all, they saw no easy options for changing their circumstances.” Well, the pandemic gave them the opportunity they were looking for to simplify their life. With knowledge workers departing, organizations need to up the ante on knowledge sharing to make sure they’re expertise doesn’t go out the door with them.

Speaking of doors, knowledge sharing is also a boon for onboarding new employees coming in the door. Giving them the freedom to access company knowledge at will and in context gets them up to speed faster while making custom face-to-face training more efficient and effective (i.e., trainees can find answers to common questions in the wiki or knowledge base on their own time). A majority of HR professionals cite improved onboarding as beneficial to overall employee engagement.

As promised, a high note: Knowledge sharing encourages and rewards greater employee involvement, especially when the sharing mechanism is easy, intuitive, and trustworthy. Organizations with highly engaged employees earn about 150% more than their less engaged counterparts. So they have that going for them, which is good.

What is a corporate wiki?

A corporate wiki is developed using an open source model. This means that anyone can submit edits or gain access. Although touted for being “collaborative,” they are not always reliable because anyone can make changes and include inaccurate information. Democracy works in politics and when making decisions with your fellow lifeboat occupants. Crowdsourcing worked for Tom Sawyer and tells you if police are ahead on Waze. Neither are good fits for business content.

As far as knowledge sharing is concerned, corporate wikis follow the rules of the jungle. While they certainly encourage greater employee involvement, power users tend to elbow out the specialists. They also get out of control fast. It’s an environment where content seeds are planted and then vines grow depending on what’s most popular or controversial. Without any strategy or rules in place, old vines don’t get pruned, some seedlings get overshadowed, and Barry from engineering starts every edit with, “Whoever wrote this is an idiot. The correct answer is…” Not the sort of collaborative vibe you were hoping for.

What is an internal knowledge base?

An internal knowledge base exists in a self-contained solution designed to streamline access, creation, and review of your business content. Unlike corporate wikis, internal knowledge bases have verified writers, so that all team members using the knowledge base can feel confident that the answers they are finding are accurate. Whereas wikis are open to any user creating or editing content, internal knowledge bases are read-only. If the corporate wiki is the jungle, then the internal knowledge base is a curated nursery.

Structure and strategy are the two biggest differentiators between corporate wikis and internal knowledge bases. Within an overarching content strategy developed for the internal knowledge base, writers create and edit content based on a schedule, which is informed by data-driven insight. Tags, collections, and custom fields define its information hierarchy, making it more user-friendly and efficient to search.

Depending on how you set up your internal knowledge base, you can also gather data to derive intelligence on how it’s being used, what it’s missing, and what it doesn’t need. For example, through RFPIO, users can output an Answer Library Insights Report to see which content gets used most often as well as which search terms receive very few or zero results. In the latter example, content managers can build content production plans around zero-result search terms so users will be able to find answers they need during their next search.

Creating an internal knowledge base is a 6-step process:

  1. Consolidate existing knowledge: Import your most recent sales proposals, DDQs, security questionnaires, and RFPs.
  2. Grow as you go: Add new content as products come and go, markets change, audience triggers evolve, and new departments come on board based on your initial tag, collection, and custom field structure.
  3. Stay accurate and up-to-date: Curate content to keep it fresh (corporate content every 90 days, product content every 6-12 months, and evergreen content that doesn’t change much every 12-24 months).
  4. Provide open access: Make sure everyone who needs to use the content has access to the content. Don’t get restrained by user licenses.
  5. Train your team: Even if the tool is intuitive and easy to use, set up time to train new users or else risk them never even trying it.
  6. Conduct regular audits: Don’t let the internal knowledge base turn into the wiki jungle. Keep it clean.

Learn more about these six steps here.

What’s better: a corporate wiki or an internal knowledge base?

Guessing I probably showed my hand too early with that wisecrack about Barry from engineering. You got it: The internal knowledge base takes the checkered flag when it comes to organizational knowledge sharing.

Its structure and the processes that support it make it a more trustworthy single source of truth, which reduces knowledge hoarding and shadow development of content that may exist in individual hard drives. And just because content is created and edited by designated writers doesn’t mean that all expertise hasn’t been tapped. Systems such as RFPIO enable content owners to automate collaboration with subject matter experts so that knowledge is captured accurately and efficiently, while maintaining consistency in message, voice, and tone throughout.

Besides, it also offers much more functionality compared to a corporate wiki. Instead of opening a new browser window or tab and navigating to the Intranet wiki, users can search content from almost anywhere. RFPIO® LookUp is a portal into the Answer Library, which can be searched from Chrome like you’re searching the Internet. According to Hope Henderson at Alera Group, “We market RFPIO as our internal content Google. If anyone that’s client-facing has a question about a specific product, the RFPIO Answer Library will be the first place they’ll go.”

“We market RFPIO as our internal content Google. If anyone that’s client-facing has a question about a specific product, the RFPIO Answer Library will be the first place they’ll go.”
-Hope Henderson, Marketing Coordinator at Alera Group

RFPIO also integrates with CRM, communication, cloud, and other applications so users don’t have to toggle back and forth to find content. Vicki Griesinger, Director of Business Strategy, Worldwide Public Sector at Microsoft, said, “RFPIO® LookUp is available right from Microsoft Teams and surfaces content from all of our content collections without the maintenance overhead.”

With fewer writers and more controls, you might think content ends up sounding too institutional, with too few opportunities to personalize it. On the contrary. With a finely tuned internal knowledge base, prospect- and client-facing workers can find accurate content faster and easier so they’ll have more time to spend on personalizing the interaction.

Plan for unknown knowledge

In your pursuit of the ultimate knowledge repository, remember one thing: It’s going to have to change. In five years, you may need the knowledge you have now or you may not. You’ll definitely need some of the new knowledge you’re going to gain on the way.

Both corporate wikis and internal knowledge bases are updateable, but five years hence do you want to be hacking through a jungle to see what you can update? Or would you rather have the new knowledge curated and grafted onto the existing content for you so that all you have to do is harvest the fruit?

To learn more about using RFPIO to build your internal knowledge base, schedule a demo today.

Improve user adoption in 7 steps

Improve user adoption in 7 steps

Give a person a fish, they’ll eat for a day. Teach a person to fish, and they’ll eat for a lifetime. Surprise all the end users of your new software purchase with a fishing trip and they’ll wonder, “Do I have to do this, and how do I get off this boat?”

As a proposal manager with a shiny new RFPIO lure guaranteed to attract every big fish you can reach with a cast, sometimes it feels like you’re stranded on dry land with a map to the fishing hole but no way to get there.

Introducing new software into your sales enablement tech stack and workflow is no joke. Change management is a sophisticated discipline that examines the processes behind organizational transformation. It’s way too deep a rabbit hole to fall into here, other than to say that 99 out of 100 proposal managers I work with during RFPIO onboarding don’t have any specific experience in change management or software deployment. Which can make the prospect of convincing end users that their jobs and lives will improve with RFPIO somewhat daunting.

As soon as I get my chance to work with the person or team in charge of deploying RFPIO — whether it’s a proposal manager, sales manager, or IT specialist — I recommend inhabiting the following mindset: “How do I set myself up for success?” Now we have a bite-sized challenge we can overcome, rather than an amorphous source of anxiety such as “change management.”

My response to the question, “How do I set myself up for success?” is “Follow 7 steps to improve user adoption.” Let’s roll through them.

#1: Get executive buy-in

Trying to implement any change without executive buy-in is akin to growing a garden without any seeds. The need and desire may be there, but you just don’t have anything to get started. So take that need and desire and use it to build a business case for adding RFPIO to your sales technology stack.

This all has to happen before deployment even appears on the horizon. Gaining and maintaining buy-in from managers and executive sponsors will be critical to making end users more receptive to your excitement and the possible benefits. According to Steve Silver at Forrester, a leading global research and advisory firm, “Every business case must have an executive to champion the investment.”

To build the business case, Silver advises to call out timing of adding RFPIO (i.e., answer, “Why now?”), identify risks and dependencies (key to which he includes this nugget, “Tie the consequences of not using the technology to failure to meet specific goals that a sales organization has committed to attaining”), and clarify budget allocation and source of funding.

After you secure executive buy-in for the purchase, you’ll need to keep them engaged with monthly or quarterly status updates on implementation and RFPIO benefits. It’s important to obtain and maintain their endorsement so that they continue to encourage their teams to use RFPIO.

Here’s an email template of what one of the initial updates might look like.

SUBJECT: RFPIO has already accelerated response time by 40%

Hi [EXECUTIVE NAME],

We’re off and running with RFPIO, and I wanted to give you a quick update on how it’s going:

    • [X#] of end users are now using RFPIO
    • We have used it to respond to [X#] of RFPs this month
    • Compared to the same month last year, we responded 40% faster to RFPs
    • Of the RFPs submitted this month, we know we won [X#] at a valuation of [$X]

End users are picking it up quickly: “It takes about 10-30 minutes to train the client-facing teams on how to search for information in RFPIO.”

As we continue to add content to the Answer Library, we expect to see an even greater leap in proposal quality, greater usage of Auto Respond functionality, and more efficient workflows.

I’ll send another update next month, but feel free to reach out if you have any questions!

Thanks,
[YOUR NAME]

#2: Make sure you have bandwidth

Before you kick off your RFPIO implementation, make sure you have an accurate expectation of the amount of time you’ll need to dedicate to the project. It will require some extra bandwidth. On average, expect to spend about five hours per week for the first three to six months.

Some RFPIO admins prefer to assign their regular duties to another team member so they can “cram” on RFPIO. They’ll spend 15-25 hours per week to focus solely on the rollout and learn RFPIO as quickly as possible. Then they’re able to pare back to a few hours a week. You’ll need to determine which method works best for your team and goals.

As far as what you’ll be doing with that time, here’s an overview of what to expect:

  • Deployment processes: From generating excitement to coordinating with IT, and from amassing content to scheduling training, you need to balance your daily workflow and responsibilities with what’s expected of you during deployment. This will be a short-term issue. While we’ll be there to lend you support, you need to make sure your bandwidth can handle being the point person on this project.
  • Ongoing “office hours”: End users will have questions, especially at the outset. And every time there’s a new hire in sales or pre-sales or proposals or customer support you’ll need to make sure they’re trained and able to thrive in RFPIO. Plus, you’ll want to encourage feedback, negative and positive, to adapt your usage, increase functionality, or add integrations in the future.
  • Driving response management processes: Any tool is only as good as the processes behind using it. Even a hammer has to be swung accurately to hit the head of a nail. A huge benefit to AI-enabled tools like RFPIO is that it will be able to automate most of your existing manual processes. You will still need to work behind the scenes to execute schedules, push collaboration buttons, and drive deadline management. In other words, the robot can swing the hammer as long as you put the hammer in its robotic appendage.
  • Auditing content: Do a full content audit to make sure you are starting off with a cohesive, succinct Answer Library. Watch this webinar to learn more about completing a content audit in RFPIO, or follow these four steps to set your Answer Library up for success:

#3: Admin team, assemble!

Make sure to recruit admin team members from each department that needs to be involved, and has the bandwidth to help with implementation, rollout, and RFPIO day-to-day operations. Sometimes admin teams are made up of only one or two people, and that’s okay, too. Whatever the makeup, they will in turn be responsible for evangelizing RFPIO, reinforcing the value message from executive sponsorship, and liaising with you to provide team-specific training for end users in their department.

For larger, global organizations, the admin team will also be responsible for figuring out a rollout plan. They’ll determine which departments get onboarded first, taking into consideration metrics such as proposal volume, knowledge sprawl or content silos, and collaboration challenges. They’ll also develop a repeatable onboarding process that can be turnkey for new hires or other new end users.

This team will continue to exist beyond the initial deployment of RFPIO. Their meeting cadence will likely be weekly at first, but that cadence will slow down to monthly as you meet a critical mass of end users.

The admin team will also create and monitor milestones that mark success and check in regularly with leadership to report on the milestones. It will be responsible for communicating RFPIO’s value to leadership and end users, promoting transparency for feedback and user expectations, and overseeing the strategy for #4…

#4: Generate excitement through an “awareness campaign”

Start generating excitement, even if you’re still finalizing the purchase. Involving your power users during the early stages of launch will increase the likelihood that they’ll use new software by 55%.

You can do this by setting up an internal email campaign. In addition to informing end users what’s coming, this will also get the organization used to hearing from you about RFPIO training and product updates. Ultimately, you want to provide clear concise answers to the following questions that are common to end users:

  1. Why do we have RFPIO? (e.g., “To automate manual response processes, streamline content management and access, and create higher quality proposals.”)
  2. Why is RFPIO exciting for me? (e.g., for a sales end-user, “Locate answers to prospect questions in near real-time based on updated content that’s searchable from the application you’re already working in.”)
  3. How will it help me do my job better? (e.g., for pre-sales end-user, “Spend more time creating innovative solutions instead of answering the same questions over and over.”)
  4. When will I be trained on RFPIO? (e.g., “Go-live for RFPIO is XX/XX/20XX. Your department is scheduled to be trained the week prior to that go-live date.”

One of the first couple of emails should come from the executive sponsor (some proposal managers like to send a short teaser about an impending big announcement about changing the game for sales enablement). It will validate the addition of RFPIO to your sales tech stack while communicating a high-level value proposition of improvements in productivity, efficiency, and outcomes. It will also set the expectation of cooperation and collaboration among end users to plow the road for your deployment.

Make each email short and informative. Respect your readers’ time. Include links for more information for end users who choose to learn more. Set up the next step in the process. Here’s an example of an announcement email to get you started.

SUBJECT: Announcement: Help with sales response and content is on the way!

Hi everyone,
I’m excited to announce that we are adding RFPIO — one of the best AI-powered sales enablement solutions available today — to your toolbox in the next few weeks. RFPIO will save us a bunch of time, allow us to focus on improving response and proposal quality, unify all sales content, and improve how we collaborate.

You’ll receive more information about RFPIO from me or your manager as we finalize the rollout plan. I’ll also schedule you for a quick training so you can hit the ground running (no worries, RFPIO is super intuitive and will integrate with other apps you’re already using!).

Meanwhile, learn more about how RFPIO will make life easier and more productive:

Let me know if you have any questions. You’ll be hearing from me again soon!

Thanks,
[YOUR NAME]

#5: Train yourself

You’re the tip of the spear on this project. No matter how much help you have from your admin team, executive sponsor, IT, or evangelized end-user base, you’re going to be the person handling initial questions. Even when you tell everyone that they’re free to create a help ticket of their own with RFPIO, they’re going to ask you first.

Best to be prepared.

During onboarding, we’ll take you through extensive training until you feel comfortable with the tool. We’ll also be available when something arises that stumps you. But you can also refer to the following for help, too:

  • RFPIO Help Center (RFPIO customers only): Access an RFPIO self-guided tour and New User Training Checklist as well as expert insight into importing your first documents, organizing your Answer Library, and more.
  • New User Training ChecklistFollow this checklist to get the most out of your RFPIO experience. Each step includes links to Help Center articles to set you up for success.
  • RFPIO University (RFPIO customers only): Watch video training modules on project management, content management, and other powerful capabilities such as user management and Auto Respond.
  • Customer webinars: Sign up for the next live webinar or dig into the on-demand archive of recent webinars for further instruction, product updates, and response management best practices.

#6: Schedule training by role

RFPIO is an intuitive tool. Even so, we have your back when it comes to user adoption. Institutionally, we have prioritized it. You’ll recognize our efforts in user experience upgrades, the new learning management system (LMS) RFPIO University mentioned above, and certification events designed to help you train end users.

Learning how to use RFPIO is relatively simple. Eric Fink, Dynamics & Business Applications Specialist at Microsoft, said, “The first time I logged into RFPIO, it took me about 10 minutes to get comfortable with the platform. After that, I quickly found responses to all of my open questions — seeing 100% value from the very beginning.”

Sales users are savvy. They can pick it up in an hour-long training. You should follow up with shorter, recurring training sessions to make sure they’re really using it, understand its benefits, and feel comfortable asking for help, if necessary. Respect end users’ time by training them only on what they need to know.

Again, manager buy-in is crucial here. Work closely with sales managers to make sure they fully comprehend the opportunity offered by RFPIO. They will help you overcome any pushback from sales end users, who may hesitate at the request to disrupt their workflow for a training, no matter how short and helpful it may be. They will also help ensure their team is using the tool consistently.

#7: Monitor, collect feedback, adapt

The push for greater user adoption is never complete, but it can most certainly be less painful and onerous. The good news is that user-adoption pushback fades as win rates increase.

After the rush of your initial rollout, you’ll be re-investing some of the time you used to waste on all the manual tasks of building proposals and chasing down content and subject matter experts into RFPIO administration. Beyond driving your underlying processes of project, content, and user management, you’ll also be communicating regularly with your admin team and executive sponsor.

RFPIO makes it easy to report on usage because every action is captured within the tool and spun into insight for your desired output. However, you’ll want to gather anecdotal input as well. Speaking to end users and their managers about what’s working and what’s still a struggle with regard to RFPIO or your response management strategy will help you adapt to future needs.

Depending on the size of your organization, you can expect to see value from using RFPIO 90 days to six months after implementation. You may see value in as few as 35 days if you push it, but be wary of setting unrealistic expectations that can circle back around to sabotage the overall adoption.

Want to hear from someone other than RFPIO? See how Hyland Software managed user adoption: “By making sure RFPIO is something everyone can use… everyone is using it. User adoption has been outstanding.”

Get the latest stories delivered straight to your inbox

Subscribe to our blog and never miss an important insight again.

Thank you for subscribing.

Something went wrong.