EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

CRM · Izmir

CRM for Izmir businesses

Izmir's manufacturing runs along the Cigli and Menemen line. When a price is read off a separate file, the list sits in a folder, somebody remembers which version is current, and the figure that reaches a customer record depends on that memory. On the KGM SsangYong online sales channel we cut the dependency out. The amount is not pulled from a list. It sits on the record of the trim and colour combination chosen, and so does the reason a buyer was quoted it.

Get a quote Tell us about your project

CRM — Izmir

Production and retail around Izmir both point at export, and the same product leaves the floor with different equipment and different terms. A quote follows those differences, which changes what a customer history has to hold: not a call note, but which configuration went to that buyer and on what terms. The closest work in our portfolio is the KGM SsangYong online sales channel. Where it stops should be written too. The channel was built for vehicle sales, and export paperwork, customs and dealer network management are not things we can show. What carries over is where a price is written. Laravel, MySQL records and a Redis cache sit underneath, with Tailwind and jQuery on the interface.

  • The price is not kept in a file at the side; it sits on the record of the trim and colour chosen, so nobody has to ask which version of a list is current.
  • Why a buyer was quoted that figure stays inside the record: which combination was priced, and under which sales terms, still reads months later.
  • What moves to the purchase step is the settled combination record rather than the number on screen, so the same amount is never worked out twice.

Why Algoriel

  • Booking, plan and invoice kept apart

    The dental CRM holds a treatment plan per tooth; an appointment attaches to a plan step, so moving the plan moves the calendar.

  • Request types split up front

    At Diotek a site survey and a service call are two separate flows and never share a form.

  • No second document

    Tahlil.com takes the values in and writes the specialist's reading onto the same record, so the result stays in one place.

  • History belongs to the equipment

    AlgoKlima keeps service history under the unit rather than the customer, so it travels with the unit when it changes hands.

What we build

CRM

  • A service plan that moves step by step

    A treatment or maintenance programme that runs over several sessions is kept as its own plan, separate from the bookings. In the dental clinic CRM the plan is built tooth by tooth and split into sessions spread over weeks.

  • Appointments tied to the plan

    Each appointment is attached to a step in the plan. When the plan changes or a session is added in between, the calendar updates with it.

  • Package and membership balances

    When you sell classes or services in packages, what a customer has left shows on their card. At Pilatesco a booking takes one class off the package, and cancellations and no-shows follow different rules.

  • Service history per device

    Warranty, maintenance and fault history for the equipment you service is kept against the device, not the person. At AlgoKlima three air conditioners at the same address keep three separate files.

  • History that survives a change of owner

    When a device passes to someone else, its history stays with the device instead of being retyped onto the new customer's card.

  • The work done and the invoice in one place

    The procedure sits on the customer's record, so what was billed and what was carried out are read from the same place and nothing is entered twice.

Work like this

CRM · Case study

KGM SsangYong online store — price held on the combination, not a list

A visitor configures a model through trim and colour, and the amount comes out of that configuration rather than a price file kept to one side. Every combination is recorded with its own price, its own image and its own sales terms, and that record is what moves to the purchase step. So the configuration a given figure came from is still readable afterwards. The sales channel runs on the same Laravel, MySQL and Redis set as the brand's corporate site. The scope is the sales channel itself; dealer networks and after-sales follow-up sit outside it.

Read the case study →

Working with Izmir teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • We sell into export markets, and terms differ by market. Does that fit the record?

    It does: the sales condition belongs to the combination's own record rather than a separate rules table. The limit is worth naming too — export paperwork, customs and freight are outside anything we can show. What we describe is where the price comes from.

  • Our price list lives in a spreadsheet. Would importing it into a CRM be enough?

    Importing does not solve how fresh the copy is. While the list sits apart, somebody has to maintain it, and on the day nobody does, the sales side quotes last quarter. When the price comes from the recorded choice, there is no second place left to update.

  • Do you have an office or a regional contact in Izmir?

    Neither. We work entirely remotely. Work starts in writing, mapping which choice writes a price onto which record.

  • The evidence comes from automotive and we build machinery. What actually transfers?

    Not vehicles, but how an optioned sale is recorded. Swap trim and colour for capacity and body type and the rule holds: every sellable combination carries its own price and its own terms. For machinery we have separate work to show, and there the subject is catalogue distinctions.

CRM in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Want to bring your customer tracking into one system?

Get a quote or open the service