Get a quote

Management Systems · Istanbul

Management Systems for Istanbul businesses

A course of dental treatment is decided in one sitting and delivered across many. What sets the gap between sessions is healing, not an opening in the diary. In Istanbul the crossing itself costs an hour, so a session missed on Tuesday pushes everything behind it. If an appointment is a record that stands alone, someone rebuilds that order by hand. In the CRM we wrote for a dental clinic, an appointment carries a named step of the plan, so moving the step moves the calendar with it.

Management Systems — Istanbul

Plenty of businesses in Istanbul sell time in steps: clinics, dental practices, studios, small rooms that divide the day into sessions. The complaint is rarely a full diary. It is that the hour on screen says nothing about where the commitment stands. The work closest to that shape was written for a single dental clinic, and we state the scale plainly. Say where it does not reach, too: a hospital information system, consolidation across a chain of clinics, laboratory workflow and insurance authorisation are outside what we can show. What carries over is not the screens but what an appointment is attached to. Laravel runs the process; MySQL holds patient, plan and invoice records in one schema. We keep the same technical foundation from one project to the next.

  • Every appointment carries one named step of the plan, so adding a session or reordering the course rearranges the calendar instead of leaving stray hours behind.
  • The invoice keeps no ledger of its own. Because the procedure already sits on the patient record, what was billed and what was applied are read from the same place.
  • Reporting draws on that same record from another angle, so a manager can see where a patient stands in the plan without opening a second table.

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.

  • 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

Dental clinic CRM — move a step of the plan and the calendar moves with it

A CRM written for a single dental clinic. The treatment plan is set per tooth and split into sessions that spread over weeks, and it stands as a record in its own right, independent of any appointment. The appointment then says when a particular step of that plan happens. Change the step, or slot an extra session in, and the calendar follows; no appointment is left pointing at nothing. Billing keeps no separate ledger, because the procedure already sits on the patient record. Reports read those same records from another angle. Laravel runs the process, MySQL holds patient, plan and invoice records.

Read the case study →

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

  • Our booking calendar works. What does management software add?

    A calendar holds the hour. It does not hold what the hour was promised for. The threshold is this: if the work spreads over weeks and the order of steps matters, the calendar needs a plan record to read from. If the job finishes in one visit, a calendar is enough and we say so.

  • A patient does not show up. What happens to the appointments behind that one?

    The step counts as not done and stays where it is on the plan. The appointments that follow are attached to that step, so they shift together. Nobody walks the calendar hour by hour to rebuild the sequence.

  • We run two sites on opposite sides of Istanbul. Can one system cover both?

    We have nothing to show at that scale; this CRM was built for one clinic. Where a boundary between institutions was needed we drew it at domain level in Vipkurum, but that platform was written for education institutions. Which part actually carries over is something we write down during scoping.

  • Would you not need to come and watch how the clinic runs?

    We keep no office and the work runs entirely remotely. We start with records rather than screens: what the plan holds, which step an appointment points at, which procedure the invoice reads. Development is built on that definition.

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