Get a quote

AI Consulting · Basaksehir

AI Consulting for Basaksehir businesses

Paper does not stay clean beside a machine. Oil soaks in, the corner curls, and the rest gets photographed in the shadow of the housing. If what you hold is a skewed, stained image, the AI question in the machine shops and mould workshops along the Ikitelli line starts right there: could a model just read this pile? Our answer, from the cropping tool written for Vipkurum, is a divided one. Cutting stays with the side that measures, reading with the side that interprets, and neither takes over the other's job.

AI Consulting — Basaksehir

Machine building and mould work are dense in Basaksehir. If the paperwork that records them stays where it was made, it mostly stays on paper. The portfolio work closest to that fabric is Vipkurum's question cropping tool, and how far it reaches has to be said plainly: it was written for education technology. Reading a technical drawing, producing a measurement report or sorting workshop paperwork are not things we can show, and warehouse or dispatch work is absent from the portfolio too. What carries across is not a model choice but the division of labour itself. Underneath it sit Python and OpenCV for the image work, Google Gemini and OpenAI models for interpretation, Node.js and Laravel for the service and content layers, with records held in MongoDB.

  • Where a cut falls is decided by a measurable image processing step, and the language model cannot move that boundary.
  • Interpretation lives in a separate component, because wherever one input can yield two readings you are looking at a judgement, not a measurement.
  • The limit is stated too: this split held up on education content, and we have no verified work on workshop paperwork.

Why Algoriel

  • The image does the reading

    Vipkurum reads optical form marks with OpenCV from the image of the sheet, not through the optics of a reader appliance.

  • Cropping apart from judgement

    Image processing decides where a question begins and ends; the language model only binds the answer to it. The two jobs never mix.

  • Model output lands in a record

    Vipkurum writes the answer key into the cropped question's own record instead of keeping it as a separate document.

  • A person has the last word

    At Tahlil.com the model drafts the reading and a doctor approves what reaches the patient; an unapproved reading never appears on screen.

What we build

AI Consulting
  • Where no model is needed

    Marks on an answer sheet are read from the form image itself; the threshold that decides whether a bubble counts as filled sits in the code, and no language model runs in that step.

  • Splitting the job in two

    Computer vision sets the question boundaries; a language model then ties each answer in the key to its question. Cropping accuracy never rests on a model's interpretation.

  • Removing the hardware step

    Marking stops depending on a reader device; when the form layout changes, we adjust the reading service in software instead of ordering new hardware or device-specific forms.

  • Turning existing material into a pool

    A booklet page is split into individual questions, the answer key is written onto each question's own record, and the questions already on hand become the pattern for new ones.

  • Tying the output to a person

    At Tahlil.com AI prepares the first reading, a specialist physician writes and approves the interpretation, and responsibility for the text that reaches the patient stays with the physician who signed it.

  • Queueing the generation

    In Secretum text and images come out of two separate generation paths; image generation is not instant, so that work goes onto a queue, and the finished file is stored once instead of being regenerated in the feed. Secretum is the product we are building now.

Work like this

AI Consulting · Case study

Vipkurum question cropping — cutting left to measurement, reading to the model

Vipkurum works in education technology, and a page of its question booklet is separated into single questions. We split the job in two. Cutting sits with Python and OpenCV: a measured operation decides where a question ends, and that decision is never put to a model. Interpretation sits with Gemini and OpenAI: an answer from the key is attached to its question. Neither side reaches into the other: the model cannot shift a cut, and the image work does not settle meaning. Cropped images and records live in MongoDB; the Python service reaches Laravel through Node.js. The scope is education content, not drawings or shop paperwork.

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

  • We have years of workshop paperwork. Could a model be pointed at it?

    We cannot promise that. The work we can show ran on education content, over printed question booklets. We have nothing verified on technical drawings or measurement reports, and we do not make promises without evidence behind them. What we can discuss is the arrangement itself: which decisions are settled by measurement and which by interpretation.

  • Why not hand the whole job to one model?

    Because the two decisions are not the same kind. A cut boundary is measurable and repeatable; which question an answer belongs to is a judgement. Pile both into one place and the errors pile up there too, leaving you unable to tell which step went wrong.

  • Our photographs come out skewed and stained. Does this still hold?

    Image quality is the cutting step's burden, and repeatability is what matters there. At Vipkurum we worked from scanned booklet pages; oily paper shot on a phone at the bench is not the same condition. We do not judge it without measuring, so we start from a sample you send.

  • Would you not need to come and see the paperwork in the workshop?

    We keep no office, work fully remotely, and do not offer on-site support. Instead of visiting a floor, we work through a sample set you send and write down which step is measured and which is interpreted.

Let us look at which step needs a model and which one needs computer vision.