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

Software Consulting for Izmir businesses

A print run happens once and then waits in a box. Material you hand out at the Gaziemir fairground keeps carrying whatever was true on the day it left the press, and whoever takes it into an export meeting speaks from that until the box is reprinted. Consulting questions in Izmir often begin here: what gets frozen and what stays editable. QRVizit, the product we are building now, sits on exactly that split. The address is fixed, the page behind it is not.

Get a quote Tell us about your project

Software Consulting — Izmir

In Izmir what goes onto a printed page is settled once, and only the page behind it can be corrected later. If you decide with an export target in view, material gets prepared for more than one market and more than one language. The nearest work we have to that is QRVizit, and we will say plainly what it is: our own product, still under construction, with no installable version today, and neither an export catalogue nor a product configurator. Its scope is one profile page. What it carries into consulting is a way of deciding, which is to freeze the part that goes to print and leave the rest in the panel. Underneath sits Laravel, with MySQL holding the records, Redis the cache and React fed through Inertia.

  • The first deliverable is usually a line rather than a build: what goes to print, and what stays changeable from a panel.
  • In QRVizit the only fixed thing is the address the code points to; page content is rewritten from the panel while the printed piece already in circulation stays as it is.
  • Because the product is still being built we promise no delivery date and no installable version, and what we describe here is the construction rather than a finished tool.

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

QRVizit — under construction: one fixed address, a page that keeps changing

This is our own product, still being built, with no version to install, so what follows is the construction rather than a finished tool. The decision behind it is a consulting decision: which part freezes and which stays open. The frozen part is the address: where the printed code points is settled once and never moved. The open part is the page content, rewritten from the panel as often as needed. Whoever scans installs nothing; a camera is enough, and we build the page in Tailwind to read on a small screen. Panel and visitor page share one Laravel application, React fed through Inertia. Content sits in Redis, records in MySQL.

Read the case study →

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

  • Does this mean dropping print altogether?

    No. The decision is not to drop print but to narrow what goes onto it. In QRVizit the only printed thing is the address; the title, the phone number and the description stay in the panel.

  • Can you install QRVizit for us now?

    No. QRVizit is our own product and it is still under construction, with no deliverable version. What this page describes is the shape of the record, not something you can buy today.

  • We want a multilingual export catalogue. Is that in scope here?

    QRVizit is a profile page, not a catalogue or a configurator. Listing work is a separate piece of evidence for us, the Plastik ve Makina platform, and we keep the two apart rather than stretch one over the other.

  • Do you have a team in Izmir?

    We keep no office anywhere and work fully remotely; that is the working model rather than a gap. No step in the work needs somebody in the room. QRVizit is settled in writing before it is built: which field freezes onto the print, which one stays in the panel.

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