4–6 weeks
AI assistant MVP
A working assistant on your data, ready for pilot users.
Turn GPT, Claude or Gemini into a product: AI apps, assistants and LLM integrations built on your data and workflows. Senior team in Kosovo, MVP in weeks.

We turn large language models like GPT, Claude and Gemini into focused products: AI assistants, copilots inside your app, document Q&A over your knowledge base, and automated workflows. We add the guardrails, retrieval and cost controls that separate a product from a prompt.
4–6 weeks
A working assistant on your data, ready for pilot users.
8–12 weeks
AI actions embedded in your existing app and workflows.
3–5 months
A standalone AI product with billing, accounts and analytics.
An LLM app is mostly ordinary product engineering with one unpredictable component in the middle. We design around that component first, then build the product around it in thin, usable slices.
01
Sitting with future users of the app, we write down the inputs a user brings, the artefact they expect back, such as a drafted letter, a filled form or a sourced answer, and what they do with it next. That contract shapes prompts, screens and test cases, and settles whether the task is narrow enough to ship.
02
Two or three models from OpenAI, Gemini or open-weight families work through the same real tasks. We compare output quality, time to first token and cost per completed task, then choose a primary model and a fallback. You get the comparison table and an estimate of model spend per active user.
03
Sign-in, one complete flow, streamed responses, a rating control on every output and usage logging, deployed to a staging environment your pilot users can open. This is the scope of the 4–6 week assistant MVP, and it ends with a choice: widen the scope, swap the model, or stop.
04
Workspaces with data isolated per customer, plan quotas and rate limits, abuse filters, provider failover, subscription billing where the app is sold, and an admin screen where your support staff can see a conversation and the sources behind each answer. Everything runs in your repositories and cloud accounts.
05
Each week we review low ratings, heavily edited outputs and abandoned sessions. Failures turn into new test cases, prompts and retrieval are adjusted, and cheaper models take over steps where quality holds up. One dashboard shows answer quality, response time and margin per plan.
Build work is billed at €45–65 per engineer-hour or as a squad from €15k a month, and a clearly defined first version can be a fixed-price MVP from €15k. Every AI app also carries a running cost per request, so we plan the build and run budgets side by side.
Plenty of teams can connect a chat box to a model API in a day. Use these questions to find out whether a vendor can build an AI app that keeps both its users and its margin; we expect to answer them too.
The questions your legal, security and finance teams will ask, answered before the first line of code.
It depends on quality, latency, cost and data rules. We usually benchmark two or three models on your real tasks and keep the app model-agnostic so you can switch later.
We ground answers in your sources with retrieval, show citations, constrain outputs with tools and schemas, and test against an evaluation set before release.
We estimate cost per conversation during design and add caching, model routing and usage limits so running costs stay predictable.
It can be. A thin layer over a public model is easy to copy and exposed to the provider adding the same feature. Products that last own something around the model: proprietary or customer data, a workflow fitted to one profession, integrations with the tools people already use, and feedback that improves results over time. We help you check which of these you have.
Yes, and many should. A small, fast model can classify the request, a stronger one can write the answer, and an embedding model handles search. Routing by task keeps quality where it matters and lowers cost elsewhere. All of them sit behind one internal interface, so changing a provider means a configuration change and a test run.
If you have product engineers with spare capacity, building in-house keeps knowledge close. An outside team helps when you need the first version quickly or lack experience with evaluation and running costs. Many clients combine the two: our engineers work alongside theirs, then hand over the code, prompts and test sets.
Tell us what you need to build or scale. You will get a proposal and estimate within 24 hours.