Get a quote

Enterprise & Commercial Software · Catalca

Enterprise & Commercial Software for Catalca businesses

In Catalca, in a shop off the Kaleici market square, an appointment is a time pencilled into the margin of a ledger. The customer comes down from Karacakoy or Binkilic and, having given up a day for the trip, wants two jobs done one after the other. In a booking setup where duration and gaps are fixed per sector, nothing stacks. AlgoRandevu, which we are building right now, moves that rule into the product itself.

Enterprise & Commercial Software — Catalca

Trade in Catalca runs on food retail and rural shopping, and coming into the centre costs a day. Catalca is the one district where we can name a client next to it: Merkez Kasap really is here. That job was a menu page, so it is not the evidence for this one. The evidence here is AlgoRandevu, and its status is plain — our own product, under construction, not a delivered installation. We have never written anything for farming or livestock. What we are working on is the appointment rule: how long it runs, what resource it holds, what gap sits between one booking and the next. It goes on the same Laravel and Inertia ground as AlgoKlima and AlgoCar, with MySQL records, a Redis cache and a Tailwind panel.

  • How long an appointment runs and what gap follows it are product settings rather than something buried per sector, so changing the rule changes a setting and not the code.
  • In the structure we are working on an appointment can hold a person, a room or a piece of equipment, so a business picks its own resource and we write no separate arrangement per sector.
  • The aim is to pull a booking that today runs across a calendar and a messaging thread into one panel, and until that is finished we do not describe it as a working installation.

Why Algoriel

  • Many institutions, one system

    Vipkurum runs seven institutions on the same system while each one keeps its records to itself.

  • Adding one adds a boundary

    Each Vipkurum institution signs in at its own domain under its own brand, so adding one does not mean a second installation.

  • Each branch runs its own work

    A branch marks its own exam sheets, so one broken device does not stall every institution at once.

  • Each role, its own view

    Timetable, exams, students, parents, payments and reporting sit on one platform, and who can see what is settled up front.

  • Each institution signs in through its own domain

    At Vipkurum, seven education institutions open under their own address and their own brand, and the name of the software never appears on a user's screen.

  • No reinstallation for a new institution

    Adding one more institution means writing a definition. No second copy of the system is stood up, and the maintenance stays in one place.

  • Office and field on the same record

    AlgoKlima's office panel and field app read and write the same record. A technician closes the job where there is no signal, and the entry reaches the office panel once the connection returns.

  • Operational and commercial records close together

    At AlgoCar the service record and the commercial record sit in the same system, so the cost of a job and its revenue are not reconciled across two programs.

  • One institution's data stays closed to the next

    Student, parent and payment records stay inside the boundary of the institution they belong to. That boundary is how the system is set up, not a view switched off on a screen.

  • One technical footing we can maintain for years

    Nothing goes into your system that the team maintaining it does not already know. AlgoKlima and AlgoCar are our own products, built on that same footing, and we work on it every day.

Work like this

Enterprise & Commercial Software · Case study

AlgoRandevu — we are building the back-to-back gap as a product setting

Our own product, under construction; we do not present it as a finished installation. How long an appointment runs, what gap follows it and what resource it holds are kept definable inside the product rather than baked into a sector. One business can remove the gap and put two jobs back to back while another leaves room between them, and both run inside the same product with no separate release. An appointment can hold a person, a room or equipment. We build it on the same Laravel and Inertia ground as AlgoKlima and AlgoCar: MySQL holds the records, Redis is the cache layer, Tailwind shapes the panel.

Read the case study →

Working with Catalca 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 customer travels in from a village and wants two jobs back to back. Can the calendar do that?

    That is precisely the setting we are working on. The gap between consecutive appointments is held as a product setting, so removing it or widening it is a configuration decision rather than developer work. AlgoRandevu is being built around that rule right now.

  • Is the product ready? When could we install it?

    It is not ready, and we write it that way. AlgoRandevu is in development; what we can show today is the arrangement we are working on and the ground under it, not a running installation. If you want finished work, AlgoKlima and AlgoCar are live and we carry their upkeep.

  • Do you actually work with a business in Catalca?

    Yes, Merkez Kasap. This is the only district where a client's name can sit beside it. Being straight about it: that job was a QR menu page, with no booking, resource or staff layer built into it.

  • Booking is a small part of what we do; enterprise software should cover more.

    Then narrowing the scope early is the honest move. This page describes one rule: where an appointment's duration, resource and spacing are defined. Accounting, stock and purchasing are outside this product, and we make no claim where we have none.

How many institutions and branches should we plan your system around?