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

Software Consulting · Sariyer

Software Consulting for Sariyer businesses

What gets inherited may not be one system but three programs open side by side, with a person carrying information between them. On the head-office floors along Sariyer's Maslak plaza line, if that chain only lines up at the monthly close, it lines up exactly when nothing can be touched. So the first thing we ask is not the name of a program: how many times does one record get typed? If the answer is more than once, the thing to fix is the entry. AlgoCar was built around that question.

Get a quote Tell us about your project

Software Consulting — Sariyer

Sariyer's fabric leans on the technology and head-office towers along the Maslak plaza line and on the university campus edge around Ayazaga; on a head-office floor the work is management rather than making, so the numbers form elsewhere and are gathered there. The work closest to that fabric is AlgoCar, and it fails to match on two counts: it was written for vehicle servicing, and it is not a client system we inherited but our own product, whose upkeep we carry. We have never done finance or banking work and have nothing to show for consolidated reporting. What carries is the chain itself: a work order becomes a container, the part consumed drops into it, the stock movement forms at that moment, and the invoice comes off the same record. Service history hangs on the plate and chassis record. Laravel sits underneath, with MySQL holding the records, Redis the cache and Inertia the interface.

  • On a takeover we count how many times the same information is typed, not how many programs are running; a second entry is where the month-end gap comes from.
  • In AlgoCar the part drops out of stock the moment it is written to the work order, so the warehouse movement is not waiting to be keyed into another screen.
  • Service and repair records hang under the vehicle record, so a vehicle that changes hands brings its history along instead of having it retyped onto the new owner's card.

Why Algoriel

  • We read the code first

    We did not build the KGM SsangYong corporate site; we read the inherited codebase and left the parts that worked untouched.

  • Fix where the load sits

    The same catalogue query hit MySQL on every page open; that read moved to a Redis cache and nothing else was disturbed.

  • We stay inside your framework

    On the KGM SsangYong site the inherited Laravel, Tailwind and jQuery set was kept; the cache layer was the one addition to the stack.

  • We reconnect broken chains

    At Resterm the calculation sat in a sheet, the catalogue in a file, the quote somewhere third; selection now runs to cart, project, and customer.

What we build

Software Consulting

  • Reading the code first

    We read the inherited codebase through, then name what moves and what stays untouched, one item at a time. The scope of the change comes out of that reading rather than a template.

  • Staying on the existing framework

    A library the maintaining team has never worked with would be a cost we left behind on our way out. KGM SsangYong's corporate site arrived with its framework and front-end libraries already chosen, and not one dependency was added to that set.

  • The limit of the change

    Only the slow places get opened; heavy spots are handled one at a time and the rest stays where it is. Where that limit falls is written down for you once the reading is done.

  • Tidying the file layout

    Scattered files move into a single naming and folder scheme. Which model uses which file becomes visible without reading code.

  • Taking weight off the reads

    The same query repeated for every visitor can be run once and shared from there. On KGM SsangYong's catalogue pages that query no longer runs until the data changes.

  • The decision taken before code

    Some decisions are made before the first line and are expensive to correct later. Resterm's software was built on the manufacturer's own product structure, because it was clear from the start that a general-purpose quoting tool would not carry it.

Work like this

Software Consulting · Case study

AlgoCar — one entry travels the service, stock and accounting chain

Our own vehicle service software, whose upkeep we carry, not a client handover. A work order opens, the part consumed drops into it, stock falls at that moment and the invoice comes off the same record; the chain closes inside one system. The warehouse movement never waits to be keyed into a second screen. Service and repair history hangs under the vehicle record, so a vehicle that changes hands brings it along. The trading and accounting side attaches to the same install, so the cost and the income of one job are not matched across two programs. The vehicle context is AlgoCar's own; what transfers is how the record is shaped.

Read the case study →

Working with Sariyer 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 run three separate programs and do not want to replace them all.

    You may not need to. What we look at is how many times the same information is typed. If one record goes into the service side and again into a warehouse screen, the thing to fix is that second entry, not one of the programs. In AlgoCar the part leaves stock the moment it is written to the work order, so no line is left waiting.

  • Our month-end numbers never agree. Where do we start?

    Where the difference appears, not at the close. If the same movement is written in two places, the gap is waiting for month end by design. Once the entry has a single source, the close stops being a reconciliation session.

  • Do you work with financial institutions in Sariyer?

    No. We have nothing to show in banking or fintech and we do not imply work we have not done. The evidence we point to is AlgoCar: our own product, written for vehicle servicing, with its upkeep on us.

  • What does it mean that AlgoCar is your own product?

    That we do not describe maintenance cost from a distance. We carry AlgoCar's weight ourselves, so when we say what will get expensive later inside an inherited system, that comes from living with one. We keep no office and work fully remotely, handovers included.

Software Consulting in other cities

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

Other services for this location

Would you like us to read the system you already have?

Get a quote or open the service