Set scope and the team before writing anything
Most CRM RFPs go wrong before the document exists. Sales wants pipeline tools, marketing wants campaign attribution, support wants ticketing, and finance wants clean data for forecasting. If you do not settle this up front, the RFP turns into a wish list and every vendor looks the same.
Start with a one-page scope note that answers:
- Which teams will use it in year one, and which might join later
- How many users by role (full users, read-only, admins)
- What it replaces: spreadsheets, an old CRM, point tools
- What it must connect to: email, calendar, ERP or accounting, billing, marketing automation, data warehouse
- Budget range and who approves it
- Target go-live date and any hard deadlines, such as a current contract expiring
Name a small evaluation team: one owner (usually procurement or revenue operations), one senior user from each team in scope, someone from IT or security, and finance. Agree now on who has the final say. A committee with no tiebreaker drags selection out for months.
Write requirements as use cases, not feature lists
"Supports opportunity management" gets a yes from every vendor. Requirements only separate vendors when they describe what your people actually do.
Write each requirement as a short scenario, then tag it by priority:
- Must have: you will not buy without it
- Should have: important, but a workaround is acceptable
- Nice to have: tiebreaker only
Keep the must-have list short. If everything is a must, nothing is.
Example requirement (Must have): A sales rep logs a call from their phone, and the activity appears on the account and the open opportunity without manual linking. The manager sees it in a weekly activity report filtered by team.
Example requirement (Should have): When an opportunity reaches Closed Won, the system creates a customer record in our accounting system with billing address, payment terms and contract value, with no re-keying.
Cover these areas at minimum:
- Contact, account and opportunity management
- Pipeline stages, forecasting and reporting
- Email and calendar sync
- Integrations and API access
- Permissions, roles and territory rules
- Data import from your current system
- Mobile use
- Security, compliance and data residency
- Admin effort: what your team can configure without a developer or consultant
Questions to ask CRM vendors
Ask questions that force a specific answer. Where you can, ask for evidence: a screenshot, a documentation link or a customer reference.
Product and fit
- Which of our use cases work out of the box, which need configuration, and which need custom development or a third-party app?
- What does the product roadmap look like for the next 12 months, and which items are committed versus planned?
Integrations and data
- List native integrations with the systems we named. For each one, is it built and supported by you, a partner or the customer?
- What are the API rate limits on each pricing tier?
- How do we export all our data, in what format, and at what cost if we leave?
Implementation
- Who does the implementation: you, a partner or us? Provide a sample project plan for a customer of our size.
- What does a typical timeline look like, and what usually causes delays?
- What internal staff time should we plan for?
Security and compliance
- Which certifications do you hold (for example SOC 2 Type II or ISO 27001)? Share the latest report under NDA.
- Where is our data stored, and can we choose the region?
- Which subprocessors handle our data?
Pricing and commercial
- Give a full price for our user counts, including edition, add-ons, sandbox environments, storage, API access and support tier.
- What price increases apply at renewal, and are they capped?
- What is the minimum contract term, and can we reduce seats at renewal?
Support and references
- What are your support hours and response targets by severity?
- Provide two references in our industry at a similar size, one of which went live in the last year.
Structure the document and timeline
A clear RFP gets comparable answers. Use this structure:
- Company background: who you are, the teams in scope, current systems
- Objectives: the three to five outcomes you need
- Requirements: the use-case list with priorities
- Vendor questions
- Pricing template: a fixed spreadsheet every vendor fills in, so you can compare line by line
- Instructions: format, page limits, deadline, single point of contact
- Evaluation process and timeline
A reasonable timeline for a mid-sized CRM selection:
- Week 1: issue the RFP to four to six vendors
- Week 2: deadline for vendor questions; share all answers with every vendor
- Week 4: responses due
- Week 5: score responses and shortlist two or three
- Weeks 6 to 7: scripted demos and reference calls
- Weeks 8 to 9: negotiation with the top two
- Week 10: decision and signature
Route all vendor contact through one person. Side conversations with individual evaluators muddy the process and let vendors shape the outcome.
Score responses and run scripted demos
Set scoring weights before responses arrive. If you set them afterward, people tend to weight toward the vendor they already like.
Example weighting (adjust to your priorities):
- Functional fit to requirements: 35%
- Integrations and data: 20%
- Total cost over three years: 20%
- Implementation approach and support: 15%
- Security and vendor stability: 10%
Score each item on a 1 to 5 scale with written definitions, for example 5 = meets the requirement out of the box, 3 = meets it with configuration, 1 = needs custom work or a third-party app. Have each evaluator score on their own before you meet as a group to discuss.
For demos, send the shortlisted vendors a script of five to eight of your use cases a week ahead. Ask them to use your sample data and show those scenarios, not their standard pitch. Give every vendor the same script and the same time slot. Have your actual users run parts of the demo, or at least drive the questions. Finally, check references with specific questions about implementation delays, hidden costs and support quality.
Negotiate contract terms before you choose
Negotiate with at least two vendors in parallel. Once you name a winner, most of your leverage is gone.
Terms worth pushing on:
- Renewal price cap: limit annual increases to a fixed percentage or an inflation index
- Seat flexibility: the right to reduce seats at renewal, not only add them
- Ramp pricing: pay for seats as teams go live, not all on day one
- Price protection for add-ons you may buy later
- Data export and exit: full export in a standard format at no extra cost, with a defined window after termination
- Implementation milestones: payment tied to delivery if the vendor or its partner runs the project
- Service levels: uptime commitment with service credits
Example clause: "Upon expiration or termination, Vendor will make all Customer Data available for export in CSV or another mutually agreed standard format for a period of not less than 60 days, at no additional charge."
Compare three-year total cost, not year-one price. Discounts that disappear at renewal can wipe out the savings.
Let pingpong run it for you
pingpong drafts the RFP, finds and invites vendors, collects proposals through a private portal, scores them with five AI models and flags the gotchas above. It drafts every negotiation message for your approval, then keeps watching the market so you renegotiate before renewal. $100 for the first month, then $799 a month.
Common questions
How many vendors should receive a CRM RFP?
Four to six is a common, workable range. Fewer limits your negotiating position, and more creates scoring work without improving the decision. Use a short pre-screen on budget, user count and must-have integrations to narrow the list before you send the full RFP.
Should we share our budget in the RFP?
Sharing a range usually helps. It stops vendors from proposing editions you cannot afford and lets them shape a realistic offer. Ask for pricing in your fixed template so you can compare vendors directly, whatever range you share.
Do we need an RFP for a small CRM purchase?
For a small team, a lighter process often works: a short requirements list, a pricing template and scripted demos with two or three vendors. Keep the core habits of use-case requirements, weights set in advance and checked exit terms. Those matter at any size.