The team that rolled Salesforce out on 200+ projects built its own CRM.
During our Salesforce era we delivered enterprise projects in that ecosystem. What we learned went into our own product: a WhatsApp inbox built in, an assistant that writes records by voice, and a rollout we perform ourselves. We hold no formal Salesforce partnership today.
The short answer: what we are, and what we are not
For Turkey-based B2B teams with at least 5 users, this is what Rapitek CRM is: the web interface is available in Turkish, English and Arabic while support and training are in Turkish, the WhatsApp inbox is part of the product rather than a project, and each customer gets a separate database. We do the setup, the data migration and the training ourselves; the scope, and any fee, is put in writing at discovery.
We do not compare ourselves with another product on this page. We write down what we do and what we do not do; which of those matters for your business is your call. How to decide what to move is written out step by step in our migration guide.
What Rapitek CRM does, and how
| Area | Rapitek CRM |
|---|---|
| Who does the rollout | The team that builds the product; scope is worked out in discovery and the fee put in writing |
| Typical time to go live | We do not commit to a duration before discovery; after the discovery call we give you a date, not a range |
| Web interface language | Turkish, English and Arabic; other languages can be added on request — the scope is worked out in discovery |
| Support and training language | Turkish — from the team that builds and runs the product |
| Inside the product: shared inbox, logged on the customer record | |
| Approach to AI | You connect your own Claude account over MCP; access is capped by that user's permissions. Rapi is off by default |
| Data separation | A separate database per customer; the separation is at the database level, not an application setting |
| Data location | European Union: database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany) |
| Customization | Fields, objects, flows and page layouts are configurable without code; we do it as part of setup |
| Ecosystem breadth | Narrow. We have no marketplace and no trained partner network — we say so plainly |
| Global multi-region operations | Not our focus; we have no local partner support outside Türkiye |
What stands out in Rapitek CRM
Rapi — an assistant that writes records by voice
In the mobile app it creates and updates records from speech. It asks for your confirmation before writing — control stays with you.
Connect your own AI
Your CRM is open to AI over MCP. You connect your own Claude account and you decide what it does. Access can never exceed the permissions of the user who connected it.
Shared WhatsApp inbox
The team writes from a single work number and every message is logged on the customer record. Even when a rep leaves, the conversation history stays with the business.
A mobile app that scans business cards
Fields are extracted from a photo of the card and a lead record is created. The iOS and Android apps are both live.
Field sales and visit tracking
Mobile record-keeping, GPS visit check-in and performance reports for teams that sell in the field. Route plans and field visit records are a separately priced module — 25 USD per user per month.
A separate database and an audit trail
A separate database per customer, two-factor authentication, role-based access and a field-level audit trail.
How does a migration from Salesforce work?
-
1
Current-state analysis
We map together which objects, fields and automations you use today. This step is run by a team that has delivered more than 200 Salesforce projects — we know what to look for.
-
2
Scope and a written quote
What moves, what gets rebuilt, what gets left behind — all in writing. If there is a setup fee, you see it before the work starts.
-
3
Data migration and configuration
Your records are migrated and duplicates cleaned out; fields, stages, roles and reports are set up around your process.
-
4
Training and go-live
We train your team ourselves and stay close through the first week. Go-live is on the date we gave you after the discovery call — a date, not a range.
When we are not the right product
We are not the right fit for every company, and we would rather say so upfront. We do not recommend moving in these four cases:
- Your current system has settled in and your team is trained. Replacing a working implementation carries a cost that never shows up on an invoice — the team relearns and the processes get rebuilt.
- You depend on marketplace add-ons. We have no marketplace; the add-ons you rely on may have no equivalent here, and we can only tell you which ones by going through them in discovery.
- You run a global, multi-region operation. We have no local partner support outside Türkiye; this is not where we are strong.
- You are mid-contract on your current software. The right moment to move is at renewal; before that you pay for two systems at once.
If one of these describes you, we will say the same thing in the discovery call — we do not write it on the page and soften it in the meeting.
Frequently asked questions
What does Rapitek CRM cover?
Can our existing CRM data be migrated?
How much does Rapitek CRM cost?
How long does the migration take?
Can we try it first?
Let's work out together whether moving makes sense.
Tell us about your current Salesforce implementation and we'll talk through what would move, what wouldn't, and whether the migration is right for you. If it isn't, we'll say so.
30 minutes · No obligation · The call is held in Turkish
