11 Steps to a Better RFP Document
 

11 Steps to a Better RFP Document

on

  • 2,939 views

A good RFP isn’t just a list of technical requirements you’re ticking off; there are people interacting with your support software. Your customer support tool touches so many parts of your ...

A good RFP isn’t just a list of technical requirements you’re ticking off; there are people interacting with your support software. Your customer support tool touches so many parts of your organization—it’s serious business—so be prepared to invest some time in getting it right from the start.

Statistics

Views

Total Views
2,939
Views on SlideShare
1,028
Embed Views
1,911

Actions

Likes
1
Downloads
19
Comments
0

11 Embeds 1,911

http://www.zendesk.com 1641
https://www.zendesk.com 195
http://cloud.feedly.com 29
http://zendesk.local 14
http://feeds.feedburner.com 12
http://www.newsblur.com 11
http://newsblur.com 5
http://pt.zendesk.com 1
http://feedly.com 1
http://analyst.test.ciradar.com 1
http://en.zendesk.tv 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

11 Steps to a Better RFP Document 11 Steps to a Better RFP Document Presentation Transcript

  • 11 Steps to a Better RFP Document How planning ahead can extend the life of your new customer support solution
  • Define the objective Know what you want the outcome to be and state it. What specific problems will the new tool solve? What will success look like?
  • Narrow the field Shortlist your vendor options based on critical criteria like licensing model and budget.
  • Factor in all the costs Don’t forget to include support and training, implementation, customization, annual licensing fees, and future upgrades.
  • GATHER REQUIREMENTS FROM ALL STAKEHOLDERS 1 2 3 4 Support staff Customers Partners and suppliers Managers 5 IT
  • Assign priority weightings When prioritizing features and capabilities, know the difference between a showstopper and a nice-to-have.
  • Allow for growth Try to anticipate things you may not need today, but you may want or need in the future.
  • Profile the vendors on your shortlist Do your research. What do their customers say? What’s the support experience like? What does their product roadmap look like?
  • Ensure security and uptime If you’re considering SaaS solutions, be sure to ask about security policies, uptime history, and maintenance downtime.
  • Request a tailored demo Insist on a demo customized to your specific use case. Even if you follow best practices, there may be variations in your approach.
  • Understand deployment time Ask how long a typical implementation takes and be prepared to manage those expectations with your stakeholders.
  • Don’t forget company culture Ask about the vendor’s vision, company culture, and values. Make sure they match the product and the cultural values of your organization.