Industries
Every industry has work that should run itself.
We build the software that carries a sector's paperwork, and our engineers install it inside the systems you already run.
An isometric drawing of a city block with seventeen small buildings, one for each sector: a hospital with its ambulance bay, a bank with its columns, a factory with a sawtooth roof, a depot with dock doors, a warehouse, a building site with a crane, a hangar with an aircraft tail, a school with its bus, a laboratory, an office with a reception awning, a glass tower, a hotel, a restaurant with a striped awning, a shop front, a terrace of houses, a townhouse and a pharmaceutical plant with its silos, linked by orange pipes along the streets.
Each page follows one job through one sector's building, shows where a person still decides, and names the systems our software works inside. The sectors listed are the ones published so far.
How we work
Our engineers sit in your building.
Our engineers sit in your building and build agents around the work your people already do, inside the systems you already run.
An agent is software with a login to your systems and one task. It reads a form, a feed or a record, works out the next step, and writes the result back. It cannot do anything it was not given rights to do.
What every sector page shows
- The work as it runs today
- One job, step by step, and where a person decides
- Our engineers, room by room
By sector
The sectors, by the kind of work.
Operations and movement
Care and regulation
Service and property
Before you write to us
Five things managers ask first.
What we need from you
A room, an owner, and the people who do the work.
A room to sit in. A named owner for the outcome on your side. Read access to the systems in scope, granted by your IT team. The clerks, nurses, officers or operators who will show us how the work is really done.
What happens first
One job, mapped and run beside your people.
We follow one job through your building and write down what the agents may and may not do. Then one department runs with agents beside your people, and nothing goes live until that department says it works.
How it stops
Every workflow has a hold.
We build every workflow with a hold, and a held workflow waits for a person. Your IT team can stop the whole system, and your records are untouched when it stops.
How engagements are priced
Scoped around your workflows, agreed before we start.
Every business operates differently, so every engagement is scoped around its workflows, existing systems, integration requirements, deployment complexity, and operational needs. We begin by understanding the problem, define the engineering scope, and where appropriate, propose a focused pilot before expanding into a broader deployment. Pricing and delivery responsibilities are agreed before implementation begins.
Who is accountable
A named owner on your side, our engineering team on ours.
Our engineers work directly with your managers and your IT team, on site, remote or hybrid. Who owns which part, where a person approves and how the system is handed to your team are written down when the engagement is scoped. On your side a named owner holds the outcome. On ours the engineering team that builds it answers for it until it is handed over.
We don't automate the decisions a licensed or accountable person must make, and we don't start without a named owner on your side.
By job, or by delivery
Two other ways in.
Prefer to start from the job instead of the sector?
Every sector is delivered the same way: our engineers work inside your systems, on site, remote or hybrid, as the work needs.
Your sector isn't listed?
The method is the same. Tell us the desk and the paperwork.
Start
Tell us your sector,and its paperwork.
An engineer reads every enquiry and replies with questions, not a deck.
Name the desk, the form and the system it ends up in. That is enough for the first reply.