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

CRM · Basaksehir

CRM for Basaksehir businesses

Ikitelli in Basaksehir is machine and mould country. Where the measurement is discussed at the bench and the quote is typed in the front office, a sheet of paper travels between the two. Months later a buyer calls back, and what remains is a note about the conversation rather than the calculation itself. Calculator Resterm records it the other way round: projects sit under the buyer, and the items the calculation chose sit under each project.

Get a quote Tell us about your project

CRM — Basaksehir

The trade on the Ikitelli side of Basaksehir is machine building, and in that trade work arrives as a specification: dimensions, temperature and volume get discussed, and a product code appears last. In a shop like that, customer history is not who called when. It is which requirement produced which selection for that buyer. The work closest to this district's sector profile is Calculator Resterm. Where the evidence ends deserves saying: the software was built for choosing electric heaters. Campaign management, call logging and pipeline reporting are not things we can show. Laravel runs the workflow, MySQL holds the records, and the calculation screen was written in Vue.

  • Two jobs for the same buyer never collapse into one history; each carries its own project record, and the items hang beneath it.
  • The technical reasoning behind a quote stays inside the record, so when a figure is questioned the answer is not hunted for in somebody's memory.
  • The schema the software sits on is the maker's own product family, so a new option is defined from inside that structure rather than loaded as a list into a generic tool.

Why Algoriel

  • Booking, plan and invoice kept apart

    The dental CRM holds a treatment plan per tooth; an appointment attaches to a plan step, so moving the plan moves the calendar.

  • Request types split up front

    At Diotek a site survey and a service call are two separate flows and never share a form.

  • No second document

    Tahlil.com takes the values in and writes the specialist's reading onto the same record, so the result stays in one place.

  • History belongs to the equipment

    AlgoKlima keeps service history under the unit rather than the customer, so it travels with the unit when it changes hands.

What we build

CRM

  • A service plan that moves step by step

    A treatment or maintenance programme that runs over several sessions is kept as its own plan, separate from the bookings. In the dental clinic CRM the plan is built tooth by tooth and split into sessions spread over weeks.

  • Appointments tied to the plan

    Each appointment is attached to a step in the plan. When the plan changes or a session is added in between, the calendar updates with it.

  • Package and membership balances

    When you sell classes or services in packages, what a customer has left shows on their card. At Pilatesco a booking takes one class off the package, and cancellations and no-shows follow different rules.

  • Service history per device

    Warranty, maintenance and fault history for the equipment you service is kept against the device, not the person. At AlgoKlima three air conditioners at the same address keep three separate files.

  • History that survives a change of owner

    When a device passes to someone else, its history stays with the device instead of being retyped onto the new customer's card.

  • The work done and the invoice in one place

    The procedure sits on the customer's record, so what was billed and what was carried out are read from the same place and nothing is entered twice.

Work like this

CRM · Case study

Calculator Resterm — the customer record rests on the maker's product structure

Resterm manufactures electric heaters, and we built the software on the maker's own product structure rather than loading a list into a ready-made quoting tool. A user enters a heating requirement instead of a product code, and the software picks the heater that fits. On the customer side, projects sit under the buyer's record and the chosen items sit under each project. Two jobs for the same buyer never dissolve into one history, and which requirement produced a given line still reads back later. Laravel runs it, MySQL holds the records, and the calculation screen is Vue.

Read the case study →

Working with Basaksehir 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 you have an office in Basaksehir, or someone who visits the workshop?

    No to both; we work entirely remotely. The first session happens over text rather than on a shop floor, writing down how your product family is actually distinguished.

  • Our product family is already in a catalogue. Could we not load it into an off-the-shelf CRM?

    A list can be loaded; a rule cannot. A ready-made tool carries line items but does not know which measurement produces which product, so that knowledge stays on one person's desk. When the schema comes from the maker's product structure, the selection is produced inside the record.

  • We do several jobs for the same firm. How does the history stay separate?

    Items hang off a project rather than the buyer directly, and the buyer record carries the projects. Two different jobs never merge into one list, and nobody sorts out which line belonged to which job at month end.

  • Resterm makes heaters and we make moulds. What actually transfers?

    Not the sector, but where the record sits. Replace a heating requirement with cavity count, material and tolerance and the question holds. If the software rests on your own product logic, the reasoning behind a quote lives in the record; if it does not, it lives in a spreadsheet again.

CRM in other cities

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

Other services for this location

Want to bring your customer tracking into one system?

Get a quote or open the service