Anyone can generate. The work is what comes after.

Text, code, content — the first draft has become cheap. This page is about what counts afterwards.

The commodity is cheap

A subscription and a prompt, and the draft exists: the text, the code, the image. The step from idea to first result costs next to nothing now — and so it says little about whether anything good comes out in the end.

The hard part comes afterwards: four jobs that are not add-ons, but the work itself.

  • Privacy Where does the data stay — yours and your customers’?
  • Reproducibility Will the same job return the same result tomorrow?
  • Sound, secure code Generated code is code: it ships in the system and has to be as secure and as good as any other code.
  • The seam Where does the machine end, where does code begin that computes instead of guessing?

Models are a commodity. Architecture is the craft.

On the device, inside your own records, or agentic with a threshold. Three products, three answers to one question: how much machine does this job take?

01

On the device

Jone

Jone turns “next Friday at nine at mum’s” into a time, a place and a person, on the phone itself. No server, no per-call bill, no question about where the data sits.

The price is size: whatever ships inside the app cannot outweigh the app. So you cut the task down instead of scaling the model up.

02

Much machine, clear sign-off

kofel Studio

The co-pilot is allowed to work far: create leads, maintain customers, read receipts, straight in the system or over MCP. The boring parts get so fast you stop noticing them. But the sensitive things sit in the same system: customer data, quotes, invoices. One mistake there costs more than every saved minute combined.

So it stays traceable who touched what, and everything critical sits behind a human sign-off. A quote doesn’t go out and an invoice isn’t booked until someone says yes. And the data stay where they belong: processed in the EU, under GDPR. Full speed on the bulk, a person as the last step on everything that counts.

03

Small models, narrow jobs

Lithify

Lithify doesn’t run one general-purpose machine but a row of small models, each cut for one job: one screens out spam and prompt injection, one groups reports by meaning, one writes the code at the end.

A small model with one job and a known limit delivers better, reproducible results. When one misses, you know which. Hence the threshold per project: above it the agent carries on, below it a person. Just enough machine to make the result reproducible, bounded clearly enough to say where it stops.

04

Not always the right choice

Totals, deadlines and balances are computed, not estimated. A guessed number looks exactly like a right one. Searching by label and status is a database query. And anything legally binding is written by a person.