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

Enterprise & Commercial Software · Beylikduzu

Enterprise & Commercial Software for Beylikduzu businesses

In the industrial estate at Beylikduzu a production floor and a sales desk can share one building without sharing what they know. Whoever answers the phone may not be the engineer who sizes the product, and a caller describes a volume to heat and the conditions around it rather than a product code. A catalogue does not close that gap; it makes someone wait for the engineer. The selection software we wrote for Resterm turns the input around: the requirement goes in and the software picks the heater.

Get a quote Tell us about your project

Enterprise & Commercial Software — Beylikduzu

Between Yakuplu and Gurpinar in Beylikduzu a manufacturer's sales office sits a few doors from what it sells. Even with a narrow range, if every order begins with a calculation then searching a catalogue is not what does the sizing. The closest match in our portfolio to this district's profile is Resterm, written for electric heater manufacturing. Say where it does not reach: production planning, purchasing, shift rosters and human resources fall outside that scope, and we have nothing to show in them. What carries over is where the calculation lives. We built the software onto Resterm's own product structure instead of bolting a catalogue onto a general quoting tool, so a chosen heater reads back to the requirement that produced it. Laravel, MySQL and a Vue interface sit underneath, and we work remotely with no office.

  • The input is a heating requirement rather than a product code, so the catalogue search step disappears and the calculation itself picks the unit.
  • The chosen heater drops into a basket, the basket attaches to a project and the project to that project's customer, so nobody carries figures by hand between the technical choice and the commercial line.
  • The software was built onto the manufacturer's own product structure, with Laravel running the flow, a Vue interface, and MySQL holding the chain in one place.

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.

What we build

Enterprise & Commercial Software

  • 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

Calculator Resterm — the sales desk states the need, the software runs the sizing

Resterm manufactures electric heaters, and the input is not a product code but a heating requirement: the user states the volume and the conditions, the software runs the engineering and selects the unit. Nobody searches a catalogue. The selection drops into a basket, the basket attaches to a project, the project to that project's customer, and the calculation becomes a quote line. Built onto Resterm's own product structure rather than a generic quoting tool, a quote reads back to the requirement behind it. Laravel runs the flow, Vue the interface, MySQL the records.

Read the case study →

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

  • Nobody on our sales team is an engineer. What does handing the sizing to software mean?

    It means the sizing is settled once instead of being re-argued at every desk. The product structure and the selection logic are written into the software, and after that the user enters only the heating requirement. In Resterm the split is exactly that: the software chooses, and the manufacturer's own product structure is what it checks against.

  • We expect production planning under the words enterprise software.

    We have nothing to show there, so we promise nothing there. What Resterm demonstrates is narrow and stated plainly: requirement to selection, selection to basket, basket to project, project to quote line. Purchasing, shift rosters and human resources sit outside that line.

  • Our range is nothing like heaters. What does this tell us?

    What travels is the direction of the input, not the heater. The user types a condition rather than the answer's code, and a calculation returns the product. If your range can be written down as a structure, the same line can be built on it; if it cannot, we say so before we start.

  • Would you not have to see the production to map our range?

    We keep no office and the work runs remotely from start to finish. Rather than walk a floor, we write down together which condition in your range returns which product, because that written rule is what the software runs afterwards. Leave one condition vague and it surfaces later, inside the calculation, then on the quote line.

Enterprise & Commercial Software in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

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

Get a quote or open the service