Most CRM quotes go wrong before a developer writes a line of code. A founder sends a message like 'we need a CRM with a pipeline and reports,' three agencies reply with three very different estimates, and nobody is sure what is actually included. A clear custom CRM requirements checklist fixes that. It gives every vendor the same picture, makes quotes comparable, and forces your own team to agree on what matters.
This guide is written for small sales teams, roughly three to twenty people, who have outgrown spreadsheets or a generic tool and are considering a custom build. It walks through the areas you need to define, shows a copyable requirements table, separates launch essentials from later features, and ends with acceptance criteria so you know when the work is done. It does not cover pricing. For budget ranges and cost drivers, read RuhaniSoft's CRM cost guide alongside this article.
Before you write anything: define the problem
A requirements document is not a feature wish list. Start with three short statements:
- What is broken today? Example: leads get lost between the website form and the inbox, and nobody knows who owns a follow-up.
- What should be different in 90 days? Example: every lead has an owner, a next step and a due date.
- Who will use it daily? Salespeople, a sales manager, an assistant, maybe a finance person who needs closed deals.
Keep these statements at the top of your document. When a vendor suggests a feature you did not ask for, you can test it against the problem. If it does not help, it can wait. For a general template, see this guide to writing a requirements document.
Contacts and accounts
Contacts are the foundation of a CRM, and small mistakes here are expensive to fix later. Decide how your business actually thinks about customers.
Questions to answer
- Do you sell to companies, individuals, or both? If both, do you need separate company (account) and person (contact) records?
- Can one person be linked to several companies, such as a consultant who works with multiple clients?
- Which fields are required? Name and email are obvious. What about phone, job title, lead source, country, industry, or a customer size band?
- Do you need custom fields, and who should be able to add them later without a developer?
- How should duplicates be handled? Warn on entry, block, or merge afterward?
- Do you need tags or segments, such as 'partner' or 'event lead'?
- What activity history should appear on a record: calls, emails, notes, file attachments, meetings?
Be specific about lead source. Teams often say they want 'lead tracking' but never define the list of sources. If reporting on marketing channels matters, the source field should be a controlled list, not free text.
Pipeline stages and deals
Your pipeline is the sales process written as software. If your team cannot describe it on one page, the CRM will not describe it for you.
Map the stages
List each stage in order, with a plain-language entry rule. For example:
- New lead: a contact exists, nobody has spoken to them yet.
- Qualified: budget, need and timing confirmed in a call.
- Proposal sent: a quote or proposal has gone out.
- Negotiation: the client is discussing terms.
- Won or lost: with a required reason for lost deals.
Then answer the practical questions. Can a deal move backward? Are any fields mandatory before moving to a stage, such as a deal value before 'Proposal sent'? Do you need more than one pipeline, for example new business and renewals? Do deals have products or line items, or just a single value? Do you need currency support or tax handling?
A good rule: if two people on your team would describe a stage differently, write down the definition before you request a quote. Vague stages lead to vague reports.
Tasks, reminders and activities
Many CRMs fail because they store data but do not drive action. Tasks are where the system earns its keep.
- Can tasks be attached to a contact, an account or a deal?
- Who can assign tasks to whom? Can a manager assign to a rep?
- What reminders do you need: in-app, email, or both? How far ahead?
- Should the system create tasks automatically, such as 'follow up in 3 days' when a proposal is sent?
- What happens to overdue tasks? Do managers see a list?
- Do you need a calendar view, or is a daily task list enough?
Automation is where scope can quietly expand. Write down the two or three automations you truly need on day one, and park the rest. This guide on choosing what to automate first can help.
User roles and permissions
Permissions are easy to under-specify and painful to retrofit. Describe your roles in plain terms and say what each can see and do. Our roles and permissions planning guide goes deeper.
A typical small team might have:
- Admin: manages users, fields, stages and settings.
- Sales manager: sees all deals and reports, reassigns records.
- Sales rep: sees own contacts and deals, plus shared accounts.
- Read-only user: a finance or operations person who views closed deals.
Clarify the edge cases. Can a rep see colleagues' deals? Can they export data? Who can delete records? Is there an audit trail that records who changed a deal value? If you handle sensitive client data or operate under privacy rules, say so, and mention any requirement for data retention or deletion on request. A developer cannot guess your compliance obligations. The OWASP Top Ten is a useful reference for access control risks, and GDPR guidance covers deletion rights.
Reporting and dashboards
Reporting is where requirements are most often too vague. 'We want good reports' is not a requirement. Start from the decisions you make each week and work backward.
Write reports as questions
- How many new leads came in this month, by source?
- What is the value of deals in each stage right now?
- What is our win rate, and how long does a deal take from lead to close?
- Which reps have overdue tasks or deals with no next step?
- Why do we lose deals?
- What revenue do we forecast for the next quarter?
For each question, note who needs the answer, how often, and whether it should be a live dashboard, a scheduled email or an export to a spreadsheet. A live dashboard with filters costs more to build than a CSV export. Choosing consciously keeps the quote honest.
Also decide which numbers must match your existing figures. If finance already reports revenue a certain way, the CRM should agree with it, and that needs to be written down.
Email integration
Email integration can mean anything from a simple link to a deep two-way sync. Be clear about which one you need.
- Email provider: Google Workspace, Microsoft 365, or something else?
- Logging: should sent and received emails appear automatically on the contact record, or is manual logging acceptable?
- Sending: do reps send from inside the CRM, or from their normal inbox?
- Templates: do you need shared templates with merge fields such as first name?
- Tracking: do you need open or click tracking? Treat this as optional unless it affects your process.
- Bulk email: is newsletter-style sending needed, or will you keep using a dedicated marketing tool?
- Privacy: should reps be able to mark personal emails as private so they are not logged?
Also list other integrations: website forms, calendar, phone or messaging, accounting software, e-signature. Mark each as required at launch or later. Every integration adds testing, third-party limits and ongoing maintenance, so naming them early matters. Our API integration checklist covers the details.
Data migration
Migration is the part teams underestimate most. Your data lives somewhere now, and its quality will shape the first impression of the new system. See also this spreadsheet migration plan.
Inventory what you have
- Where is the data: spreadsheets, a current CRM, email, a shared drive?
- Roughly how many contacts, companies, deals and notes? A rough order of magnitude is enough.
- What history must be kept, and what can be archived? Do you really need five years of closed deals?
- How clean is it? Duplicates, missing emails, inconsistent company names, free-text fields that should be lists?
- Are there attachments or documents to bring across?
Decide who is responsible for cleaning data. Often the best split is that your team removes obvious junk and confirms the field mapping, while the developer builds and runs the import scripts. Ask for a trial import into a test environment so you can check real records before go-live, and agree on how you will handle records that fail to import.
A copyable custom CRM requirements checklist table
Copy the structure below into a spreadsheet or document. Each row is one requirement. Use the columns Area, Requirement, Priority (Must, Should, Later), Owner, and Acceptance test. Here are sample rows to show the level of detail that helps a vendor quote accurately.
- Area: Contacts | Requirement: Company and person records, linked | Priority: Must | Owner: Sales manager | Acceptance test: A contact can be linked to one or more companies and shows all related deals.
- Area: Contacts | Requirement: Duplicate warning on email | Priority: Must | Owner: Sales manager | Acceptance test: Entering an existing email shows a warning with a link to the existing record.
- Area: Pipeline | Requirement: Five stages with lost reason required | Priority: Must | Owner: Founder | Acceptance test: A deal cannot be marked lost without selecting a reason.
- Area: Tasks | Requirement: Tasks with due dates and email reminders | Priority: Must | Owner: Sales reps | Acceptance test: A reminder email arrives on the due date for the assigned user.
- Area: Permissions | Requirement: Reps see only their own deals | Priority: Must | Owner: Admin | Acceptance test: A rep account cannot view or search another rep's deals.
- Area: Reporting | Requirement: Pipeline value by stage | Priority: Must | Owner: Sales manager | Acceptance test: Totals match a manual count of a sample of 20 deals.
- Area: Email | Requirement: Log emails from Google Workspace | Priority: Should | Owner: Sales reps | Acceptance test: A sent email to a known contact appears on their timeline within a few minutes.
- Area: Migration | Requirement: Import contacts and open deals from spreadsheets | Priority: Must | Owner: Operations | Acceptance test: Trial import completes with an agreed error report and a spot check of records.
- Area: Reporting | Requirement: Forecast by month | Priority: Later | Owner: Founder | Acceptance test: Forecast uses deal value and close date, and is reviewed against one past quarter.
- Area: Automation | Requirement: Auto-create follow-up task after proposal sent | Priority: Later | Owner: Sales manager | Acceptance test: Moving a deal to Proposal sent creates a task due in three days.
Aim for 25 to 50 rows for a small team. If you have 200, you are probably describing a larger product than you need to start with.
Launch essentials versus later features
The most useful decision you can make is what the first release must include. A smaller first version reaches your team faster, gets real feedback and lowers risk. Use this split as a starting point, and see how to reduce scope without losing purpose.
Launch essentials
- Contact and company records with the fields you really use
- One pipeline with clear stages and required fields
- Tasks with due dates and basic reminders
- Simple roles: admin, manager, rep
- Two or three core reports or a basic dashboard
- Import of current contacts and open deals
- Basic email logging or at least a clean way to record email activity
- Activity history and notes on every record
Later features
- Advanced automation and workflow rules
- Forecasting and goal tracking per rep
- Two-way calendar sync and meeting scheduling
- Email open tracking and bulk campaigns
- Quote and proposal generation with e-signature
- Accounting or billing integration
- Mobile app (a responsive web app often covers early needs)
- AI features such as lead scoring or email summaries
- Customer portal
This list is not a rule. If your whole business depends on quoting, quote generation may belong at launch. The point is to make the choice deliberately and ask vendors to price the two groups separately, so you can see what each phase costs.
Acceptance criteria: how you will know it is done
Acceptance criteria turn requirements into tests. They protect both sides: you get what you asked for, and the developer knows when a feature is finished. Good criteria are observable and specific. For more, see these acceptance criteria examples.
- Weak: 'Reports should be accurate.' Better: 'Pipeline value by stage matches a manual count of a sample of 20 deals.'
- Weak: 'The system should be fast.' Better: 'The contact list loads and searches in a few seconds with your full imported dataset.'
- Weak: 'Permissions work properly.' Better: 'A rep account cannot view, search or export another rep's deals.'
Also agree on the wider conditions for sign-off:
- A test environment with imported sample data where your team can try real scenarios.
- A short user acceptance period, for example a week, with a list of defects and a process for fixing them.
- Agreement on what counts as a defect versus a change request, since changes may affect timeline and cost.
- Basic training or documentation for admins and reps.
- A go-live plan, including when the old system becomes read-only and who is available for support in the first weeks.
What to include when you request a quote
Package your document so a vendor can respond quickly and accurately:
- The problem statement and goals
- Your team size, roles and user count at launch and in a year
- The requirements table, with priorities
- Existing tools and integrations, with access details to be shared later
- A description of your data sources and rough volumes
- Your preferred timeline and any fixed deadline, such as a sales season
- Questions you want answered: hosting, ownership of the code, support after launch, and how changes are handled
Ask each vendor to list assumptions and exclusions. The differences between quotes usually live there. For how scope, integrations and team setup affect price, see RuhaniSoft's CRM cost guide, which covers that in detail so this checklist does not have to. You can also read how to choose a development company, and learn how projects are estimated.
Common mistakes to avoid
- Copying a big CRM's feature list. You pay for complexity your team will not use.
- Skipping the people who use it daily. Ask two reps what slows them down before you finalize anything.
- Treating migration as an afterthought. Bad data makes a good system feel broken.
- Leaving permissions until the end. They affect the data model, so they are cheaper to design early.
- No owner for decisions. Pick one person who can say yes or no on scope.
Many of these problems are covered in why software projects fail. Weigh whether to build or buy software before committing.
Conclusion
A strong requirements document does not need to be long. It needs to be specific, prioritized and testable. If you work through contacts, pipeline, tasks, permissions, reporting, email, migration and acceptance criteria, and separate launch essentials from later ideas, you will get quotes you can actually compare and a project that starts on solid ground.
If you would like a second pair of eyes on your draft, the RuhaniSoft team can review it with you, flag gaps and suggest a sensible first release. Get in touch to talk through your CRM project, or learn about our development process. Background on the sales pipeline concept is on Wikipedia's CRM overview, and the NIST Cybersecurity Framework helps with data protection planning.