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

Software Consulting for Besiktas businesses

Once a list is split in two it is hard to put back together. If the used ones were added years ago and what got built was a second catalogue rather than a field on the record, today that means two admin panels, two sets of records and a spreadsheet merged by hand at month end. Software consulting in Besiktas opens on that question: should the distinction be a list, or an axis you filter on. In Plastik ve Makina it is the second.

Get a quote Tell us about your project

Software Consulting — Besiktas

A list serving traffic from a head office floor cannot simply be taken down, so merging two catalogues gets planned while the site stays live rather than shipped as an overnight cut. Besiktas leans on head offices and multi-brand corporate structures, and the work closest to that fabric is Plastik ve Makina. The gap, stated plainly: the platform was built for trading plastic processing machinery, we have nothing to show for how a media or agency shop runs its own production, and consolidated reporting across a multi-brand group sits outside it as well. What carries across is where the distinction lives: condition is a field on the record rather than a second catalogue. Underneath sits Laravel, with MySQL holding the records and Redis the cache; the list is rendered on the server and carried by Inertia and Tailwind.

  • New and used listings stay in one list, and a buyer opens condition as a filter to compare both options inside a single search.
  • Laravel prepares the list on the server and Inertia hands it to the browser, so changing a filter refreshes results in place instead of reloading the page.
  • The limit is written down: consolidated group reporting, media production workflow and brand-level budget tracking sit outside this work.

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

Plastik ve Makina — condition is a filter axis, no second catalogue opens

A sector listing platform for people who buy and sell plastic processing machinery. The whole category tree is built on the distinctions of a single machine family, so a split that would be a subheading on a general listings site becomes the main axis. New and used listings are not divided into separate catalogues: they sit in one list and condition opens as a filter, letting a buyer compare both in one search. Laravel prepares the list on the server, Inertia carries it to the browser, and results refresh in place when a filter changes. MySQL holds the listing records, Redis the cache layer. Scope is listings and catalogue.

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

  • Do we have to take the system down to merge two lists?

    Merging is not one big move. We first map the fields where the two records differ, then reduce that difference to a single field while the live list keeps reading from the old catalogue. In Plastik ve Makina the distinction was a field from day one.

  • Do you rewrite the code you inherit?

    No. If a part works, we leave it. That is what we did on the SsangYong corporate site: the system was taken over, the improvements and the storage layer rework happened on the existing code, and the jQuery legacy stayed in place.

  • Plastik ve Makina is a listings platform. We run a multi-brand head office.

    We name the difference. What travels is a decision, not a sector: do you keep a distinction as a list or as a field. Brand, condition or region: once it becomes a field, the second panel and the month-end merge disappear.

  • Would a second site not be cheaper than adding a filter?

    It looks cheaper on day one. A second site means a second set of records, and sooner or later somebody reconciles them by hand. The cost is not in the build; it arrives every month the same information is kept in two places.

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