Nina Labs
View this page as Markdown

Approach

How we work with you

We measure first, build in your environment, prove the result on real cases and then hand the system to your team. Here is what that looks like in practice.

01 Approach

Four phases, from map to run

Most projects move through the same four phases. The time in each depends on how many systems the work touches.

  1. 01 1–2 weeks

    Map

    We sit with the people who do the work, measure the current process and pick the tasks where an AI system can finish most cases end to end.

    • Ranked use cases
    • Baseline metrics
    • Architecture and risk notes
  2. 02 4–8 weeks

    Build

    We build the system in your environment: the agent or workflow, the tools, the permissions and the eval suite. Your engineers pair with us from day one.

    • Working system in your cloud
    • Eval suite from real cases
    • Tracing and dashboards
  3. 03 2–4 weeks

    Prove

    The system runs in shadow mode on live cases while people do the real work. We compare the results and fix what the evals and the traces show.

    • Shadow-mode results
    • Go-live criteria
    • Runbook and on-call guide
  4. 04 Ongoing

    Run

    We turn it on in stages, watch quality and cost, and re-run the evals on every model or prompt change. Then we hand it over to your team.

    • Staged rollout
    • Monthly quality and cost report
    • Handover and exit plan

02Engagements

Four ways to work together

Most clients start with an assessment or a build. The other two follow when the first system is live.

  • Assessment

    1–2 weeks · fixed scope

    We map one area of your business, measure it and tell you where an AI system would pay off, and where it would not.

    • Process and system review
    • Ranked use cases with business cases
    • Architecture and risk notes
    • A plan for the first build

  • Build

    6–12 weeks

    We build one system and take it through shadow mode to a staged go-live, in your environment and with your engineers.

    • The agent, workflow or pipeline
    • Eval suite and tracing
    • Runbook and on-call guide
    • Training for the team that will own it

  • Embedded team

    Quarterly

    Our engineers work inside your team on a shared roadmap, usually after a first build has shown results.

    • A roadmap agreed each quarter
    • Pairing with your engineers
    • Shared standards and code review
    • Monthly results review

  • Run and improve

    Monthly

    We watch the systems in production, re-run the evals on every model or vendor change and keep cost and quality on target.

    • Monitoring and incident response
    • Eval runs on every change
    • Cost and latency tuning
    • Monthly quality and cost report

03Principles

Our working principles

  • 01

    You own everything

    Code, prompts, eval sets, infrastructure definitions and documentation live in your repositories and your cloud accounts from the first day.

  • 02

    Measure before and after

    Every project starts with a baseline and ends with the same measurement. If the numbers do not move, we say so.

  • 03

    People approve what matters

    Irreversible actions go through a person until the evals and the production data show the system can do them alone.

  • 04

    No lock-in

    We choose models and platforms per task and build on open protocols such as MCP and A2A, so you can switch later.

  • 05

    Every engagement has an exit plan

    From week one we write down what your team needs to run the system without us, then we work through that list.

  • 06

    Small teams, direct contact

    You work with the engineers who build your system, not with a layer of account managers.

04 Standards

What every system we ship includes

These are part of the build, not extras. If one is missing, the system does not go live.

01 Evals
A suite of real cases runs on every change to prompts, tools or models.
02 Tracing
Every step, model call and tool call is recorded in OpenTelemetry format.
03 Approvals
Actions that move money, change records or contact customers need a person until the data says otherwise.
04 Permissions
Each tool has a written scope. Agents act with the user's rights or a narrow service identity.
05 Budgets
Cost, token and latency limits per run, with alerts before they are reached.
06 Hosting
Your cloud account or VPC by default. Open-weight models when data must stay on your hardware.
07 Models
Chosen per task on measured quality, latency and cost. Switching is a configuration change.
08 Ownership
Code, prompts, eval sets and infrastructure live in your repositories from the first day.
09 Handover
A runbook, training for your team and a written exit plan in every engagement.

05Security and data

How we handle your data

  • We work in your environment, under your access policies.
  • Client data is never used to train models. We use enterprise model agreements that exclude training on your data.
  • Production data stays in your accounts. We use anonymized samples for evals where possible.
  • We sign NDAs and data processing agreements before we see any data.
  • Access is removed at the end of the engagement and confirmed in writing.

Tell us which process you want to hand to an agent

A 30-minute call with an engineer. We will tell you whether an AI system is the right tool for it, and what it would take to run it in production.

Talk to an engineer contact@ninalabs.ai