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

Management Systems · Uskudar

Management Systems for Uskudar businesses

One room used in turns by two practitioners is the constraint an appointment book cannot see. On the consulting-room and tuition floors between Uskudar's Ahmediye and Dogancilar the hour is written against a name, while the thing that actually fills up is the room. That is why we are building AlgoRandevu, our own product: what an appointment occupies is not assumed by the software but declared by the business. We show no finished installation and give no delivery date.

Get a quote Tell us about your project

Management Systems — Uskudar

Health, education and advisory institutions sit close together in Uskudar and the work turns largely on institutional records. Where an appointment binds to whatever is scarce rather than to a name, that resource can be a room, a device or a hall. The status of the work closest to this district belongs on the page: AlgoRandevu is our own product and we are building it now, not a delivered job. Where it does not reach is plain. Patient files, treatment plans and institution records are not inside it. In the structure under development an appointment attaches to a person, a room or a piece of equipment. The ground is the Laravel and Inertia setup our AlgoKlima and AlgoCar panels stand on, with MySQL, Redis and Tailwind beneath.

  • The software does not decide in advance what an appointment occupies: the resource can be a person, a room or a piece of equipment, and the business names which from inside the product.
  • Conflicts are read off whatever is genuinely scarce, so one room shared in turns stops producing hours a name-based calendar still shows as free.
  • The state of the product is information too: AlgoRandevu is under construction, we show no finished installation, and what we can show today is how the decision is shaped.

Why Algoriel

  • Capacity and credit stay apart

    Pilatesco keeps class capacity and a member's remaining package credit as two different things, so filling one does not quietly consume the other.

  • The same data is entered once

    In AlgoCar service, stock and accounting read the same record, so nothing gets retyped into a second screen.

  • Reports come off the record

    Invoices and reports derive from the work that was logged, so no separate month-end sheet has to be filled in.

  • Sale and use meet on one record

    At Pilatesco an invoice is raised when a package is sold while use is read from a calendar spread over weeks, and both meet on the member's record.

What we build

Management Systems

  • The rule is written into the record

    What each situation leads to is defined in advance. At Pilatesco a cancellation, a no-show and a completed session each hit the entitlement differently, and nobody decides on the spot.

  • Capacity is more than a single number

    How many people an hour holds is worked out from the instructor, the equipment and the time together. A one-to-one session and a group class open under their own rules.

  • Where the work stands, on one screen

    At AlgoCar a job moves along one record from the moment it opens to the moment it closes. In the dental clinic the manager sees which step of the plan a patient has reached without leaving that screen.

  • One record, seen to the limit of each role

    Vipkurum keeps timetables, classes, exams and payment records in one place, and a teacher, a guardian and an administrator each reach that record at their own permission level.

  • A report is the same record from another angle

    The month-end picture does not require a second set of books; it is the sum of what was recorded during the day.

  • A team that does the maintenance daily

    AlgoCar and AlgoKlima are our own products and both are live. We do the maintenance on software of this kind every day in our own panels, so it is not a promise we make for after handover.

Work like this

Management Systems · Case study

AlgoRandevu — the business names the resource, the software does not assume it

Our own product, under development: a structure we are working on rather than a delivered installation. Most booking tools accept from the outset that an appointment is written against a person, while in many businesses the thing that fills up is a shared room or a single device. So we keep that binding inside the product. What the resource is gets declared there, the business names whatever is scarce on its side, and no separate flow is written per trade. The ground stays identical to our AlgoKlima and AlgoCar panels: Laravel and Inertia, with MySQL holding records, Redis as cache and Tailwind shaping the panel.

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

  • We write appointments against a person, but the single consulting room is what actually fills. How is that handled?

    By changing what the appointment binds to. In the structure under development, selecting the room as the resource means conflicts are read off the room, so two practitioners working in turns cannot both take the same hour. The person is still recorded; it simply stops being the constraint.

  • Can we install AlgoRandevu this quarter?

    No. We are building the product now and we give no delivery date. What we can discuss today is not an installation but a decision: writing down which resource is scarce and what an appointment should bind to. If you want to see finished work, we look at the AlgoKlima and AlgoCar panels instead.

  • Will patient files and treatment plans live in the same product?

    They will not. AlgoRandevu is an appointment product, and patient files, treatment plans and institution records fall outside its scope. That is a separate piece of work, and we say so before anything is agreed.

  • Our institutional records sit across two buildings in Uskudar. Would you come and see them?

    We work with no office at all, and never on site. Rather than watching a floor, we answer one question together: when an appointment is written, which resource counts as taken. Once that is settled, the rest of the calendar follows from it.

Management Systems in other cities

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

Other services for this location

Which rule in your business still depends on somebody remembering it?

Get a quote or open the service