Service catalogue
IT servicesin detail
Eight areas of work, each described by its typical scope, the process it follows and what is handed over at the end. No prices, certifications or performance guarantees are stated.
Custom software development
Applications built for a specific operational problem, where existing products would force awkward compromises.
Typical scope
- Requirement framing workshops and a written problem statement
- Domain and data modelling, including migration of existing records
- Application implementation with automated test coverage
- Deployment configuration and environment setup
Process
Framing, then an architecture note, then incremental implementation in short cycles with review at the end of each. Scope changes are agreed in writing before they enter a cycle.
Deliverables
Source code in a repository the client can access, database migrations, automated tests, deployment configuration and operating notes.
Web applications and digital platforms
Browser-delivered products, internal portals and content-driven sites engineered for maintainability.
Typical scope
- Information architecture and route structure
- Component library and typographic system
- Server rendering or static generation decisions per page
- Accessibility, responsive behaviour and metadata implementation
Process
Structure and content model first, then interface implementation against real content, then performance and accessibility review before release.
Deliverables
Implemented pages and components, reusable design tokens, build pipeline, and documentation of the content model.
Cloud infrastructure
Environment design and operation, with configuration held in version control rather than in someone's memory.
Typical scope
- Environment topology for development, staging and production
- Infrastructure defined as configuration files
- Continuous integration and deployment pipelines with rollback
- Logging, metrics, alerting, backup and restore procedures
Process
Review of current hosting and constraints, a target topology note, then staged migration or provisioning with verification at each step.
Deliverables
Infrastructure configuration, pipeline definitions, monitoring and alert setup, and a runbook covering deployment, rollback and restore.
Systems integration
Reliable exchange of data between internal systems and third-party services.
Typical scope
- Inventory of systems, owned data and available interfaces
- Field-level mapping with transformation and validation rules
- Synchronisation or event-driven flows with retry handling
- Reconciliation checks and error reporting
Process
Mapping and agreement on the source of truth for each field, a small pilot flow, then expansion once the pilot reconciles cleanly.
Deliverables
Integration services or jobs, mapping documentation, monitoring for failed transfers and a replay procedure.
Automation
Repetitive manual routines converted into scheduled or event-driven processes that report their own results.
Typical scope
- Documentation of the current manual steps and their exceptions
- Implementation of the automated process with logging
- Notification of failures and of results requiring human review
- Handover so staff know how to inspect and re-run a job
Process
Observe and record the manual routine, automate the common path first, then handle exceptions explicitly rather than hiding them.
Deliverables
Automated jobs or workflows, schedule configuration, log output, alerting rules and written operating instructions.
Quality assurance and testing
Verification work that states intended behaviour and detects regressions when code changes.
Typical scope
- Test strategy proportionate to the risk of each area
- Unit, integration and end-to-end test implementation
- Pipeline configuration so tests gate every change
- Exploratory and accessibility review before release
Process
Acceptance criteria are agreed before implementation; tests are written with the code and run automatically on every change. Reported defects gain a regression test.
Deliverables
Test suites, pipeline configuration, coverage reporting where useful, and defect reports with reproduction steps.
Technical consulting
Independent assessment and planning where a decision needs an engineering view before money is committed.
Typical scope
- Review of an existing codebase, architecture or hosting setup
- Options analysis with trade-offs stated plainly
- Sequenced improvement or migration plan
- Technical input to requirements and supplier evaluation
Process
Structured review against agreed questions, then a written report with findings, risks and recommended sequence. Findings are described with the evidence behind them.
Deliverables
Written assessment, prioritised recommendations, and an implementation sequence the client can act on with any provider.
Maintenance and support
Ongoing care of systems already in production, keeping them current and correcting faults.
Typical scope
- Defect investigation and correction
- Dependency, framework and platform updates
- Monitoring and log review with configuration adjustments
- Small agreed improvements on a regular cadence
Process
Reported issues are triaged by impact, corrected, and explained in writing. Preventive work is scheduled rather than left until something breaks.
Deliverables
Change log of corrections and updates, updated documentation, and periodic notes on system health and recommended next steps.
How services are combined
Most engagements draw on several of these areas. A new application usually involves development, infrastructure, quality assurance and later maintenance; an integration project often begins with consulting and ends with automation.
Scope is agreed in writing before implementation, and revised in writing when circumstances change. Estimates describe expected effort and the assumptions behind it, not guaranteed outcomes.
Enquiries are handled by email at [email protected], shown here as plain text.
