Services
Six areas of IT work, described without embellishment
Each service below sets out its purpose, the scope it typically covers and the deliverables it can produce. Scope is always agreed per engagement; nothing here is offered as a guaranteed outcome.
Service 01
Custom software development
Purpose
To support a process that is specific enough to the organisation that configuring an off-the-shelf product would cost more, in effort or compromise, than building the part that is genuinely missing.
Typical scope
- Requirement clarification and written problem definition
- Data modelling, state transitions and permission design
- Application development in mainstream, well-supported technologies
- Automated test suites covering business rules
- Deployment into an environment the client controls
Possible deliverables
- Running application in a hosted environment
- Source code in the client's own repository
- Database schema with versioned migrations
- Setup, configuration and operating documentation
- Record of architecture decisions and their trade-offs
Service 02
Web application development
Purpose
To give distributed users one place to work, with nothing to install, central access control and a single code path to update when something changes.
Typical scope
- Responsive interface implementation across common screen sizes
- Authentication, roles and server-side permission enforcement
- Reporting views, filtering and data export
- Performance work: image optimisation, lazy loading, script restraint
- Accessibility basics — semantic markup, headings, alternative text
Possible deliverables
- Deployed web application with staged environments
- Component structure documented for future contributors
- End-to-end checks for the critical user journeys
- Administrative interface where the workflow requires one
Service 03
Cloud and infrastructure
Purpose
To make environments reproducible, so releases are routine, recovery is plausible and running costs are visible rather than discovered.
Typical scope
- Environment design for development, staging and production
- Container image builds and configuration held in version control
- Automated build, test and deployment pipelines
- Log aggregation, basic metrics and alerting
- Backup scheduling and a rehearsed restore procedure
Possible deliverables
- Infrastructure and pipeline definitions in the client's repository
- Deployment runbook with a documented rollback path
- Monitoring dashboards and alert rules
- Access and credential inventory handed to the client
Service 04
Workflow automation
Purpose
To remove routine copying, re-entry and manual coordination from a process, and to make the remaining steps traceable.
Typical scope
- Process mapping to identify repetition and error-prone steps
- Scheduled jobs, event handlers and rule-based routing
- Document and report generation
- Notification and approval flows
- Logging, failure handling and manual override paths
Possible deliverables
- Automated workflows running on a defined schedule or trigger
- Execution logs and failure notifications
- Written description of each rule and its exceptions
Service 05
API and systems integration
Purpose
To stop the same data being entered twice, and to make disagreements between systems visible instead of silent.
Typical scope
- Field-level mapping between differing data models
- HTTP API design, versioning and authentication
- Scheduled and event-driven data transfers
- Verified inbound webhook endpoints with idempotent processing
- Adapters for older systems that cannot be modified
Possible deliverables
- Documented API or integration service
- Mapping specification agreed in writing
- Error log and reprocessing procedure for rejected records
- Monitoring on transfer volume and failure rate
Service 06
Software maintenance and quality assurance
Purpose
To keep working software safe to change — addressing dependency risk, performance drift and accumulated shortcuts before they force a rewrite.
Typical scope
- Review of code, dependencies and deployment setup
- Dependency and security updates on a regular cadence
- Defect investigation, resolution and regression tests
- Performance profiling and targeted optimisation
- Test suite development for code that arrived without one
Possible deliverables
- Written assessment of current risks and a proposed sequence of work
- Regular maintenance releases with change notes
- Expanded automated test coverage over critical paths
- Defined route for reporting and triaging issues
Engagement notes
How scope and expectations are handled
Every engagement begins with a written problem statement and a set of deliverables with acceptance criteria. Assumptions are listed explicitly, because an estimate without its assumptions is not information.
Work is delivered in short cycles, each producing something reviewable in a running environment. Priorities can change between cycles; what does not change silently is scope.
No performance guarantees, uptime promises or business results are offered on this page. What is offered is a described method and deliverables that can be inspected.
Contact