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.

Why Business Units are best for visibility and control

Why Business Units are best for visibility and control

If you’ve attended an RFPIO webinar or conference recently—or read the Freedom to Thrive white paper—then you’ve heard us mention […]


Category: Tag: RFx automation

Why Business Units are best for visibility and control

Why Business Units are best for visibility and control

If you’ve attended an RFPIO webinar or conference recently—or read the Freedom to Thrive white paper—then you’ve heard us mention RFPIO’s ability to break down silos. If you’re an RFPIO customer, then hopefully you’re already living the silo-flattening dream.

Through knowledge management in the Content Library and Content Library in-app collaboration and project management tools, and real-time accessibility by way of RFPIO® LookUp to all of this content, silos can be reduced to rubble. Greater efficiency and productivity ensue, correlating quickly to improved response quality and increased win rates.

Nevertheless, sometimes separation is a good thing. Whether it’s for security or compliance purposes, or even perhaps geographic locations, there are RFPIO customers who want greater control and visibility. For this, we have Business Units.

“RFPIO’s enterprise-level capabilities enable multiple business units, including partners, to collaborate on a single platform. It also reduces communication channels during the proposal development process.”
-Page Snider, Director of Business Program Management, Microsoft Consulting Services What are Business Units?

Business Units (BUs) allow you to create distinct operating units within a single RFPIO instance. Think of them like individual villages within a kingdom. These BUs give you the control in keeping people, projects, and content confined to a specific BU, but also allow you to share any of those across your instance to another BU. User profiles remain unchanged as they’re shared with each Business Unit. Additionally, advanced features are available to provide cross-unit functionality across your entire enterprise.

While Collections pertain to simply restricting content, and complete separate RFPIO instances provide no collaboration between people on projects and content, Business Units can provide a level of control and collaboration to fit any growing enterprise business.

When should you use Business Units?

Software business units are quite common in enterprises, but they’re growing in popularity with small- and mid-sized businesses, too. Prior to the pandemic, it was standard operating procedure for sales teams to work remotely while marketing, InfoSec, and customer support worked onsite. With the trend toward hybrid and fully remote work for all teams, content accessibility and control—as well as visibility into how it’s used (or not used)—has rocketed up the priority list for many companies.

For businesses of any size, there are 3 typical use cases for Business Units.

Use case #1: Separate cost centers or business groups

Business Units are most often separated by business group (Marketing, Sales, etc.) or region (EMEA, NAM, LATAM, etc.).

Business unit - cost center

Many RFPIO customers start with two Business Units, separating InfoSec content from all other content that responders will be sharing with prospects, customers, analysts, or investors.

Regional separation would mean your organization wants a Business Unit for each GEO where business is conducted. Factors such as language and compliance weigh heavily into the determination to split an RFPIO instance into Business Units according to GEO boundaries.

business units - GEO

Use case #2: Mergers

The mergers and acquisitions trend in 2021 was off the charts, and it doesn’t appear to be letting up in 2022. According to Wolters Kluwer, the U.S. saw a record $2.9 trillion in transactions (up 55% from $1.9 trillion in 2020). As RFPIO grows in popularity (250K users and counting…) and response management gains traction as an integral part of the sales tech stack, it’s more and more likely that mergers will take place between businesses that are each running their own RFPIO instances.

When a merger occurs with two businesses that both use RFPIO, it’s certainly an option to maintain the two separate instances. However, if you want more control and visibility, then you can convert one instance into the primary instance and then add the team or teams from the other company as a Business Unit.

Use case #3: Projects portion control

Depending on how your business operates and is structured, separate teams may need different numbers of active projects enabled in RFPIO. Whereas you have a set number of active projects in a single RFPIO instance—50, for example—without Business Units it’s a free-for-all for teams to use those projects. If you find that one or two teams are constantly clamoring for additional active projects, then Business Units can help set aside a suitable amount of active projects for those teams.

Let’s take the example of a single RFPIO instance with 50 active projects. In the case of a software business, sales and InfoSec may need more active projects than marketing and customer support. Business Units can allocate projects to meet each department’s needs: 15 for sales, 15 for InfoSec, 10 for marketing, and 10 for customer support.

business units project allocation

What are the benefits of Business Units?

Primarily, project control and content visibility, which result in additional benefits, including:

  • Ability to scale RFPIO across multiple departments to increase win probability and close deals faster.
  • Rolled-up reporting allows for the most comprehensive visibility available for your RFPIO instance.
  • Identify areas that may need more project management support (we see this a lot in InfoSec).
  • Allow for greater content detail and answer accuracy, and, ultimately, a more robust content repository (which pays off when you need to share content across multiple Business Units).
  • Better, granular visibility into projects, people, and content in each Business Unit but still administered within a single RFPIO instance.

Cross-Business-Unit collaboration is something that we’ve seen more as use cases for BUs have evolved. For example, projects can be shared across Business Units. Say you’re running an InfoSec Business Unit project and you notice that some of the questions may be mapped to brand messaging, which would better be handled by someone in marketing. Share that project to the marketing Business Unit to 1) delegate to a suitable subject matter expert, and 2) ensure that you’re delivering the best possible response. There are some user permissions at play, but it’s certainly possible.

Here’s a real-world benefit example from an RFPIO customer I worked with. This client had a Business Unit for North American and another for EMEA. They wanted Business Units so that EMEA could more effectively track its project workflow and would not have to wait to be granted projects from a global team managing the original single instance.

Teams, content, and templates (by language) were separated. Leaders from both GEOs were connected, however, and collaborated on strategic initiatives. They set up the roll-up reporting so that executives could more effectively track time savings to determine how many more opportunities the EMEA team could pursue.

How do you know if you need Business Units with your RFPIO instance?

Review these 6 questions. If you answer “yes” to any of them, then schedule a consultation to see if Business Units may be a good option for you:

  • Do multiple teams/departments/cost centers use RFPIO?
  • Do you want to expand RFPIO in your organization?
  • Do you have RFPIO users located in multiple GEOs?
  • Do you respond to bids, RFx, security questionnaires, or other external requests in multiple languages?
  • Do you have a single executive stakeholder or team that reviews the effectiveness of RFPIO in the enterprise?
  • Have you merged, or are you planning to merge with a company that is also using RFPIO or RFP360?

If you’re still not sure but want to know more about Business Units, you can review my webinar in the Help Center if you’re an RFPIO customer.

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 Content 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.

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.