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

CRM for Bakirkoy businesses

Along the Florya and Yesilyurt stretch in Bakirkoy a studio's day is cut into hours on a calendar. Read that calendar as the single source of truth and the box decides: full means closed, empty means room. How many people that box actually holds is defined in the record, not on the screen. When two people want the same hour at once, the capacity rule decides it rather than whoever refreshed the page first. Pilatesco was built that way — the calendar shows the rule and never sets it.

Get a quote Tell us about your project

CRM — Bakirkoy

At the western end of Bakirkoy, studios, small clinics and service points cut the day into appointments, and how many people an hour opens to is a rule rather than a screen. The closest work we have is Pilatesco. Here is where it stops: the system was written for a pilates studio. We have nothing to show at hospital or clinic-chain scale, and no healthcare client in this district. What travels is where the quota is defined — the rule sits on the record and the calendar reads it. The stack ends in two parts: Laravel runs the workflow, MySQL holds customers, packages and bookings.

  • How many people an hour opens to is defined on the session's own record rather than the box drawn on screen, and the calendar renders that rule instead of producing it.
  • Once the quota is met a booking is not taken into the record at all, so the refusal comes from the rule and not from when somebody last reloaded the page.
  • The package balance is kept on the customer's own record, a right comes off it as the booking is written, and no second ledger is needed.

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

Pilatesco — the quota lives on the session record, the calendar shows it

A booking and membership system for pilates studios. How many people an hour opens to comes from the session's own rule rather than the look of the calendar. Once the quota is met a booking is never taken into the record, so the moment the screen refreshed changes nothing. A customer buys a package; writing a booking takes one right off it, and what remains sits on the customer's record. Cancellation and a no-show land on the balance differently, and which of them returns the right is set in the rule beforehand. Invoicing happens at the sale. Laravel and MySQL carry it.

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

  • Do you keep an office in Bakirkoy, or send anyone to the studio?

    Neither. We work entirely remotely, and the first round of work happens on paper: which rule decides how many people an hour opens to. Package rights, cancellations and no-shows are settled in the same document before anything is built. Nothing in that sequence needs somebody standing in the studio.

  • Two people take the same free hour at the same moment. What happens?

    One booking enters the record and the other does not. Freshness of the screen decides nothing; the rule on the record does. A booking that never entered leaves the package balance untouched, so the person turned away keeps the right they came with.

  • Would an off-the-shelf booking app not cover this?

    If holding hours is all you sell, it does, and we say so rather than quote a build. The line starts where the same hour opens to different numbers under different arrangements, and where the remaining rights have to live on the customer record.

  • We run a small clinic and schedule consultations, not classes. Does the evidence hold?

    The mechanism belongs to where the quota is written, not to pilates. If rooms, equipment or available specialists decide how many people an hour takes, the rule sits in the same place. We also say plainly that we have nothing to show at hospital or chain scale.

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