What I worked on
The financial shape is what makes this sector distinct. Costs accumulate against a project over long periods, revenue recognises against milestones and completion rather than shipment, and the reporting that matters is cumulative position rather than this month’s throughput. Integrations here feed a ledger that people will still be asking questions about several years later, which raises the bar on traceability.
The rest was approval and document flow — routing, capturing sign-off, and keeping the generated paperwork consistent with what the system actually held. Less technically exotic than high-volume work, but the failure mode is worse: a document that disagrees with the ledger is a dispute rather than a retry.
Systems & platforms
Representative work
Project cost and billing interfaces
Integrations feeding project costs and milestone-based billing into the ledger, with the audit trail needed to answer questions about a figure long after the period closed.
Approval and sign-off routing
Workflow configuration and supporting integrations for multi-level approvals, so routing followed the delegation rules the business actually operated under.
Generated documentation
BI Publisher templates producing the billing and project documentation issued to counterparties, driven from ledger data rather than re-keyed.
What the sector taught me
A short engagement, but a useful contrast. It made clear how much of an integration’s design is dictated by the shape of the money underneath it — and that a system optimised for throughput is not automatically good at answering questions about the past.