Practice · Operating software
Software built for the work, owned outright.
Websites, dashboards, and operational systems delivered with the same discipline that commissions our water and energy projects. Owned outright by the client, documented from day one, and built to hold under scrutiny. Discovery, build, and a documented handover run under one named partner, with stewardship retained after go-live.
- Established
- 2003
- Practice
- Partner-led
- Regional hubs
- 6
- Handover
- Documented
Representative engagement posture for operating-software mandates. Stack, licensing, and handover scope are fixed in the written brief.
Regional desks
Held through the firm’s city desks.
Bucharest builds and maintains the operating-software record, governed to Vienna’s standard, with Lisbon coordinating European systems.
Mandate fit
Digital systems governed like infrastructure.
The digital brief is treated like a commissioning package: ownership, risk, performance, data flow, and handover are fixed before production build.
- 01
Operating case
The workflow, audience, and failure cost are written before interface work.
- 02
Resilient delivery
Security, performance, accessibility, and editorial control are baseline.
- 03
Named stewardship
Hosting, monitoring, and change control stay with the same accountable team.
Capabilities
Software that holds its shape under load.
Purpose-built systems for organisations where downtime, data loss, or a brittle interface carry real operational cost. Not templates, not low-code, not outsourced.
Delivery
Survey. Design. Build. Steward.
Four stages, one partner across all of them. From written brief to retained hosting.
Engagement cadence
i–iv · single partner
- Listen
Survey
Stakeholder interviews, workflow mapping, and a written brief of what the system must do, and what it must never do.
1 – 2 weeks
- Write
Design
Information architecture, security model, and data flow issued as a stamped package. Scope fixed before any code is written.
2 – 3 weeks
- Deliver
Build + commission
Fortnightly demos, full test pass, and production cutover under the name of the partner who signed the brief.
6 – 12 weeks
- Hold
Stewardship
Hosting, monitoring, quarterly reviews, and a retained line back to the engineers who built the system.
Retained
One partner signs across all four stages. No subcontracted handovers.
Next step
A short call, a written scope.
Thirty minutes to understand what the system has to do, who uses it, and what it must never do. You leave with a written brief and a realistic cost estimate.