Implementation included in the price · 48 hours for a standard configuration

CRM implementation built on your real processes

Implementation starts from the way you work today, not from our feature catalogue: we follow the real workflow, configure the platform around it, move data from your current systems with a sample check and train each team on its own role. With a standard configuration the system is up and running in 48 hours, and with customisation to internal procedures it takes up to 14 working days. When you buy a Zarina CRM licence, implementation is included, and go-live comes with a six-month technical warranty.

Screenshot from Zarina CRM: the getting-started guide with the implementation steps: company details, SMTP, scheduled tasks, team, first client, first quotation and first invoice
Workflow audit, not a catalogueVerified data migrationRole-based trainingKnow-how transfer6-month warranty
Implementation packages

CRM implementation packages: three levels of assistance

The difference between packages lies in how much administration your internal team takes on, not in the platform’s functionality. All three install the same application, on your company’s infrastructure.

Zarina Kickstart

For companies that want the system up and running immediately, with simple workflows.

  • Installation on your server
  • Configuring the key steps together with the consultant
  • Basic structure for the client portfolio
  • Administration basics, learned by actually working in the system
  • Suitable for small teams with clear processes

Standard Onboarding

For companies with an internal person who can take over administration.

  • Specialist training of an internal administrator, included
  • Detailed definition of quotation and contract templates
  • Advanced organisation and verified import of the client base
  • Removing dependence on us for future changes
  • Step-by-step support during the settling-in period

Extended Onboarding

For organisations moving their entire activity into the platform.

  • Additional resources allocated for detailed customisation
  • Configuration of extended modules: invoicing, inventory, projects
  • Tailored automations: follow-up, campaigns, alerts
  • Reports built on management’s indicators
  • Phased plan by department
The 6 steps

The stages of a CRM implementation

Each stage ends with a deliverable that you validate. A stage that is not validated does not move on to the next.

1

Workflow audit

We follow how information flows today: from first contact to payment, who approves what, what is done on paper and where time is lost. The result is a map of the workflow, not a list of catalogue features.

2

Platform configuration

Roles, permissions per module, pipeline stages, custom fields and value lists, laid out on the map from step 1. Anything not activated does not appear in the menu.

3

Document customisation

Quotation, contract, job sheet and invoice templates are built with your company’s letterhead, clauses and numbering, not generic models.

4

Data migration

Clients, contracts and history from Excel, email or the previous system go into the new structure, with a sample check before the full import.

5

Role-based training

Separate sessions for operators, coordinators and management. Each gets only what they need, and the materials stay with you.

6

Go-live and warranty

Going into production happens on a date agreed together, with us available in the first days. A six-month technical warranty follows.

Preparation

Information and documents needed before the first meeting

Having the six items listed below ready allows the workflow audit to be completed in a single meeting and significantly shortens the implementation time.

  1. The person who knows how the company worksNot necessarily the managing director: the person who can explain why something is done a certain way. Without them, configuration rests on assumptions.
  2. The list of departments and rolesWho does what, who approves what and up to what amount. A one-page chart is enough.
  3. The files with your current dataClients, contracts, quotations in progress, in whatever form they exist now — even if they are disorganised. We do the clean-up together; it does not need to be done beforehand.
  4. The documents that leave the companyOne copy of each: quotation, contract, job sheet, invoice. We build the templates from them.
  5. The reports you track monthlyIf there is already a file someone fills in by hand every month, that is the most valuable document for us.
  6. Technical access, or the person who can grant itServer details or your administrator’s contact. If you do not have a server yet, we discuss the options in the same meeting.
Workflow analysis

The workflow audit: analysing processes before configuration

Failed implementations generally start from a configuration based on the vendor’s feature catalogue, not on the organisation’s real processes. The following questions are addressed in the first meeting.

  1. Where do enquiries come from, and who takes them?Phone, website form, referral, trade show, campaign. If we do not know the sources, we cannot set up automatic assignment or reporting per channel.
  2. Who is allowed to see what?Separation by team, branch or client type is an organisational decision, not a technical one. It is set beforehand, because rewriting roles after go-live means redoing all permissions.
  3. Who approves a quotation, and up to what amount?If there is a threshold above which a director signs, the workflow in the application reproduces it. If there is none, we do not invent one.
  4. Which documents leave the company?Quotation, contract, job sheet, invoice, annex. Each has its own letterhead, clauses and numbering, which go into the templates.
  5. What is done today on paper or in messaging apps?This is where the biggest time savings are, and also the greatest resistance to change. We deal with them explicitly, we do not ignore them.
  6. Which report does management ask for, and how often?If a report is built by hand at the start of every week, that is the first one to automate.
What gets configured

The elements configured in the application during implementation

The list sets out what is delivered configured and what remains under internal administration. The complete module inventory is on the features page.

User structure

Accounts, roles, permissions per module and per action, data separation per team or branch, password policy.

Sales stages

The pipeline on your real stages, with probabilities, loss reasons from a fixed list and deadlines per stage.

Custom fields

The company’s value lists: client types, sources, categories, mandatory fields per stage. Kept through updates.

Document templates

Quotation, contract, job sheet, invoice — with your own letterhead, clauses and numbering, generated straight from the client record.

Starter automations

Enquiry assignment, deadline reminders, alerts on opened quotations and the daily report to management.

Active integrations

Your own SMTP server, payment gateways, calendar and the other connectors you actually use. Anything not activated transmits nothing.

Data migration

Migrating data from existing systems

Migration determines how much the new system is trusted. Validation is done by you, on records you know, before the full import.

  1. Inventory of sourcesExcel files, personal contact lists, email, the previous system, sometimes a database from a website. We decide what goes in and what stays in the archive.
  2. Cleaning up duplicatesThe same client appears three times, written differently. Matching rules — tax registration number, email, phone — are agreed together, because they decide what gets merged.
  3. Sample importWe bring in a sample agreed together and you check it. Structural corrections are made here, not after the full volume is in.
  4. Full import and reconciliationWe compare totals with the source: number of clients, pipeline value, attached documents. Differences are explained point by point, not approximated.
  5. What cannot be migratedIf the previous vendor does not export interaction history or attachments, we say so from the start. We do not promise a migration the source export does not allow.
  6. The source archive is keptThe original export stays with you, for reference, even after the new system goes into production.
Training

User training, by role

A general presentation of the whole system has a low retention rate. Sessions are separated by role and cover strictly the work of each user category.

Operators

Only their workflow: taking the enquiry, the client record, the quotation, activities. No modules they will never open.

Coordinators

The team view, reassignment, checking overdue activities and stage reports.

Management

The dashboard, period indicators and consolidated reports. A short session on what is tracked monthly.

The internal administrator

With the Standard and Extended packages, a person from your company is trained to configure roles, fields and templates on their own. That is the real transfer of know-how.

The materials stay with you

Procedures and training recordings stay in the company, for future employees. You do not pay again for every new person.

Refresher on request

If questions come up after a few weeks, we revisit that specific area. The questions at go-live are never the same as the ones in the second month.

Timelines

Implementation timelines, from contract to go-live

The timelines shown are the ones met in typical configurations. The factor that extends them is usually internal decision time, not the technical side.

Standard configuration: 48 hours

Installation, roles, pipeline and basic import. Suitable when processes are clear and do not require complicated templates.

With workflow customisation: up to 14 working days

When your own document templates, automations and approval flows come in. Still included in the price.

What extends the timeline

Disorganised source data, postponed organisational decisions and the unavailability of the person who knows how the company works. We flag them from the first meeting.

Phasing by department

In large organisations, go-live is done by department, not all at once. The first department becomes the reference for the rest.

The go-live date is agreed together

We do not go live during your peak season. Better two weeks later than in the middle of a busy period.

The parallel period

Where there is a previous system, we recommend working in parallel for an agreed period, until the figures match.

Why implementations fail

The main causes of failure in a CRM implementation

A CRM is not abandoned because of missing features, but because of low usage after the first months. The causes are listed in the order we encounter them most often.

  1. The system was configured from the catalogue, not the workflowIf the application requires steps that did not exist in the company, people work around it. That is why configuration starts from the workflow audit and reproduces existing procedures, even if they are not perfect.
  2. There is no internal ownerWithout someone in the company responsible for the system, every small problem stays unsolved until it becomes a reason to abandon it. Specialist training of an internal administrator is included in the Standard and Extended packages.
  3. The migrated data could not be trustedIf on day one a coordinator finds duplicate clients or wrong amounts, they never open the application again. That is why the sample check is done by you, before the full import.
  4. People did not understand what they gainAn operator who only sees more fields to fill in will resist. Role-based training shows what disappears from their work, not just what appears.
  5. Everything was switched on at onceAll modules active from day one means a cluttered interface and impossible training. We activate what is used now and add the rest when the need arises.
  6. Management did not use the reportsIf the indicators in the system are not the ones decisions are based on, the team immediately understands that real reporting happens elsewhere. Reports are built on what management actually tracks.
Integrations activated during implementation

Integrations configured and tested as part of implementation

Connection is not postponed until after go-live: the integrations actually used are configured and tested on real data before go-live. Each integration runs on your company’s own accounts with the respective providers, and modules not activated transmit no data.

Trendyol integration with Zarina CRMTrendyol
WooCommerce integration with Zarina CRMWooCommerce
Shopify integration with Zarina CRMShopify
PrestaShop integration with Zarina CRMPrestaShop
GLS integration with Zarina CRMGLS
DPD integration with Zarina CRMDPD
Stripe integration with Zarina CRMStripe
PayPal integration with Zarina CRMPayPal
WhatsApp integration with Zarina CRMWhatsApp
Messenger integration with Zarina CRMMessenger
Instagram integration with Zarina CRMInstagram
Facebook Lead Ads integration with Zarina CRMFacebook Lead Ads
Zadarma integration with Zarina CRMZadarma
3CX integration with Zarina CRM3CX
Brevo integration with Zarina CRMBrevo
Google Calendar integration with Zarina CRMGoogle Calendar
Outlook Calendar integration with Zarina CRMOutlook Calendar
Google Sheets integration with Zarina CRMGoogle Sheets
Google Forms integration with Zarina CRMGoogle Forms
Google Ads integration with Zarina CRMGoogle Ads
Zoom integration with Zarina CRMZoom
Google Meet integration with Zarina CRMGoogle Meet
Zapier integration with Zarina CRMZapier
Make integration with Zarina CRMMake
Claude integration with Zarina CRMClaude
ChatGPT integration with Zarina CRMChatGPT
Gemini integration with Zarina CRMGemini
What it costs

What implementation includes and what is contracted separately

The breakdown below removes any confusion on the invoice. Configurations and module packages are on the pricing page.

Included: installation

Go-live on your infrastructure, with technical requirements checked beforehand. Details on hosting options on the CRM on your own server page.

Included: configuration around your workflows

Roles, permissions, pipeline stages, custom fields, document templates and the automations agreed at the audit.

Included: data migration

Transfer of clients, contracts and history from your current systems, with a sample check and reconciliation of totals.

Included: role-based training

Separate sessions for operators, coordinators and management, plus specialist training of the internal administrator with the Standard and Extended packages.

Separate: new developments

A module that does not exist, a special report or an integration with your own system is estimated and contracted separately.

Separate: maintenance

Optional, with a response time set in the contract. The platform works without it, and the six-month warranty applies anyway.

Cost calculator

What it costs you NOT to have Zarina CRM

A monthly per-user subscription never stops: you pay it every month, it grows with every new employee and, at the end, you are left with nothing. The lifetime licence is paid once. Move the two sliders to your team’s real size and see the difference over 36 months.

If you pay a flat subscription, divide the monthly amount by the number of users. If you do not use a system yet, leave the default values: they are typical cloud platform rates.

Monthly subscription, 36 months —
Zarina CRM lifetime licence $3,480

What you lose over three years with the subscription

—

—

The calculation covers the licence only, not hosting. The licence price does not change when you add users. At the end, the licence remains an asset of the company.

Request a quote Packages and pricing

After go-live

Warranty and assistance after go-live

Implementation does not end on the go-live date. The first six months concentrate real-use situations, a period fully covered by the technical warranty.

Six-month technical warranty

Bugs and inconsistencies appearing in real use are fixed at no extra cost, whether or not you have a maintenance contract.

What the warranty does not cover

New modules, additional automations and developments requested later. These are estimated separately, so it is clear from the start.

The first days, with us available

At go-live we remain available for the questions that come up in the first days of real work, not only through tickets.

Expansion comes when you ask for it

A new module package is activated on the existing installation with a licence key, without reinstalling and without losing data.

You do not stay dependent on us

The trained internal administrator can change roles, fields and templates without asking us for anything. That is the stated purpose of the training.

The source code stays with you

You receive the code of the installed application. If you continue with your in-house team or another provider, the system keeps working.

Fit

How to choose the implementation package

The level of assistance needed differs by organisation. The criteria also include the situations where an extended package is not justified.

The Kickstart package is enough

A small team, clear processes, no complicated templates and no large history to migrate. There is no point paying for resources you will not use.

The Standard package is the right choice

You have an internal person who can take over administration and you do not want to depend on us for every later change.

The Extended package is justified

You are moving your entire activity into the platform, with invoicing, inventory, projects and reports on management’s indicators, across several departments.

No decision-maker available in the organisation

If nobody in the company can make time for the workflow audit and the organisational decisions, implementation stalls, whatever the package.

Fully internal administration

If the intention is to buy the licence and administer it entirely in-house, just tell us: we will not build a services package that does not match the real need.

A one-day go-live deadline

Analysis, migration and training take time. A same-day start is only possible without migration and without customisation, and we say so in advance.

What clients say

References: companies that have been through the implementation process

Reviews from clients in different fields — manufacturing, construction, real estate, services, trade, hospitality and healthcare — who run Zarina CRM on their own infrastructure. The texts are the ones they sent us, translated from Romanian.

I warmly recommend Zarina CRM Construction. Automations, reporting and the integration of artificial intelligence into our process help us every day, easing repetitive work and increasing our office’s productivity.

Paul Ciprian RusuSite supervisor and technical managerElectrical installations

We are satisfied with our work with Zarina CRM, both for our company’s web marketing and for the automation integration.

Ciprian StruluciucManaging directorMetod Sistem, Iași

We are fully satisfied with the whole of our collaboration with your company, which has lasted 14 years, both for our online presence and for the automations and integrations that make business life easier.

Catalin-Stiglet InsurateluSite supervisorSICC Project Services, Iași

Our tyre hotel service is integrated with the inventory catalogue. Automatic reminders help us call customers proactively at the change of season, fully optimising the workshop schedule.

Cristian ColotinFounderMoldo Garage SRL · automotive and service

Allocating projects to translators is now fully traceable. Requests from the website become leads instantly, PDF quotations are tracked when opened, and clients receive automatic communication.

Ciobanu LaurențiuGeneral ManagerAxa Traduceri Iași SRL · professional services

Zarina CRM organised our medical conference management workflows down to the last detail. We centralise thousands of attendees, corporate partners and sponsors in a clean pipeline, monitoring payments and granting access automatically.

Sorana AmuntenceiProject coordinatorHighLife Events SRL · events

Birthday bookings and group appointments are organised asynchronously right on the calendar. Automatic push sync sends the data to operators’ phones in real time, eliminating double bookings.

Ciprian PopaFounderZuzu Land · education and events

Automation, centralising all our data and integrating artificial intelligence into our caviar trading process, both in Europe and in Asia (Dubai, Abu Dhabi and even Saudi Arabia), have helped us enormously. Thank you for your commitment and constant support.

Andrei IekelLe Roi du Caviar

Integrating CRM software into our sales automation was the best investment. Operations that often took us hours now take two clicks, and we spend the time saved on the processes that really matter. We have saved time and staff. I recommend it.

Prof. Dr Laura Gheucă-SolovăstruSenior consultant dermatologistDermaPharmaShop.ro and DermaArt.ro

In our premium butcher’s shop in Belgium, traceability of special one-off orders from restaurants is essential. Inventory management gives us complete clarity over daily deliveries.

Stefan StreinuFounder and Master ButcherMeat Me Up · Belgium

Leads from marketing campaigns are captured instantly in the CRM through webhooks. We issue financial proposals, check stock in real time and control the team’s profit margins from the office.

Paul Ciprian RusuGeneral ManagerMagnum Heating SRL · distribution

Managing corporate business guests demands close attention to detail. The platform gives us secure local storage of guest profiles and automated reviews, raising loyalty to luxury standards.

Andrei AdomnicaiGeneral ManagerHotel Palas Grand View

Email tracking notifies us through WhatsApp-style interface alerts when partner companies open our quotations. This gives the team the perfect moment to make the follow-up call.

Adomnicai AntoneiGeneral ManagerGrey Boutique Hotel Palas

The unified ticketing and support system streamlined booking confirmations. We have solid cash-flow trend reports and monitor staff schedules without paying recurring per-user fees.

Borgovan MarianCEOBucovina Resort SRL

For a dermatology clinic, the confidentiality of patient records is an absolute priority. The fact that the system runs locally gives us iron-clad protection. Managing the doctors’ appointments works flawlessly every day.

Prof. Dr Laura Gheucă-SolovăstruSenior consultant dermatologistClinica Lauderma (Romania)
CRM implementations

Companies that have trusted Zarina CRM

Le Roi du Caviar - Zarina CRM clientLe Roi du Caviar
DermaPharmaShop - Zarina CRM clientDermaPharmaShop
SICC Project Services - Zarina CRM clientSICC Project Services
Metod Sistem - Zarina CRM clientMetod Sistem
Lapis Residence - Zarina CRM clientLapis Residence
Onyx Residence - Zarina CRM clientOnyx Residence
Iași Clinical Hospital of Pulmonology - Zarina CRM clientIași Clinical Hospital of Pulmonology
Regional Office for Cross-Border Cooperation Iași - Zarina CRM clientRegional Office for Cross-Border Cooperation
Arpa Imobiliare - Zarina CRM clientArpa Imobiliare
Rubin Capital - Zarina CRM clientRubin Capital
Hotel Palas Grand View - Zarina CRM clientHotel Palas Grand View
Grey Boutique Hotel Palas - Zarina CRM clientGrey Boutique Hotel Palas
Bucovina Resort and Spa - Zarina CRM clientBucovina Resort & Spa
HighLife Events - Zarina CRM clientHighLife Events
PavMar Beton - Zarina CRM clientPavMar Beton
Clinica Lauderma - Zarina CRM clientClinica Lauderma
Axa Traduceri Iași - Zarina CRM clientAxa Traduceri
AFQ Accounting - Zarina CRM clientAFQ Accounting
Moldo Garage - Zarina CRM clientMoldo Garage
Zuzu Land - Zarina CRM clientZuzu Land
Ziarul Unirea - Zarina CRM clientZiarul Unirea
Meat Me Up Belgium - Zarina CRM clientMeat Me Up Belgium
Joues et Croquettes Belgium - Zarina CRM clientJoues et Croquettes Belgium
Frequently asked questions

Questions about implementing a CRM

Do I need technical knowledge or an in-house IT department?

Not to use it. For the server side you need an administrator, in-house or outsourced, or the option with hosting provided through our partner. We configure the application during implementation, and with the Standard and Extended packages we train a person from your company to change it on their own afterwards.

How long does the actual implementation of the software take?

With a standard configuration, 48 hours. With customisation to internal workflows — your own document templates, automations, approval flows — up to 14 working days. What extends the timeline is almost always the response time on organisational decisions, not the technical side.

Is implementation paid for separately from the licence?

No. Installation, configuration around your workflows, data migration and role-based training are included in the price, in every configuration. Only new developments and, optionally, maintenance are contracted separately.

What happens if the business grows and we want new modules later?

A module package is activated on the existing installation with a licence key, without reinstalling and without losing data already entered. The new module is configured when it is activated.

Do you provide technical support after implementation is complete?

Yes, in two forms. The six-month technical warranty covers bugs and inconsistencies appearing in real use and applies anyway. Separately, you can sign a maintenance contract with a set response time, but the platform works without it.

What data can be migrated from the current system?

Clients, contacts, opportunities, quotations, invoices, attached documents and interaction history, to the extent the previous vendor exports them. From the start we check what the source can and cannot export and tell you in advance if something cannot be moved.

How do we make sure the migrated data is correct?

We first import a sample agreed together, which you check on records you know. After the full import we compare totals with the source — number of clients, pipeline value, attached documents — and explain every difference.

Can we work in parallel with the old system for a while?

Yes, and we recommend it wherever there is a previous system. The old way of working stops once the new system produces the same figures, not before.

What should we prepare before the first meeting?

The person who knows how the company works, a chart of departments and approvals, the files with your current data in whatever form they exist, one copy of each document that leaves the company, the reports tracked monthly and technical access to the server or your administrator’s contact.

Do we stay dependent on you for changes?

No, and that is the stated purpose of the training. The trained internal administrator can create roles, custom fields, stages and templates without asking us for anything. You also receive the source code of the installation, so the system can be taken over by your in-house team or another provider.

Next steps

Decisions related to implementing a CRM

Implementation is the process. The platform configuration and the installation model are separate decisions, covered on the following pages.

Installation on your own server

Hosting options, server requirements, data protection and the split of security responsibilities. CRM on your own server

Development to your own requirements

When a workflow does not fit any standard configuration and needs a new module. Custom CRM

Industry configurations

Specific modules for real estate, medical, construction, services, retail or hospitality. Industries

Pricing and packages

The core, the thirteen module packages and the price configurator. Zarina CRM pricing

Product sheet

Get the complete product sheet by email

A six-page document with everything you need to know before a sales conversation. No obligation and no sales call.

  • The platform core and the 13 module packages, with what each one contains
  • The features and modules of the edition you choose, plus available integrations
  • Full pricing and what it includes: installation, training, data import, warranty
  • The native integrations available and the situations where the platform is not a good fit

No monthly subscription

Take control of your operations, once

We install Zarina CRM on your hosting, configure it around your own workflow and train your team. From that moment on, the application is an asset of your company, not a recurring expense.