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

Web Software · Kadikoy

Web Software for Kadikoy businesses

If everything arriving through your site lands in one form, the sorting has to happen on a phone call afterwards. We do that sorting where the request arrives instead, so which record it belongs to is settled at the start. The work closest to Kadikoy's consulting rooms, studios and small retail is Diotek: a survey booking and a service call were built there as two separate intake flows.

Get a quote Tell us about your project

Web Software — Kadikoy

Kadikoy's texture is service businesses that run by appointment: the consulting rooms, studios and small retail around Caferaga and Bahariye. What arrives through a form is not one kind of thing, though. One request concerns something not on record yet: a room to be measured, a first visit. The other is attached to something already recorded, an installed unit or an open file. A single form flattens that difference, and only the phone recovers it. When both land in the same afternoon the queue loses its order and the team prepares for the wrong job. On Diotek the flows carry different subjects, so that recovery step disappears: the booking is about a space, the service request about a unit already on the wall.

  • Separate the request at its source: a survey booking attaches to a space and a service request to an installed unit — two forms, two queues.
  • Take intake off the phone line: requests arrive from the site in writing, after-hours ones included, so the order stops depending on a phone note.
  • Keep the public pages and the intake in one application: Inertia moves between pages in the browser, form validation stays in Laravel, and content and request records share one MySQL schema — no second panel to maintain.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software

  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

Diotek — survey bookings and service calls built as two intake flows

An air conditioning and ventilation company receives two unlike requests; both used to arrive on one phone line, and at the start of a season only a conversation told them apart. The flows were built apart. A survey booking asks for a date before any equipment is chosen, because capacity depends on the room. A service request opens after installation, around the unit fitted. Intake no longer waits on the line, so a request sent outside working hours lands in writing. Both sit in the same Laravel application as the public pages, with Inertia handling page transitions and requests sharing the content's MySQL schema.

Read the case study →

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

  • Bookings and fault reports both come through our site. How do you tell them apart?

    By what the request is about. One points at something not yet on record, a space or a first visit; the other at a unit already in their records. Two forms, two queues — Diotek was built in that order.

  • Are you based in Kadikoy? Can someone come and look on site?

    We keep no office and work fully remotely; that is the working model, not a gap in it. We write down which request belongs in which record, and the build follows.

  • We are a small business. Do we really need this separation?

    The split follows the subject of a request, not the volume. One form causes no trouble in a quiet week; once the two types overlap, the difference can only be recovered by asking.

  • Our booking flow is specific to our sector. Are you installing an off-the-shelf product?

    We are building AlgoRandevu now for booking flows that differ by sector. In client work the flow goes inside the company's own Laravel application, as on Diotek, in the same schema as the marketing content — nothing extra to look after.

Web Software in other cities

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

Other services for this location

Let's work out what your site needs behind it.

Get a quote or open the service