Every engagement, and the record it leaves.
11 engagements · 7 public sector
The complete register: what kind of institution, what came out of it, and whether it sits inside government. Naming a client is their decision, not ours. Reference contacts go out on request.
- 01
Regulated financial institution
Verifies a new customer in under ten seconds at above 90% match accuracy, on a flow the financial regulator cleared before it went live.
Regulated - 02
National sporting venue
Moves 20,000 people through the gates at 500 ms a scan, with anti-passback fraud prevention on every turnstile.
Public sector - 03
Central government agency
Handles citizen requests with a complete audit trail, on an architecture built to survive an audit two years later.
Public sector - 04
National police service
Case and resource administration on government-grade architecture, with every consequential action written down.
Public sector - 05
City council
Vendor registration and permit administration, replacing a paper register with a record that can be queried.
Public sector - 06
National transport sector
Owners, conductors and associations on one system, so the route data exists in the same place as the money.
Public sector - 07
Regional intergovernmental summit
Delegate accreditation and attendance, captured at the door rather than reconciled afterwards.
Public sector - 08
Municipal parking operator
Runs a city's parking with no paper and no cash, from bay tracking through to mobile settlement.
Public sector - 09
National holding group
Quotation and procurement workflow, with the approval chain recorded as it happens.
Private - 10
Events and retail operator
Sells tickets online and across reseller tills on one pool of stock, on our payment and messaging rails.
Private - 11
Construction group, United States
Project tracking, scheduling and resource allocation off manual handoffs, reported into one executive view.
Private
Every one of these writes down something that was not written down before.
A permit register, a gate count, a case file, a route’s takings. Administration is what the system does; the record is what it leaves. That is the difference between planning against last year’s survey and planning against last month’s actual figures.
- What gets written
- Who asked, what was asked for, which gate allowed it, what came back, and when. The same trail that satisfies an audit is the one that answers a planning question.
- What it answers
- Where demand actually is rather than where it was assumed to be. Which offices are slow. Which routes carry the volume. Which months move. Questions a ministry currently answers with a sample.
- How it is delivered
- Built into the system from the start, not sold back afterwards as a reporting module. You own the data, and the export is a term of the contract.
Administration is what it does. The record is what it leaves.
Every engagement above writes down something that was not written down before. What that is worth is easier to see than to say.
Swipe to see the whole drawing
Bring the objections. A technical review puts your engineers and ours on the architecture, the data boundary and the integration surface, before anything is scoped.