Capabilities
We work in four areas. Most engagements combine two or three of them. The same engineering team delivers all four, on both our US federal and international development pathways.
Every release passes automated regression testing. Systems ship with observability, defined recovery targets and runbooks. Deployment is automated and repeatable. Code and documentation are handed over, not withheld.
Government information systems and MIS
This is our core track record. We build the systems that ministries and agencies use to plan, appraise, approve and monitor public spending.
What it covers. Public investment management, project banks, appraisal tooling, parameter databases, monitoring and evaluation, and integration with finance and budget systems.
Typical engagements. A new project bank for a ministry of finance. A submission and approval workflow with decision gates. A public database of economic parameters. A monitoring module that reports on implementation across agencies. Replacement of spreadsheet-based processes used across central government and public bodies.
What you get. A working system with a documented data model and a workflow engine configured to your procedures. It includes administration tools, and a public portal where one is needed. You also get the source code, deployment scripts, user documentation and training for your staff.
In delivery. Automated regression tests cover the submission, appraisal and approval paths before each release. We instrument the system so your team can see usage, errors and processing times. We agree recovery targets with you and write the runbooks that meet them.
Platform engineering and modernization
We move systems that are already in use onto architecture that can be maintained. The people who depend on them keep working throughout.
What it covers. Legacy to modern architecture, cloud deployment, reliability engineering, observability, automated delivery pipelines and security hardening.
Typical engagements. Breaking up a monolithic application in stages. Moving a self-hosted system to managed cloud infrastructure. Introducing an automated test suite where releases are tested by hand. Building a delivery pipeline so a release takes minutes rather than a weekend. Hardening a system before an audit or a new user group.
What you get. A migration plan with stages that can each be stopped or reversed. A deployment process your own engineers can run. Monitoring, alerting and recovery procedures that match the service you have promised your users.
In delivery. We write the regression suite before we change the code, so behavior is held constant through the migration. DevOps and site reliability work is part of the engagement from the first week, not a handover task at the end.
Data and AI
We apply AI where the work the system does justifies it. We say so when it does not.
What it covers. Applied AI inside the systems we deliver: document classification, automated screening of submissions, appraisal assistance, anomaly detection and analytics. AI enablement for organizations: readiness assessment, data foundations, pilot to production, governance and responsible-use controls.
Typical engagements. Classifying and routing incoming project documents. Screening submissions for missing or inconsistent data before an officer sees them. Flagging outliers in cost or timeline data. Taking a pilot that works on a laptop into a production service. Setting the rules under which an agency will and will not use AI.
What you get. A narrow, measurable use case in production, with the data pipeline that feeds it and the controls that govern it. Where a conventional rule or a better form would do the job, we build that instead.
In delivery. Model behavior is tested like any other behavior, with recorded cases and expected outputs. We log what the system decided and why, so your staff can review it and your auditors can follow it.
Technical advisory and delivery assurance
We act for the organization buying or inheriting a system, not for the firm building it.
What it covers. Architecture review, build-versus-buy analysis, vendor selection and technical evaluation of bids. We also oversee third-party delivery and act as owner’s engineer for agencies procuring or inheriting systems.
Typical engagements. Reviewing an architecture before a budget is committed. Writing the technical sections of a tender and scoring the responses. Reviewing a supplier’s code, tests and deployment practice during delivery. Assessing a system an agency has taken over and setting out what it would cost to keep running.
What you get. A written assessment with findings, risks and recommended actions. Each item is ranked by the cost of fixing it against the cost of leaving it. We attend the meetings where the decisions are made.
In delivery. Our reviews use the same standards we hold ourselves to: regression coverage, observability, recovery targets, repeatable deployment and a complete handover.
How we engage
We take direct contracts for appropriately sized work. We subcontract to primes. We join consortia with consulting partners such as Cambridge Resources International.