In short
Custom CRM software manages customer and sales processes according to a company’s own workflow, built from scratch or from modules. It is for companies that can’t make off-the-shelf CRMs fit their processes, or that want to keep their data on their own infrastructure. CybUP covers process analysis, the sales pipeline, roles and permissions, WhatsApp, email and IP PBX integration, reporting and a data model built for KVKK.
When is an off-the-shelf CRM not enough?
An off-the-shelf CRM works well as long as your sales process fits the pattern the software assumes; once the process departs from it, the team starts working around the CRM. The symptoms are familiar: the real tracking happens in Excel, records go into the CRM only because they have to, reports don’t answer the questions management asks, and every new field needs an add-on module or a higher plan.
Take an industrial equipment supplier that sells project by project. A quote first goes through a technical site survey, then engineering approval, and reaches the customer only after several revisions. You need to know who sent each revision, at what price and on what delivery terms. A generic CRM’s “opportunity” object struggles to carry that process. In a custom CRM, quotes, revisions and approval steps are part of the data model itself.
Custom software isn’t always the answer. If configuring an off-the-shelf CRM would meet the need, we will say so; custom development is a decision that also brings maintenance responsibility.
How do you design the sales pipeline and user roles in a custom CRM?
A sales pipeline defines the stages an enquiry passes through from first contact to a won or lost deal, and what has to happen at each stage. In a custom CRM we name the stages in your team’s own language and make the information needed to move from one stage to the next mandatory. A record can’t reach the quote stage without the quote document and the decision-maker’s details.
Roles and permissions get the same care. A sales rep sees their own customers, a regional manager sees their region, management sees everything, and accounting sees only billing details. Where needed, this kind of row-level permission is enforced in the database layer as well: PostgreSQL’s row security policies, for example, limit which records a user can see directly in the database. When a rep leaves, their customers are reassigned to someone else in a single step.
“In addition to the SQL-standard privilege system available through GRANT, tables can have row security policies that restrict, on a per-user basis, which rows can be returned by normal queries or inserted, updated, or deleted by data modification commands.”
How does a CRM integrate with WhatsApp, email and an IP PBX?
The aim of integration is for every customer contact to land on the right record without anyone typing it in. Once the CRM is connected to your company mailboxes, correspondence with a customer appears on their record, and a quote sent by email is attached automatically.
For WhatsApp we use the official WhatsApp Business Platform. Incoming messages are linked to the contact in the CRM, and the agent replies from the CRM screen. According to Meta’s documentation on sending messages, once the 24-hour window after the customer’s last message has closed, only approved templates can be sent; the CRM screen tells the agent when that is the case. If you want an AI-powered first response, it works together with a WhatsApp AI chatbot.
For telephony, integrating with an IP PBX that offers an API means the caller’s customer record opens when a call comes in, the call duration and, where available, a recording link are added to the record, and agents can click a number to dial. What can be passed across depends on the interface the PBX provides; we check this during analysis.
“When the window closes, you can only send pre-approved template messages.”
How do you connect CRM reporting to your other systems?
Reports are designed from the questions management actually asks: how many quotes are waiting at which stage this month, how long the average sales cycle is, which lead sources convert best, why quotes are being lost. Answering them means capturing the right fields from day one, which is why we discuss reporting on the first day of analysis.
Connections to existing systems such as ERP or accounting software are usually limited to synchronising data such as customer records, product lists and order status. They are built through the APIs those systems offer, or with an n8n workflow in between. Marketplace and e-invoicing integrations are outside our scope; if you need them, we suggest using your ERP or accounting software’s own solution.
Who owns the CRM data, and what does KVKK require?
With a custom CRM, you own the data: the database sits on your server or in your own cloud subscription, and the source code is handed over to you under the contract. There is no wrestling to get your data out when a licence subscription ends.
A CRM processes a great deal of customer and employee personal data. The data security provisions of KVKK, Türkiye’s Personal Data Protection Law (Law No. 6698), require appropriate technical and administrative measures. In the software we support this with role-based access, audit logs recording who viewed or changed which record and when, encrypted connections, backups, and tools for deleting or anonymising data once its retention period has expired.
- Role- and region-based access permissions
- Audit logs for views and changes
- A deletion and anonymisation tool for records past their retention period
- Regular database backups and restore tests
How does a custom CRM project run?
The project starts by mapping the current process with the sales team. Then the scope of the first release is set: usually customer and contact records, the sales pipeline, activities and core reports. Integrations and advanced reporting are left for later releases. Once the team has used the first release for a few weeks, their feedback steers the next round of development.
Migrating existing data is a separate work item. Records from Excel files and the old CRM are cleaned of duplicate customers, missing fields and inconsistent spellings. The review is free; once the scope is clear we prepare a written quote broken down into phases. If you might one day sell the product to other companies, it may be worth building the architecture for SaaS from the start.
What you receive
- A process map and an approved scope for the first release
- A web-based CRM with your sales pipeline, roles and permissions
- Email, WhatsApp Business Platform and IP PBX integrations (depending on scope)
- Reports built around the questions management asks
- Existing customer data cleaned and migrated
- Source code, installation documentation and user training
How we work
- 1
Free review
We assess your sales process, current tools, number of users and integration needs.
- 2
Analysis and scope
The process map is drawn up, and the screens and data model for the first release are approved.
- 3
Development
The CRM is built in short iterations and tried out with your team at each stage.
- 4
Data migration and training
Existing data is cleaned and imported, and users are trained according to their roles.
- 5
Launch and further development
The system goes live; integrations and reports are added based on feedback.
Frequently asked questions
Custom CRM or off-the-shelf CRM: which makes more sense?
If your process is standard and you have few users, an off-the-shelf CRM is often enough. If the process is unusual, you need many integrations or you have to keep the data on your own infrastructure, a custom CRM is the better fit. We weigh up both options openly during the review.
How long does custom CRM development take?
A first release with the core modules is usually in use within a few months. The timeline depends on the number of screens, the integrations and how much data has to be migrated. We include a phased schedule with the quote.
Will we own the source code?
Yes. The contract provides for the source code and the database to be handed over to you. That also leaves you free to continue development with another team later.
Can the CRM be used on mobile?
Yes. The CRM is built with a responsive web interface that works properly on phones and tablets. Special requirements, such as field staff working offline, are assessed separately.
Do you build e-invoicing or marketplace integrations?
No, we don’t build e-invoicing or marketplace integrations. We can connect the CRM to your ERP or accounting software at the level of customer and order data; invoicing runs through that system’s own solutions.
How much does a custom CRM cost?
We send a written quote once we have reviewed the scope; the review is free. The quote shows the first release, integrations, data migration and maintenance as separate items.
Do you provide support after launch?
Yes. Under a maintenance contract we cover bug fixes, security updates, backup checks and new development requests. We set the scope according to how heavily the system is used.