Six services.
One engineering standard.
Each service below states its purpose, its typical scope, the deliverables you receive, and how delivery is run. Services are frequently combined inside a single engagement.
Custom software development
To build applications and services around the rules of a specific organisation, where existing off-the-shelf products cannot represent the domain accurately.
Typical scope
- Requirement analysis and domain modelling
- Database schema design, migrations, and data integrity constraints
- Backend services, business logic, scheduled and event-driven processing
- Administrative interfaces and reporting where required
Deliverables
- Source repository with commit history and review records
- Automated test suite covering the agreed behaviour
- Data model and API documentation
- Deployment instructions for each environment
Delivery approach
Work proceeds in short increments. Each increment closes with a demonstrable change, an updated test suite, and a written note of what was decided. Scope adjustments are agreed before implementation rather than absorbed silently.
Web application engineering
To deliver browser-based applications and websites that are fast, accessible, and structured so that both people and crawlers receive meaningful content.
Typical scope
- Routing and information architecture
- Server-rendered or prerendered pages with per-page metadata
- Design-system implementation with reusable tokens and components
- Responsive layout work and accessibility review
Deliverables
- Application source with a documented component structure
- Design tokens and layout conventions defined in one place
- Accessibility and performance notes with known limitations listed
- Build and deployment configuration
Delivery approach
Interfaces are assembled from a shared token layer so that spacing, typography, and colour remain consistent. Content and metadata are rendered server-side where indexability matters, and motion honours reduced-motion preferences.
Cloud infrastructure and DevOps
To make environments reproducible and releases routine, so that deploying is an ordinary action rather than an event.
Typical scope
- Infrastructure-as-code definitions for networks, compute, and storage
- Container images and orchestration configuration
- CI/CD pipelines that build once and promote a tested artefact
- Logging, metrics, health checks, and alerting
Deliverables
- Version-controlled infrastructure definitions
- Pipeline configuration with build, test, and deployment stages
- Observability dashboards and alert definitions
- Runbooks for deployment, rollback, and routine operations
Delivery approach
Environments are defined in code and created from those definitions, never by hand. Changes to infrastructure follow the same review process as application code, and rollback paths are established before a release, not after a failure.
Systems integration and automation
To connect applications, third-party platforms, and internal services reliably, and to remove repetitive manual steps from routine operations.
Typical scope
- Interface and contract design, including versioning strategy
- Authentication, rate-limit handling, retry and backoff policies
- Data mapping, transformation, and reconciliation checks
- Scheduled and event-driven automation workflows
Deliverables
- Integration services with documented payload schemas
- Failure-handling and reconciliation reports
- Monitoring for queue depth, error rates, and processing latency
- Operational documentation for each connection
Delivery approach
Every integration is specified before it is built: what is sent, what is expected back, what happens on failure, and how duplicates are prevented. Operations are made idempotent so that a retry is safe.
Quality assurance and testing
To establish evidence that a system behaves as agreed, and to catch regressions in a pipeline instead of in production.
Typical scope
- Test strategy covering unit, integration, and end-to-end layers
- Automated suite construction and pipeline integration
- Exploratory and accessibility testing of user-facing paths
- Defect reproduction, triage, and regression coverage
Deliverables
- Automated test suites running on every change
- Test strategy document with coverage boundaries stated
- Defect reports containing reproduction steps
- Regression tests added for each confirmed defect
Delivery approach
Tests are written alongside the behaviour they protect. Automation covers repeatable paths; exploratory testing covers judgement. Coverage gaps are documented rather than left implicit.
Technical consulting
To give an organisation a clear, written view of its technical position before it commits budget to a direction.
Typical scope
- Architecture and codebase review
- Technology and platform selection assessment
- Security-practice and dependency review
- Modernisation or migration planning with sequencing options
Deliverables
- Written assessment describing current state and identified risks
- Recommendation set with trade-offs and estimated effort
- Prioritised sequence of work with dependencies noted
- Review session covering findings and open questions
Delivery approach
Findings are evidenced from the codebase, infrastructure, and pipelines rather than from impressions. Recommendations state what is being traded away, and options are presented so the decision remains with the client.
07 / Engagement
How an engagement is agreed
Every engagement starts with a written scope: the objective, the systems involved, the deliverables, the review method, and the assumptions being made. Nothing is built against an unwritten expectation.