Services
Engineering
services
Six areas of work, each described by its purpose, typical scope and deliverables. Every engagement is shaped around the system in front of us rather than a fixed package.
Overview
What we are engaged to do
These areas overlap in practice: a cloud migration usually involves integration work, and a new application eventually becomes a maintenance engagement.
01
Custom Software Development
Applications built around a specific operational process rather than adapted from a generic product.
02
Web Application Development
Browser-based systems with considered interface design, accessible markup and measurable performance.
03
Cloud Solutions
Infrastructure that is provisioned as code, observable in production and sized to real demand.
04
Systems Integration
Reliable connections between the systems your organisation already depends on.
05
IT Consulting
Independent technical assessment and planning before commitments are made.
06
Software Maintenance and Technical Support
Ongoing care for systems that are already in production.
Service 01
Custom software development
For processes that are central to how an organisation works and that no off-the-shelf product models accurately. A bespoke system encodes the real rules, including the exceptions.
Typical scope
- Requirements analysis with the people who perform the process
- Domain and data modelling, including migration of existing records
- Application and service implementation with automated test coverage
- Role-based access control and audit trails where the process requires them
- Deployment pipeline, environment configuration and release process
Deliverables
- Working application deployed to agreed environments
- Source code in your repository with commit history and review record
- Architecture notes, data model documentation and runbook
- Automated test suite running in continuous integration
Service 02
Web application development
For customer portals, internal dashboards and operational tools that must work reliably across devices and remain pleasant to use as functionality grows.
Typical scope
- Interface architecture, component library and responsive layout system
- Authentication, authorisation and session handling
- API design and integration with backend or third-party services
- Accessibility review covering semantics, contrast and keyboard operation
- Performance work against measured budgets for loading and interaction
Deliverables
- Responsive web application with documented components
- API contracts and integration documentation
- Accessibility and performance findings with the changes applied
- Build and deployment configuration
Service 03
Cloud solutions
For teams moving workloads to the cloud, or operating cloud infrastructure that has grown organically and is now hard to reason about or forecast.
Typical scope
- Current-state assessment of workloads, data stores and dependencies
- Target architecture covering networking, compute, storage and identity
- Infrastructure as code for repeatable environment provisioning
- Containerisation and automated deployment with rollback
- Monitoring, log aggregation, alerting, backup and restore procedures
Deliverables
- Documented target architecture with the trade-offs recorded
- Infrastructure-as-code repository and deployment pipelines
- Monitoring dashboards and alert definitions
- Migration plan, cut-over checklist and rollback procedure
Service 04
Systems integration
For organisations where the same information is entered more than once, or where two systems disagree because nothing connects them reliably.
Typical scope
- Interface inventory covering APIs, exports, schedules and file transfers
- Data mapping, transformation rules and canonical identifier strategy
- Synchronous integrations or asynchronous, queue-based delivery
- Retry, idempotency, error queue and reconciliation design
- Monitoring of integration health and data drift
Deliverables
- Integration services or jobs deployed and monitored
- Field-level mapping documentation and transformation rules
- Error-handling and reconciliation procedures
- Operational alerts for failures and backlog growth
Service 05
IT consulting and technical planning
For decisions that are expensive to reverse: choosing a platform, planning a rewrite, assessing an inherited codebase, or sequencing work across several teams.
Typical scope
- Code, architecture and infrastructure review against stated objectives
- Technology and platform evaluation with explicit selection criteria
- Risk assessment covering security, scalability and maintainability
- Delivery roadmap with dependencies, sequencing and estimation ranges
- Technical due diligence for acquisitions or vendor transitions
Deliverables
- Written assessment with findings ranked by impact and effort
- Recommended architecture or platform direction with alternatives considered
- Phased roadmap suitable for planning and budgeting
- Walkthrough session with your technical stakeholders
Service 06
Software maintenance and technical support
For systems already in production that need consistent attention: dependency updates, defect resolution, monitoring follow-up and steady improvement.
Typical scope
- Defect investigation and correction with root-cause notes
- Dependency, runtime and security patch management
- Monitoring, alert triage and incident investigation
- Performance and cost review as usage changes
- Small enhancements delivered in agreed increments
Deliverables
- Maintenance log covering changes, fixes and updates applied
- Incident records with cause and preventive action
- Updated runbooks and configuration documentation
- Periodic review of system health and recommended next steps
Delivery process
How an engagement runs
The same sequence applies whether the work is a new build, a migration or a maintenance handover — only the depth of each step changes.
Discovery
Clarify objectives, constraints and the systems involved; agree what success is measured by.
Technical planning
Produce the architecture direction, scope boundary, sequencing and estimation ranges in writing.
Implementation
Build in reviewed increments, with automated checks running on every change.
Verification
Test against the agreed criteria, including integration points, error paths and performance.
Release
Deploy through an automated pipeline with a documented rollback route and post-release checks.
Operate and improve
Monitor behaviour in production, resolve findings, and plan the next increment from evidence.
FAQ
Questions we are asked most
All answers are shown in full.
- Can you work with an existing codebase you did not write?
- Yes. We start with a review of the repository, its dependencies, tests and deployment process, then agree the first change set. Understanding an inherited system before modifying it is part of the engagement.
- How is scope defined for a new build?
- Through a short discovery step that turns objectives into a written scope: the process being supported, the data involved, integrations required and the boundaries of the first release. Anything outside that boundary is recorded rather than silently included.
- Do we own the source code and infrastructure definitions?
- Work is delivered into repositories and cloud accounts you control, including application code, infrastructure as code and documentation, so nothing depends on our continued involvement.
- Which technologies do you use?
- Selection follows the requirement and what your team can maintain. We favour widely supported, well-documented technologies over novel ones, and we record the reasoning behind each significant choice.
- Can you take over maintenance without rebuilding the system?
- Frequently, yes. Many systems need patching, monitoring, targeted refactoring and documentation rather than replacement. Where a rewrite genuinely is the lower-risk option, we explain why in writing.
- How is progress communicated?
- Through a regular written update stating what changed, what is next and what is blocked, together with access to the repository, the issue tracker and the deployed environments.