Services
Services
Each service below is described in terms of the business need it addresses, the scope of work involved, the process followed, and the artefacts typically handed over. Timeframes and outcomes depend on the specific system and are agreed per engagement.
§ 01Custom software development
Custom software development
Business need
An organisation runs a process that no packaged product models correctly. The rules live in spreadsheets, email and the experience of individual staff, which makes the process slow to run, hard to audit and difficult to hand over.
Scope
Domain modelling, database design, business rule implementation, user interfaces for the people performing the work, role-based access, audit trails, and reporting or export surfaces. Integration with the systems that already hold related data is included where required.
Process
Discovery documents the process as performed today and the data it relies on. An architecture is agreed, then implementation proceeds in reviewable increments, each covered by automated tests and deployable on its own.
Typical deliverables
- Source code in the client's repository with commit history
- Data model and migration scripts
- Automated test suite covering agreed behaviour
- Architecture and decision notes
- Deployment and environment setup instructions
§ 02Web applications
Web applications
Business need
A service must be reachable from a browser on any device, by staff, customers or partners, without installation and with a consistent experience across screen sizes.
Scope
Interface architecture, responsive layout, state and data handling, authentication flows, form and validation behaviour, accessibility, performance budgets, and the server-side rendering or indexing strategy appropriate to the content.
Process
Key journeys are defined first and built end to end so the whole path can be exercised early. Accessibility and responsive behaviour are verified as each view is built rather than retrofitted, and interaction cost is measured rather than estimated.
Typical deliverables
- Responsive application covering the agreed journeys
- Component structure documented for future extension
- Accessibility notes covering structure, focus order and contrast
- Automated tests for critical user journeys
- Build and deployment pipeline configuration
§ 03Cloud and infrastructure
Cloud and infrastructure
Business need
Environments have been configured by hand and cannot be reproduced reliably. Releases are manual, monitoring is partial, and recovery from failure depends on individual knowledge.
Scope
Declarative environment definitions, container or runtime packaging, build and deployment pipelines, secret management, logging and metrics collection, alerting thresholds, backup schedules and documented restore procedures.
Process
The existing setup is inventoried and its gaps recorded. Environments are then expressed as code and promoted through a pipeline that builds once and deploys the same artefact to each stage. Restore procedures are exercised rather than assumed.
Typical deliverables
- Infrastructure definitions held in version control
- Automated build, test and deployment pipeline
- Logging, metrics and alerting configuration
- Backup and restore runbook
- Documented rollback path for each deployable component
§ 04API development and integrations
API development and integrations
Business need
Two or more systems hold parts of the same information and are kept in step by people re-keying data, exchanging exports, or reconciling records at the end of a period.
Scope
Interface design and documentation, authentication and authorisation between systems, payload contracts and versioning, data mapping and transformation, retry and error handling, and audit records for every exchange.
Process
The data owned by each system is established first, along with the direction of truth for each field. Contracts are written before implementation, exercised against test environments, and instrumented so that any individual message can be traced.
Typical deliverables
- Documented, versioned interface specification
- Integration services with retry and failure handling
- Field-level mapping documentation
- Per-message audit and replay tooling
- Test coverage including failure paths
§ 05Workflow automation
Workflow automation
Business need
Repetitive operational steps consume staff time and introduce variation: reports assembled by hand, notifications sent manually, records updated in sequence across several tools.
Scope
Event and schedule triggers, rule engines, document and report generation, notification routing, exception queues for cases requiring judgement, and monitoring of the automated runs themselves.
Process
The current sequence is documented step by step, including the exceptions people handle informally. Automation is introduced where the rule is stable and the input reliable; everything else is routed to a person with the context needed to decide.
Typical deliverables
- Automated workflows with defined triggers and rules
- Exception handling and escalation paths
- Run history and failure alerting
- Operational documentation for the automated process
§ 06Quality assurance
Quality assurance
Business need
Changes carry uncertainty. Without systematic verification, defects reach production, regressions repeat, and teams become reluctant to modify code they cannot test.
Scope
Test strategy, unit and integration suites, end-to-end coverage of critical journeys, exploratory testing of new functionality, test data management, and continuous execution of the suites on every change.
Process
Risks are identified and tests placed at the level where each risk lives. Suites run automatically in the pipeline. Defects are recorded with reproduction steps, expected and observed behaviour, and a severity based on operational impact.
Typical deliverables
- Written test strategy with agreed coverage targets
- Automated suites executed in the pipeline
- Defect records with reproduction steps and severity
- Regression tests added for every production defect
§ 07Maintenance and technical support
Maintenance and technical support
Business need
A system in production continues to require attention: dependencies publish advisories, runtimes reach end of support, data grows past original assumptions, and business rules change.
Scope
Monitoring and incident response, dependency and platform updates, performance investigation and tuning, small change requests, and planning for larger modernisation work.
Process
Support terms are agreed in writing: what is monitored, how issues are reported, how they are prioritised, and when updates are applied. Recurring issues are traced to their cause rather than repeatedly mitigated.
Typical deliverables
- Written support scope and reporting procedure
- Monitoring dashboards and alerting rules
- Scheduled dependency and platform update cycles
- Incident records with cause and corrective action
- Maintained operational runbooks
