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

Management Systems for Sisli businesses

A studio or an aesthetic clinic in Sisli keeps two counts running at once. One is how many places are left in tonight's session. The other is how many classes a member still holds from a package bought weeks earlier. The work closest to how businesses here operate is Pilatesco, a booking system for Pilates studios. Capacity there belongs to the session record, the remaining credit to the membership record. They move together, yet neither is derived from the other.

Get a quote Tell us about your project

Management Systems — Sisli

Sisli's Nisantasi–Mecidiyekoy line is dense with businesses that sell time in sessions: studios, aesthetic clinics, small teams working by appointment. Money arrives once, as a package, and the service it pays for spreads across weeks of calendar. Demand does not spread evenly either: evenings pile into the same slot, and that slot is only a few places deep. So two numbers describing different things start to look like one. A full hour is a limit the business owns; a remaining credit is something the member is owed. Pilatesco keeps them in separate tables for exactly that reason, and a reservation moves both in the same instant. The system runs on Laravel and MySQL.

  • One reservation record lowers two counts at once: places left in the session, credits left on the membership. Nobody reconstructs a balance by reading back through the calendar.
  • A full session refuses the write, and a reservation that never entered the records cannot draw a credit. A member turned away from a busy hour keeps everything they had.
  • Undoing a reservation opens the place again; returning the credit is a separate movement with its own condition. Money already collected reads from the invoice record, service still owed from the membership.

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

Pilatesco — capacity on the session record, package credit on the membership

A booking and membership system for Pilates studios, where selling a package opens a credit balance under the membership. Writing a reservation is one event that moves two records: places left in the session, credits left on the membership. No second count is kept. A full session refuses the write, so the balance stays untouched. Member records, reservations, programme steps, invoicing and reporting stay separate processes; the month-end view reads those same records from another angle. Laravel and MySQL.

Read the case study →

Working with Sisli 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 sell packages, but nobody can say for certain how many classes a member has left.

    The count lives in one place, the membership record, and it falls as the reservation is written. An answer is read off that record, not worked out again from the calendar.

  • We turned a member away from a full hour. Did they lose a class?

    No. Nothing was written, so nothing was drawn. The credit stays on the membership until a reservation actually lands, and a busy evening never quietly empties a package.

  • Would an off-the-shelf booking app do the job for us?

    If a calendar and a member list cover the work, use one — we say so plainly. The threshold sits elsewhere: when the remaining credit, the programme step and the invoice all have to live on the same record, a generic app stops keeping up. We are building AlgoRandevu, our own booking product, right now.

  • Our studio is in Sisli, off Tesvikiye. How do you work — are you nearby?

    We keep no office, and site visits are not part of the service. The first deliverable is written, not code: what a reservation, an undo and a no-show each do to which record. Development follows that.

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