Skip to content
SOAVM Tech logo

Data & AI

AIwhoseanswerscanbetraced,testedandgoverned.

We build data platforms, pipelines, analytical products, applied machine learning and agentic workflows with automatic lineage, evaluation floors, drift monitoring and recorded human control.

  • Read/Summarise
  • Draft/Propose
  • Act with Authorisation
  • Bounded Autonomy
  • Read/Summarise
  • Draft/Propose
  • Act with Authorisation
  • Bounded Autonomy
  • Read/Summarise
  • Draft/Propose
  • Act with Authorisation
  • Bounded Autonomy

Who this is for

The situation that makes this urgent

The mandate and boundaries below come directly from the approved service catalogue.

Three ways to engage

Assess, Transform, Operate

Each package has a defined duration, retained outputs, commercial model and objective exit criterion.

  1. Assess

    Data estate and AI readiness baseline.

    Duration
    2 weeks; 3 for 5+ sources
    What you keep
    Source inventory, quality measures, lineage gaps, governance register and ranked use cases
    Commercial model
    Fixed price
    Exit criterion
    Client accepts baseline, register and roadmap
  2. Transform

    Platform and applied AI build.

    Duration
    10 weeks – 9 months
    What you keep
    Data contracts, pipelines, quarantine, lineage, evaluated models and governed agents
    Commercial model
    Milestone-billed
    Exit criterion
    Lineage proven and every model passes its floor
  3. Operate

    Managed data and model operations.

    Duration
    12 months minimum
    What you keep
    Pipeline SLOs, drift reporting, retraining cycles and unit economics
    Commercial model
    Monthly by pipelines, models and tier
    Exit criterion
    Renewal, transition or governed retirement

Capability detail

The technical substance, on the page and not behind a form

The operating capabilities and controls that define this practice.

Technical standard

Requirements that apply to every engagement

Must and should requirements from the board-approved practice standard, made visible before a conversation.

  1. Validate schemas at ingestion and quarantine invalid payloads with rejection reasons.

  2. Generate lineage automatically from ingestion to every published metric.

  3. Place every model behind an evaluation harness, performance floor and drift monitoring.

  4. Enforce absolute client data isolation, including prompts, outputs and derivatives.

  5. Record human review before consequential financial, legal, clinical, employment or regulatory actions.

  6. Publish a model card for every production model.

  7. Classify sensitivity and residency at ingestion and enforce placement technically.

  8. Version data contracts with source owners and fail pipelines on breach.

  9. Make published figures reproducible from versioned code, data and execution environment.

  10. Report inference cost and cost per successful outcome quarterly.

Engagement gates: Discover and Design passed, Deliver in progress, Operate upcoming

How we work

Four phases. Objective exit criteria.

A gate passed on assertion has not been passed. One exit criterion per gate is shown here; the full set sits on each practice page.

  • Discover

    Workload profile, dependency map and recovery objectives written down and signed off by the client owner.
  • Design

    Target architecture reviewed against the vendor-supported pattern for the engine in question; failure modes enumerated.
  • Deliver

    Recovery tested from backup within the stated RTO, evidenced by a timestamped test record.
  • Operate

    Runbooks in place, rota published, first quarterly service review held with measured figures.

The boundary

What we do not do

A capability list without explicit limits is only marketing.

  1. Out of scope

    Training foundation models from scratch or operating a research laboratory.

  2. Never autonomous

    Irreversible financial, legal, clinical or employment action without human authorisation.

  3. Data boundary

    No data brokerage or personal-data enrichment without evidenced lawful basis.

Evidence

The artefacts that make the claim testable

Evidence replaces unqualified promises and unattributed metrics.

Get started

A readiness baseline separates valuable, feasible AI work from demos that cannot survive production governance.

You keep the written baseline whether or not we continue together.