AI products people ask for now. Software you own.

We put current models into live workflows and hand over the product. We can take the shapes below even when we do not have a public case for every one. We do not sell six named packages.

What we can build

Shapes of job. Not a catalogue. If the brief mixes more than one, that is still this page.

  1. 01

    Private knowledge

    Ask over your files, with sources. Search and answers as a product your staff can run — not a chat window on our site.

  2. 02

    Assistants that do work

    Draft, file, route, update the system you already use. A chat box that does nothing in your tools is not the job.

  3. 03

    Voice and meetings

    Speech in. Notes, actions, and a record out. On the machine or in a product you own.

  4. 04

    Vision on cameras you have

    Detect, locate, alert on feeds you already operate. Operations get something they can act on. Not a demo reel.

  5. 05

    Generation inside a tool

    Quizzes, slides, documents, copy — as a feature of software people already use. Not a public toy.

  6. 06

    Extraction

    PDFs, forms, invoices into structured data your team can run. The model is the means. The records are the product.

How we take the job

  1. 01

    You own the result

    The software, the accounts, and how it runs are yours. We do not keep the model as our product.

  2. 02

    We say where it runs first

    Your machines, your cloud, or ours. Licences and data stay in the scope we sign — before we write it.

  3. 03

    Current models when that is honest

    Retrieval, APIs, and existing models when that is the right path. We train when the brief needs it. We say which.

  4. 04

    Not a wrapper

    We will not ship a public chatbot with your logo and call it done. The workflow has to move.

Before you send

Do you have a case for each of these?
No. The named work at the end is what we can show. The list above is what we can take. We would rather say that than invent screenshots.
What do I attach?
The workflow, the files or cameras you already have, and what a correct result looks like. A sketch is enough.
Will you train a model from scratch?
When the brief needs it. Often the job is to put an existing model into your data and ops — which is still engineering.
Who owns it?
You. The software, the accounts, and how it runs. Model weights follow the licence the brief requires — we say that up front.

If the job is a model in a live workflow, send that brief.

Send a brief