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

ERP · Besiktas

ERP for Besiktas businesses

Where what you sell does not finish in one sitting, the decision is signed in one room while the work lands in pieces across several weeks. Head offices cluster along Besiktas's Zincirlikuyu and Levent line, and the floor where a decision is made need not be the floor where the work happens. That split puts a hard question to an ERP: where does a half-finished job live? In the CRM we built for a dental clinic the answer sits on the plan record. The program is a record in its own right, and which step comes next is read off it rather than off a calendar. Our scope covers how a job runs and how it is billed.

Get a quote Tell us about your project

ERP — Besiktas

Besiktas is thick with head offices and multi-brand corporate groups. Where one head office watches several brands move at their own pace, each brand delivers at its own speed and the question of where the sequence is kept lands back at the centre. The work closest to this district's sector profile is a CRM we wrote for a dental health clinic. Where it does not overlap comes first: it was built for a single clinic, it carries no stock movement and no purchasing, production planning was never part of it, and we have no agency or media client to point at. What travels is where the sequence is kept. Laravel runs the process, MySQL holds the patient, plan and invoice records. Human resources, consolidated finance and the supply chain are not in this page's promise.

  • The program is a record of its own, so the question of which step is due gets answered by the plan and not by the appointment book.
  • Across a job that runs for weeks, a manager can see from one screen how far each client has got.
  • A part-finished program can still be billed: the amount is read from the steps actually carried out, with no separate collection list to keep.

Why Algoriel

  • Work order through to invoice

    In AlgoCar information is entered once and carried on the same record from the work order to the invoice.

  • Stock moves next to the job

    Parts leave stock against a work order, so nobody hunts for where a part went at month end.

  • The calculation becomes the quote

    Resterm sizes a unit with an engineering calculation, and the result drops into the cart and the project record.

  • Where the scope stops

    Operations, stock and accounting are in scope. Production planning, supply chain, consolidated finance and HR are not.

What we build

ERP

  • Work order, part and invoice on one chain

    At AlgoCar a work order opens, the part consumed is written to it, and the invoice comes from that same record. The chain never splits across three programs.

  • The same movement is never typed twice

    A part leaves stock the moment it is written to the work order. No warehouse screen sits waiting for the same consumption to be keyed in again.

  • Cost and revenue in one system

    The trading and accounting side runs in the same system as the service record, so the two faces of a job are not reconciled after the fact.

  • Spend that accumulates on the asset

    At AlgoCar servicing and repair build up under the plate and chassis record, so what a vehicle has cost in total is read from its own file.

  • Where a quote line came from

    At Resterm you can trace a quote line back to the heating requirement that produced it.

  • From calculation to basket to project

    The product the engineering calculation selects drops into the basket, the basket attaches to a project, and the project to its customer. The records stay on one chain.

Work like this

ERP · Case study

Dental clinic CRM — the program spans weeks, the sequence sits on the plan

A system we wrote for one dental health clinic; we state its scale plainly. What a clinic sells is not a service that finishes in a single visit but a program that runs over weeks. So the program was not buried inside the calendar: it stands as its own record and carries the sequence. An appointment opens as the counterpart of a particular step; slot a step in or bring it forward and the calendar follows. The amount does not pile up elsewhere: the work carried out lives on the patient record, so payment is read from there too. Laravel runs it and MySQL keeps the records. Stock movement and purchasing were never built here.

Read the case study →

Working with Besiktas 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 are looking for an ERP and you are showing us clinic software. Where is the link?

    The link is in the shape of the record, not the screens. When a job runs for weeks the real question is where the sequence is held: in the calendar, or in the job's own record. At the clinic we loaded it onto the plan record. Call the container a maintenance program or an installation stage instead of a treatment and the chain holds.

  • We run several brands under one roof. Can they sit in one system?

    They can, and Vipkurum is the evidence. There, seven institutions share one system, each with its own domain and its own brand. What they share is the structure of the record; the face each one shows stays separate.

  • Does this cover production planning, the supply chain and human resources?

    It does not. On the ERP side what we describe is the operations record, stock movement and accounting. Production planning, supply chain, consolidated finance and human resources are things we have nothing to show for, so we do not promise them.

  • Can this start without meeting at our head office in Besiktas?

    It can. We have no office to meet at and the team works fully remotely, so a job starts in writing rather than at a table. Together we write down which piece of information lives in which record, and the sequencing decision is made there.

ERP in other cities

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

Other services for this location

Is the cost of a job still meeting its revenue at month end?

Get a quote or open the service