Questions to ask a custom CRM development vendor before you sign
What should you ask a custom CRM development vendor?
Ask a custom CRM development vendor five things: how they will migrate and reconcile your existing data, who owns the code and the schema, what the system costs to run each month, how escalations work after go-live, and what happens if you leave. Everything else is detail.
Ask a custom CRM development vendor five things before anything else: how they will migrate and reconcile your existing records, who owns the code and the database schema, what the finished system costs to run every month, how an escalation reaches an engineer after go-live, and what leaving them looks like. A team that has shipped answers all five without hedging.
This article is a question bank rather than an essay. It gives you the wording, what a confident answer sounds like, the warning signs, and the three questions most buyers forget until the invoice arrives.
Why the proposal tells you less than the answers do
Custom CRM proposals converge. Every vendor lists modules, a phased plan, a training week and a support period, because everyone reads the same brief. What does not converge is how a team behaves when you push on the unglamorous parts: the 60,000 contact records with three spellings of the same company name, the sales director who will not give up her spreadsheet, the sync with an accounting system whose API has no sandbox.
Custom CRM development due diligence is therefore a conversation, not a document review. You are testing whether the people in the room have lived through a go-live, or whether they have only sold one. The questions below are ordered by how much money they save you.
The questions, and what a good answer sounds like
Take these into the second meeting, when a solution architect rather than a salesperson is present. Ask them in front of the person who will actually lead delivery.
| Question | A good answer | A warning sign |
|---|---|---|
| How will you migrate our existing records? | A profiling pass first, a written cleansing rule set, a dry run into staging, a reconciliation report you sign off | "We will import the CSV in week one" |
| Who owns the code, schema and documentation? | You do, in writing, in the contract, with the repository under your organisation from day one | Ownership "on final payment" or a licence rather than assignment |
| What does this cost us to run per month? | Named hosting, licence, email and telephony lines with figures, plus a support tier | "Hosting is negligible" |
| Who answers at 9am on a Monday after go-live? | A named engineer, a response target in hours, a defined severity ladder | A shared inbox and "we are very responsive" |
| What happens if we stop working with you? | A handover pack, credentials transfer, a paid transition period, no proprietary runtime | Silence, or a framework only they can operate |
| Which parts will you not build custom? | Billing, email delivery, telephony and identity bought in, integrated properly | Everything built in-house, quoted as a strength |
| How will you test that it works for sales? | A named pilot team, scripted scenarios, acceptance criteria written before the build | User acceptance testing in the last two days |
| What has gone wrong on a project like ours? | A specific story with the cost and the fix | "Nothing, we deliver on time" |
What should you ask about data migration?
Ask for the reconciliation plan, not the migration plan. Every vendor has a migration plan; few have written down how you will prove afterwards that nothing was lost. The answer should name the counts you will compare, the money fields you will total, and the person who signs off before the old system is switched to read-only.
Press on duplicates and on history. Most CRMs being replaced contain a decade of accreted contacts, half of them stale. Ask whether cleansing happens before the move or after, because doing it after means cleansing a live system while a sales team works in it. We cover the sequencing in data migration for platform implementations, which is the sequence that keeps a sales team working while the move happens.
Then ask what the vendor will do with records that fail validation. "We will fix them" is not an answer. A quarantine table, an exception report and an owner on your side is.
What should you ask about ownership, security and exit?
Ask for the assignment clause in writing before you sign, and read it. You should own the source code, the database schema, the infrastructure configuration, the integration credentials and the documentation. At Eazyware you own all of it, including prompts and model choices where AI features are involved, and the repository sits in your organisation from the first commit. The contract terms that matter are set out in who owns the code, prompts and models and defined in code and IP ownership.
On security, ask which verification standard the team tests against rather than whether they are "secure". OWASP publishes an Application Security Verification Standard that gives both sides a common vocabulary for authentication, access control, logging and data protection requirements, and a vendor who has used it will say so immediately. Ask separately about role-based access control, because a CRM is the one system where every salesperson wants to see every account. Ask how role-based access control will be configured, and by whom, after you go live.
What should a custom CRM cost, and what should the quote contain?
Custom ERP and CRM development at Eazyware starts at $28,000 or ₹18,40,000 and runs to $105,000 or ₹72,00,000 for multi-entity systems with heavy integration, and all starting figures are published on the pricing page rather than quoted on request. The scope behind those numbers sits on the custom ERP and CRM development page. If your requirements are not yet firm, a ten-day Sprint Zero at $3,250 or ₹2,00,000, credited against the build, produces the module list and the migration plan the quote should price.
A quote worth comparing names the modules, the integrations by system and direction, the migration scope in record counts, the number of user roles, the training days and the support tier. A quote that gives one number and one date is a negotiation position. What a fixed-price quote should contain lists the line items, and the real cost of a custom CRM or ERP covers the running costs that sit underneath.
The three questions buyers forget
- What is the support arrangement in month seven? Warranty periods end. Ask for the monthly figure now. Care Plans run from $1,000 or ₹68,000 a month for business-hours cover with an eight-hour response, to $5,250 or ₹3,40,000 for 24 by 7 cover with a one-hour response and a named engineer.
- Who trains the next joiner? The vendor trains your current team. Ask who trains the person who joins in March, and whether recorded sessions and written runbooks are deliverables or favours.
- What happens when a source system changes? Your accounting package will push a breaking API change. Ask whether integration maintenance sits inside the support contract or is billed as new work.
- How do we get our data out? Ask for a documented export, in a format a human can read, tested once during the project rather than promised for later.
- Who owns the decision when scope changes? Name the person on each side who can approve a change, and the format the change request takes.
When this question list is the wrong tool
If you have fewer than twenty users and a standard sales process, do not run this exercise. Buy a platform, configure it in a fortnight and revisit in two years. Interrogating a custom development vendor is expensive attention spent on a decision you should not be making yet, and custom CRM vs off-the-shelf walks through where that line sits.
The list is also wrong if you are buying a licensed platform implementation rather than a build. There the questions change shape: configuration versus customisation, upgrade safety, and how much of the vendor's work survives the next platform release. And if your real problem is that nobody enters data into the CRM you already have, a new system will not fix it. That is an adoption problem, described honestly in why enterprise software implementations fail on adoption.
What good answers look like in practice
A university came to us with a fifteen-year-old ERP, a finance team that trusted none of its reports, and three failed replacement attempts behind them. The questions that mattered were not about features. They were about whether anyone could migrate two decades of student and finance records without a gap, and whether the system could be replaced in pieces while admissions ran. We answered by building an anti-corruption layer and cutting over module by module, described in the university ERP modernisation case study.
The pattern generalises to CRM. A vendor who reaches for a phased cutover and a reconciliation report has done this. A vendor who reaches for a Gantt chart with a single go-live date in month five has not, or has and has forgotten.
Before you sign: a final pass
- Read the intellectual property clause yourself, not through a summary
- Confirm the repository, cloud account and domain are in your name
- Get the monthly running cost in writing, with the assumptions listed
- Name the delivery lead and check they are on the project, not just the pitch
- Agree the reconciliation sign-off before migration, not after
- Fix the support tier and response target in the same contract
- Ask for one reference who had a problem, and what happened next
Related reading
The hidden costs of custom CRM development covers the lines that quotes omit, what to put in a custom CRM development RFP gets you better answers by asking better questions on paper, and what a Care Plan should cost sets expectations for the years after launch. If you want the questions answered against your own situation, talk to us.
The vendor you want is the one who answers the awkward questions first and volunteers the cost you had not thought to ask about.
Frequently asked questions
What is the single most important question to ask a custom CRM vendor?
▾
How they will reconcile migrated data. Every CRM project imports records; few prove afterwards that counts, totals and relationships survived. A vendor who names the reconciliation report, the fields being compared and the person signing off has run a real cutover before.
Should a custom CRM vendor own the code they write for us?
▾
No. You should own the source code, database schema, infrastructure configuration and documentation outright, assigned in the contract rather than licensed. At Eazyware the repository sits in your organisation from the first commit, and ownership is not contingent on final payment.
How much should I budget for CRM support after go-live?
▾
Budget from the month the warranty ends. Eazyware Care Plans start at $1,000 or ₹68,000 a month for business-hours cover with an eight-hour response and ten hours of work, rising to $5,250 or ₹3,40,000 for 24 by 7 cover, a one-hour response and a named engineer.