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

Software Consulting for Uskudar businesses

In an institution the same contact detail can live in more than one place. Uskudar's fabric leans on the health, education and service organisations around Altunizade and Baglarbasi; if a desk number is printed on a card, typed into the contact line of a page and signed on an appointment confirmation, changing it means somebody has to walk all three. Whichever gets missed keeps answering with the old number. QRVizit is what we are building against that repetition: when a number, a title or an address changes, the record is updated rather than the cards.

Get a quote Tell us about your project

Software Consulting — Uskudar

Health, education and service organisations in Uskudar run on appointments and institutional records. Where roles rotate often, the title is what moves and the address stays put. If you already have a working site and a printed identity, the consulting job is not to throw either away but to bring the changing detail onto one record. Closest to that is our own product QRVizit, still in development with no live installation to show. Where it does not overlap is written down: QRVizit is being built to put a record behind a printed business card, not to run an appointment book, a course enrolment flow or a staff directory. Panel and visitor page sit inside one Laravel application; records stay in MySQL, the page off a Redis cache, Inertia carries React, Tailwind sizes small screens.

  • Once the changing detail lives on one record, an update is typed once, because the card, the page and the confirmation read that entry instead of keeping copies.
  • When someone hands over a role, what moves is the record behind the page rather than a print run: the new holder takes the entry and the card stays as it is.
  • The boundary is written down: appointments, payments and an internal staff directory sit outside this scope, and QRVizit does not stand in for them.

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 — in development: a detail changes on the record, not on the cards

Our own product, being built right now; we show no live installation. The code printed on a card points at an address that never moves again, while the page behind it is edited from a panel. When a number, title or address changes, what gets updated is the entry in the panel; cards already handed out stay as they were. If the holder leaves the role, the record passes to whoever takes it. Panel and visitor page sit inside one Laravel application, with Inertia feeding React and no separate API layer. The page comes off a Redis cache while the records stay in MySQL. Appointments, payments and staff directories are outside the scope.

Read the case study →

Working with Uskudar 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 already have a working site. Does this mean replacing it?

    No. The site stays where it is. What moves is the detail that keeps changing: it comes down to one record, and the card, the page and the confirmation text read that record instead of holding their own copies.

  • The desk number changed. How many places have to be edited?

    One, once the detail lives on a record. Before that, as many places as it was typed into, and whichever is missed keeps answering with the old number. The first thing consulting measures is where that repetition sits.

  • Can we put QRVizit into service now?

    Not yet. It is our own product and still in development, so there is no live installation to show. What we can show is the decision behind it: the printed thing points at a record, and the record is what gets edited.

  • Would you need to work inside the institution?

    We keep no office and the work runs remotely throughout. Instead of taking a desk, we write down with you which detail belongs on which record.

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