Skip to content
OverviewMethodEngagementsOwnershipDecay
The engagement model

Understand, Build, Own. Start where you are.

Three structured engagement shapes, each with its own scope and sign-off. Fixed-fee discovery with an honest-verdict guarantee, scope protection, and a clear picture of what you own at every stage.

Phases 1–3 · Discovery Sprint · Solution Design · Project Plan

Understand

Before any money goes into a build, you need to know how your operation actually works — not the brief, the reality — and whether technology is the right answer at all. That is what Act 1 delivers.

Where every engagement starts

Discovery Sprint

We do not take a brief and design to spec. We spend time in the operation — talking to the people who run it, visiting the sites where it happens, and looking at the systems already in place. We are trying to understand not just what you want, but what the operation actually needs.

What you walk away with
Requirements specification — in plain language, no longer held in one person's head
Site assessment report — including the workarounds and constraints the brief never mentions
Constraints and assumptions register — every dependency surfaced before a build, not halfway through one
Feasibility assessment — whether technology is the right answer, and what kind

Typically two to four weeks, scoped to your operation.

Two reassurances, both genuine
The honest-verdict guaranteeA Sprint that concludes you shouldn't build is still a successful Sprint. You're paying for a straight answer, not a sales pitch.
Fixed fee, with scope protectionIf we underestimate work that was within the agreed scope, we absorb it — you never get a surprise invoice for our misjudgement.
Proof
For Air Environment, the knowledge and systems that ran a critical operation were trapped in a single person. We turned that into a detailed breakdown and a workflow map — the operation, finally on paper and readable by the people who depend on it.

Phases 4–6 · Field Prototype · Production Platform

Build

Act 2 is where we build. Hardware, software, automation — or all three. The scope comes from what we learned in Act 1. We build for the environment it will actually operate in, and we hand it over in a way your team can genuinely own.

Before you commit to the full build

Field Prototype

Prove the approach works in the conditions it will actually operate in. Not a lab demo — a working version in your real environment, tested against dust, vibration, connectivity loss, and access limits.

What you walk away with
Tested in your actual environment — conditions and all
A clear go / no-go decision before full investment
Early identification of the dependencies nobody thinks about until they break
Pre-tested before it goes to site — commissioning is validation, not the first switch-on
The full build

Production Platform

The complete system — designed, built, installed, validated, and handed over. Not just something that works at launch. Something your team can run, change, and recover without calling us.

What you walk away with
Installed, configured system — with full integration into what you already run
Documentation written as we build, for the people who will maintain it
Runbooks for common scenarios and known failure modes
Training until your team can operate, diagnose, and change the system without us
A signed handover certificate — not just a delivery

Phase 7 · Operations Retainer

Own

Act 3 is where most firms disappear. We stay. Systems drift, requirements change, people leave — Act 3 is the commitment to keep the system running and genuinely owned as the operation around it changes.

After handover

Operations Retainer

This is not a helpdesk. We monitor proactively, flag issues before they become visible problems, and keep the system evolving with your operation instead of quietly degrading away from it.

What you walk away with
A named point of contact at Slash Tech — not a ticketing system
Proactive monitoring — we tell you before something breaks, not after
Monthly reporting on system health and work completed
Scheduled maintenance — planned, not reactive
Ongoing evolution as your operation grows
Continuity over time
Year 0Ownership continues

Stabilise and document operational behaviour

Year 1Ownership continues

Reduce drift and refine rollout policy

Year 3+Ownership continues

Evolve safely without losing context

Which act are you in?

Most conversations start with a question, not a scope.

Bring the situation — mid-build, post-handover, or still deciding. Twenty-five minutes is usually enough to tell you which act you’re in and whether we’re the right team for it.

Book a Fit Call See the seven phases