Custom Software
Bespoke Water Engineering Applications
Custom desktop and web applications for water engineering calculations, design workflows, and compliance reporting. Built around a specific pain point — not a generic platform.
Examples
- Hydraulic calculation automation across a standardised catalogue of design events
- Design-flood report generation that pulls inputs from the project GIS and produces municipal-ready deliverables
- Compliance tracker for water-use licence obligations, with audit trail and renewal prompts
- Internal scenario-builder that lets non-modellers run pre-configured hydraulic runs
Who it’s for
Teams who find themselves rebuilding the same spreadsheet, re-running the same calculation chain, or stitching the same report across every project. We build the tool so the work is done once and reused.
The trigger tends to be either capacity (a senior engineer is the bottleneck) or consistency (the same calculation is happening slightly differently across the team). Bespoke software addresses both.
What you get
- A purpose-built application — desktop or web — scoped around one team’s workflow.
- Source code, licensed to you.
- A short handover document and demo.
- An agreed bug-fix window after go-live; ongoing support scoped separately if you want it.
How we work
Phased, always. A bespoke app that tries to be v1 of a platform usually ends up being neither. We build the thinnest version that removes the specific pain, ship it, use it on a live project, and expand from there.
- Discovery. We watch the workflow in practice and list the decisions, inputs, and outputs. Often this is enough to show that a plugin or dashboard would be a better fit — we will tell you if that is the case rather than over-scoping.
- Phase 1 scope. The smallest piece of software that removes the largest piece of pain. Typically 8–12 weeks.
- Build with the user in the loop. Sprints that end with the intended user trying the tool on their work, not with a demo.
- Handover and iterate. Production-ready v1, then Phase 2 extensions based on real usage.
Stack & interoperability
- Desktop: Python with Qt; Electron for cross-platform needs with a web-like UI; we avoid platforms that lock you out of the binary.
- Web: Astro or Next.js frontends with Python/Node backends; PostgreSQL for anything with meaningful state.
- Integration: CSV, Parquet, GeoTIFF, shapefile in/out. REST APIs where the app sits in a larger pipeline.
What this is not
- Not a platform play. We are not building you a product to resell.
- Not a low-code tool builder. If your problem fits a low-code tool you already own, we will tell you up front.