Get a quote

Management Systems · Izmir

Management Systems for Izmir businesses

When a manufacturer chooses software the question is often not about this month but about the third year: who maintains this, what happens when the team changes. Along the Torbali and Isikkent line a firm working toward export orders sells the machine and then services what it sold, so both kinds of booking sit in the same week. We are building AlgoRandevu now, and there is no version to install today. What we can state is where it sits: on the Laravel and Inertia base that already carries AlgoKlima and AlgoCar.

Management Systems — Izmir

Production and retail here work toward export orders, and buyer visits, a sample room and after-sales service line up inside the same week. In a firm like that the lifespan of the software can matter as much as its feature list. The closest thing we have to that expectation is not finished work: AlgoRandevu is our own product and it is under construction. Be clear about where it does not reach — nothing is installable today, and we have no work to show for export paperwork, customs procedures or production planning. What we can speak to is the base. We pick one stack that can be maintained for years rather than a fresh one per project: Laravel runs it, MySQL keeps the records, Redis takes the cache, and Inertia with Tailwind sit at the interface.

  • AlgoRandevu is going up on the base that already carries our own panels, so all three products stay in one maintenance routine and an infrastructure update is not three separate jobs.
  • Booking records go into MySQL, Redis takes the read load, and Tailwind shapes the panel interface — the same setup AlgoKlima and AlgoCar run on.
  • What we can offer today is a scope with its limits written down rather than a product: AlgoRandevu is not presented as finished and has no installable release.

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

AlgoRandevu — the product we are building, on the base under AlgoKlima and AlgoCar

Our own booking product, currently under construction. Not a finished system: there is no release to install today. We are building it on the same Laravel and Inertia base that carries AlgoKlima and AlgoCar: booking records live in MySQL, Redis takes the caching layer, Tailwind shapes the panel interface. That choice is about upkeep over years rather than style, and a business already using a panel from the same family finds the screen logic familiar. Instead of burying the length of a booking and the gap between consecutive ones in the sector, we are leaving them as product settings, so a changed rule need not mean changed code.

Read the case study →

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

  • Is there a release we can install today?

    No. AlgoRandevu is under construction and we say so as it is. The products running today are AlgoKlima and AlgoCar, both our own, both maintained by us. AlgoRandevu is growing on the same base.

  • We already use one panel. Does a second product mean learning everything again?

    Because it sits on the same base, the screen logic stays familiar: menus, lists and form behaviour work the way they do in AlgoKlima and AlgoCar. What has to be learned is the subject of the new product, not the interface around it.

  • Would this system carry our export documentation?

    It would not. We have no work to show for export paperwork, customs procedures or production planning, and we do not promise a capability we cannot demonstrate. What we describe is the management of a booking and the record attached to it.

  • Do you have anyone based in Izmir?

    No. We work entirely remotely and every client we have is in Türkiye. Working with a business in Izmir looks the same as everything else in the portfolio: the scope goes on paper first, and development starts after that.

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