Get a quote

Management Systems · Besiktas

Management Systems for Besiktas businesses

When an asset moves from one unit to another, its history usually stops at the door. The maintenance file sits in the folder of whoever was using it, and the unit taking it over begins again from nothing. In Besiktas the head-office buildings between Ortakoy and Ulus show the plainest version of this: the pool cars in the basement. AlgoCar was built around the vehicle for exactly that reason: service and repair records hang off the plate and chassis, so a vehicle that changes hands takes its history along.

Management Systems — Besiktas

Besiktas is dense with head-office floors and multi-brand groups. Where decisions are made centrally while equipment circulates between brands, whoever keeps the record changes at every handover. The work closest to that texture is AlgoCar, our own product, whose upkeep we carry rather than hand over. Where it does not overlap is easy to state: it was written for a vehicle workshop, so fleet management and tracking hardware fall outside it, and we hold no client on the agency or media side of this district. What travels is what the record attaches to — the asset's own identity, not the card of whoever used it. Laravel runs it, with Inertia and Tailwind on the interface and React Native (Expo) in the field; MySQL keeps the records and Redis the cache.

  • The chain stays on one record: an order opens, the part spent is written under it, and the invoice is raised from the same place.
  • Stock movement follows from writing the part to the order rather than from a separate warehouse screen, so a second entry step never appears.
  • The maintenance record belongs to the asset's own identity, so a change of user copies nothing onto a new card and the history moves with the record.

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

AlgoCar — service history on the plate and chassis, travelling with the vehicle

Our own service management system, built around the vehicle in the workshop; a product we keep running, not a handover. The chain stays on one record: an order opens, the part spent is written under it, stock falls at that moment, and the invoice is raised from the same place. Service records hang off the vehicle's identity: plate and chassis. A vehicle that changes hands carries its history along rather than having it retyped onto a new card. Cost and revenue for a job close in one application, with nothing to reconcile across two programs. Laravel, MySQL, Redis and Inertia underneath; field app in React Native (Expo).

Read the case study →

Working with Besiktas 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 run equipment, not vehicles. What would the maintenance history attach to?

    To the asset's own identity rather than to the unit using it. In AlgoCar that identity is the plate and chassis record; on your side it becomes a serial or an asset number. Whatever sits under that record follows the asset wherever it goes.

  • Equipment circulates between the brands at our Besiktas head office. What does carrying the history actually buy us?

    The unit taking over does not rediscover the first service. Which part was replaced when, which fault keeps returning, all of it reads off one record. Because nothing is copied between cards, two versions that disagree never appear either.

  • Do you also do fleet management and tracking hardware?

    No. AlgoCar runs a service workshop: work orders, parts, invoices and vehicle history. Location hardware, driving data and corporate procurement sit outside that scope, and we do not promise what we cannot show.

  • Is AlgoCar an off-the-shelf product or written for us?

    AlgoCar is our own product and we carry its upkeep, which is a different position from an agency that ships and leaves. What we describe on your side is not the same screens but the same record shape: the job is a container, what is spent is written under it, and history lives on the asset's identity.

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