A bad RFP produces five proposals that look similar, quote similar numbers, and reveal nothing about which provider will actually work. The fix is asking questions that are hard to answer generically.
This guide is for the operations leader or owner writing their first call centre or BPO RFP, or rewriting one that produced five interchangeable proposals last time. It covers what to include so providers can quote accurately, the questions that separate real capability from copywriting, the commercial terms people forget, and how to run the process so the answers you get back can actually be compared.
Give them enough to quote accurately
Providers cannot price what you have not described. Vagueness produces padded quotes, and padding is invisible. The minimum a provider needs to quote your work rather than a generic version of it is below.
Include your bad month. Quote against peak as well as average, or your first busy period becomes a change request.
- Contact volume by channel, by hour of day and by day of week, for at least a full year so seasonality is visible.
- Contact type breakdown: what share is billing, technical, orders or complaints, and the average handling time of each if you have it.
- Coverage hours required, and which of those hours are essential and which are preferred.
- Languages, with the actual volume in each rather than a wish list.
- Systems agents must use, with a line on whether the provider will get direct access or work through your interface.
- Compliance requirements that apply to the work: for example, PCI DSS if agents take card payments, HIPAA if they handle protected health information, TCPA if there is outbound calling to US consumers.
- Your current performance, so the provider can see what it is being asked to match or beat.
Explain your own situation honestly
The RFP should also say why you are issuing it. A provider that knows you are replacing an incumbent that failed on quality will propose differently from one that thinks you are outsourcing for the first time, and both will propose better than one guessing. State what is working today and what is not. State what happened last time if there was a last time. State the constraints you cannot move, such as a launch date tied to a product release, a system that will not change or a regulatory requirement that shapes the work.
State the decision timeline and who decides. And state what a successful first year looks like in your own words, because that is the standard the provider will be held to and the one it should be designing for. Providers rarely get this context and usually ask for it in the question period; putting it in the document saves a round and produces proposals that answer your problem rather than a generic one.
Ask questions that resist boilerplate
'Describe your quality process' produces a paragraph anyone can write. 'Send us a redacted quality scorecard and a coaching record from a real account' does not. Similarly: what is attrition on the specific team we would sit in? How many accounts does a team lead carry? What happened the last time a client escalated a service failure, and what changed afterwards?
Other questions in the same family: describe the last agent you removed from a client account and why. Show us the onboarding plan you used for the most recent programme of our size, with the dates. Tell us which of our requirements you would push back on and what you would propose instead. A provider willing to disagree with your RFP in writing is showing you what the relationship will be like.
Ask, too, how the provider will learn your process. The answer should describe a discovery conversation, a named project manager who maps the process and prepares the systems, training built around your standards and a reporting rhythm agreed before launch. A provider that describes launch as 'we assign agents and go live' has told you what onboarding will feel like.
The commercial questions people forget
What is included and what is billed separately: supervision, quality assurance, reporting, tooling, training? What happens when volume rises sharply for a month, and when it falls? What are the minimum commitment and notice periods? What are the exit terms and who owns the data and recordings?
Also ask about the engagement model. Some providers quote only dedicated agents; some quote pooled; some offer task-based project work, monthly dedicated professionals and managed multi-skill teams as distinct models, with pricing that depends on role complexity, hours, coverage, tools and management. Ask which models are on offer and whether you can move between them as the work changes, because the shape you need in month one is rarely the shape you need in month twelve.
Requirements that quietly inflate every quote
Insisting on a specific location, dedicated agents where pooled would do, or 24/7 coverage you do not need will raise every bid you receive. Mark requirements as essential or preferred so providers can show you the cost of each.
The common culprits are a named location, a fixed agent count rather than a coverage requirement, a specific tool the provider must license, an agent profile with qualifications the work does not use and coverage hours copied from a competitor rather than from your own contact data. Each one narrows the field and raises the price without a corresponding gain. The fix is to state the outcome you need and let providers propose how to reach it. Where you do have a genuine constraint, say why, so the provider can address the concern rather than the constraint.
Every 'must have' you cannot justify is a discount you chose not to take.
Compare on the same scope
Ask everyone to quote the identical scope in their own pricing model, then convert to cost per resolved contact. It is the only comparison that survives contact with reality. See what outsourced customer service costs for the models you will encounter.
The conversion takes work, and it is worth doing in a spreadsheet you build rather than one a provider sends. For each proposal, list everything included in the base price, everything billed separately, and the assumptions about volume and handling time. Then estimate what a normal month and a peak month would cost, and divide by the contacts you expect to resolve. The proposal with the lowest headline rate is frequently not the lowest on this measure, and the difference is usually in what was left out of the base.
Run the process so the answers stay comparable
A well-run process produces better answers than a well-written document alone. Set a timeline with a question period, and share every question and answer with every bidder, so nobody quotes on information the others did not have. Hold a short call with each shortlisted provider before final proposals, with your operations lead in the room, and give them the same scenario to walk through. Ask for a reference on an account like yours, and speak to the reference's operations contact rather than their executive sponsor.
Visit, or video-tour, the site where your team would sit and ask to see the quality and coaching tools in use rather than in slides. Where a provider's answer was thin, go back and ask again rather than guess. The process should take long enough to do these things properly and no longer, because a drawn-out RFP loses the attention of the providers you most want.
Score what you can verify
Score proposals on evidence, and weight the criteria before you open the first one. Verifiable items are the ones a provider showed you: the redacted scorecard, the attrition figure for the specific team, the named team lead's account load, the reference call, the onboarding plan with dates. Claims are the ones a provider told you. A scoring model that gives equal weight to both rewards the best writer.
Put the largest weights on the capabilities that failed last time or that your contact data shows matter most, such as first-contact resolution for a technical queue or save rate for a retention queue, and hold the scoring to what each provider demonstrated. Where two providers score close, the difference usually lies in how they answered the questions they were not expecting, and in what they said they would push back on.
Turn the winning proposal into the operating agreement
The RFP does not end at the award. The winning proposal becomes the basis for the operating agreement, and the items you asked about become the items you hold the provider to: what is included, what happens at peak, the notice and exit terms, who owns the data and recordings, the quality process and the reporting rhythm. In our own engagements this is where the discovery call and the strategy phase pick up: a project manager maps the process the RFP described, prepares the systems and trains the agents against the standards the proposal committed to, and the reporting cadence is agreed before launch rather than argued about after it.
Launching an outsourced support team: the first 90 days covers what happens next, and call centre KPIs that matter helps you choose the numbers the reporting should carry. If the RFP is surfacing a support problem a vendor cannot fix, customer experience consulting is the diagnostic step that belongs before it. Nearshore versus offshore call centres helps with the location question if it is still open.