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

CRM for Uskudar businesses

How many people fit into a session is settled where three things meet: who is teaching the hour, what equipment the room holds, and which slot of the day it falls in. Burhaniye and Bulgurlu in Uskudar carry studios and rehabilitation practices on their upper floors. When all three shift through the day, a calendar carrying a fixed headcount fills the wrong hour. At Pilatesco capacity is worked out from the three together.

Get a quote Tell us about your project

CRM — Uskudar

Health, education and appointment-led service businesses dominate the institutional fabric of Uskudar. When a service is tied to a room, a person and an hour at once, capacity stops being one number. The work closest to how this district operates is Pilatesco. We will write down where it stops: it was built for a single sports and fitness business, and a clinic's patient record, a school's student file or shared capacity across several branches of one brand are not work we can show. What carries across is where capacity is computed from. A one-to-one session and a group class open under their own rules while sharing one calendar. Laravel runs the workflow and MySQL holds the records.

  • How many places an hour holds is settled by the instructor, the equipment and the hour together, so changing any one of the three changes that slot's capacity.
  • A one-to-one session and a group class open under their own rules, and because both sit on one calendar the same equipment is never committed twice.
  • We state the limit: Pilatesco was built for a single business, and shared capacity across several branches of one brand is not something we can show.

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 — capacity settled by instructor, equipment and hour together

How many people can take a class in one slot is not a fixed number; the instructor, the equipment and the hour are computed together. So the same hour opens with different capacity on different days, and a one-to-one session and a group class open under rules of their own. Both sit on one calendar, so equipment is never committed twice. A package is bought on the customer side: a reservation draws one class off the balance, a cancellation and a no-show land on it differently, and which case returns the credit is in the rule. Laravel and MySQL carry it. Scope is one business.

Read the case study →

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

  • Would you not need to visit the studio and watch how it runs?

    Nobody visits; we work remotely. Instead we write down together what decides how many places an hour holds: the instructor, the equipment and the hour. Building starts once those three are settled.

  • Why does the same hour open with a different number of places?

    Because capacity is not one number. The instructor taking the hour, the equipment set in the room and the slot itself are computed together, so changing any one of the three changes what that slot holds.

  • Can we keep one-to-one sessions and group classes on the same calendar?

    Yes. They share the calendar but open under their own rules, and because equipment is never committed to two jobs at once, a group class and a private session cannot claim the same set.

  • We run several locations. Would capacity work across all of them?

    That is not something we can show. Pilatesco was built for one business, shared capacity across locations was never tried there, and we will not say otherwise.

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