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

Management Systems for Esenyurt businesses

A quotation comes back months later and the question is always the same: where did this figure come from. Whoever wrote it is at another branch that day, and what remains is the name of the line rather than the calculation behind it. Esenyurt is thick with small multi-branch businesses, and around Akcaburgaz that question repeats at every re-pricing. Calculator Resterm leaves no line hanging in the air: a quote can be read backwards to the heating requirement it came out of.

Get a quote Tell us about your project

Management Systems — Esenyurt

Business in Esenyurt is small and spread across branches; the same name can stand at several addresses, and private education providers run the same way. When one person writes the quotation, somebody else has to defend the number later. The work closest to that texture is Calculator Resterm. Where it does not overlap comes first: written for selecting electric heaters, it holds no production planning or purchasing, and we have nothing to show on till flow, staff records, warehousing or wholesale dispatch. What carries across is that the link holds: nothing is moved by hand between the technical selection and the commercial line, so the line stays attached to its input. Laravel runs it, records sit in MySQL, and Vue draws the calculation screen.

  • The user enters a heating requirement rather than a product code, and the software runs the calculation and picks the heater, so no catalogue search step is ever created.
  • The selection drops into a basket, the basket belongs to a project and the project to that project's customer, with every link of the chain held in a field of its own.
  • Because the quote line and the input that produced it sit on the same chain, a figure can be defended later without the person who wrote it being at the desk.

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

Calculator Resterm — a quote line stays tied to the need that produced it

We wrote selection software for an electric heater maker. The user enters a heating requirement, not a product code, and the software runs the engineering calculation and picks the heater. The selection drops into a basket, the basket attaches to a project, the project to its customer, all held as one chain in MySQL. Because the calculation's result becomes the quote line, nothing is retyped between technical and commercial sides. The payoff is traceability: a quotation reads backwards to the requirement behind it, and holds up months later. Laravel runs it, Vue draws the screen.

Read the case study →

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

  • The colleague who wrote the quotation is at another branch today. Who explains the figure?

    The record does. The input that produced the line sits underneath it, so which requirement was entered and which product was chosen read off the same chain. Nobody has to come back to the desk or dig through old files for it.

  • We already keep a price list. Why add a calculation layer?

    A list prices a product whose code is already known. On your side the conversation usually starts from a requirement instead: this volume, this condition. The calculation layer closes that gap — the requirement goes in, the software picks the product, and the choice becomes the quote line directly.

  • We do not make heaters. What does Calculator Resterm say to us?

    Not the heating maths but the direction of the chain: the input is a record, the selection is its result, and the line is what that selection turns into. On your side the input becomes a dimension, a duration or a headcount. The engineering side of heater selection does not transfer; what transfers is the line staying traceable.

  • We are a small multi-branch business in Esenyurt. Would this scope be too heavy for us?

    If a spreadsheet does the job, keep it — we say that plainly. The threshold starts elsewhere: when several people write the same kind of quotation and a figure has to be defended months later, the link between input and line has to live in the record. We keep no office, and on-site work is not something we do.

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