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

CRM for Esenyurt businesses

In a small business trading from several addresses, the balance can easily live somewhere else. Movements sit in one place, and the sheet showing who is still owed what sits in another. Once those two drift apart, no argument is settled by looking at the sheet. Between Saadetdere and Yesilkent in Esenyurt, on branch and course floors, the same month-end question waits: which record counts? The construction workforce attendance system never opened that second sheet: entitlement is produced from matched entry and exit records themselves.

Get a quote Tell us about your project

CRM — Esenyurt

Esenyurt's business fabric is small-scale and branch-spread, private courses among them. When movements land in one system and the arithmetic in another, the two get reconciled by hand each month. The closest work to that profile is the construction workforce attendance system we built. What it does not cover belongs up front: written for building sites, it holds no sales funnel, no quote tracking and no customer history; warehousing and haulage are nothing we can show. What travels is where the arithmetic comes from — a closed pair of records yields both span and entitlement, with no second sheet beside it. The field app runs on the worker's phone in React Native (Expo); Laravel receives records, MySQL keeps them.

  • Entitlement rides on closed record pairs rather than a sheet kept alongside them, so a disputed figure is argued out against the same record everyone else reads.
  • An entry whose exit was never scanned stays an unclosed record, which stops a missing line dissolving quietly into the total.
  • The system runs on the worker's own phone, so no fixed reader is bought and nothing is left installed once the job ends.

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

Construction workforce attendance — entitlement calculated from a closed record pair

A building site is temporary and nobody passes a fixed gate, so entry and exit are captured by a QR scan on the worker's phone with a location check. What this page rests on is where the arithmetic comes from: entitlement is not held in a sheet kept alongside, it rides on matched entry and exit pairs. The span comes from the two ends of the pair, and an entry whose exit was never scanned stays open as an unclosed record instead of dissolving into a total. The field app runs in React Native (Expo); Laravel receives the scans and MySQL holds them. Boundary: written for building sites, with no customer history or quote tracking.

Read the case study →

Working with Esenyurt 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 run branches of a course business, not a building site. What does this tell us?

    The shared part is where the arithmetic comes from. On the attendance system entitlement is not kept in a second table; it is produced from closed record pairs. A branch business faces the same question: does the balance come out of the records, or out of a file kept next to them?

  • What is actually wrong with keeping entitlement in a separate sheet?

    Once there are two sources, one of them being right is not enough. If they disagree at month end, nobody can show which one drifted. When the arithmetic rides on the record, the argument finishes in one place.

  • Would you build for our warehouse and dispatch side?

    There is no warehousing, dispatch or haulage work in our portfolio, and we do not promise on evidence we lack. What we can describe is the shape of the record: who, when, and in which pair.

  • Could customer history and quote tracking live in the same structure?

    Those records are not in this project and we say so. They can be written, but the work we can point at sits elsewhere: the CRM we built for a dental clinic on the plan and booking side, and AlgoKlima on device service history.

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