In episode 179 of the Content Strategy Experts podcast, Sarah O’Keefe and Alan Pringle share the inside scoop on how to write an effective request for a proposal (RFP) for content operations. They’ll discuss how RFPs are constructed and evaluated, strategies for aligning your proposal with organizational goals, how to get buy-in from procurement and legal teams, and more.
When it comes time to write the RFP, rely on your procurement team, your legal team, and so on. They have that expertise. They know that process. It’s a matter of pairing what you know about your requirements and what you need with their processes to get the better result.
— Alan Pringle
Related links:
*
Survive the descent: planning your content ops exit strategy (podcast)
*
The business case for content operations (white paper)
*
Content accounting: Calculating value of content in the enterprise (white paper)
*
Building the business case for content operations (webinar)
LinkedIn:
*
Sarah O’Keefe
*
Alan Pringle
Transcript:
Disclaimer: This is a machine-generated transcript with edits.
Alan Pringle: Welcome to the Content Strategy Experts Podcast brought to you by Scriptorium. Since 1997, Scriptorium has helped companies manage, structure, organize, and distribute content in an efficient way. In this episode, we talk about writing effective RFPs. A request for a proposal, RFP, approach is common for enterprise software purchases, such as a component content management system, which can be expensive and perhaps risky. Hey everybody, I am Alan Pringle.
Sarah O’Keefe: And I’m Sarah O’Keefe, hi.
AP: So Sarah, we don’t sell software at Scriptorium, so why are we talking about buying software?
SO: Well, we’re talking about you, the client buying software, which is not always, but in many cases, the prerequisite before we get involved on the services side to configure and integrate and stand up the system that you have just purchased to get you up and running. And so, because many of our customers, many most, nearly all of our customers are very, very large, many of those organizations do have processes in place for enterprise software purchases that typically either strongly recommend or require an RFP, a request for proposal.
AP: Which let’s be very candid here. Nobody likes them. Nobody.
SO: No, they’re horrible.
AP: Vendors don’t like them. People who have to put them together don’t like them, but they’re a necessary evil. But there things you can do to make that necessary evil work for you. And that’s what we want to talk about today.
AP: So the first thing you need to do is do some homework. And part of that homework, I think, is talking with a bunch of stakeholders for this project or this purchase and teasing out requirements. So let’s start with that. And this is even before you get to the RFP itself. There’s some stuff you need to do in the background. And let’s talk about that a little bit right now.
SO: Right, so I think, you know, what you’re looking to get to before you go to RFP is a ...
