Service catalogue
IT services described in operational terms
Each category below sets out what the work covers, the situations it typically applies to, how delivery is organised and the general benefits an organisation can expect. Outcomes depend on context, so nothing here is presented as a guarantee.
01Service
Custom software development
Purpose-built applications for processes that off-the-shelf products do not fit, designed around an organisation's own rules and data.
What it covers
- Requirements analysis and technical specification
- Backend services, data models and business logic
- User interfaces for internal and external users
- Automated tests, documentation and release tooling
Typical business use cases
- Replacing spreadsheet-based workflows that several teams depend on
- Building an internal tool for scheduling, tracking or approvals
- Rebuilding a legacy application whose vendor support has ended
Delivery approach
We start with a written specification and a lightweight prototype of the core workflow, then deliver in reviewable increments with tests included in each one. Source code and deployment definitions are handed over as work progresses.
Expected general benefits
Software that reflects how the organisation actually operates, with a codebase the internal team can read, extend and hand to another supplier if needed.
02Service
Web application development
Responsive, accessible web applications and portals built with modern frameworks and standards-based markup.
What it covers
- Frontend architecture, component systems and state management
- API design and integration with backend services
- Accessibility, responsive layout and performance work
- Search-engine-friendly rendering where content is public
Typical business use cases
- A customer portal for account information and self-service tasks
- An internal dashboard consolidating data from several systems
- A public informational site that must load quickly on mobile networks
Delivery approach
Interfaces are built from a shared component library, reviewed against accessibility guidance, and measured for load performance before release. Content structure and metadata are considered during build rather than retrofitted.
Expected general benefits
Interfaces that behave consistently across devices, remain usable with keyboard and assistive technology, and are cheaper to extend because they share common components.
03Service
Cloud and infrastructure services
Design, provisioning and operation of hosting environments, with infrastructure described as code and reproducible across stages.
What it covers
- Environment design for development, staging and production
- Infrastructure as code, container images and deployment pipelines
- Backup, restore procedures and recovery testing
- Monitoring, alerting and cost review
Typical business use cases
- Moving an application from a single unmanaged server to a managed environment
- Introducing repeatable deployments instead of manual releases
- Reducing avoidable spend on over-provisioned resources
Delivery approach
Existing environments are documented first, then rebuilt as code so they can be recreated deliberately. Migrations run in stages with a tested rollback path at each step.
Expected general benefits
Environments that can be recreated from source, releases that follow the same path every time, and clearer visibility of what infrastructure is running and why.
04Service
IT consulting
Independent technical assessment and planning for organisations deciding what to build, buy, replace or retire.
What it covers
- Architecture and codebase review
- Technology selection and build-versus-buy analysis
- Roadmap sequencing and delivery risk assessment
- Technical due diligence on existing systems
Typical business use cases
- Deciding whether to refactor or replace an ageing application
- Reviewing a proposed architecture before committing budget
- Understanding the maintenance burden of an inherited system
Delivery approach
We review code, infrastructure and documentation, interview the people who operate the systems, and produce a written assessment with prioritised options and their trade-offs.
Expected general benefits
A clearer basis for planning decisions, with risks named explicitly and options described in terms of effort, dependency and long-term maintenance.
05Service
System integration
Connecting applications, databases and third-party services so information moves between them reliably.
What it covers
- API and message-based integration design
- Data mapping, transformation and validation rules
- Error handling, retries and reconciliation processes
- Integration monitoring and failure alerting
Typical business use cases
- Synchronising records between a CRM and an internal system
- Consuming or publishing partner APIs with predictable error handling
- Replacing manual file transfers with automated, validated exchanges
Delivery approach
Interfaces are specified as contracts, built with validation at the boundary, and tested against representative payloads including failure cases before they carry live traffic.
Expected general benefits
Fewer manual re-entries, earlier detection of data problems, and integrations that fail visibly and recoverably instead of silently.
06Service
Cybersecurity support
Practical security work applied to applications, dependencies, access control and operational routines.
What it covers
- Application and configuration security review
- Identity, authentication and access-control design
- Dependency and vulnerability monitoring
- Logging, incident response preparation and patch routines
Typical business use cases
- Hardening an application before it is exposed to external users
- Reviewing who holds access to production systems and why
- Establishing a routine for applying security updates
Delivery approach
We assess the current state against recognised secure-development practice, prioritise findings by realistic risk, and implement remediation alongside the team that will operate the system afterwards.
Expected general benefits
A reduced and better-understood attack surface, controlled access to sensitive systems, and documented routines for handling updates and incidents.
07Service
Data and automation solutions
Data pipelines, reporting foundations and automation of repetitive operational tasks.
What it covers
- Data collection, cleaning and transformation pipelines
- Reporting datasets and dashboard data sources
- Workflow automation and scheduled processing
- Data quality checks and pipeline monitoring
Typical business use cases
- Consolidating reporting data currently assembled by hand each month
- Automating recurring file processing or notification tasks
- Creating a consistent dataset several teams can report from
Delivery approach
Pipelines are built to be idempotent and re-runnable, with validation steps and logging so failures are traceable to a specific stage and input.
Expected general benefits
Less manual repetition, more consistent figures across teams, and processing that can be re-run safely when upstream data changes.
08Service
Software maintenance and technical support
Ongoing care for systems already in production: updates, corrections, small improvements and operational response.
What it covers
- Bug investigation, correction and regression testing
- Framework, library and runtime updates
- Performance review and incremental improvement
- Agreed response routines for operational issues
Typical business use cases
- Keeping an application supported after its original build team moved on
- Handling a steady stream of small change requests
- Preventing gradual dependency drift and end-of-life runtimes
Delivery approach
Work is tracked in a shared queue with agreed priorities. Routine updates are scheduled rather than deferred, and each corrective change is covered by a test that reproduces the original fault.
Expected general benefits
Systems that stay current and supportable, with a predictable route for reporting problems and requesting changes.
Environments
Where these services run
Work is delivered on managed cloud platforms, containerised runtimes and existing on-premises environments, depending on what an organisation already operates and what its data handling requires. We do not push a migration where the current environment is appropriate.
Whichever environment applies, we aim for the same properties: reproducible provisioning, versioned configuration, monitored runtime behaviour and a documented recovery procedure.
Engagement shapes
How work is structured
- Defined project
- A scoped piece of work with agreed deliverables, suited to builds, migrations and integrations with a clear endpoint.
- Continuous delivery team
- Ongoing capacity working from a shared, re-prioritised backlog, suited to products that keep evolving.
- Maintenance and support
- Scheduled updates and a defined route for reporting faults on systems already in production.
- Advisory review
- A time-boxed assessment producing written findings and prioritised options, without an implementation commitment.
Enquiries
Discussing a requirement
Written enquiries about any of the categories above can be sent to the company email address. A short description of the current systems and the outcome you are aiming for is usually enough to begin a useful conversation.
patrickgom16@gmail.com