Choosing a CRM: The Questions That Actually Decide the Outcome
Most CRM evaluations start the same way: a spreadsheet with vendors across the top and features down the side. Six weeks later the spreadsheet is full, every vendor scores well, and the decision is no easier than on day one.
Across 200+ CRM implementations we delivered during our Salesforce era, the projects that went badly almost never failed on a missing feature. They failed because the software did not match how the team actually worked, because the data that came in was a mess, because nobody owned the system after go-live, or because the real cost showed up in month four.
This guide covers the questions that decide it, written for the person who has to sign: a company with a sales team of five or more, real customers, and a process that already exists, even if it currently lives in spreadsheets and WhatsApp threads.
Feature lists do not predict outcomes.
Contents
Start with how your team actually works
Before you look at any product, write down how a deal moves through your company today.
Take three deals from last quarter: one you won, one you lost, one still stuck. For each, list every step and every place information was recorded. The WhatsApp thread. The quote in someone's downloads folder. The email chain the manager was never copied on.
Then answer:
- How many people touch a deal between first contact and invoice?
- Where does the work happen: office, phone, customer site, showroom?
- How long is a normal cycle, and what does "stuck" look like in practice?
- Who approves a discount, and how does anyone else know it was approved?
- What does your sales manager genuinely need to see on Monday morning?
This takes an afternoon and it is uncomfortable, because it usually reveals that nobody agrees on the process. It is also the only thing that makes a demo useful. Without it every demo looks impressive, because every demo is built to look impressive.
Process fit beats feature count
A feature you never use costs you nothing. A mismatch costs you every day, in small amounts, forever. Five extra clicks per record is not a rounding error when a rep enters twenty records a week.
So do not let the vendor drive the demo. Ask them to enter your deal, with your stages, your product names and your approval step, while you watch. Count the clicks. Count the fields a rep would fill in on a phone, standing in a customer's warehouse, with one hand.
You will also hear the opposite advice: adopt the software's process, because it encodes best practice. Sometimes that is right and a bad habit is worth losing. But be honest about which is which. If your process exists because your customers pay in stages, or because dealers order differently from direct accounts, that is not a bad habit. That is your market.
Configuration, automation or development: know which one you are buying
Almost every vendor says "fully customizable." The phrase covers three different things with three different price tags, set out in the table below.
Take your requirement list into the pre-sales conversation and ask the vendor to sort every item into one of those three buckets, in writing. Then ask the question people forget: what happens in month six, when you need a change? Who makes it, how long does it take, and is it billable? A system you cannot change is a system you will outgrow, faster than you expect.
| What you are buying | What it covers | What it costs |
|---|---|---|
| Configuration | Fields, pipeline stages, page layouts, roles and permissions | Should be included, and done before go-live rather than left as homework |
| Automation | Assignment rules, approval flows, reminders, alerts when a deal goes quiet | Usually included, sometimes limited by tier |
| Development | A custom object your business needs, logic nobody else has asked for, an integration with a system the vendor has never touched | A project with a scope and a price |
Data migration is the project, not a step inside it
Ask what is in your current system before you ask how it moves. In most companies the honest answer is duplicates, three spellings of the same company name, contacts that exist only in one person's phone, and quotes in a shared drive nobody has opened since last year.
Decide these before migration starts, not during:
What actually moves
Accounts and contacts only, open deals, or full history?
How far back does history go?
Five years of dead leads is not an asset.
Who does the cleanup?
You know which records are real. The vendor does not.
Can you export from your current system?
And in what format? Ask for a full export now, while you are still a paying customer with leverage.
Insist on a test migration into a sandbox before go-live, and have two people who know the data check it. Once a rep finds three wrong records, they quietly go back to their own spreadsheet, and you do not get them back.
Adoption is decided in the first six weeks
Training is not a day. It is short, role-based sessions on real data after migration: one for reps, one for managers, one for whoever handles orders and back office. A single four-hour session for everyone at once teaches nobody anything.
One thing decides adoption more than all the training: the manager. If the weekly sales meeting still runs off a spreadsheet or from memory, the CRM is already dead, and the team knows it within two weeks. If the meeting runs off the pipeline, and "it is not in the CRM" means "it did not happen," adoption takes care of itself.
Settle two more things before go-live. Who owns the system internally, by name? And what does the field team see on a phone? If your reps work outside, mobile is the whole product for everyone on the team who never sits at a desk.
Total cost of ownership: the lines that are not on the pricing page
The per-user monthly price is the smallest number in this decision. Build a three-year total instead, and make the vendor answer every line:
- License, per user per month, and what happens to it at renewal.
- Implementation and configuration, one-off, with the scope written down.
- Data migration: included or priced separately, and up to how many records?
- Integrations, usually priced per integration: accounting, e-invoice, website forms, WhatsApp, telephony.
- Training sessions, including refreshers for people you hire next year.
- Ongoing changes: hourly, retainer, or included?
- Your own internal hours. No invoice arrives, but the cost is real.
- Limits on storage, API calls, automation runs and email volume, since overages are where "cheap" becomes expensive.
- Adding users mid-term, and exporting everything if you part ways.
A platform with a low license fee and expensive changes can cost more over three years than one with the opposite shape. Neither is wrong. You need to know which one you are signing.
Buying a CRM in Turkey: the questions international checklists skip
Four things matter here that a generic evaluation list will not raise.
KVKK and the paperwork. Your company is the data controller. The vendor is a processor acting on your instructions. You need a written data processing agreement, and your VERBIS entry and privacy notice have to reflect the new system. Ask for the vendor's agreement text early. If they do not have one ready, that itself is information.
Where the data physically sits. Ask for the country and the hosting provider, in writing. This is not paranoia, it changes your obligations. Under Article 9 of KVKK, personal data sent to servers outside Turkey is a cross-border transfer: it needs a valid legal basis, disclosure in your aydınlatma metni, and depending on the route you choose, explicit consent from the data subject.
Here is our own answer, plainly. The Rapitek CRM database runs in Helsinki, Finland; uploaded files are stored in Frankfurt and database backups in Falkenstein, both in Germany. All three are in the EU. So yes, using Rapitek CRM involves a cross-border transfer under KVKK. And there is a second one you need before you write your notice: if you switch on the AI features, that request goes to the United States. We say all of this during the sales conversation, not after signature, and we give you the wording for your privacy notice and the consent line on your web forms. We are direct about it because "don't worry about it" is the answer that should worry you: a vendor who cannot name the country their servers are in cannot help you defend that choice to an auditor. What we do not claim: we hold no ISO 27001 or SOC 2 certification, because we have not completed those processes. What we do have is specific: TLS on data in transit, a separate database for your CRM records rather than shared tables, and two-factor authentication on accounts.
E-fatura and accounting. A CRM is normally not the system that issues your e-fatura or e-arşiv document; your accounting software or integrator does that. The real question is the handoff. When a deal is won, does the order reach accounting automatically, or does someone retype it? Ask which specific integrators and ERP systems the vendor has actually connected before. Do not ask whether integration is possible. Everything is possible. You want to know whether it has been done.
Support and WhatsApp. Ask what language support is delivered in, what hours, and whether the person answering has seen your configuration before. Our own position: support is in Turkish, in Turkish working hours, from the same team that built your setup. In practice we reply the same working day. We deliberately do not put a number on that: we have no system measuring ticket times yet, and we do not publish a duration we have not measured — so treat it as our working practice, not as a commitment. We run no 24/7 desk and no ticket queue. Separately, in the projects we have worked on, a great deal of B2B conversation in Turkey happens on WhatsApp, and if those conversations live on personal phones your pipeline is fiction and your customer history walks out with the employee. Ask every vendor how a WhatsApp conversation ends up attached to the customer record.
What good looks like six months in
Four signals tell you it worked. The weekly sales meeting runs off the pipeline, not a spreadsheet. The forecast comes from records rather than memory and optimism. A new hire can read an account's history without asking a colleague what happened. And the number of required fields has gone down, not up, because someone kept pruning.
A quieter fifth signal: you have changed something twice without paying a project fee and without waiting on a change-request queue. That is usually the difference between a system you own and a system you rent.
Frequently asked questions about choosing a CRM
What should I evaluate first when choosing a CRM?
How long does a CRM implementation take?
Which costs are missing from the price list?
Does CRM data have to be stored in Turkey?
Can I try Rapitek CRM on a free trial?
See it against your own process
If you are evaluating, the useful next step is not another feature list. It is a working session with your real deals in front of you.
We do not offer a self-service free trial, and that is deliberate. Rapitek CRM is configured for you: your fields, your pipeline, your data migrated and your team trained. After the discovery call, we give you a date, not a range. There is nothing meaningful to try alone inside an empty system.
Book a demo, or message us on WhatsApp: +90 212 963 22 84 — the same line we answer ourselves, every working day. Bring one real deal and your current spreadsheet. That is enough for us to tell you honestly whether we are a good fit. Rapitek CRM is built for teams of five or more with a real sales function, so if you are a one-person office looking for a ten-dollar-a-month tool, we will tell you that too.
Kerim Yıldırım
Founder, Rapitek CRM · 200+ enterprise CRM projects during our Salesforce era
