How we work
An architecture firm's engagement, not a software purchase
An architect does not move into the house. They understand the site, draw the plans, stay close during construction, and leave you with a building and the drawings for it.
If you buy software
You start next week, which is genuinely valuable. You also accept someone else's definition of what the watching should do, and their roadmap for how it changes.
When their priorities move, yours move with them. When they are acquired, you find out what that means at renewal.
If you commission a one-off build
It is fully yours, which matters. It is also designed from scratch, at integrator rates, with no accumulated body of patterns behind the decisions.
Every hard question — what the system may decide alone, what happens when it is wrong — gets answered for the first time, on your budget.
We sit between those. The frameworks were designed once, across many engagements, and are adapted and owned by each organisation that uses one.
Stage One
Three to five weeks
We come and look at the ground
We spend time with the people who actually watch your territory — the field staff, the duty officer, the analyst who assembles the numbers before a board meeting. We ride along where we can.
What we are looking for is where attention runs out. Which locations get visited because they are due rather than because something happened. Which findings die in an inbox. What everyone knows and nobody has written down.
What you hold at the endA written account of how attention currently gets allocated, including the parts that are nobody's fault and everybody's problem.
Stage Two
Six to ten weeks
We design the architecture
This is the drawing stage. We define the specific watching roles, what each one reads, what each is permitted to conclude on its own, and the exact point at which it hands a decision to a named human role.
We write it in your vocabulary — parcels, basins, line miles, claims, service territory — because the people who have to approve it are not technologists and should not have to become ones.
The governance answers are written here, not afterwards. Every role gets a stated limit, an accountable person, and a way to be switched off.
What you hold at the endThe plans: role definitions, decision boundaries, handoff design, data assumptions, governance rules, and an honest list of what we could not resolve.
Stage Three
Your schedule
Your team builds it — with us alongside if you want that
Some organisations take the plans and build internally. Some ask us to sit with their engineers for the first stretch. Some contract a builder they already trust and use us to review the work against the design.
All three are normal. What does not happen is us building it and keeping the keys.
What you hold at the endSomething running in your environment, built by people who will still be there next year.
Stage Four
Ongoing, without us
You keep it
Models change. Vendors get acquired. Your priorities shift after an election, an acquisition, or a bad season. When that happens you are editing documents you own, with a team that understands why each line is there.
We are available for a redesign when something big changes. We are not a dependency for the ordinary kind of change.
What you hold at the endA capability that does not have our name on the renewal notice.
What we are honest about up front
Sometimes the finding is that you are not ready. If nothing is being observed on the ground yet, no design will conjure observations, and we will say that in week two rather than month five.
Sometimes the finding is that a spreadsheet and a phone tree already work, and the honest recommendation is to leave them alone.
And we do not know how the underlying models will behave in three years. Nobody does. That uncertainty is a reason to own your plans rather than rent someone's product.