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

Process Tracking · Bakirkoy

Process Tracking for Bakirkoy businesses

In a business that runs on appointments, the process lasts longer than the hour on the calendar. In a studio, clinic or service point around Atakoy in Bakirkoy the wall is a familiar one: how long an appointment takes, what it attaches to and what may follow it get baked into the software as a sector assumption. Change the rule and the code changes. Process tracking software for Bakirkoy, Istanbul is where we are building the opposite right now.

Get a quote Tell us about your project

Process Tracking — Bakirkoy

Bakirkoy's texture is the western retail line and a concentration of private health providers. If work arrives by appointment, one business ends up planning people, rooms and equipment in the same day. We have no finished product to demonstrate on this page, so we describe the one we are working on as it stands. AlgoRandevu is being built now; we do not present it as a finished system and there is no version to install today. We are putting it on the same ground as our own panels: whichever Laravel and Inertia setup AlgoKlima and AlgoCar run on, AlgoRandevu sits there too. Appointment records go to MySQL, the cache to Redis, the panel interface to Tailwind. We have nothing to show at hospital or clinic-chain scale.

  • Rather than burying appointment length and the gap between consecutive slots in a sector assumption, we are leaving them as product settings, so that a changed rule need not change the code.
  • In the structure we are working on, an appointment can attach to a person, a room or a piece of equipment; the business picks the resource and we ship no separate build per sector.
  • The ground is not new: the same Laravel and Inertia setup sits under AlgoKlima and AlgoCar, which keeps the panel logic familiar for a business already using one of them.

Why Algoriel

  • Keeps working offline

    The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.

  • Entry from QR and location

    Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.

  • Records land the same hour

    Jobs close in the field, so the office sees where each one stands without waiting for end of day.

  • Office and field read one source

    The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What we build

Process Tracking

  • What the record attaches to

    Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.

  • The entry that stays open

    Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.

  • Who was where, on the record

    Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.

  • What is left when the figure is disputed

    Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.

  • Records taken beyond coverage

    In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.

  • Process rules kept out of the code

    Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

AlgoRandevu — a product under construction on the AlgoKlima and AlgoCar ground

Our own product, currently in development: not a delivered job but a structure we are still working on. Instead of burying an appointment's length, what it attaches to and how slots follow one another in a sector assumption, we are leaving all three definable inside the product, with the aim that a changed rule need not change the code. In the structure under development an appointment can attach to a person, a room or equipment, and the business picks the resource. We are building it on the same Laravel and Inertia ground as AlgoKlima and AlgoCar; records go to MySQL, Redis carries the cache, Tailwind shapes the panel.

Read the case study →

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

  • Could we install AlgoRandevu today?

    No. The product is in development and there is no version to install; we do not present it as a finished system. What we describe is the structure we are working on and the ground it sits on.

  • Our appointment length varies by sector. Does that need a custom build?

    Making that unnecessary is exactly the aim. Length and the gap between consecutive slots are being left as product settings, so a changed rule does not change the code and no separate build appears per sector.

  • What does an appointment attach to — a person or a room?

    In the structure we are working on, all three are possible: a person, a room or a piece of equipment, with the business picking the resource. Because it is still in development we cannot show a running installation today, only describe what is written so far.

  • We already use the AlgoKlima or AlgoCar panel. Will the screen logic change?

    We are building on the same Laravel and Inertia ground, so the panel logic stays familiar. Records go to MySQL, Redis carries the cache and Tailwind shapes the interface — the same setup our other products already run on.

Process Tracking in other cities

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

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service