Guide · CRM selection

How to choose a CRM: a buyer's guide written in the field

We delivered more than 200 enterprise CRM projects during our Salesforce era, and we watched right and wrong choices play out up close. This page is not a PDF to download — it is the guide itself: what to look at, what to ask, where each cost hides, and why implementation decides more than the license.

Why this guide exists — and why it is honest

Let's be upfront: we sell a CRM too. The reason we try to stay fair on this page is not virtue but experience: we delivered more than 200 enterprise CRM projects in the Salesforce ecosystem, and we saw up close, again and again, how badly chosen systems end.

We won't dress up the cost of a wrong choice with an inflated statistic. The cost we saw in the field is this: a system nobody enters data into after six months, a quiet retreat to Excel, and a second migration paid for within two years. None of it shows up on the license invoice; all of it costs more.

This page is not a document you trade your email address for; it is the guide itself. Read it in order, or jump straight to what you need: the selection process, evaluation criteria, the hidden-cost map, questions to ask vendors, and how to measure adoption. You can put every question in this guide to every vendor you talk to — including us.

Process

CRM selection in six steps

1

Write the need down

"Let's get a CRM" is not a need. Write down the three to five concrete problems you want solved: follow-ups get forgotten, quotes go out late, the management report is compiled by hand. How many users, which teams, which processes — this list defines the scope.
2

Cut the shortlist to three

There are hundreds of CRMs on the market; you cannot look at them all. Filter with your hard criteria (language, data location, budget range, industry experience) and continue with at most three candidates. Spend your energy testing three candidates deeply, not making the list longer.
3

Ask for a demo with your own scenario

The vendor's canned scenario looks flawless in every product. Have them walk your flow: a lead comes in, a quote goes out, a follow-up task drops in, the report reflects it. Run the same scenario with every candidate so the comparison is real.
4

Calculate cost over three years

The monthly license is the visible tip of the iceberg. Add implementation, data migration, training, integration, the support package, renewal increases and the exit cost. The hidden-cost map below exists exactly for this calculation.
5

Ask for proof

Ask for a reference at a similar scale with a similar process. If a trial environment is offered, test it with your own real records; if not, demand the same depth in the demo. You want to see it done, not hear that "it can be done."
6

Sign the rollout plan along with the decision

Selection doesn't end with the contract. Who configures the system, when data moves, when the team is trained, which date you go live — tie it all to a written plan. Define adoption metrics from day one; we suggest some below.

Nine evaluation criteria

Data model and customization

Can fields, objects and sales stages be adapted to your process? Don't settle for "anything is possible"; watch an example from your own process being configured in the demo, and ask who does the configuration.

Ease of use

How many clicks does the most frequent job take — opening a record, adding a note, closing a task? If the sales team can't create records on their own from day one, the system stays empty no matter how powerful it is.

Integration approach

Look past shiny logo walls to the method: which system, in which direction, and who will build it should be pinned down in writing. An open REST API with webhook support outlives any list of prebuilt connectors.

Reporting

Canned reports impress in demos; the real question is whether you can build a report for your own question. Ask who keeps the management dashboard current and whether building a report requires code.

Mobile use

If your team is in the field, the real test of a CRM is on a phone. If updating a record after a visit means going back to a desk, the data doesn't get entered that day — and usually never does.

Security and data location

Ask plainly which country the data is kept in. For companies in Turkey, data hosted abroad is a cross-border transfer under KVKK, Turkey's data protection law (No. 6698, Art. 9), which sets out tiered bases for transfer: adequacy, then appropriate safeguards, and only exceptionally incidental cases. Find out whether permissions reach record level and how customers' data is kept separate.

Artificial intelligence

Look at the scenario, not the show: which task does it cut from how many steps to how many? Whether an assistant with write access asks for confirmation on risky operations matters more than an impressive demo.

Support model

Who answers your question: an agent in a ticket pool, or a team that knows the product? Get the language, channel and response-time commitment in writing before you buy.

Data ownership and exit

Plan the exit before the entry: in what format, and at what cost, can you export all of your data? If the answer is vague, you are leaving your negotiating power at the door.

Total cost of ownership

The hidden-cost map

Run this table on every vendor you talk to — including us. Our own pricing page states plainly which items are included in each plan.
Cost item	Where it hides	The question to ask the vendor
Implementation and configuration	The "not included in the license" line usually surfaces in a contract annex	Are implementation, configuration and training included in the price? If not, how many days of work, and at what cost?
Data migration	Moving data from the old system is billed separately as "professional services"	Is migrating our existing records, including de-duplication, part of the scope?
Training	Charged per session or per user	How many training sessions are included? How is training for people who join later charged?
Integration	"There is an API" does not mean the integration will be built	Who builds this connection? Are the scope and cost given in writing before the quote?
Forced plan upgrades	The one feature you need sits in a higher tier	Which plan is this feature in? What else would we be paying for in that plan?
API access	In some products the API is a separately priced add-on	Are API access and request limits included in the plan?
Support	Standard support is email-only; phone and priority handling cost extra	Who answers support requests, through which channel, and within what time?
Renewal increases	The first-year discount reverts to list price in year two	How is the second-year renewal price set? Can we have it in writing?
Exit cost	Exporting your data is restricted or charged	If we leave, in what format and at what cost do we get all of our data?

20 questions to ask before you buy

Send these questions to the vendor in writing before the meeting. Written answers are far more binding than verbal "yes"es during a demo — and every question that goes unanswered is an answer in itself.

Data and security

Which country is our data hosted in? If it is outside Turkey, how do you handle the cross-border transfer requirements of KVKK Art. 9?
Is our data kept in a separate database, or in tables shared with other customers?
Do permissions go down to record level? When an employee leaves, what happens to their access and record history?
How often are backups taken? Can we recover a record that was deleted by mistake?

Customization and implementation

Who configures the fields, stages and flows specific to our process — you or us? Is it included in the price?
Do you commit to an implementation date? What is your typical timeline?
After go-live, who do we reach when changes are needed, and at what cost?
Is migrating our existing records, including de-duplication, part of the scope?

Integration

Who builds the connection to the ERP or accounting software we use? Are the scope and cost given in writing before the quote?
Is API access included in the plan? What are the request limits?
Do you support webhooks for pushing data to our systems?

Usage and adoption

How many training sessions are included in the price? How does repeat training for people who join later work?
What languages are the interface and support available in?
Which platforms is your mobile app available on?
Who works alongside us in the first months after go-live?

Contract and exit

How is the second-year renewal price set? Can we have it in writing?
What are the minimum commitment period and the early exit terms?
If we leave, in what format and at what cost do we get all of our data?
When and how is our data deleted after the contract ends?
Can you share the full list of items not included in the price?

You can ask us every one of these questions too; we answer all of them in writing at the demo. Where our answer is "we don't have that", we prefer to say so plainly — that is why this guide exists.

Behind this guide

Written in the field, not at a desk

200+

Enterprise CRM projects completed for other companies during our Salesforce era

A date, not a range

We give you a go-live date after the discovery call

Data location: database in Finland, media in Frankfurt

Implementation decides more than the license

What we saw again and again across 200+ projects is this: CRM projects fail not because of the product but because of implementation and adoption. Badly designed stages, twenty required fields nobody fills in, a team dropped into the system without training — that turns even the best product into an empty database within six months.

So when choosing, weigh "who implements it, and how" as heavily as "which product". A product whose license looks cheap can turn out to be the most expensive option once implementation and training are billed separately — and the reverse is just as true.

How do you measure adoption?

Login counts are a misleading metric; looking at the system and using the system are not the same thing. In the first 90 days, watch these four:

Record discipline: How much of the team's contact with customers actually lands in the CRM? If people still write in phone notes and notebooks, the system is only alive on paper.
Field completion: Are required fields genuinely filled in, or waved through? A field that keeps getting skipped is a badly designed field.
Meeting source: Is the weekly sales meeting run from the CRM screen, or has it drifted back to Excel? A manager compiling the report by hand is the first crack.
Direction of questions: If the team asks "how do I do this in the system", adoption has begun; if they ask "do I really have to enter this into the system", revisit the setup.

How do you calculate the return?

We won't promise a template with multipliers; we suggest three measurable items. Measure the current state before implementation so you have something to compare against:

Share of leads left without follow-up — how many inbound inquiries go unanswered?
Time to quote — how many days pass between the request and the quote going out?
Hours spent on reporting — how many people spend how many hours on the management report each week?

We have seen this picture so often that we built our own model around it: we do the setup ourselves, and after the discovery call we give you a date, not a range. We also apply our own advice to ourselves — whatever sits outside the plan price, including the scope of setup, is worked out in the discovery call and put in writing before the work starts. You can find the current plans on our pricing page.

From our CRM implementation projects

From our CRM projects

As Anatolia Tile, we place great importance on digital transformation to maintain our leadership position in the global market since 1995. The CRM project we initiated with Rapitek completely transformed our sales processes. By consolidating our customer data on a single platform, we increased team efficiency and accelerated our decision-making processes. Rapitek's industry experience and solution-oriented approach enabled us to achieve results beyond our expectations.

Şemun Alp Biber General Manager · Anatolia Tile

As a former Salesforce user, getting to know Rapitek was an opportunity that opened the doors to different solutions for us. With the smart solutions their consultants provided, we significantly increased our efficiency. In addition, thanks to our collaboration with Rapitek, we seamlessly integrated our product with Salesforce and made our processes more efficient.

Utku Aydın Business Development Director · Iyzico

The most important element of bringing new business ideas to life is your IT infrastructure and applications. Rapitek offered much more than just providing an application — they became our solution partner. Thanks to their quick responses in unexpected situations and their flexibility during the development process, we reached our first product quickly and ensured healthy project continuity.

Denizhan Edeer CEO · Aktif Filo

Check the fit in 60 seconds

You do not have to read this guide end to end. The fit check asks five questions and tells you whether Rapitek CRM fits. The answer may be that waiting is the better call for now.

Open the fit check

No signup, no email required.

FAQ

Frequently asked questions about choosing a CRM

What should you look for when choosing a CRM?

Look at nine areas: data model and customization, ease of use, integration approach, reporting, mobile use, security and data location, artificial intelligence, the support model, and data ownership and exit terms. The one-sentence summary: choose the system your team will actually use and whose total cost is predictable — not the one with the most features.

How should CRM pricing be calculated?

The monthly license alone is misleading. Calculate the three-year total cost of ownership: license, implementation and configuration, data migration, training, integration, the support package, renewal increases and exit cost. Ask the vendor for a written list of everything not included in the price. We do the same: the items priced outside the plan — including the scope of setup — are listed one by one on our pricing page, and the cost is worked out in the discovery call and put in writing.

Does a small team need a CRM?

Below 5 users, simple self-service tools are usually sufficient and usually the smarter choice; we say that openly. A CRM investment starts to make sense when the team grows and knowledge can no longer live in one person's phone. Rapitek CRM, where we do the setup ourselves, focuses on growing teams of 5 users or more.

What is the advantage of a CRM over Excel?

Excel is tied to a person: whoever has the file has the knowledge; there is no record history, no reminders, two people can't comfortably work in it at once, and when an employee leaves, the relationships leave with the file. A CRM turns the same data into the team's shared property, with permissions, record history, tasks and reminders, and reporting. If your spreadsheet is now managed with color codes and "final_v3_FINAL" file names, it is time to move.

How long does a CRM implementation take?

It depends on scope: user count, data volume, integration needs and the number of processes set the timeline. Implementations that drag on for months usually trace back to scope never being pinned down at the start. In Rapitek CRM, the rollout covers discovery, configuration, data migration and training; after the discovery call we give you a date, not a range, and the scope of the rollout — along with any fee for it — is put in writing before the work starts.

Should you choose a free CRM?

For a small team it can work at the start; honesty requires saying so. You pay the price elsewhere: user and record limits, limited support, often unclear data location, and an unavoidable migration cost when you grow. When choosing your permanent system, put the very same questions from this guide to the free product; every question you can't get answered marks a limit.

Does it matter whether the vendor is local or international?

The label alone measures nothing; the criteria stay the same. The practical differences are these: support language and working hours, interface language, the currency the price is set in, familiarity with KVKK and local business practices, and data location. A local vendor or an international one can both be the right choice if they answer these five points well; if they answer badly, the label is irrelevant.

Where should CRM data be stored, and what matters legally?

What matters is not the place but transparency: the vendor must be able to say plainly which country your data lives in. For companies in Turkey, data hosted abroad is a cross-border transfer under KVKK Art. 9, so a lawful transfer ground and disclosure processes must be in place. Rapitek CRM hosts the database in the European Union, in Finland, with media files in Frankfurt — and we state this openly. TLS protects data in transit, credentials and two-factor secrets are protected at rest, and every customer gets a separate database.

Are AI features in a CRM actually useful?

The right question is not "does it have AI" but "which task does it cut, from how many steps to how many". An assistant that can create records genuinely saves time — but an AI with write access must ask for confirmation on risky operations. In Rapitek CRM, the voice assistant Rapi works only in the mobile app; it takes spoken Turkish commands to create and update records across 11 objects, and asks for confirmation before saving risky changes. The scanner that turns a business-card photo into a lead works on both web and mobile.

What happens to our old data when we switch CRMs?

Data migration is the topic discussed last in selection meetings and the most critical job of implementation. Customer, company and opportunity records from spreadsheets or your current system are imported, and duplicates are cleaned up at that stage. Always ask the vendor whether migration is in scope and who handles de-duplication. In Rapitek CRM, data migration is part of implementation; the scope of setup, and any fee for it, is worked out in discovery and put in writing.

From guide to product

We applied these criteria to ourselves first

We built Rapitek CRM to give clean answers to the questions in this guide: a separate database for every customer, hosting in the European Union, an open REST API, and a transparent model where anything outside the plan price — including the scope of setup — is put in writing before the work starts.

Explore the product See pricing

Rapitek CRM dashboard: open opportunities, daily tasks, new leads and total pipeline value — Rapitek CRM — management dashboard

Put us on your shortlist too

In a 30-minute demo, ask us every question in this guide; we will walk the product through your own scenario, live. Where the answer is "we don't have that", we say so plainly.

Request a demo

The scope of setup — and any fee for it — is agreed in writing before the work starts.