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 · Fatih

CRM for Fatih businesses

An enquiry at a hardware counter seldom arrives as a product name: the buyer names a family, then a size class, then whether they will take it new or used. Rüstempaşa's wholesale halls and the hardware counters of Fatih are that kind of trade. An off-the-shelf CRM offers one product dropdown for all three, so those distinctions end up in a notes box and stop being searchable the moment they are typed. Plastik ve Makina settles the same question inside the catalogue: the tree is built from one machine family's own divisions rather than a broad industrial heading.

Get a quote Tell us about your project

CRM — Fatih

Fatih's trade fabric is wholesale food and hardware, around Rüstempaşa and the counters near Beyazıt. In that trade the line count is long and the differences fine: one screw length is a row, one packaging size another. On the hospitality side an enquiry splits between rooms and service items instead. The work closest to this district's sector profile is Plastik ve Makina. Where it does not overlap: it is a listings platform, so a customer card, a quote history or collections tracking is not work we can point to. What carries across is the shape of the record: the trade's own division becomes the main axis, and condition is a filter on one list rather than a second catalogue. Laravel runs it, MySQL holds the records, Redis the cache, Inertia the interface, Tailwind the list and detail screens.

  • An enquiry is filed against a tree built from the trade's own divisions rather than a product dropdown, so what sits as a sub-heading elsewhere becomes the main axis here.
  • Condition does not open a second catalogue: new and used stand in one list, and a buyer compares them inside a single search.
  • The list is prepared on the server and carried to the browser, so a changed filter refreshes results in place rather than reloading the page.

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

Plastik ve Makina — a tree built from one machine family, condition as a filter

A sector listings platform for people buying and selling plastic processing machines. The whole category tree is built from the divisions of a single machine family, so a distinction that would sit as a sub-heading on a general listings site becomes the main axis here and a buyer searches in the language of the trade. New and second-hand listings never split into two catalogues: both stand in one list and condition opens as a filter. Laravel prepares the list on the server and Inertia carries it to the browser, so a changed filter refreshes results without a page reload. MySQL holds the listing records and Redis carries the cache.

Read the case study →

Working with Fatih 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

  • Our line count is high. Why would an off-the-shelf CRM not cover it?

    If it covers the work it covers the work, and we will say so rather than quote a build. The line falls where the buyer asks by distinction — family, size, condition — because those distinctions land in a notes field and stop being searchable. On Plastik ve Makina they became the axis the catalogue is built on.

  • We keep new and second-hand stock as two separate lists. Is that not tidier?

    Two lists make the buyer search twice, and the same item then needs upkeep in two places. On Plastik ve Makina condition is not a catalogue but a filter across one list, so the comparison stays inside a single search.

  • Do you have an office in Fatih? Would somebody come and see the counter?

    There is no office and nobody drives out; we work fully remotely. The first thing we hand over is written rather than built: which distinction becomes a node in the tree and which becomes a filter.

  • We run a guesthouse alongside the shop. Does the same idea hold there?

    The mechanism belongs to where a distinction is written, not to machinery, so a room type or a service item can be a node in exactly the same way. The honest limit sits elsewhere: a booking ledger or channel management is not work we can show.

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