Custom AI development
MS Labs designs and builds complete AI systems. Calling an API is the small part: the work is in custom harnesses and pipelines around the models, with triage, evidence checking, evaluation against human judgment and an audit trail.
What is custom AI development
Getting a language model to answer questions is easy. Getting it to produce results a company can trust, every day, at scale, is engineering. The difference is the harness: the system around the model that decides what goes in, how the work is split into steps, which model handles each part, how output is validated and how quality is measured.
MS Labs designs and builds these systems from scratch, for each client's problem. Calling an AI API is a small part of the job.
When the AI needs to work with the company's data and processes, it becomes part of a custom-built system.
How we build AI you can trust
These principles come from systems we have put into production:
- A pipeline of steps, not one giant prompt. Each step does one job. A fast, cheap triage model filters out what can't be analyzed before the expensive analysis runs.
- Full context where absence matters. Similarity search can't find what didn't happen. When the costliest mistake is a missing step, the model needs to see the whole method, not just the similar passages.
- Verified evidence. Every claim that cites a source is checked against that source. No proof, no score.
- Math in code. The model judges; the system computes. Scores, weights and totals are never left to the model.
- Immutable versions. Prompts, rubrics and knowledge bases are versioned, and every result records the exact configuration that produced it.
- Measured against human judgment. A golden set scored by experts measures every change, so you know whether it got better or worse.
- Data is not instructions. Analyzed content is never treated as a command, which blocks manipulation through the content itself.
- Humans have the final word. Review, disputes and manual overrides are part of the flow, and every correction becomes calibration data.
What you get
- Custom harnesses and pipelines for analysis, classification, extraction and generation with language models;
- Tool-using agents that query your systems and data with limited permissions;
- Knowledge bases built from documents, audio and video, with transcription and curation;
- Continuous evaluation (evals) with a golden set and a drift dashboard;
- Audit views that show why every result came out the way it did;
- Assistants and automations for support, operations and sales;
- Cost control per step and per model, with the right model chosen for each task.
For a concrete example, see the sales call analyzer case study, a pipeline that transcribes, audits and scores recordings against the client's own methodology.
How it works
- Discovery. We define the task, the available data and how to measure whether the AI is right.
- Proof of concept. A short test on real data to validate quality before investing in the full system.
- Proposal. Scope, timeline and price in writing, including an estimate of model usage cost.
- Harness build. Steps, validation, versioning, evaluation and auditing.
- Operation. We track quality, cost and failure cases, and recalibrate against the golden set.
Technology
| Layer | Technologies |
|---|---|
| Models | OpenAI, Anthropic and others through OpenRouter, chosen per task |
| Orchestration | Node.js (NestJS), Python, job queues |
| Data | PostgreSQL, cloud storage for media |
| Infrastructure | Cloudflare, Oracle Cloud, Hostinger, Dokploy |
| Integrations | MCP, APIs, webhooks, WhatsApp |
| Interfaces | React, Next.js, Flutter |
How much an AI project costs
AI projects have two costs: development, a fixed price for a defined scope, and model usage, which varies with volume. The proposal estimates both. A good harness also lowers the second: cheap triage before the expensive step and the right model for each task.
Starting with a proof of concept is the cheapest way to find out whether AI solves your problem. Tell us what you need.
Frequently asked questions
What is an AI harness?
It is everything around the language model: how data comes in, which steps run and in what order, which model handles each task, and how answers are validated, measured and audited. The model is one part; the harness is what makes the result reliable.
Do I need to train my own model?
Almost never. The gains come from the harness: splitting tasks, giving each step the right context, validating output and measuring quality. Training a model from scratch is expensive and rarely necessary.
How do you know the AI is getting it right?
We build a reference set scored by people (a golden set) and measure the AI against it every time a prompt, rubric or model changes. Tuning without measurement is guessing.
Can the AI make things up?
It can, so the system checks what it claims. Citations are verified against the source, math runs in code, and when there is no proof the answer is flagged for human review instead of being delivered as fact.
Is my data safe?
During discovery we define what can reach the model, we isolate each client's data in the database, and analyzed content is treated as data, never as instructions, which blocks manipulation attempts.
Do you build agents that use tools?
Yes. Agents that query databases, APIs and internal systems through defined tools, with limited permissions and a log of every action.