Engineering Services

Engineering services for intelligent connected products.

We help teams design, build, pilot, and operationalize AI + IoT systems across the device, data, intelligence, and governance stack. Every engagement ends with something the client can run, audit, and extend.

Scope Device → Fleet
Architecture Stack-agnostic
Output Runnable + documented
Handover Client-operable
4–6 wk Pilot-ready system timeline
4 Integrated service areas
20+ Defined deliverables across engagements
100% Engagements end with handover pack
Core Services

Four service areas. One integrated system.

Each service area produces specific, documented deliverables. Work can be engaged individually or as a full-stack programme — both paths are designed to leave client teams able to operate without ongoing dependency.

01 / Device and embedded systems
Hardware-to-firmware, designed for constrained environments

Sensor selection, electronics architecture support, MCU/SoC firmware, telemetry protocols, OTA update strategy, and reliability planning for constrained environments — built around operational requirements, not a generic stack.

What we work on
  • Sensor selection and validation against environmental and power constraints
  • Electronics architecture support for custom or COTS hardware
  • MCU or SoC firmware development in C/C++ or Rust
  • Telemetry protocol selection and implementation (MQTT, CoAP, LwM2M, LoRaWAN)
  • OTA update architecture, rollback logic, and delta patching
  • Reliability and failure mode planning for unattended operation
  • Power profiling and sleep-mode optimisation
↳ Deliverables
Device architecture brief
Sensor and connectivity recommendation with rationale
Firmware plan and module map
Power budget and reliability assumptions
Prototype or pilot-ready device scope
Tools & platforms ESP32 STM32 nRF52840 Zephyr RTOS FreeRTOS LoRaWAN MQTT CoAP LwM2M
🧠
02 / Data and intelligence systems
Edge and cloud inference, instrumented for operational use

Data pipeline design, edge or cloud inference architecture, model compression, thresholding, drift monitoring, and performance instrumentation — aligned to operational goals, not benchmark scores.

What we work on
  • Telemetry data schema and ingestion pipeline design
  • Edge inference vs cloud inference architecture tradeoffs and decision
  • Model selection, compression (quantisation, pruning), and export to target runtime
  • Confidence thresholding and safe fallback logic
  • Drift monitoring with alert thresholds and retraining triggers
  • Performance instrumentation aligned to operational SLAs
  • Labelling workflow and training data governance
↳ Deliverables
Data schema and pipeline specification
Intelligence workflow and inference architecture brief
Model deployment approach and runtime configuration
Monitoring metrics and drift alert design
Performance review report against operational targets
Tools & frameworks TensorFlow Lite ONNX Runtime Edge Impulse PyTorch MLflow Apache Kafka TimescaleDB InfluxDB
☁️
03 / Cloud, dashboards, and integration
Secure ingestion, fleet observability, and system integration

Secure telemetry ingestion, operational dashboards, alert logic, APIs, and access-aware integration — giving teams visibility into device health, fleet status, and system behavior at scale.

What we work on
  • Secure device-to-cloud telemetry ingestion with TLS and certificate provisioning
  • Operational dashboard design for fleet health, anomaly rate, and uptime
  • Alert and notification logic tied to operational thresholds
  • REST and event-driven API design for downstream system integration
  • IAM and access control policy for multi-role operations
  • Device shadow, twin, and state management patterns
  • Cloud infrastructure sizing and cost modelling for pilot and scale
↳ Deliverables
Telemetry pipeline architecture and configuration
Dashboard prototype with key operational panels
Alerting logic and notification routing plan
API specification and integration plan
Fleet observability checklist and SLA instrumentation guide
Platforms & tools AWS IoT Core Azure IoT Hub Google Cloud IoT Grafana InfluxDB Prometheus Terraform OpenAPI
📋
04 / Governance and transfer
Documentation, controls, and training so teams can operate independently

Runbooks, deployment checklists, risk controls, maintenance guidance, access policies, training, and documentation — so client teams can own, audit, and extend the system without continued dependency on us.

What we work on
  • Deployment runbook authoring and review
  • Security and privacy checklist against NISTIR 8259 and ETSI EN 303 645
  • Incident playbooks and escalation paths
  • Maintenance schedule and component lifecycle guidance
  • Access control policy and role documentation
  • Operator training session design and delivery
  • Audit-ready technical documentation package
↳ Deliverables
Deployment runbook
Security and privacy checklist
System maintenance guide
Operator training session (recorded or live)
Full handover pack — audit-ready, client-owned
Standards referenced NIST AI RMF NISTIR 8259 ETSI EN 303 645 ISO 27001 IEC 62443
Engagement Models

Four ways to engage. All scoped before work begins.

Every engagement starts with a written scope, a defined deliverable set, and agreed acceptance criteria. No open-ended retainers. No ambiguous outputs.

Sprint · 1–2 weeks
Discovery and architecture sprint

A structured technical review that produces an executable architecture brief, a component recommendation, and a clear risk register. Designed to remove ambiguity before build decisions are made — useful for grant applications, board review, or procurement scoping.

Best for: Early-stage teams validating feasibility, de-risking a proposal, or preparing for a larger programme.
Sprint · 4–6 weeks
Pilot build sprint

An end-to-end build sprint producing a pilot-capable system with working device firmware, a cloud pipeline, a monitoring dashboard, and an initial handover pack. Performance benchmarked against defined operational targets. Acceptance tested before handover.

Best for: Teams ready to build, with a defined use case and access to a test environment or device.
Sprint · 2–4 weeks
System recovery sprint

A structured diagnostic and remediation engagement for systems that have stalled in pilot. We assess the architecture, identify root causes — whether data quality, model performance, integration gaps, or governance — and produce a recovery plan with prioritised actions.

Best for: Teams whose pilot has stopped progressing, or systems exhibiting unexplained performance degradation.
Ongoing · 4–12 weeks
Capability transfer support

Structured knowledge transfer, documentation review, and embedded coaching for internal engineering or operations teams. Covers system architecture, operational procedures, monitoring interpretation, and governance. Ends when the internal team can operate and extend the system without external support.

Best for: Organisations that have built or acquired a system and need to bring operational competence in-house.
Standards and governance

Built to be audited, not just deployed.

Deliverables are structured to support grant reporting, procurement evaluation, and internal governance review. We reference established standards and document decisions so outputs are traceable and defensible.

Security by design

Device and cloud work references NISTIR 8259 for IoT device cybersecurity baselines and ETSI EN 303 645 for consumer IoT. Security controls are documented with rationale, not just implemented.

NISTIR 8259 ETSI EN 303 645 IEC 62443

AI risk and governance

Intelligence system design references the NIST AI Risk Management Framework. Model decisions, thresholds, fallback logic, and monitoring are documented in a format suitable for review by non-technical stakeholders.

NIST AI RMF Model cards Drift audit logs

Procurement and grant credibility

Architecture briefs, risk registers, and handover packs are structured to support procurement due diligence and grant milestone reporting — including Innovate UK, UKRI, Horizon-adjacent programmes, and technology readiness assessments.

TRL documentation Milestone reports Risk registers

Data and privacy controls

Data pipeline design includes a data classification step, retention policy, and processing record. For systems involving personal or sensitive data, we work to privacy-by-design principles with documented controls.

ISO 27001 aligned GDPR-aware design Processing records
Start a conversation

Tell us where the system is blocked.

We will recommend the shortest execution path and the deliverables needed to de-risk it — whether that is a single architecture brief or a full pilot sprint.

What to bring to the first call
01
A short description of the system or product — what it is supposed to do, and what it is not yet doing.
02
The constraint that is blocking progress — technical, resource, timeline, or knowledge.
03
Any existing documentation — architecture diagrams, previous proposals, test results, or grant deliverables.
First call
45 minutes. We will listen, ask clarifying questions, and confirm whether and how we can help — before any scope is proposed.