CRM playbook
CRM Buying Guide: RFP Questions That Separate Demos from Reality
CRM demos are designed to feel inevitable. A polished board, a cheerful implementation manager, and a price that looks smaller than the pain of your current process. Six months later, teams discover that export is ugly, the automation they saw was a sandbox trick, or the quote did not include the seats marketing just requested.
This buying guide is a practical RFP you can copy. It is written for operators, not procurement theater. Use it even if you are a 20-person company sending questions in an email instead of a formal portal.
Write the problem before you write the scorecard
If you cannot describe the jobs the CRM must do in a page, vendors will fill the vacuum with features. List the jobs: capture inbound, run one or two pipelines, forecast monthly, log activity, hand off to success, report to the board. List the constraints: budget range, must-keep tools, industries you sell into, and whether you have anyone who can own administration.
Then list non-goals. “We will not run customer support in this CRM in year one” saves you from a platform tour you will not use.
The scorecard that keeps demos honest
Score each vendor 1–5 on the same criteria. Weight the criteria before you watch anyone click. Suggested weights for a sales-led B2B team:
| Criterion | Why it matters |
|---|---|
| Data model fit | Companies, contacts, deals, and custom needs without gymnastics |
| Daily seller experience | Speed, mobile, inbox, and views people will actually open |
| Admin complexity | Can one operator change a stage without a ticket |
| Integrations | Email, calendar, billing, and the one industry tool you cannot drop |
| Permissions and audit | Who sees what, and whether you can prove it |
| Reporting | Forecast, conversion, and a board-ready export |
| Exit | Full export of records, files, and activity |
| Total cost | Seats, add-ons, storage, implementation, and required paid tiers |
Questions to send before the demo
Ask for written answers. Demos hide footnotes.
- What is included in the quoted edition versus what requires a higher tier?
- How is pricing calculated: users, contacts, marketing sends, API calls, storage?
- What happens to price at the next band of contacts or seats?
- Can we export every object, including notes, files, and activity, without professional services?
- Where is data hosted, and what is the subprocessors list?
- What is the standard SSO and MFA story on our tier?
- Which of our must-have integrations are native, certified, or “use Zapier and hope”?
- What does implementation look like if we have no dedicated admin?
- What is the average time to first value for a company our size?
- How are sandbox or trial environments limited?
What to demand in the live demo
Do not let the salesperson drive only the happy path. Bring three real records, with names changed if you must: a messy inbound lead, a multi-threaded mid-market deal, and a renewal. Ask them to create the records in the trial, not in a pre-built dream workspace.
Watch them change a stage, add a required field, build the report you will use on Monday, and impersonate a seller who should not see everyone else’s amounts. If they say “we would configure that in implementation,” write it down as a cost and a delay.
Ask to see a failed automation and how an admin debugs it. Systems look great until a loop emails a customer twice.
Implementation and the first 90 days
Vendors sell a go-live date. You should buy a date when the weekly pipeline meeting runs only from the new system. Those are different. Require a written plan: data mapping, training by role, integration owners, and a hypercare window.
Keep the old system read-only until you have completed one full forecast cycle. Parallel typing in two tools is how both stay wrong.
Total cost, not list price
Add seats you will need in 12 months, not the seats you have today. Add the marketing add-on if inbound is in the plan. Add a specialist if nobody on staff can own fields and permissions. Add the cost of the integration platform if native connectors are thin. Then compare vendors on that number.
A cheaper seat that requires a contractor every time you add a pipeline is not cheaper.
The best CRM on a slide deck is the one your sellers will update on a Thursday night after a hard demo. Score usability with the people who live in it, not only with the buyer who signs.
30-day evaluation plan
- Write jobs, constraints, and non-goals on one page.
- Build the weighted scorecard before vendor calls.
- Shortlist three tools, not seven.
- Send the written question list and compare answers side by side.
- Run the same three real scenarios in each trial.
- Have two sellers and one manager score the daily experience.
- Check export, SSO, and one critical integration yourself.
- Negotiate the edition, not only the discount, and write the go-live definition.
Frequently asked questions
Do we need a formal RFP?
Only if policy requires it. A structured email with the same questions is enough for most mid-size teams. The discipline matters more than the letterhead.
Should we include Salesforce automatically?
Include it if you already know you need its ecosystem. Do not include it as theater if your motion is simple. Evaluations are expensive.
How long should a trial last?
Two weeks is enough to test daily work if you import a slice of real data. A 30-day trial helps if legal or IT must review security in parallel.
Who should own the relationship after signature?
Name an internal admin even if they are not full-time RevOps. Vendors cannot own your stage definitions.
What is a reasonable implementation window?
For a straightforward sales CRM, four to eight weeks of focused work is common. Multi-product, multi-region rollouts take longer and need a project plan.
Operating notes before you sign a CRM contract
Convert the RFP into a scored test plan rather than a questionnaire the vendor can answer with yes. For every critical requirement, ask the finalist to demonstrate it using your sample data and workflow. Mark whether the capability is native, requires configuration, needs a paid add-on, or depends on a partner. Those distinctions often matter more than the checkbox itself.
Ask for the full commercial model in writing. Include implementation, data migration, support tier, required minimum seats, API limits, storage, sandboxes, telephony, AI features, and renewal terms. Compare three-year cost under realistic growth, not just first-year discounting. A procurement win on license price can become an operating loss if basic controls sit behind higher tiers.
Validate administration and support with the people who will own the system. Have an internal operator create a field, change a permission, build a report, troubleshoot an automation, and export data during the evaluation. The day-to-day admin experience is rarely the part shown in executive demos, yet it determines how quickly the CRM can adapt after launch.
Put portability and termination in the decision file. Confirm export formats, API access, attachment retrieval, data retention after cancellation, and the process for obtaining a complete copy of your records. Save the final requirements, vendor answers, and exceptions alongside the contract so future teams know which compromises were intentional.