This engagement is confidential. We share the pattern, the architecture, and the outcome.
The pattern
A state government department was replacing the legacy systems that perform $1B+ in contract validations and funding request approvals.
At the heart of these systems sat thousands of business rules - hardcoded in SQL and stored procedures, invisible to business users, and increasingly difficult to maintain. The department needed a centralised, auditable business rules service that could be shared across three core systems being built as part of the transformation programme. The solution supports hundreds of registered service providers submitting regular funding approvals, requiring the ingestion of millions of rows of reference and transactional data and hundreds of complex, matrixed validation rules. Some of those organisations submit millions of funding requests per month.
The solution
The solution provides a centralised no-code rules engine serving three domains: contract management, activity validation, and payment processing. Enterprise-grade architecture supports clustered production environments, batch processing at scale, reference data management, and full business event logging for auditability.
Business users can see, understand, and modify the rules that govern their domain without developer involvement.
The outcome
- A competitive win through a structured government procurement process.
- Thousands of lines of hardcoded logic replaced with visible, auditable, manageable rules.
- Three core systems served from a single centralised rules service.
- Full traceability - every rule execution logged with inputs, outputs, and the rule version applied.
Key facts
See more of our work in Government →
What this demonstrates
Let's talk about your version of this.
Every engagement starts with understanding the problem. If something here resonates, we'd like to hear about yours.