Skip to content
zinto

Zinto/Approach

The same five steps on every engagement

We are not the advisory firm that leaves you with an expensive PowerPoint. We sit with your business, get our hands dirty and implement the change.

Steps
05
Starts with
Discovery
Ends with
Handover to your team
Runs on
Your servers, on premises

Each step hands you something you keep

  1. Step 01

    Discovery

    An intro call on your objectives and goals, then we sit with your team to learn the business and how the work runs today. We agree the decision the system supports and the one metric that says it works.

    You get

    • How the work runs today, from sitting with the people who do it
    • The decision the system supports, and who owns it
    • One metric that says it works
    • A written list of what we will not build
  2. Step 02

    Ground the data

    We find where the data lives, who owns it and whether it reconciles, and plan where the data and the model will sit.

    You get

    • A map of each source system, its owner and its access path
    • Reconciliation checks between systems, with the breaks listed
    • A plan for where the data and the model sit
  3. Step 03

    Prototype and evaluate

    We build on your real data and score the output against an evaluation set from your own past cases before it carries load.

    You get

    • A working prototype on your own data
    • An evaluation set built from your past cases
    • Scores against a baseline, including where it fails
  4. Step 04

    Integrate

    It goes into the workflow and your systems of record, with review points where an error costs money, monitoring and an audit trail.

    You get

    • Integration into your systems of record
    • Review queues with confidence thresholds
    • Monitoring with Langfuse, OpenTelemetry and Grafana, and a full audit trail
  5. Step 05

    Operate and hand over

    We run it with your team, then hand over the code, the evaluation suite, runbooks and training. It is not finished until you are satisfied.

    You get

    • A period of running it together with your team
    • Code, infrastructure and the evaluation suite in your accounts
    • Runbooks and training for the people who own it

You own all of it at handover

Everything lands in your accounts, on your servers.

your-org / ai-system
├── src/       # The code, in your repository
├── infra/     # Hardware spec, build scripts, infrastructure code
├── evals/     # The evaluation suite and every result it produced
├── models/    # Model, prompt and data versions
├── logs/      # Logs and audit trail, in your monitoring
└── runbooks/  # Runbooks and the on call guide

The model and the data stay on your servers

On-prem AI deployment covers the build. An Australian cloud region is the fallback.

  1. DefaultServers in your building
  2. AlsoYour data centre or colocation
  3. AlsoBare metal GPU servers
  4. FallbackAustralian cloud regions

We design around the rules you answer to

Access control, logging and data location are set to match them.

  • 01Privacy Act 1988
  • 02APRA CPS 234
  • 03APRA CPS 230
  • 04AML/CTF Act 2006
  • 05ISO 27001
  • 06ASD Essential Eight

There are four ways to work with us

01Forward deployed teamInside your teamSenior engineers work in your systems and alongside your staff, from discovery to production.02Project deliveryFixed scope or time and materialsOne build scoped and priced up front, or billed on time and materials while the scope is still moving.03Advisory retainerMonthlySenior help on vendors, architecture, governance and board papers, with no build attached.04Build, operate, transferHandover at an agreed pointWe build the system and run it with your team, then hand over the code, the runbooks and the on call.

Tell us where your hours go.

We map the work, size the hardware and price what is worth automating.

Talk to our team →