One platform to run a government's back office.
A First Nation government in British Columbia was running its Infrastructure department on manual processes — invoices keyed in by hand, approvals chased over email, and no single system connecting the work to what it cost. We built one operations platform that does all of it.
A back office held together by hand.
The Infrastructure department of a First Nation government in British Columbia ran its back office by hand. Vendor invoices arrived by email and were keyed in manually. Approvals were chased over email threads. Work orders, costs, invoices, and budgets lived in separate places, so no one could see a job from dispatch through to the dollar it spent.
Off-the-shelf software didn't fit. A band government's workflows — its approval chains, its funding sources, its accounting — aren't the workflows a generic SaaS tool assumes. They needed a system built around how the department actually operates, not the other way around.
One system, built around how the department works.
A single platform with a shared core, so each capability connects to the next instead of becoming another silo.
One platform, not eight tools
Rather than stitch together separate apps, we built a single operations platform with a shared core — identity, work items, notifications, scheduling, documents, audit, and AI services. Each new capability inherits that machinery instead of rebuilding it, so the department's data stays connected end to end.
AI invoice intake & contract matching
Vendor invoices arrive by email and are read by AI — vendor, amount, date, reference, and a confidence score — then matched to the right contract before a person ever touches them. Ambiguous matches are flagged for a human, and a bad reading never stops the batch.
Approvals, roles & secure sign-in
Multi-step approval chains with amount tiers are enforced in software, not in inboxes. Role-based access controls who can see and do what, and staff sign in with a passwordless email link — no passwords to manage, no shared logins.
Work orders & accounting export
Work orders, cover memos, and send-to-accounting packages move approved spend into the department's accounting system cleanly. Verification pages — internal and public — let anyone confirm a record is genuine without exposing the system behind it.
Fund & grant roll-up
Spending is tracked two levels deep — from the funding source down through the ledger to the individual contract — so the department can answer, at any moment, how much of a given fund or grant has been committed and against what.
Built to last
Every change runs through automated tests against a real database and an automated code review before it ships. The AI is model-agnostic — the provider can be swapped by configuration alone — and Xerad hosts and operates the whole system.
From manual and scattered to automated and connected.
Invoices handle themselves first
Invoices are captured, read, and matched to a contract automatically — before anyone opens them. Staff start from a clean, pre-filled record instead of a PDF and a keyboard.
Approvals you can trust
Every approval is enforced by the system and written to an immutable audit log. There's a defensible trail for who approved what, when, and against which budget — without anyone maintaining it by hand.
One connected operation
A job links to its cost, its invoice, and its funding source. The department sees its operations as one system instead of reconciling between spreadsheets and tools.
Delivered department by department
We shipped a working pipeline in the first build window and expanded from there — one shared platform growing capability by capability, rather than a big-bang rollout.
Have an operation worth systematizing?
If your team is running on manual steps and disconnected tools, tell us what the work looks like. We'll come back with a short read on whether it's a good fit and what a first engagement could look like.
Start a conversation →