Skip to content
EP 596June 20, 2022

Your RFP Process

Tony MartignettiJosh Riman
Nonprofit Radio
Episode 596
0:00 / 0:00

About this episode

There’s a better way to manage requests for proposals, so that you weed out vendors who aren’t right, choose the best finalists, select the best provider, and transition smoothly to project launch. Josh Riman from Great Believer explains. (This is part of our coverage of #22NTC, hosted by NTEN.)

Here’s the transcript

Tony MartignettiHello and welcome to Tony Martignetti Nonprofit Radio, big nonprofit ideas for the other 95%. I'm your aptly named host of your favorite hebdomadal podcast. And oh, I'm glad you're with me. I'd get slapped with a diagnosis of ophthalmodynia if you pained me with the idea that you missed this week's show. Your RFP process. There's a better way to manage requests for proposals so that you weed out vendors who aren't right, choose the best finalists, select the best provider, and transition smoothly to project launch. Josh Riman from Great Believer explains. This is part of our coverage of 22NTC hosted by NTEN. On Tony's Take Two, thank you. We're sponsored by Turn 2 Communications, PR and content for nonprofits. Your story is their mission. turn-2.co. And by Fourth Dimension Technologies, IT infra in a box, the affordable tech solution for nonprofits. tony.ma/4d, just like 3D, but they go one dimension deeper. Here is your RFP process. Welcome to Tony Martignetti Nonprofit Radio coverage of 22NTC. It's the 2022 Nonprofit Technology Conference. Of course, you knew it was coming on Nonprofit Radio, and we're kicking off our '22 NTC coverage with a returning NTC guest. Very welcome, very glad to have you back, Josh Riman, president and founder of Great Believer. Josh, welcome back.

Josh RimanThanks for having me.

Tony MartignettiPleasure, real pleasure. Thank you for kicking off our '22 NTC coverage. Your session topic at the conference was running an RFP process while keeping your cool. And I see that you're solo this time. In the past, you've had, you've had the support of other Great Believer team members. Now you're solo. Let's see, let's see how the founder and CEO does by himself.

Josh RimanNo pressure, right?

Tony MartignettiAll right. Your team is watching. That's right. So what about this RFP process? I imagine you've filled out, I don't know, scores, maybe hundreds of these through the years at Great Believer. What, just like overview, what are we not quite getting right about our RFPs?

Josh RimanYeah, I think I've got an interesting perspective because I'm not the one who's writing the RFP or sending it around or reviewing it, but the one who's actually receiving it and responding to it. And like you've said, yeah, we've seen scores and seen the good and seen the bad and seen the ugly. And some RFPs are great and some RFPs leave a lot to be desired when they're not specific enough or they're not clear enough. And we've essentially created a session that organizes the RFP process into 6 stages, which are write the RFP, distribute it, hold Q&A, review proposals, interview finalists, and select a winner. And in looking back at other RFPs we've received and things that work and things that don't, put together a series of dos and don'ts that we thought could be helpful for organizations that are working on RFPs, whether it's someone who's an RFP wizard who does it all the time, or someone who's making their first RFP, trying to give them a good place to start from.

Tony MartignettiOkay. Um, before you even— all right, so you have 6 steps, so I'm gonna be a little troublemaker. I'm gonna be like, before even the, the first one, which is writing,

Josh RimanYeah.

Tony MartignettiWhat about, you know, do you need an RFP? Does this project require an RFP? Do you need that kind of formal process? Do you—

Josh RimanIf we had it our way, nothing would have an RFP.

Tony MartignettiNothing would have.

Josh RimanYeah. Our understanding from talking to organizations is that there could be a lot of reasons. The 2 that I'm aware of that organizations put out RFPs are, A, if there's a certain amount of budget being invested, there's a policy that says you need to consider a certain number of vendors. And in doing so, you should release an RFP to make sure it's a level playing field. field. That's one reason. Another reason is that often the board stipulates that no matter what the project size might be, they want to have multiple candidates they can review and, and assess who might be the best fit. And I think there could be other reasons also to play into it, but those are the ones that we often hear. I don't think anybody likes the RFP process, whether you're the one writing it, receiving it, or reviewing it, but it feels like it's a necessary evil for a lot of nonprofits.

Tony MartignettiOkay. And, uh, and, uh, let's acquaint listeners with what Great Believer does. Like, what kind of RFPs are you seeing? What— what is it? Web design, I know, but maybe you may go much deeper than web— website development.

Josh RimanNo, it's mostly that. We're a graphic design agency for nonprofits. Web design and development is our core area of focus, and most— the vast majority of the RFPs that we apply to are for web. And I think that makes sense because Web is often a large investment that a nonprofit's making compared to something smaller, a one-off project, let's say an annual report or something of that nature. And when they're doing a website project, it's often years in the making to collect the funding, to get the executives on board to go for it, and to actually engage someone in this project. I think because of that, they want to review multiple vendors, candidates, and they also want to have a document that says, here's exactly what we're looking for. So all of the proposals they receive are as apples to apples as can be.

Tony MartignettiRight, right, right. Like you said, everybody's level playing field, everybody's had a chance to answer the exact same questions, everybody's seen the exact same specs, et cetera. All right.

Josh RimanExactly.

Tony MartignettiAll right, let's get into your 6 steps. Writing, what do you wanna see us do better?

Josh RimanYeah, so we did a poll on—

Tony MartignettiDon't, actually just stop. Don't, don't write.

Josh RimanRight, right, exactly, yeah.

Tony MartignettiIf you have to, if you have to, all right, let's get started, yeah.

Josh RimanExactly. We, we did a poll at the session and asked, of these 6 phases, which one do you most detest? And again, the 6 phases are write it, distribute it, hold Q&A, review proposals, interview finalists, select a winner. The vast majority of people most detest writing the RFP. It's definitely the hardest thing, and because of that, we have the most dos and don'ts that apply to that stage. So I'm happy to just start ripping through them, and if you have any thing you want to add or questions you want to ask, go for it.

Tony MartignettiYeah, okay. My, my fear here is that people feel that they have to be like, oh, formal, you know, like they're almost writing a legal document.

Josh RimanYes.

Tony MartignettiThey want to be such, such great degree of specificity that, I don't know, maybe the, maybe the overall purpose gets lost in the, in the, in the, in the weeds. We'll find out. All right, yeah, go ahead, tick off some and, and, uh, we'll see. Yeah.

Josh RimanWell, that's a good point because one of our dos is be specific about your needs, but I think there is a limit there where some groups try to be so overly specific that it becomes prescriptive and you're not letting the candidates themselves showcase their process and how they would actually solve your problems. So

Tony Martignettiyeah,

Josh Rimanbe specific enough that the right people apply for your RFP, but not so specific that it puts them into a box.

Tony MartignettiRight, that we have to do it exactly this way. Or, you know, even though we think we have a better way, and it leaves out the possibility of some— I mean, you're— a lot of your creativity is, is in not only graphic design, but in like database design, right? You know, the, the back end.

Josh RimanExactly.

Tony MartignettiAnd, you know, they're not availing themselves of, you know, maybe half your expertise if they're just— if they're speccing it out so much detail that, uh, you know, they just want you to be an artist or a graphic designer. And then, and then like a Drupal coder or something. All right.

Josh RimanRight, right. We're more focused on WordPress, but your point is totally legit. We don't expect the RFP to have all the answers, and we also don't expect to be able to solve everything through our proposal, but at least we wanna get somewhere where it's feeling like this could be a promising fit and we're understanding your needs. I think that's the balance.

Tony MartignettiAnd what? Say?

Josh RimanI think that's the balance is we shouldn't expect the RFP to have all of the right questions, and then you, the organization, should know expect our proposal to have all the answers. We only know so much at this point. But if it seems like there's good chemistry, and it could be a good fit, then let's move forward and talk more about the potential of working together.

Tony MartignettiRight. And you want to give your vendors a chance, you mentioned this, to showcase their expertise. Here's what we bring to it. You know, let us, let us share some ideas that we have that we think may be better than yours, because this is what we do.

Josh RimanExactly.

Tony MartignettiIf you did it, you wouldn't need us, you know, if you All right, what else, what else you got in the writing stage?

Josh RimanWell, related piece to that is you definitely want to get input when you're working on the RFP. I think there are 2 groups you can get input from, because writing an RFP, when you start it off, you can be thinking, I don't even know where to start. How do I frame this thing? How do I organize it? How do I structure it? So 2 thoughts here. One is ask other organizations who have put out similar RFPs how they did it, and ask them to share their RFP if they're comfortable doing so, and then use that as a template. And use it as a starting point, modify it as needed to best serve your organization's needs, but don't feel like you need to reinvent the wheel. There are lots of good RFPs out there, and by asking friends in the space what they've done for their RFPs, you can probably get a good template to start from.

Tony MartignettiOkay, what else you got? That's, that's a straightforward one. Good.

Josh RimanThen the other thing in terms of asking people for input is people at your organization. So maybe there's a group that's assembled, that's the RFP team. And it's perhaps mostly the comms team, maybe some people from development, you'll still wanna survey, you know, folks in IT, executives, other people to make sure the RFP you put out is as comprehensive as can be in terms of collecting the goals and input from other groups at your organization. So then you get the right agency to work on this project in a way that helps everybody and doesn't just help comms or just help development, so on and so forth.

Tony MartignettiI can see, you know, this is generic advice that's gonna apply to any RFP. Exactly. It's not only a web development project RFP conversation.

Josh RimanYep. This is, this is, this is for any RFP that anybody puts out.

Tony MartignettiYeah. Yeah. More, more on the, on the writing stage?

Josh RimanYeah. Got a, got a couple more dos in the writing stage. The first is, this is kind of sounds like a simple one, but when you receive a proposal, you're gonna learn so much about these agencies you're considering, you know, their project team, their process, their budget, their timeline, and so on and so forth. In the RFP, it's nice if you, the organization, also introduce yourselves, not just your mission and vision, but your project team. So we, the agency, can get a sense for who we'd be working with. You know, how big is the team? Who are they? How long have they worked there? What are their positions? That's just a nice way to kind of level the playing field and give us, the recipient and respondent to the RFP, a sense for what it might be like to work with these people.

Tony MartignettiYeah, like, what, what's their expertise? You know, the expertise may be all, all, uh, maybe it's all technical, or, or maybe it's on the other side, maybe it's all graphic and communications marketing related, and there isn't anybody with it with a, with, with a technical background. That's, that's valuable for the RFP respondents to know, right?

Josh RimanYou got it. All right, I've got one more do on the write the RFP section, which is there's something called intent to bid. Which can be a deadline you set in your RFP that says, you've received this RFP, you've read it through, if you plan to submit a proposal, let us know by X date. And that's great for the organization primarily, 'cause then, you know, let's say we distributed this RFP to 8 groups, we know we're gonna get 5 proposals, and we don't need to play a guessing game. Maybe one of the people we distributed to is one that we're secretly hoping is the best fit for us. Yeah. And then you'll know if you say, again, submit your intent to bid, which is just an email where we would email the organization and say, we intend to bid on this RFP. You'll know who's bidding, you'll know who's not. And then there are fewer surprises when the actual proposal deadline hits as to who submits and who doesn't.

Tony MartignettiWhat if your secret insider, or not necessarily insider, your secret favorite is not, has not, said that they intend to bid. Do you— now, I mean, you're supposed to be fair about this too, but I mean, there's nothing legal around it. It's just, it's really just ethical and moral, right? You know, you, you're not supposed to be favoring— the whole purpose of an RFP— well, no, that's not the whole— a purpose of an RFP is a level playing field. So you're not supposed to be favoring your, your favorite, you know, and So what do you, what do you do then? You just, you ought to just let it go and hope you get another, another good one that rivals what you, what was your favorite. That's what you ought to do. Is that, you think people do that? Or have you, I don't know, have you seen shenanigans? Have you seen, uh, dirty tricks around RFPs? You don't have to name names, but—

Josh RimanI've definitely seen some shenanigans. I think something that you could do as the organization to inquire as to who's going to submit while still leveling the playing field is maybe a day before the deadline for organizations, for agencies to submit their intent to bid, email everybody that you sent the RFP to and just say, just a reminder, tomorrow is the deadline for receiving your intent to bid. So in case, you know, your favorite, your secret love, it falls off their radar, but they do intend to bid and they just honestly forgot, it gives them a second chance to do so. And then if— or a second reminder to do so. And if they don't submit, then c'est la vie. I think you've done everything you can while still remaining as impartial as you can.

Tony MartignettiYes, impartiality, you know, right. All right, but you've seen shenanigans.

Josh RimanOh yeah.

Tony MartignettiWe'll leave it at that. All right.

Josh RimanYeah,

Tony Martignettimaybe you've been the insider, maybe you've been the beneficiary of the shenanigans. We'll leave it there. I'm not— maybe you have, maybe you have not. Uh, this is just the host speculating.

Josh RimanYeah.

Tony MartignettiPure speculation. It's time for a break. Turn to communications. Have you got your crisis communications plan in place so that you know who's responsible for message creation in the face of a crisis? Is it one person or a couple of folks? Who needs to approve the messaging? Who's authorized to speak? Who speaks internally? Who speaks externally. There is more to a crisis communications plan than that. Turn 2 can help you with yours. Turn 2 Communications, turn-2.co. Now back to your RFP process. You had some don'ts. Yeah, some don't— uh, just give us a couple of, like, 2, your top 2 don'ts for the, for writing.

Josh RimanI'll give you just one don't for writing, and that is don't withhold your budget. It's so important that the organization puts a budget in their RFP. It could be a specific number, it could be a range, it could be a don't exceed this number, but if you really want that apples-to-apples comparison, you need it. And also, it helps to filter down the right types of candidates. So if your budget is X, And you're clear about it, you're going to get candidates that can do your work for that amount. You're not going to get a much larger agency who can never work with you because their price for that work is 4 times that. And you also probably won't get a small freelancer who is a one-person show and isn't able to do work with the kind of capacity they have. So I think budget's important because it doesn't waste the candidate's time in submitting a bid if they're not the right fit from a financial perspective. And doesn't waste the organization's time reading through proposals that ultimately have budgets in them that are way too high to make work. So sharing the budget is essential.

Tony MartignettiThat's an important point, that last point, because, you know, let's continue your hypothetical. You submit to— or you send it to 5— sorry, you send it to 8, and 5 submit, uh, they say they're going to, and then they do, and then like 4 of them are out of your budget range. So now you've got— now you're down to 1 Or you've got to expand your budget. You know, but so I'm emphasizing that point because the obvious pushback on the nonprofit side is, well, if I give them my budget or even a range, then they're going to go to the top end of it. They're going to expend my budget. I tell them it's a $30,000 project. They're going to bill me $30,000 when they would have done it for $22,500.

Josh RimanThat's fair. But I would say just give your budget honestly. Put a number in there that you're comfortable spending, and no matter who it is that you choose to work with, just know that you found the right fit. And sure, maybe they could have done it for $5,000 less, but ultimately, if that's a budget you set aside, who cares? That was already set aside for the project, so just put it toward it.

Tony MartignettiOkay, well put. I agree. And, and it is, it is valuable. I, I, you know, as a planned giving consultant, When I'm at the inquiry stage, I don't— I think, I don't know, in 19 years of consulting, I've probably done like 2 RFPs. So they're highly, very rare. But, you know, but in conversations, I always ask for a budget or a range.

Josh RimanYeah.

Tony MartignettiYou know, I need to know, is, you know, everything we just scoped out in a great, you know, 30-minute conversation, Is your budget in line with the aspirations that you just identified?

Josh RimanAbsolutely.

Tony MartignettiIf I'm thinking this is a $30,000 project and you're thinking it's an $8,000 project, we're not— either you've got to scale down your aspirations or you've got to bring up your budget because we're not even close. So it's critical. It is critical to share your budget. All

Josh Rimanright. And I do think that the way things are moving, More organizations are more comfortable sharing budgets. And I think this is in some ways working in parallel to job listings. I feel like many more job listings these days have the actual salary requirements, whether it's a specific number or a range, especially in the nonprofit space. I know that websites like Idealist essentially mandate that you share a salary, which I think is great. And I think those things again are moving in parallel and there's definitely a movement toward transparency.

Tony MartignettiA lot of that is equity too. That minority populations are going to be disadvantaged when it comes to the salary discussion because they're generally, you know, paid less. So Enten is another example of that. Enten requires either a number or a range. They require at least a range in their job listings too. So—

Josh RimanI love that.

Tony MartignettiI agree. Yeah. Distribution.

Josh RimanYes. Now it's time. You've, you've, you've written your RFP. Now it's time to send it out. I've got one do and one don't that are essentially opposite sides of the same coin. Do is you need to find qualified candidates. So consider people you've worked with before. Ask around, ask other organizations who have done similar projects in the past who they worked with and how well it went. Do some research, you know, do some online digging, search for some keywords that take you to groups that maybe you're not aware of or people in your network or not aware of, but you think could be a good fit. We get a lot of RFPs from people that find us online through searching for, you know, design agencies in New York City or nonprofit-focused design agencies in Brooklyn, whatever the keywords are that bring people to us. So it's essential to find qualified candidates. And the flip side to this coin is, do not blast out your RFP to the masses. And, you know, we see this happen a lot, and I understand why it happens. There are websites like rfpdb.com. There are other places to post your RFPs. You can put it on a listserv like the Progressive Exchange. And you are going to get a lot of respondents, and you're going to get a ton of junk. You're going to get people who don't thoroughly read your RFP, that are just spending 10 minutes on it, that don't really understand who you are. And it's going to create a lot of extra work for you to review these and try to pick out the, you know, the needles in the haystack that are actual fits for you. So it will take time to find the right groups to send your RFP to. I know we said 8 as a number before. I think 8 is a good number to shoot for. Try to shoot for at least 5. Yeah. that you feel good about. But if you spend the time to make sure those you send it to are actual potentially good fits, it'll pay off in the end, save you some time.

Tony MartignettiUh, I like the idea of asking for a— an intent, uh, what did you say, an intent to—

Josh RimanIntent to bid.

Tony MartignettiIntent to bid. Because then if, you know, if you only come back with 1 or 2 intents to bid, then to be fair to everybody, you might want to revise your RFP Or you might end up sending it to more, more agencies than you, you know, and then you have to expand the deadline, I guess. Yeah, you would, uh, you know, but you want to reassess if you're only going to get like 1 or 2 out of, out of however many you, you, you distributed, you know, 1 or 2 is not, it's not so good. Well, 1 is terrible.

Josh RimanYeah.

Tony Martignetti2 is, is all, it's like, is, is half as bad as terrible. Yeah, that's terrible. 3 is 1/3 as bad. So You know, you want to have a decent number to choose from.

Josh RimanYes. All right.

Tony MartignettiIt's time for a break. Fourth Dimension Technologies. Their IT solution is IT infra in a box. It's budget-friendly. It's holistic. You pick what you need and you leave the rest behind. That's why it's your IT buffet. Why is it budget-friendly? Because you're picking what you can afford from their extensive buffet. Your budget can't afford Chateaubriand for 2? Have a hamburger. No chocolate soufflé? Get the brownie. You choose what's right for your IT situation and your budget. Fourth Dimension Technologies, tony.ma/4d. Just like 3D. But they go one dimension deeper. Let's return to your RFP process. The Q&A stage should be— the Q&A, that's for— who's that? Is that for the bidders to ask questions?

Josh RimanExactly. So 2 things here. The first is that there should be a deadline in your RFP that says you need to send us all of your questions by X date. And That's important to give people an opportunity to help to put things into focus or clarify different parts of your RFP to make sure they're the right fit, and also that they understand how to price it out and how to develop a process around it. And then, so that's a do— set a deadline for all questions. I would say give candidates at least 2 weeks from when they receive your RFP to submit their questions to you and just submit them through email. And then the don't is don't withhold Q&A results. And by that I mean, don't just send the answers directly to the people that ask the questions.

Tony MartignettiI was gonna ask you this one. Okay. Yeah. Share. Should you share these questions?

Josh RimanSend the answers to every question, to everyone you sent your RFP to. Even if someone didn't ask you a single question, you need to share the answers with them because there might be things that you answer that fundamentally change the structure of your RFP or the process or the old ultimate goal that you're looking to strive toward. So it's essential. And what we often receive, and we love, a Google Doc or a Word doc that just has all the questions in there divided into categories. So maybe there's a question about timeline, a question about budget, a question about process, a question about logistics, whatever it might be. And it's not saying like, Great Believer asked this question, and so-and-so asked this question. It's just questions and answers. It's very generically formatted. Ideally divided into sections, and it's so helpful for everybody to receive.

Tony MartignettiDo you only do that at the end of the question period, or are you doing it— are you updating it as questions come in? Because it might stimulate— because those questions might stimulate new questions, and if you only did it at the deadline, then, then it's too late for the people to ask those new questions.

Josh RimanYeah, it's That's a good question. I would recommend doing it once, and then if people still have questions after that, then they can make clear that they're making assumptions in the— in their proposal, and that's okay. They can just say like, here's a piece I'm not sure about, we're going to approach it like this, but if you have other thoughts, then we can reevaluate. But I think the way it usually works is the Q&A where all the questions are collected and then all the answers are distributed. Usually answers like 95% of the questions, because if you've got 5 groups that are really engaged in the process and sending really thoughtful questions, between those 5 groups, you're gonna answer almost everything. And between those 5 groups, they're probably gonna have a lot of similar questions also.

Tony MartignettiOkay. Okay. So one time, one shot. All right. All right. Reviewing, right? We're at the review stage.

Josh RimanYeah. You've held your QA. You've, you've received the proposals. Now it's time to review them. And the first— well, these 2 dos are related, because you've got to get an RFP review team. It shouldn't just be on like a single person, let's say, to review all these proposals and say who the winner is. You need to develop a team. Ideally, it should be people that span different departments— somebody in comms, somebody in development, somebody in IT, so on and so forth. There should be some nice representation there. And you also need scoring criteria. So there should be kind of a rubric that you develop, where you can score each proposal based on, let's say, the plan they put together, the experience they demonstrate, the budget they share, their timeline, the reference—

Tony MartignettiLike a 1 through 5, you know? So again, you're trying to level playing field. Should, should every evaluator evaluate every proposal?

Josh RimanYeah, that, that's, that's the goal. Everybody evaluates every proposal. But you could also say, okay, we've got these 5 scoring criteria. You know, let's say it's project plan, experience, budget, timeline, and the understanding of your mission. You may say, I don't want those to be equally weighted. For us, I think project plan is 40%, and we think that the budget is 10%, whatever that is. You can then assign different weights to different categories, but you should still evaluate every proposal the same way. And literally, when you finish reviewing a proposal, score it. Yeah. Have those, those 5 columns right there and give it a score on a scale of 1 to 5, and then do it blindly, and then come together as a team afterwards and look at how you all reviewed these groups and see which one has the highest average score, or which, let's say, 3 had the highest average score, and those are the ones you might want to interview in the next stage.

Tony MartignettiYou mentioned something, uh, review blindly. So are we— is your recommendation that You not know who the, who the respondent is? Is that what you meant?

Josh RimanI think it's okay to know who they are. What I meant was, um, if you've got a review team of 4 people, review them in isolation from each other and then come together and share your unbiased thoughts.

Tony MartignettiOkay, okay. All right, interesting. Yeah, uh, everybody, everybody should get a shot. It's sort of like college admissions, I think. Yeah, everybody should get a shot at all the, uh, at all the bidders. Okay. Um, hmm, the review stage. So now it's, um, does it happen much in review that, that, uh, the, the organizations come back with questions, or is that more of— that's more of like interviewing the finalists stage?

Josh RimanYeah, that's the, that's the interview stage for sure. I— we— well, before I get there, I want to share one don't. That I think is really important for the review proposal stage, which is— we said this before, there could be like a secret favorite you have. Yeah. Someone submits a bid, oh, they did, hooray, and then the proposal looks good, I think we're ready to move forward. But try your best not to prejudge any candidates, because whether you're looking for a specific candidate or not, you might be surprised. Some, you know, some groups are small, some are big, some you may be aware of, some you may not be aware of, some are based in the same town as you, some are based across the country. What I found is you may be surprised by who you ultimately think is your best fit, and go into the review process with an open mind.

Tony MartignettiOkay, okay. Hard to do, but still, it's an aspiration. You know, if you have a favorite, it's hard to abandon that and keep that open mind, but you should, you should try, try. You might be shortchanging your organization. There may be an— like you said, there might be an agency out there that you don't know, or that you don't— it's not one of your favorites. Maybe you know them, but it's not a favorite. But maybe come in a little lower cost, seems to be comparable work.

Josh RimanYep.

Tony MartignettiThey seem to be a little friendlier, you know. Yes. All right. Keep an open mind. Level playing field. It's time for Tony's Take Two. Time for me to thank you again for listening, for supporting Nonprofit Radio. I'm grateful. Any sharing that you might be doing so that the love gets shared— you're learning, your friends are learning, whoever you're sharing with, your board is learning if you're sharing with your board, your colleagues are learning if you're sharing with them. So thank you. Thank you. Thank you for listening. Thank you for sharing. Share, share, that's fair. That's the way I grew up. So, no, thank you. If it wasn't for you, there wouldn't be 13,000+ listeners each week. So I am grateful that you listen to Nonprofit Radio. I'm ecstatic that it helps you. That's the point. It helps you in your work. Thank you. Thanks for listening. Thanks for supporting the show. That is Tony's Take Two. We've got beaucoup, buttloads more time for your RFP process with Josh Riman. Your finalists, you want to talk to some finalists?

Josh RimanAbsolutely. So a couple dos and a don't here when it comes to interviewing finalists. So you've done your review process, you've scored everybody, Schedule calls with a handful of candidates. So if you've submitted— if you sent your RFP to 8 people, let's say 5 groups submitted proposals, speak to 3. To your point before, don't speak with 2. That, that's too few. Don't speak with 1. You probably also should not speak with all 5, because ultimately when you look at the scores, there should be— there should be some candidates that rise above the rest, and you should save yourself the time of interviewing a candidate that you think truly might not be the right fit and you're just doing it to do it. So try to filter that process down to the handful of candidates that feel like they could be the best fit.

Tony MartignettiAre you informing the, the ones that are not finalists that, that they're out of the process, or is it better to keep them in your back pocket just in case one of your top 3 doesn't pan out?

Josh RimanYou know, this is an interesting question. I've got a really important do about this in a little bit, but I would say it's okay to keep them in the back pocket at this point. But there needs to be a lot of transparency later in the process, and I'll, I'll tease that for now. I'll get back to it in a second.

Tony MartignettiOkay, okay. What, what other advice, uh, on talking to the finalists?

Josh Riman2 things. The other do is ask to speak to your potential project team. The goal being you don't want to just speak to generic representatives from an agency you're considering. See if you can speak to the people you'd actually be working with— your account director, your designer, your developer, your project manager or your copywriter, whatever that person is, to actually see what kind of chemistry there is and what kind of vibes there are. That's essential. And it's not always possible. Some bigger agencies may say, look, I'm sorry, we don't know what our project team might be. You know, we are more of a small agency. We're about a full-time team of 10. So when we are proposing to work on a project, we already know who might be working on it. And I think that actually puts us at a bit of an advantage because you can meet the people you'd be working with, not just people that you may or may not be working with.

Tony MartignettiYou want to talk to the CEO as well? Bring in, bring in him or her as well as your, as your, your, uh, potential project team?

Josh RimanYeah, absolutely. I, I, you know, we are, again, we're a full-time team of 10, and I, as the president and founder, am creating all the proposals. So I'm always the person who's working on these and submitting them. It might be tougher if you're considering working with a much bigger agency to get the you know, the top brass into the room. But if you want to meet the people at top, you can always give it a shot. And honestly, if you ask if somebody can join, and they say no, maybe that's a sign you should keep in mind.

Tony MartignettiYeah, yeah. What, what's the value of your work to— what's the importance of your work to this, to this agency?

Josh RimanExactly.

Tony MartignettiYou know, the CEO can't give up half an hour. All right. Josh Riman will never turn you down. You ask for the CEO, you will get the CEO.

Josh RimanYes.

Tony MartignettiPresident, sorry, president. Okay, more advice around talking to finalists?

Josh RimanOne more piece, which is in these conversations, I think you mentioned this before, you alluded to it, when it comes to writing the RFP, it doesn't need to be a formal meeting. You can keep it light. One of the best meetings that we had as part of an RFP process was we ate lunch. with an organization who was considering us for the project, and we did not talk about our proposal for a single minute. We just had lunch. We talked about each other. We talked about where we came from. You know, we talked about our interests and hobbies and TV shows and whatever. Yeah. And it was a really fun hour, and they called us the next day and said, we're in. So it doesn't, it doesn't need to be that informal, but it's important to not keep things so formal and so structured and so buttoned up, because that's not what it's gonna feel like when you work with this agency. So try to replicate that feeling.

Tony MartignettiHopefully not, right? I mean, this is, this is an iterative process. There's so much back and forth, you know, this could be a 6-month project, uh, you know, you want to, uh, yeah, you want to make sure you have chemistry with the folks that you're going to be working with.

Josh RimanExactly.

Tony MartignettiYou don't want it to be so formal that you don't, you know, you feel like, oh wow, maybe I better not bother them now or something, you know, like that. That, that's, that's, that's a bad feeling. Like, you know, they wouldn't give us— they didn't give us much time, or I felt awkward asking questions. You know, that's— those are all red flags.

Josh RimanBig time. And when you think about it, a lot of projects that require an RFP are pretty long-term projects. A website could take up to a year, it could take longer depending upon the goals of the project. So you want to make sure you get along with these people because you're going to spend a lot of time with them over the course of the project. So use that meeting as a litmus test to see how well you get along with the candidate, how well the candidate gets along with you. And then make that part of your criteria as to who goes from a finalist to an actual winner that you want to work with.

Tony MartignettiWhat's like a median time for the projects you've done? Can you say, you know, what should folks plan on? What's a median time or range for a, let's say, a complete, not just a refresh, but a completely new New, new site?

Josh RimanSure. For us, it's about 10 months, and that's because the first few months of the process, we're not doing any work yet. We're just doing research. So we're doing interviews, we're researching your current site, we're talking to other stakeholders in your network, and we spent a lot of time on that before the work actually starts. So we are in the 10-month range for a full website redesign. There are groups that could do it faster, there are groups that spend more time on it, but For us at Great Believer, it's going to be about 10 months.

Tony MartignettiOkay. Okay. Um, so that's— is that it, uh, for your questioning the, uh, questioning the finalists?

Josh RimanYep, that's it.

Tony MartignettiAll right. Oh, and, uh, well, yeah, who should be doing these questions? Should, should you have— like, if you had a panel of 3 or 4 reviewers, should those 3 or 4 reviewers be in the, in the meeting? Because that's how you get— you know, you want multiple people, I would think, right?

Josh RimanYeah, I think that would be perfect. And if there are other people at your organization who you think might be on the project team, people that are on the day-to-day communications with the agency you hire, those people should also be in the meeting. And you don't want it to evolve into something where there are like 9 of you and 3 of them, but all the key players that have been involved in the process so far, and those that are going to be involved in the project with whoever you move forward with, should be there.

Tony MartignettiOkay, and selection.

Josh RimanYeah, this is it. So you've, you've interviewed your candidates, you found one that you know you want to move forward with. So a do and a don't here. The do is share the news with all candidates in a timely manner. So once you have made your selection, the contract is signed, then you can say, send an email to everybody saying like, thank you, we've made a selection, you know, we appreciate the work you put in your proposal, we're going in a different direction. And do that in a timely manner, because people I know, like myself, were wondering, you know, where do things stand? Are we still in the running? We were a finalist, but how did that meeting go? Did it go well? Are we going to get the work? So that's the do. And then in that email, this is the don't, which is don't give the people you did not select, the finalists you did not select, the cold shoulder. And what I would suggest, and what I appreciate immensely, is if in that email With the organizations.

Tony MartignettiThere have been, there have been RFPs that you did not get?

Josh RimanYes.

Tony MartignettiThat's happened to you?

Josh RimanAbsolutely.

Tony MartignettiIt's Great Believer. How could that happen? I can't, I can't imagine it.

Josh RimanI appreciate the endorsement, but for us, what we're trying to learn from those that we don't get is the why. And in that email where organizations say, you know, we've chosen to work with somebody else, for me, I understand. Like, we're, we're one of many who submitted a bid and, and we gave it our best shot. But what I want to have is the opportunity to debrief with the organization. And this could be as simple as a 15-minute phone call where the organization says, you know, here's why the agency we selected stands out. Here are some things with your proposal that we felt fell short and pushed you down to like a second tier, whereas the other group rose to the top. And the organization may also say, if they're comfortable, here's who we'll be working with. Those kind of things are so valuable. I think organizations are often well-intentioned and extremely respectful, but they can forget sometimes how much work goes into a really good proposal. A really bad one could take an hour. A really good one can take a day or more of time creating the thing, developing a timeline, developing a budget, talking to team members, making sure the process makes sense for this specific organization's needs. So Just a 15-minute phone call. And look, I know it's not the most comfortable thing to do, to talk to an agency you're not working with, but they are going to be so appreciative of the opportunity. Some may not even take you up on it, but those that do will be happy to have the conversation and learn more about the process. They're not going to go into the conversation with like a chip on their shoulder. They'll just go in looking to learn more.

Tony MartignettiYeah, they certainly should not. Yeah, you're being very generous if you're— if you offer that. Offer that to the folks who weren't selected. Yeah. And, and if, um, look, if somebody does come, you know, vindictive, you know, then you know that you made— you know that your selection process works because you sussed them out. Okay, you just had to sit through an awkward 15-minute phone call that validated your process. Good call. Yeah, yeah, I do find that valuable. I remember the last time I, I asked It wasn't offered and I asked, and then I just didn't hear back, you know, because I, you know, basically an email said, I'd like to know how I came up short. Uh, it's, it's happened to Tony Martignetti. I know it's hard to believe too, but, uh, I've, I've also, uh, not gotten something that I bid on one time. And, uh, yeah, you like to know, you know, it's just, it's just a gracious way of— it's just a gracious way of conducting business too.

Josh RimanAbsolutely.

Tony MartignettiI think share your lessons, maybe, you know, Help someone be better for next time. You know, they're not going to try to talk you out of their decision. That, that's— that would be ludicrous. They're not going to go that far. They might be vindictive, but they're not going to try to talk you out of your— you know, they're certainly not going to try to talk you out of your decision. Um, so yeah, offer that. It's very— that's a good idea, Josh. A very, um, yeah, very magnanimous.

Josh RimanAll right, it's such a— it's so much appreciated because when I look back at proposals that I submitted to organizations, let's say 5, 6 years ago, They're so much better and more thoughtful now because we've evolved as an organization, as an agency, but also because we've gotten great input from those organizations we submitted bids to that we did not win. And that's helped influence how we evolve the way we pitch ourselves. So it's, it's extremely beneficial. And again, just a nice way to be magnanimous, to use your word, and show some appreciation to these agencies that truly wanted to work with you and gave it their all. Because if they're a finalist, They really did want to work with you. It's not one of the groups that submitted this, you know, crappy fill-in-the-blank proposal.

Tony MartignettiYeah,

Josh Rimanyeah, they genuinely put effort into it. So give them 15 minutes of your time and it'll be much appreciated.

Tony MartignettiBut good, yeah, good karma. So some dates that belong in the RFP, you know, the deadlines that you're specifying. I've got, you know, the intent to bid, Then when the question period is going to be, I guess. And then should you say, you know, what your review period is going to be? Like, we're going to take these 3 weeks or these 2 or 3 weeks to— during— for review. And then, and then the selection date. Are there other— are there other milestones you should, you should be including?

Josh RimanWell, I think you got it. The one thing I'd recommend is flipping— have the Q&A deadline first and then the intent to bid after, so all the agencies can understand the questions that are being asked and then confirm if they might be the right fit to submit a bid. So Q&A deadline, you know, at least 2 weeks after the RFP is distributed. Intent to bid, maybe a week or 2 after that. And I love it when there's a little grid in the RFP that says, you know, Q&A deadline this, intent to bid deadline this, your proposals due this date. We're going to review over the span of these 2 weeks. Here's another— this is like a more off-the-top-of-the-head thing.

Tony MartignettiYeah.

Josh RimanIt's almost never that an organization says, we're going to review proposals during this time frame, that they just need that much time. They always need more time. So when you're writing a proposal, give yourself more time. If you are going to share how much time you want to spend reviewing, tack on a week, because it's going to take more time than you think, not just to get through all of them, but to have everybody internally score them. So I think it's great to have that time in there, and if you can estimate when you're going to actually interview finalists and make a selection, that's great. And look, you can put a note, these are estimated dates, they're subject to change. But if you can give organizations, or agencies rather, who are applying, a sense for what's to come, that's really great because they, they're probably pitching several other things at the same time and want to make sure they can not just get your proposal in on time but make themselves available for potential interviews.

Tony MartignettiAll right. Overall, you want to just make this a humane process.

Josh RimanI like that. Yes.

Tony MartignettiYou may be humane. We're talking to human beings. You don't have to be overly formalistic. You probably don't want to be, you know, that may put people off. That may put agencies off if, like we said in the beginning, if they feel they have no latitude, that may discourage some bids. So, yes.

Josh RimanAll right.

Tony MartignettiRunning an RFP process while keeping your cool. Yeah, be humane. Come on.

Josh RimanI like that.

Tony MartignettiWe're all humans. All right, Josh. Excellent. Anything, parting words you wanna leave folks with? Parting advice?

Josh RimanYeah, I think, you know, I think these dos and don'ts are really helpful. And I mentioned this in the session, but if you wanna skip the RFP process, come straight to us. We're happy to work with you on different website projects, design and development, and other facets also like branding and print. But I understand that RFPs are, like I said before, a necessary evil. And when they are required, hopefully these dos and don'ts make the process a little bit easier.

Tony MartignettiOkay, Great Believer. What's the website?

Josh Rimangreatbeliever.us.

Tony MartignettiJosh Riman, founder and president, Great Believer, greatbeliever.us. Josh, thank you very much. Good to talk to you. Thanks for sharing all your ideas.

Josh RimanThanks, Tony.

Tony MartignettiMy pleasure. Next week, the Chronicle of Philanthropy will go nonprofit with editor Stacy Palmer. If you missed any part of this week's show, I beseech you, find it at tonymartignetti.com. We're sponsored by Turn 2 Communications, PR and content for nonprofits. Your story is their mission. turn-2.co. And by Fourth Dimension Technologies, IT infra in a box, the affordable tech solution for nonprofits, tony.ma/4d. Just like 3D, but they go one dimension deeper. Our creative producer is Claire Meyerhoff. The show's social media is by Susan Chavez. Marc Silverman is our web guy, and this music is by Scott Stein. Yeah! Thank you for that affirmation, Scotty. Be with me next week for Nonprofit Radio, Big Nonprofit Ideas for the Other 95%. Go out and be great. Thank you.

Nonprofit Radio

More Episodes from 2022 Nonprofit Technology Conference

View All
Ananda RobieSam Dorman
EP 606August 28, 2022

Your Tech Problem Is Actually A People Problem

with Ananda Robie and Sam Dorman

Tosha AndersonZanni Miranda
EP 605August 22, 2022

Accounting For Nonprofit Leaders

with Tosha Anderson and Zanni Miranda

Alexandra Mannerings
EP 603August 7, 2022

Increase Data Literacy Across Your Nonprofit

with Alexandra Mannerings

1 / 5