Ten areas of work, described in operational terms. Each entry sets out what the service is, the business problems it addresses, its typical scope, the value it is intended to produce, and the practical considerations that affect delivery. No outcome is guaranteed, and no performance figures are claimed.
01 / Service
Custom software development
Applications built specifically for an organisation's process, where no packaged product fits closely enough to be worth the compromise.
Business problems addressed
Work spread across spreadsheets and email; packaged tools bent so far out of shape that staff maintain shadow records beside them; rules that exist only in the heads of experienced employees.
Typical scope
Process analysis, data modelling, application design, back-end and front-end implementation, role-based access, automated tests, deployment pipeline and documentation.
Expected business value
A single authoritative place for the work to happen, with rules enforced consistently and a record of what was done, by whom and when.
Delivery considerations
Delivered in increments, each usable by a small group before wider rollout. Requires access to the people who perform the process today, not only to their managers.
02 / Service
Web application development
Browser-based systems for staff, customers or partners, from internal portals to externally facing service applications.
Fig. 07 — Architecture decides what is possible later
Business problems addressed
Information requested by phone or email that the requester could retrieve themselves; interfaces that fail on mobile devices; slow pages that push people back to manual routes.
Typical scope
Interface design and implementation, accessibility work, responsive layout, API layer, authentication, session handling, performance tuning and browser testing.
Expected business value
Fewer inbound requests for routine information, faster completion of self-service tasks, and a consistent experience across devices.
Delivery considerations
Best approached with agreed content and permission rules up front. Browser support targets and accessibility expectations are defined at scope stage.
03 / Service
Business process automation
Removing repetitive manual steps by encoding rules, scheduling work and handling events between systems automatically.
Business problems addressed
Re-keying the same data into several systems; approvals stalled in inboxes; monthly routines that occupy days of skilled time; errors that appear only when someone notices them downstream.
Typical scope
Process mapping, rule definition, exception handling design, job scheduling, notifications, audit logging and reporting on automated activity.
Expected business value
Time returned to skilled staff, fewer transcription errors, and exceptions surfaced deliberately instead of discovered by accident.
Delivery considerations
Automation is only as sound as the rules behind it. Ambiguous or contested rules are resolved with the business before implementation, and exceptions always keep a human path.
04 / Service
Cloud solutions
Design, migration and operation of cloud environments for applications, data and internal services.
Business problems addressed
Servers nobody wants to touch; capacity that cannot flex; environments configured by hand and impossible to reproduce; unclear or surprising running costs.
Typical scope
Architecture design, infrastructure as code, environment separation, networking and identity configuration, deployment automation, monitoring, backup and cost review.
Expected business value
Environments that can be rebuilt from source, scaled in line with demand, and operated by more than one person.
Delivery considerations
Migration is planned as staged movement with rollback options rather than a single cut-over, and cost implications are modelled before commitment.
05 / Service
Systems integration
Making separate platforms exchange information reliably, on agreed terms, with a record of what moved.
Fig. 08 — Cloud and hosting environments under management
Business problems addressed
Duplicated master data; nightly exports repaired by hand; two systems disagreeing about the same customer or order; no one able to say which record is authoritative.
Typical scope
Interface analysis, data mapping, transformation rules, message or API design, retry and error handling, reconciliation reporting and monitoring.
Expected business value
Data entered once and trusted downstream, with disagreements between systems detected automatically rather than reported by a customer.
Delivery considerations
Third-party systems set the boundaries. Rate limits, vendor support and change windows are established early, and integrations are designed to fail loudly rather than silently.
06 / Service
Data and analytics solutions
Turning operational records into structures that can answer business questions consistently.
Business problems addressed
Reports that disagree; figures assembled manually each period; definitions of core measures that vary by department; analysis limited by how the data was stored.
Typical scope
Source assessment, data model and warehouse design, transformation pipelines, definition of measures, quality checks and reporting or dashboard layers.
Expected business value
One agreed definition per measure, refreshed on a schedule, so discussion can move from validating numbers to acting on them.
Delivery considerations
Requires agreement on definitions before construction. Data quality issues found during the work are reported rather than quietly corrected in transit.
07 / Service
Cybersecurity consulting
Practical review and improvement of how applications, infrastructure and access are secured.
Business problems addressed
Permissions accumulated over years; credentials stored in unsafe places; unpatched dependencies; no clear view of exposure or of what an incident response would involve.
Typical scope
Access and identity review, secrets management, application security review, dependency and configuration scanning, logging and alerting improvements, and written remediation planning.
Expected business value
A prioritised, realistic picture of exposure and a sequence of changes that reduces it, expressed in terms of business impact.
Delivery considerations
Advisory and engineering work, not certification. Findings are documented with severity and effort so the organisation decides the order of remediation.
08 / Service
IT strategy and technical consulting
Assessment and planning support for organisations deciding what to build, buy, replace or leave in place.
Fig. 09 — Monitoring and security review
Business problems addressed
Competing internal proposals with no shared basis for comparison; uncertainty about whether to extend or replace a system; vendor claims that are hard to evaluate independently.
Typical scope
Current-state assessment, option analysis with trade-offs and indicative effort, target architecture, sequencing plan and written recommendations.
Expected business value
A documented basis for a decision, including the option of doing nothing, so the choice can be defended later.
Delivery considerations
Short, focused engagements. We state where evidence is thin rather than presenting assumptions as findings.
09 / Service
Software modernisation
Improving or incrementally replacing systems that still serve their purpose but have become expensive or risky to change.
Business problems addressed
Unsupported frameworks; no automated tests; deployment that depends on one person; a codebase where small changes cause unpredictable effects.
Typical scope
Codebase and dependency assessment, test coverage introduction, refactoring, component-by-component replacement, data migration and parallel running where required.
Expected business value
Reduced operational risk and a system that can accept change again, without the disruption of a full rewrite and cut-over.
Delivery considerations
Sequenced so the service stays available throughout. Progress is measured by risk removed, which is less visible than new features and is reported explicitly.
10 / Service
Ongoing technical support
Continued maintenance, monitoring and small-change work for systems in production.
Business problems addressed
Issues with no clear owner; updates postponed until they become urgent; knowledge concentrated in one departed individual; no agreed route for small improvements.
Typical scope
Monitoring and alert response, security and dependency updates, backup verification, incident handling, minor enhancements and periodic health review.
Expected business value
Predictable upkeep, problems addressed before they interrupt operations, and a documented route for incremental change.
Delivery considerations
Response expectations, covered hours and boundaries are agreed in writing at the start. Support arrangements do not imply guaranteed outcomes for issues outside our control.
Discussing a service area
Enquiries about any of the areas above can be sent by email. The address is published as plain text.
