Services
Six engineering services, usually combined
Each service below sets out typical scope, how the work proceeds and what you receive. Actual scope is agreed per engagement in writing. No outcome, timeline or result is promised here that depends on circumstances we have not yet reviewed.
- 01Custom software development
- 02Web application engineering
- 03Cloud infrastructure
- 04Systems integration and workflow automation
- 05Quality assurance and testing
- 06Maintenance and technical support
Custom software development
Applications and services built for a specific operational need, where existing products do not fit the process.
Typical scope
- Requirements shaped into a data model, domain rules and service boundaries
- Backend services, scheduled processing and administrative interfaces
- Database design, migrations and data import from existing sources
Process
- Discovery sessions to map the current process and its constraints
- A written technical plan with architecture, sequence and assumptions
- Development in reviewed increments, each demonstrated as it completes
Deliverables
- Source code in your repository with commit history and review records
- Architecture notes, data model documentation and environment setup steps
- Automated test suite covering domain logic and critical paths
Web application engineering
Browser-based products and internal tools, engineered for daily use across desktop, tablet and mobile screens.
Typical scope
- Interface implementation from an agreed structure and design direction
- Server-rendered or prerendered pages for content and metadata on first load
- Authentication, roles and permission-aware views where required
Process
- Interface inventory: the screens, states and roles the application needs
- Component and layout implementation against accessibility and contrast guidance
- Cross-device review and performance measurement before release
Deliverables
- A responsive application with documented routes and states
- Accessibility and performance notes, including known limitations
- End-to-end tests for the journeys agreed as critical
Cloud infrastructure
Environments, deployment pipelines and observability so software can be released and operated predictably.
Typical scope
- Environment definition for development, staging and production
- Containerisation, build and deployment automation
- Logging, metrics, alerting, backup and restore procedures
Process
- Review of current hosting, cost profile and operational pain points
- Incremental migration or provisioning with rollback planned at each step
- Rehearsal of deployment, restore and incident procedures
Deliverables
- Infrastructure described as configuration in version control
- A deployment pipeline from commit to release with verification steps
- Runbooks for deployment, rollback, backup and restore
Systems integration and workflow automation
Connecting applications, APIs and data sources so information moves between systems without manual re-entry.
Typical scope
- Data ownership mapping across the systems involved
- APIs, scheduled jobs, event handlers and transformation logic
- Error handling, retries and reconciliation for transfers that must not be lost
Process
- Integration analysis: sources, formats, frequency and failure modes
- Contract definition, then implementation behind a versioned interface
- Parallel running and reconciliation before the manual step is retired
Deliverables
- Documented integration contracts and transformation rules
- Monitoring and run history for every automated transfer
- Operational notes describing what to do when a transfer fails
Quality assurance and testing
Automated and exploratory testing that makes releases repeatable and regressions visible early.
Typical scope
- Unit, integration and end-to-end test coverage for agreed areas
- Test execution on every change through continuous integration
- Exploratory testing and structured review of release candidates
Process
- Risk assessment to identify the flows where failure costs the most
- Incremental introduction of coverage, starting with those flows
- Release checklists that shorten as automation replaces manual steps
Deliverables
- A test suite running in continuous integration with visible results
- Documented test strategy and current coverage boundaries
- Defect reports with reproduction steps and severity assessment
Maintenance and technical support
Ongoing care for software already in production: monitoring, updates, incident response and incremental improvement.
Typical scope
- Dependency and platform updates, including security patches
- Monitoring review, alert tuning and performance investigation
- Small feature work and refactoring agreed in a regular cycle
Process
- Handover review of the current system, its risks and its monitoring
- An agreed response approach for incidents and their priority levels
- Regular written reports on work performed and issues outstanding
Deliverables
- Up-to-date dependencies with a record of what changed and why
- Incident notes with cause, resolution and follow-up actions
- A maintained backlog of technical risks and proposed improvements
How services are agreed
Work starts with a discovery conversation and a written technical plan. The plan states what is included, what is explicitly excluded, the sequence of increments and the assumptions each estimate depends on.
Larger programmes are split into phases that can be evaluated independently. Maintenance runs on a recurring cycle with an agreed scope per period. Anything outside the agreed scope is quoted before it is started.
