What we do

Built to work.

AI, custom models, automation and software. From research and prototypes to complete production systems.

What we build

AI, put to work.

Agents, retrieval and tools built around your use case.

01Applied AI02Automation03Model engineering04Software

For research, business and industry.
The problem sets the direction.

Services

What the work includes.

01Applied AI

A model is not a system. We build the system around it.

A capable model on its own produces plausible output and no accountability. The work is everything around it: how context is retrieved, how output is constrained, where a person reviews, what is logged, and how you notice the day it starts getting worse.

Retrieval
Your own sources, indexed, ranked and cited
Evaluation
A held-out set, scored automatically on every change
Guardrails
Constrained output, refusal paths, escalation to a person
Observability
Every call traced: latency, cost and outcome

What we decline. We do not put an unreviewed model in front of a customer where an error is expensive.

Discuss a project
02Model engineering

Start with the task. Measure what the model needs to do.

Small language models, fine-tuning and custom training for your use case. We work with your data and constraints, compare approaches against a useful benchmark, and build the serving and monitoring needed for production.

Data
Preparation, versioning and a held-out evaluation set
Training
Fine-tuning and model adaptation for the task
Evaluation
Accuracy, latency and cost measured against your baseline
Deployment
Serving, integration, monitoring and a documented handover

What we decline. The data and evaluation determine what we can promise.

Discuss a project
03Automation

Remove the handling, keep the judgement.

Most operational time is spent moving information between systems that will not talk to each other, and checking that the move worked. We automate the deterministic hand-offs and route the genuine exceptions to a person with the context already assembled.

Process map
Every hand-off, owner and failure mode, written down
Integrations
Typed, retried connections that never post twice
Exception queue
What could not be handled, why, and who owns it
Reporting
Scheduled, versioned and reconciled against source

What we decline. We do not automate a broken process. If the workflow is wrong, we fix it first and say so.

Discuss a project
04Software from end to end

Built around the job, not the database.

Customer products, research tools, internal platforms and the infrastructure behind them. We design the experience, build the application and data layers, and take the system through deployment and handover.

Data model
One record that matches how the business speaks
Access
Roles, least privilege and a review that happens
Audit
Who changed what, when and from where
Interfaces
Keyboard-complete, accessible, built for volume

What we decline. We do not ship a screen we have not watched somebody use.

Discuss a project

From first conversation to handover

A clear way forward.

1–2 weeksStage 1 of 5

We map how the work really runs.

We sit with the people doing the work and record the real sequence, workarounds included. The output is a written map of every hand-off and machine that matters, the volume through each, and where time and money are actually lost.

What you receive

Operational map · Constraints · Ranked opportunities

Working together
Ownership
You own the code, the data, the models and the infrastructure accounts throughout. No lock-in clause and no proprietary runtime.
Estimates
Fixed scope and fixed price after the specification. If we are wrong about the effort, that is our cost, not yours.
Access
Least privilege. We hold the narrowest credentials that let the work proceed, and they are revoked at handover.
Confidentiality
Your operation is never a case study unless you ask for it in writing.