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

Software Consulting for Istanbul businesses

Consulting is usually discussed while something is already running. If several windows sit open on one desk, the picture looks like this: the sheet where the sizing is worked out, the file where the products live, the program where the quote is typed. Copy and paste is all that joins them. In Istanbul the brief is rarely a rewrite; it is narrower than that, and it asks which record gives rise to which. Resterm is where we built that chain.

Get a quote Tell us about your project

Software Consulting — Istanbul

Istanbul's buyer list does not sit in one sector: manufacturing, head offices and retail all appear on it. The work closest to that spread is Resterm, a selection tool written for a maker of electric heaters. Here is where it does not overlap: the calculation belongs to that manufacturer's own product structure, and we hold no ready engine that will run another industry's sizing, so that part gets written again each time. Consulting begins in the same place, by reading which record creates the next one and where a value is still moved by hand. Underneath sits Laravel, with MySQL holding the records and Vue the interface.

  • The first pass is reading rather than writing: we work out what each part of the existing code does and mark the sections that stay untouched before anything changes.
  • The target is the record, not the screen. In Resterm a selection drops into a cart, the cart attaches to a project and the project to that project's customer, so a quote line can be traced back to the input it came from.
  • The limit is stated too: we do not bring a new technology set into a system somebody else will maintain, so the work stays inside the tools that team already knows.

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

Resterm — a quote line that still shows the sizing input underneath it

Resterm manufactures electric heaters, and the job was to move the sizing into the software. The user enters a heating requirement, not a product code; the engineering calculation runs and the right heater comes back chosen. From there it is one chain: the selection drops into a cart, the cart attaches to a project, the project to that project's customer. Nothing moves by hand between the technical choice and the commercial line. We built it on the manufacturer's own product structure, not a general quoting tool with a catalogue attached. Laravel runs the calculation, MySQL holds the records, Vue the interface.

Read the case study →

Working with Istanbul 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 run something that works. Do you start by rewriting it?

    No. We start by reading the code, working out what each part does and marking what stays. Only then do we discuss where to intervene, and the intervention stays with the parts carrying the load.

  • Is consulting a document or is it code?

    It can be both, but the order does not move: first we write down which record gives rise to which, then that decision becomes code. Resterm followed exactly that order, and the output of the calculation ended up as the quote line itself.

  • Can we meet somewhere in Istanbul?

    We keep no office and work fully remotely. Meetings happen online and whatever we agree stays in writing. Tell us in the quote form which system is running today, and we plan the first reading pass around that.

  • We do not make heaters. What does Resterm tell us?

    The calculation itself was written for electric heaters and does not travel. The shape of the chain does: a choice becomes a cart line, the cart belongs to a project, the project to a customer. Change the product and the links keep their order.

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