Solutions & services

Six service lines, each with a scope you can hold us to

Every line below states what we do, what you receive, and how the engagement starts. If a requirement does not fit one of these, say so and we will tell you plainly whether we are the right supplier.

Structure

How the work is organised

Three divisions. Most engagements touch more than one, which is the point — the licensing conversation and the integration work are not handed to different companies.

Service lines

What we deliver

Scope, deliverables and starting point for each line. Deliverables are artefacts you can point at — not adjectives.

01

Software licensing & deployment

Getting the right licences in place, activated correctly, and kept compliant as teams and requirements change.

Starting point

Entitlement review, typically completed within one week

Scope

  • Requirement and entitlement review across existing estate
  • Licence model comparison: subscription, perpetual, volume, academic
  • Procurement through authorised distributors
  • Installation, activation and device-level rollout
  • Renewal calendar and compliance documentation

You receive

  • Licence register with entitlement and renewal dates
  • Deployment runbook for internal IT
  • Named point of contact for renewals and audits
02

Application development

Custom web and business applications built to a defined scope, with the documentation and handover to run them without us.

Starting point

Fixed-scope discovery phase before any build commitment

Scope

  • Discovery, scoping and technical specification
  • UX and interface design against real workflows
  • Front-end and back-end implementation
  • Automated testing and staged release
  • Documentation and team handover

You receive

  • Working application in your own hosting or ours
  • Source code and repository access, owned by you
  • Technical and administrator documentation
03

Cloud & infrastructure

Migrating workloads, setting up tenants and environments, and putting monitoring and backup in place before they are needed.

Starting point

Assessment first — no migration starts without a rollback plan

Scope

  • Microsoft 365 and Azure tenant configuration
  • Workload assessment and migration planning
  • Identity, access and conditional access policy
  • Backup, retention and recovery testing
  • Cost review and rightsizing

You receive

  • Configured environment with documented settings
  • Tested recovery procedure, not just a backup job
  • Cost baseline and monitoring dashboards
04

Data & integration

Connecting systems that were never designed to talk to each other, and making the resulting data reportable.

Starting point

Pilot on a single integration before committing to the estate

Scope

  • Integration mapping across existing systems
  • API and middleware development
  • Data cleansing, transformation and migration
  • Reporting and dashboard delivery

You receive

  • Documented integration contracts and field mappings
  • Reconciliation report for every migration run
  • Dashboards against agreed definitions
05

AI & automation

Applying language and document models to specific, bounded business tasks — with a human approval step wherever the output carries risk.

Starting point

Bounded pilot on real data. We will say when a use case is not ready.

Scope

  • Use-case assessment and feasibility review
  • Document processing, extraction and classification
  • Workflow automation with defined approval gates
  • Evaluation harness and accuracy measurement

You receive

  • Scoped pilot with measured accuracy on your own data
  • Documented failure modes and escalation path
  • Human-in-the-loop review interface where required
06

Managed support

Ongoing responsibility for the systems we deliver, and for estates we did not build but can take over.

Starting point

Handover audit before any support agreement begins

Scope

  • Defined response and resolution targets
  • Patching, updates and dependency maintenance
  • Monitoring, alerting and incident response
  • Periodic review against changing requirements

You receive

  • Written service schedule with response targets
  • Named escalation contacts
  • Regular service review with open ticket history

Delivery process

Six steps, each with an output

A step that produces nothing you can inspect is not a step. Every phase below ends with a specific artefact.

  1. 01

    Discovery

    We establish the actual requirement, the systems already in place, and the constraints that are not negotiable. Fixed scope and fixed cost.

    Output Written requirement and constraint summary

  2. 02

    Specification

    Scope, architecture, data model, interfaces and acceptance criteria are documented and agreed before any build commitment is made.

    Output Technical specification and cost basis

  3. 03

    Build

    Delivered in reviewable increments against the specification, with a demonstrable state at the end of each one.

    Output Working increments in a staging environment

  4. 04

    Validation

    Testing against the acceptance criteria, including performance, access control and recovery. Findings are logged and resolved before release.

    Output Test results and resolved defect log

  5. 05

    Release & handover

    Deployment to production with documentation, administrator training and credentials transferred into your ownership.

    Output Live system, documentation and access in your name

  6. 06

    Support

    An optional service agreement with defined response targets, or a clean exit if you would rather run it yourselves.

    Output Service schedule, or a documented handover

Next step

Start with an assessment, not a proposal

Tell us the problem and we will scope the smallest piece of work that produces a useful answer — an entitlement review, a discovery phase or a handover audit. Fixed cost, written output.