Solutions / SMEs
We start with one problem and one system in production, and you decide what comes next.
These scenarios are illustrations. None of them describes a client.
Retail and e-commerce
What we would build
A content pipeline that turns supplier data into product pages in German, French, Italian and English, following your tone guide and glossary. Editors review each batch side by side with the source data before publishing.
Mistral, Akeneo API, Python
Retail and e-commerce
What we would build
Daily demand forecasts per store and product that account for cantonal holidays, weather, promotions and local events. Planners get suggested order quantities with the main drivers listed, and the models retrain on a weekly schedule, with accuracy tracked per store.
LightGBM, dbt, Airflow, MLflow
Retail and e-commerce
What we would build
A hybrid search that combines keyword matching with multilingual semantic search over the catalogue, so a query finds the right products whatever the language or wording. It runs next to the current engine and is tuned on real search logs.
OpenSearch, BGE-M3, Python
Watchmaking and luxury
What we would build
An intake assistant that reads the photos and the client's description, finds similar past repairs and drafts a preliminary quote with the likely operations and parts. A watchmaker validates or corrects the draft, and each corrected quote joins the examples used for the next ones.
PyTorch, FAISS, FastAPI, Salesforce API
Pharma and life sciences
What we would build
A literature agent that queries PubMed every week for each team's topics, screens abstracts against their criteria and sends a short digest with links and the reason each paper was kept. Scientists rate the picks, which tunes the next week's screening.
PubMed API, BGE-M3, LangGraph, Microsoft Teams
Most SMEs start with one process that takes too long. We pick it with you, build on the tools you already pay for, and keep running costs visible from the first estimate.
One engineer from our side and one person from yours who knows the process and can test the results.
A fixed price for a defined scope, with hosting and model costs estimated per month before we start.
Usually the owner or a manager decides, so a project can start soon after the first call, once the scope is agreed.
A tool your team uses on real work, typically within a few weeks.
No. We build, deploy and document the system, and train the people who will use it. Support afterwards is available if you want it.
We estimate hosting and model usage up front, so you see the monthly cost before you commit. A small server or a pay-per-use API is often enough at SME volumes.
Yes. Most projects connect to existing tools such as your shop, ERP, CRM or document storage through their APIs.
Sometimes, for the research side. Innosuisse and cantonal programmes can fund work done by a Swiss research institution; our own work is billed separately. We can tell you whether your project fits.
We start with a feasibility study on your own data, so you see results before anything is promised.