Scalable web and desktop systems
Custom Enterprise Software
Business systems built to a written specification: domain modelling, architecture, implementation, automated tests, deployment pipeline and handover of the complete source code.
The problem this solves
Most of our work starts where an off-the-shelf product stops — a process that is specific to how a company actually operates, spread across spreadsheets, email threads and a legacy database nobody wants to touch. We model that process, agree the scope in writing, and build a system your team owns outright.
What the work includes
- Domain modelling and a written functional specification before a line of code
- Web applications, internal operations platforms and back-office systems
- Relational data modelling, migrations and reporting views
- Role-based access control, audit trails and data-retention rules
- Automated test suite and a reproducible CI/CD pipeline
- Documentation written for the engineer who inherits the system
How the engagement runs
- 01
Technical discovery1–2 weeks
A paid, time-boxed discovery: we read the existing code and data model, interview the people who run the process today, and write down the constraints. It ends with a specification, not a proposal deck.
- 02
Architecture and scope1–2 weeks
Architecture decisions are recorded with the alternatives we rejected and why. Scope is split into milestones that each end in something demonstrable, so progress is observable rather than reported.
- 03
Iterative deliveryBulk of the engagement
Two-week iterations against your repository and your board. Every iteration ends with a deployable build, automated tests, and a written summary of what changed and what is still open.
- 04
Handover and support1–2 weeks, then optional retainer
You receive the source code, the infrastructure definitions, the runbook and a recorded walkthrough. Continued support is a separate, optional agreement — never a dependency we engineer in.
A note on the duration stated above
8–24 weeks depending on scope is a typical range for this shape of work, not a commitment. Real scope, existing data quality and the availability of the people who know the current process all move it. The date we commit to appears in the written quote.