ApproachAssess / Design / Build / Hand over

Start with the decision. Build what it depends on.

Every engagement follows the same path, scaled to the problem. The people who design the system build it, and everything runs in accounts you own.

The path

Four phases, each with something you can keep.

Each phase ends with a deliverable that is useful on its own. You can stop after any of them and still have something of value.

  1. 01

    Assess

    We map your systems, data flows and the decisions they need to support, and agree on what success looks like.

    You get
    A written assessment and a phased, costed plan.
  2. 02

    Design

    We recommend the simplest architecture that serves those decisions, and are clear about what we would not build.

    You get
    An architecture, agreed definitions and a fixed scope.
  3. 03

    Build

    We deliver in working increments against your real data and workflows, not a big reveal at the end.

    You get
    Working pipelines, models, reports or workflows.
  4. 04

    Hand over

    We validate, document and train your team. Code, infrastructure and credentials stay in your accounts.

    You get
    Runbooks, training and a system you control.

Engagements

Scoped to the problem, priced before we start.

Most start here

Fixed-scope assessment.

A fixed price and a written deliverable that tells you what to build first and what it would cost.

Then

Phased build.

Larger work is split into phases. Each one has its own scope and price, agreed before it starts.

After handover

Ongoing support.

Monitoring, changes and new reports, when you want them, on terms agreed with you.

What we deliver

  • 01
    Data platform

    A warehouse or database in your own cloud account, with access control and backups.

  • 02
    Tested transformations

    A version-controlled repository of data models with automated quality checks.

  • 03
    Reporting

    Dashboards and recurring briefs built on documented definitions.

  • 04
    AI workflows

    Search, extraction or supervised workflows, each with an evaluation on your data and an agreed approval boundary.

  • 05
    Runbooks and training

    Architecture diagrams, operating guides and walkthroughs for the people who will run the system.

Principles

  • Decision before tooling.
  • Definitions before dashboards.
  • Evaluation before deployment.
  • Your systems, your accounts.

Next step

Start with an assessment.

Tell us what you are trying to understand, fix or build. We will reply with a proposed scope and a fixed price for the first phase.

Start with an assessment →