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

Management Systems for Fatih businesses

In older building stock no ventilation job starts without a survey: nobody picks a unit before seeing where the outdoor half will sit. Fatih's stock between Aksaray and Findikzade is exactly that kind. So two unrelated questions land on the same site. One asks for a date at a place with no equipment yet. The other reports a fault on a unit already installed. A single form piles them together, and somebody sorts the pile by hand every morning. Diotek removes that sorting step.

Get a quote Tell us about your project

Management Systems — Fatih

Cooling and ventilation are not one trade in Fatih. In a wholesale food depot a system runs all day; in a guesthouse, units go in room by room over a season. The first hot week can put both kinds of demand on the same day. The portfolio work closest to that profile is Diotek, and where it stops belongs on the page: Diotek is where a request is taken, so technician rosters, spare-part stock and a field app sit outside it and we have nothing to show there. What carries across is what a request attaches to — a place not yet fitted, or a unit already running. The same foundation underneath: Laravel with Inertia and Tailwind, MySQL for records, Redis for cache.

  • A survey booking opens before the visitor has picked a unit, and it reaches operations on its own flow rather than joining the queue of post-installation calls.
  • A maintenance or fault report is opened from the site against the unit already installed, so the record is written down and something reported at midnight lands where the morning shift looks.
  • What we do not promise is written down too: technician rosters, spare-part stock and a field app fall outside what Diotek covers.

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

Diotek — two intake flows, so operations never re-sorts the pile

An air conditioning firm receives two unrelated things through its site: a pre-sale survey booking, and a service report after installation. Diotek built them as separate flows. On the survey side a visitor asks for a date against a room, without choosing equipment; on the service side the installed unit is the subject. Because the two never share a queue, nobody re-sorts an inbox before work begins. One Laravel application holds the marketing pages and the request screens, with Inertia for page transitions, MySQL for records and Redis for the season's opening load. Scope: rosters and parts stock are not part of this.

Read the case study →

Working with Fatih 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 already have a contact form. Why split it in two?

    One form flattens what arrives, and the distinction gets rebuilt later on a phone call. With two flows, a request turns up carrying what belongs to it: an address and a date on one side, an installed unit on the other.

  • Demand jumps when the season opens, and that is where we lose work.

    The crush is two request types landing on top of each other. Sort them at the door and survey bookings queue among themselves while fault reports queue among themselves, so preparation stops being made against the wrong job.

  • Calls suit us. What does a written request add?

    A phone note lives with the person who took it and goes home at closing time. A request opened from the site is the record itself, so something reported at nine in the evening reads the same way at eight the next morning.

  • Our depots are in Fatih, on the wholesale side. Do you need to come here to set this up?

    We keep no premises and provide no on-site support. The first thing we hand over is written rather than built: which fields each request type carries, and the order in which it reaches operations. Code 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