Ten services, one standard.
Each service below describes what the work includes, the business situations it is normally requested for, how delivery is organised, and the kinds of outcome it tends to produce. Nothing here is guaranteed in advance — results depend on the system, the data and the decisions taken along the way.
01
Custom software development
Systems built around a specific operating model, where packaged software would force the business to work backwards.
What the service includes
- Requirements analysis and domain modelling
- Backend services, APIs and integrations
- Database design, migrations and data access layers
- Automated test suites and continuous integration
- Deployment pipelines and environment configuration
Business needs it addresses
Processes held together by spreadsheets, duplicated manual entry between systems, or a workflow no off-the-shelf product supports without heavy compromise.
Delivery approach
Discovery first, then a thin end-to-end slice that proves the architecture in production conditions, followed by incremental delivery against a shared backlog with review at the end of each cycle.
Expected types of outcome
Typically, a system the client owns outright, with tests and documentation, that removes specific manual steps and can be extended by an internal team afterwards.
02
Web application development
Browser-based applications where the interface, the API and the delivery pipeline are treated as a single product.
What the service includes
- Responsive interface implementation with accessible components
- Authentication, authorisation and role modelling
- API design and server-side rendering where it helps performance
- Performance budgets, caching and asset optimisation
- Analytics-ready structure and error reporting
Business needs it addresses
Replacing a legacy internal tool, giving customers self-service access to something currently handled by email, or rebuilding an application that has outgrown its original architecture.
Delivery approach
Interface and data model are designed together. Work proceeds screen by screen against real data, with accessibility and mobile layout treated as requirements rather than a later pass.
Expected types of outcome
Generally, an application that behaves consistently across devices, loads within an agreed performance budget, and can be deployed without downtime.
03
Mobile product development
Mobile products designed for intermittent connectivity, small screens and app store review realities.
What the service includes
- Platform and technology selection based on the feature set
- Interface implementation following platform conventions
- Offline behaviour, synchronisation and conflict handling
- Release management, versioning and staged rollout
- Crash reporting and diagnostics
Business needs it addresses
A field workforce that needs data away from a desk, a customer-facing service that belongs on a phone, or an existing mobile product that is no longer maintainable.
Delivery approach
We start with the two or three tasks a person will repeat daily and design around them, then extend. Store requirements, permissions and privacy disclosures are planned from the beginning.
Expected types of outcome
Usually, a maintainable mobile codebase with a repeatable release process and clear diagnostics when something fails on a device we do not hold.
04
UI/UX and product design
Research, structure and interface design produced in a form engineering can build without reinterpretation.
What the service includes
- User interviews and workflow observation
- Information architecture and content structure
- Wireframes, prototypes and task-based testing
- Visual design and a token-based design system
- Accessibility review: contrast, focus order, keyboard paths
Business needs it addresses
Software people avoid using, support volume caused by confusing screens, or an interface that has grown inconsistent as features were added.
Delivery approach
Observation before drawing. Structure is agreed before visuals, prototypes are tested against real tasks and realistic data volumes, and the resulting system is expressed as tokens and components shared with the codebase.
Expected types of outcome
Commonly, fewer steps in the tasks that matter most, a consistent component library, and design decisions that survive implementation.
05
Cloud solutions
Cloud architecture sized to the workload, described in code, and understood by the people who have to pay for it.
What the service includes
- Architecture design across compute, storage and networking
- Infrastructure as code and reproducible environments
- Identity, access management and network segmentation
- Migration planning for existing workloads
- Cost modelling and ongoing spend review
Business needs it addresses
Cloud bills growing faster than usage, environments configured by hand that nobody can recreate, or an on-premise system that has to move.
Delivery approach
We inventory what exists, model the target architecture with its cost implications, then migrate in stages with rollback points rather than in a single cutover.
Expected types of outcome
Typically, environments that can be rebuilt from version control, clearer attribution of spend, and a documented migration path with known checkpoints.
06
DevOps and infrastructure
The delivery machinery between a merged change and a running system, made automatic and reversible.
What the service includes
- Continuous integration and deployment pipelines
- Containerisation and runtime configuration
- Environment parity between development, staging and production
- Observability: structured logging, metrics, tracing and alerts
- Backup, restore and incident runbooks
Business needs it addresses
Releases that require manual steps and a quiet weekend, environments that drift apart, or outages discovered by customers before the team.
Delivery approach
Pipelines are built incrementally alongside the team's existing workflow, starting with the step that causes the most pain, and every automated path is proved by using it for real releases.
Expected types of outcome
Often, shorter and less eventful releases, alerting that reflects real user impact, and restore procedures that have actually been rehearsed.
07
Data and analytics
Pipelines and models that turn operational data spread across systems into something people can query with confidence.
What the service includes
- Source inventory and data quality assessment
- Ingestion pipelines and scheduling
- Warehouse or lake modelling and transformation layers
- Metric definitions agreed with the business
- Reporting and dashboard implementation
Business needs it addresses
Numbers that differ depending on who produced them, reporting that arrives too late to act on, or analysis that requires manual exports every month.
Delivery approach
Definitions before dashboards. We agree what each metric means and where it comes from, build tested transformations, and expose a documented layer that reporting tools read from.
Expected types of outcome
Generally, a single documented source for agreed metrics, refreshed on a schedule, with lineage that can be traced back to the originating system.
08
Cybersecurity consulting
Security work aimed at the development and operations process, where most avoidable exposure originates.
What the service includes
- Threat modelling for specific applications and data flows
- Secure development practice review and developer guidance
- Access, secret and credential management review
- Dependency and configuration vulnerability assessment
- Incident response planning and tabletop exercises
Business needs it addresses
A security policy that exists on paper but not in the pipeline, an upcoming customer or regulatory review, or uncertainty about where sensitive data actually resides.
Delivery approach
We examine the system and the process around it, produce a prioritised written assessment with the reasoning behind each item, and where asked, implement the fixes alongside the team.
Expected types of outcome
Usually, a ranked list of concrete issues with remediation steps, tightened access and secret handling, and checks embedded in the build so regressions are caught automatically.
09
IT consulting
Time-boxed technical advice for organisations facing a decision they will live with for years.
What the service includes
- Architecture and technology selection review
- Build, buy or extend assessment
- Delivery process and team structure review
- Vendor and platform evaluation criteria
- Roadmap sequencing and risk analysis
Business needs it addresses
A major platform decision, a stalled project that needs an outside reading, or a leadership team choosing between competing technical proposals.
Delivery approach
Interviews with the people involved, inspection of the systems and code in question, and a written recommendation setting out options, trade-offs, risks and a sequence of work.
Expected types of outcome
Typically, a documented recommendation the organisation can act on independently, with the reasoning and rejected alternatives recorded for future reference.
10
Software maintenance and modernisation
Care for systems already in production, and staged renewal for those that have become risky to change.
What the service includes
- Dependency, runtime and security patch management
- Characterisation tests around untested legacy code
- Incremental refactoring and strangler-pattern replacement
- Performance profiling and optimisation
- Documentation recovery and knowledge transfer
Business needs it addresses
Software nobody wants to touch, unsupported runtimes or libraries, degrading performance, or the departure of the only person who understood a system.
Delivery approach
Stabilise before changing: add tests and monitoring around current behaviour, then replace components one at a time behind stable interfaces, keeping the system running throughout.
Expected types of outcome
Commonly, a supported dependency baseline, test coverage where it was absent, and a modernisation path that can be paused between stages without leaving the system broken.