Item: Responsive
Rating: 10
Author: Verified User

Overall Satisfaction with Responsive

Use Cases and Deployment Scope

Responsive is our database to house answers related to RFPs and security questionnaires. We've used Loopio in the past and Responsive is much more powerful in terms of tracking all the meta data and now allowing us to use AI to help craft new responses. The review cycles help us keep content up to date and features like de-duplication allow us to avoid redundancies in content.

Pros and Cons

Pros

Find similar answers
Find content that is duplicate or not assigned an owner
Track changes to content
Collaborate with others through comments

Cons

Review cycles don't allow you to notify people in advance of due date.
Merging similar and duplicate entries doesn't always capture meta data like use count or comments.

Return on Investment

Library Health Dashboard is helpful in reducing time to clean up content but could use additional improvement by showing more granular data instead of a global assessment like good, poor, moderate.
ROI is reduced for us because of additional cost for using AI
Overall, Responsive has significantly improved our proposal process.

AI Capabilities

See prior answer. Our ROI on the tool is reduced by high cost of each user under AI upgrade model we went with.

Data and Insights

See prior answers. Library Health Dashboard could be improved by showing percentages instead of broad health assessments of good, poor, moderate.

Likelihood to Renew

Responsive is really a best in class software and we rely on it for our proposal process.

Alternatives Considered

Loopio

Loopio is proposal management "lite" and seems to spend more on marketing than product upgrades.

Key Insights

Do you think Responsive delivers good value for the price?

Not sure

Are you happy with Responsive's feature set?

Yes

Did Responsive live up to sales and marketing promises?

Yes

Did implementation of Responsive go as expected?

Yes

Would you buy Responsive again?

Yes

Other Software Used

Salesforce CMS, Microsoft SharePoint, Okta

Likelihood to Recommend

Knowing what project the content first came from, along with being able to view all historical activities for an entry and where it's been used recently all help us manage content.

It's less helpful as an across-the-board platform for all our company's users as the pricing model for AI makes individual access expensive. We used to pay per-project, instead of per user, and it was cumbersome to limit the projects but we didn't have to worry about how many users could access the data.

Responsive Feature Ratings

Comments

Please log in to join the conversation

Responsive works for our proposal team