Get a quote

Management Systems · Atasehir

Management Systems for Atasehir businesses

The hardest question a head office asks is usually the plainest one: where is that job right now? If the record sits in a technician's pocket through the day, the answer only arrives in the evening — the crew moves between buildings, drops to a mechanical floor in a basement, and leaves the paperwork on a desk that evening. Multi-branch corporate management runs dense in Atasehir, and AlgoKlima was written against that gap: the job closes in the field, the technician finishes the record on the phone, and the office reads its state from the panel.

Management Systems — Atasehir

In Atasehir the floor where decisions are made and the address where work happens need not be the same. When a report is the only thing between them, the service side measures that distance in hours: every stop a technician makes during the day leaves a question mark in the office. The closest work here is AlgoKlima, our own product, whose upkeep we carry. Say where it does not reach: the software was built for air conditioning, boiler and appliance servicing. We have no finance client in the portfolio and nothing to show for head-office budgeting or consolidated reporting. What carries over is when the record closes. Laravel and Inertia carry the office panel, React Native (Expo) the field app; both write to one MySQL database and share a Redis cache.

  • The job closes where it is done. A technician finishes the record on the phone, and the office reads its state from a panel rather than from paper handed in at the end of the day.
  • Losing the connection loses nothing: the phone writes to its own queue, and once the network returns the records go up in the order they were opened, merging with any office-side correction on the same record.
  • Service history hangs on the unit rather than the address, so the office can answer what was last done to a particular machine without opening a second file.

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

AlgoKlima — the job closes in the field, the office sees it before evening

Our own product for air conditioning, boiler and appliance service firms: a system we maintain, not a client handover. A technician opens and closes a job on the phone; the record goes first to the device's local queue, so the app carries on without a connection. When the network returns, queued records go up in the order they were opened, and field and office corrections merge on one record through conflict resolution. The office therefore reads job state from the panel, not from evening paperwork. Warranty history hangs under the unit. Laravel and Inertia carry the office panel, React Native (Expo) the field app.

Read the case study →

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

  • Can we see where each job stands during the day, from the office?

    Yes, because the record is closed where the work is done. When a technician finishes on the phone the state reaches the panel; if there is no network at that moment the record waits in the queue and goes up when the connection returns. The office is not waiting on an evening form.

  • Our crews work in basement plant rooms and lift machine rooms with no signal.

    The app does not treat signal as a precondition. The form is completed in the phone's own queue, the record stays there, and the technician moves to the next job. When coverage comes back the queue empties on its own and nobody types the record a second time.

  • Could we also get a consolidated report across our branches?

    We have nothing to show on that side; AlgoKlima is built around servicing equipment. Consolidated financial reporting and budgeting sit outside the scope, and there is no finance client in our portfolio. We keep what we do not promise written down as well.

  • Can we talk at our head office in Atasehir?

    Not in person. There is no office of ours to meet at, we give no on-site support, and the agency works entirely remotely; scoping conversations run that way too. The first thing you get back is written: which movement in the field changes which record, and how.

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