Service catalogue
Twelve services,
described plainly.
Each entry below sets out what the service includes, the business need it addresses, how delivery typically works and what a client gains from it. Most engagements combine several of them.
How to read this catalogue
These services are separated for clarity, not because they are delivered in isolation. A modernisation project usually involves testing, integration and infrastructure work; a new mobile application usually involves design, back-end development and support. We scope the combination that fits the problem rather than selling packages.
Every engagement, regardless of type, follows the same delivery discipline described further down this page: a defined scope, incremental delivery, verification against agreed criteria, and a documented handover.
Custom software development
- What it includes
- Requirements analysis, domain modelling, application architecture, implementation, automated testing, deployment automation and documentation for a system built specifically for your operations.
- Business need addressed
- Organisations reach this point when off-the-shelf products force the business to change its process to fit the tool, or when a critical workflow spans several products that were never intended to work together.
- Typical delivery approach
- We begin with a discovery phase that produces a written specification and a proposed architecture. Delivery then proceeds in short increments, each ending with software you can inspect. Scope changes are recorded and re-estimated rather than absorbed silently.
- Practical value
- The result models your actual process, so the workarounds disappear. Because we build it with maintenance in mind, the system remains changeable when the process changes.
Web application development
- What it includes
- Front-end and back-end engineering, API design, authentication and authorisation, responsive layout, accessibility work, performance tuning and browser compatibility testing.
- Business need addressed
- Suited to work that must be reachable from any device without installation: internal administration tools, customer portals, dashboards, booking and ordering systems.
- Typical delivery approach
- Interfaces are built on a component system so the product stays visually and behaviourally consistent as it grows. Server-rendered pages are used where first-load speed and search visibility matter; richer client interaction is added where it earns its cost.
- Practical value
- A single application serves desktop and mobile users, updates reach everyone immediately, and performance budgets keep the experience usable on ordinary connections.
Mobile application development
- What it includes
- Application design for iOS and Android, offline data handling, background synchronisation, device permission handling, store submission preparation and post-release maintenance.
- Business need addressed
- Appropriate when people do the work away from a desk — field engineers, delivery drivers, inspectors, sales staff — or when device capabilities such as the camera, location or notifications are central to the task.
- Typical delivery approach
- We decide early between native and cross-platform implementation based on the required device access and the long-term maintenance profile, and record the reasoning. Offline behaviour and synchronisation conflicts are designed explicitly rather than discovered in the field.
- Practical value
- Staff can complete work where it happens, data reaches central systems without re-entry, and the application continues to function when connectivity does not.
UI/UX design
- What it includes
- Task analysis, information architecture, wireframing, interaction design, visual design, accessible component libraries and design documentation handed over with the code.
- Business need addressed
- Relevant when users avoid a system, make repeated errors in it, or need training to complete routine tasks — all signs that the interface does not match the work.
- Typical delivery approach
- We study the tasks people actually perform, including their shortcuts and workarounds, then design flows around them. Designs are produced as a reusable system of components and rules, not as a set of isolated screens.
- Practical value
- Fewer errors, less training, and a design system that keeps later additions consistent instead of gradually diverging.
Cloud solutions and infrastructure
- What it includes
- Environment design, infrastructure as code, containerisation, deployment pipelines, backup and restore procedures, monitoring, alerting and cost review.
- Business need addressed
- For teams whose deployments are manual and risky, whose environments differ from one another, or whose infrastructure spend has grown without a clear explanation.
- Typical delivery approach
- Infrastructure is expressed as version-controlled code so environments can be recreated identically. Deployment becomes an automated, reversible pipeline with health checks. Restore procedures are tested, not assumed.
- Practical value
- Releases become routine, recovery is practised rather than theoretical, and consumption is visible enough to be managed.
IT consulting
- What it includes
- Architecture and code review, technology selection, delivery process assessment, risk identification and a written report setting out options with trade-offs.
- Business need addressed
- Useful before a significant investment, when internal opinion is divided, or when a system's behaviour has become difficult to explain or predict.
- Typical delivery approach
- A time-boxed review combining interviews, documentation review and direct examination of the code and infrastructure. We present findings as prioritised options rather than a single mandated answer.
- Practical value
- A decision supported by independent evidence, and a record of the reasoning that remains useful long after the engagement ends.
System integration
- What it includes
- Interface design between systems, API and message-based integration, data mapping and transformation, error handling, retry strategies and integration monitoring.
- Business need addressed
- For organisations where information is re-typed between tools, reports are reconciled by hand, or two systems hold conflicting versions of the same record.
- Typical delivery approach
- We document each system's data model and constraints, define the contract between them, and decide deliberately which system owns which fact. Failure paths — timeouts, partial writes, duplicates — are designed rather than left to chance.
- Practical value
- Data moves once and reliably, manual re-entry disappears, and integration problems surface through alerting instead of through a disputed report.
Software modernisation
- What it includes
- Assessment of an existing codebase, dependency and platform upgrades, incremental refactoring, test coverage introduction, data migration and phased replacement of components.
- Business need addressed
- When an application still performs a necessary function but is hard to change, depends on unsupported platforms, or cannot be safely modified because it has no tests.
- Typical delivery approach
- We rarely recommend a full rewrite. Instead we characterise existing behaviour with tests, isolate parts of the system behind clear boundaries, and replace them one at a time while the system stays in service.
- Practical value
- Risk is spread across many small steps instead of concentrated in one launch, and the knowledge embedded in the original system is preserved rather than discarded.
Quality assurance and testing
- What it includes
- Test strategy, unit and integration testing, end-to-end automation, regression suites, exploratory testing, accessibility testing, performance testing and defect triage.
- Business need addressed
- For teams where releases regularly reintroduce old faults, where testing depends on one person's knowledge, or where nobody can state confidently what a release actually changed.
- Typical delivery approach
- Testing effort is directed by risk: the paths that carry money, legal obligation or safety receive the most attention. Automated suites run on every change, and exploratory testing covers the areas automation handles poorly.
- Practical value
- Defects are found before users encounter them, regressions are caught the day they appear, and release decisions rest on evidence.
Technical support and maintenance
- What it includes
- Monitoring and alerting, incident response, corrective fixes, dependency and platform updates, performance review, backup verification and small incremental improvements.
- Business need addressed
- For live systems that must remain dependable, particularly where the original development team is no longer available or internal capacity is fully committed elsewhere.
- Typical delivery approach
- Support operates against agreed severity levels and response expectations. Routine maintenance is scheduled in advance. Significant incidents are followed by a written review that ends with a specific preventive change.
- Practical value
- Problems are detected before they are reported, maintenance stops accumulating as hidden debt, and the system keeps improving in small, safe steps.
Cybersecurity consulting
- What it includes
- Threat modelling, secure architecture review, authentication and access-control design, dependency vulnerability review, secrets management, logging design and secure development practices.
- Business need addressed
- Relevant when a system handles personal or commercially sensitive data, when access control has grown ad hoc, or when a customer or regulator requires evidence of secure practice.
- Typical delivery approach
- We model realistic threats for your specific system rather than applying a generic checklist, then prioritise remediation by exposure and impact. Findings are documented with concrete, implementable steps.
- Practical value
- Security decisions become explicit and reviewable, the most likely avenues of attack are closed first, and secure practice is embedded in how changes are made.
Data and automation solutions
- What it includes
- Data modelling, migration, ETL and reporting pipelines, scheduled and event-driven workflows, document generation, notification systems and internal tooling.
- Business need addressed
- For organisations where staff spend significant time on repetitive transfer, reconciliation and formatting of data, or where reporting depends on manually maintained files.
- Typical delivery approach
- We map the manual process end to end, identify the steps that genuinely require judgement, and automate the rest. Automated workflows are built to be observable, with clear handling and reporting of failures.
- Practical value
- Recurring manual effort is removed, reports become reproducible from source data, and people spend their time on the decisions rather than the transcription.
The same discipline applies to every service
Scoping
Interviews, process mapping and a written specification with explicit assumptions, dependencies and acceptance criteria.
Planning
Work broken into increments with sequencing driven by risk: the uncertain and the critical are tackled early.
Implementation
Short cycles ending in reviewable software, with peer review and automated checks on every change.
Verification
Testing against the agreed criteria, with defects triaged by severity and impact rather than by convenience.
Release
Automated, reversible deployment with health checks, followed by a period of heightened monitoring.
Handover
Source code, infrastructure definitions, runbooks and architecture notes transferred in a usable state.
Where our engineering time is spent
- Application layer
- TypeScript and JavaScript across browser and server, with Python, Java, Kotlin and Swift used where the platform calls for them.
- Interfaces
- React component systems, server-rendered pages, design tokens and accessible patterns tested against keyboard and screen-reader use.
- Services and APIs
- REST and GraphQL interfaces, message queues, scheduled jobs and event-driven workflows with explicit failure handling.
- Data
- Relational schema design, migrations, document stores, caching, reporting pipelines and archival strategy.
- Infrastructure
- Containers, infrastructure as code, CI/CD pipelines, environment parity, monitoring, logging and alerting.
Verification is part of building
Quality assurance is not a phase appended to the end of a project. It runs alongside implementation, which is the only way defects are found while they are still cheap to correct.
Risk-directed coverage
Test effort concentrates on logic with financial, legal or safety consequences.
Continuous execution
Suites run automatically on every change, not on a weekly schedule.
Accessibility verification
Keyboard operation, focus order, contrast and semantics are checked before release.
Performance thresholds
Agreed response-time and payload budgets are measured as part of the pipeline.
Exploratory testing
Structured manual investigation of areas automation covers poorly.
Transparent triage
Defect severity is agreed openly, with known issues recorded rather than quietly carried.
Security decisions made in the open
Threat modelling
Realistic attack paths for your specific system are identified during design, not after deployment.
Least privilege
Accounts, services and integrations receive the narrowest access that allows them to function.
Secrets management
Credentials are stored in managed secret stores, rotated, and never committed to source control.
Dependency hygiene
Third-party packages are inventoried, pinned and monitored, with a defined route for security updates.
Data protection
Sensitive data is identified, encrypted in transit and at rest, and retained only while there is a reason to keep it.
Auditability
Security-relevant actions are logged in a form that supports investigation without exposing the data itself.
After release, the work continues
Support arrangements are agreed in writing and sized to the system: what is monitored, which severity levels apply, how updates are scheduled, and who is responsible for what. Questions about a support arrangement can be sent to [email protected], or through the form on the Contacts page.
Monitoring and alerting
Instrumentation that detects failure and degradation before users report them.
Corrective maintenance
Defect resolution against agreed severity levels and response expectations.
Preventive maintenance
Scheduled dependency, platform and certificate updates with owners and dates.
Incremental improvement
Small, regular enhancements that keep a system aligned with how the work changes.