Skip to content
Discuss a project

Practice 02 · Software & Digital Solutions

Software that fits the work. Not the other way around.

Business systems, web and mobile applications, integrations and dashboards. We build software that stands on its own for the teams who use it every day, and software that connects to the devices and equipment they operate.

Discuss a software project See the five service areas
StandaloneWorkflow tools, portals and products for people and processes.
ConnectedThe same foundations, reading data from the field.
Layered software architecture, standalone or connectedFour stacked layers drawn as thin plates. The top layer holds a web screen listing purchase requests and a phone screen showing a live pump reading. Below it, a services layer lists API endpoints, a data layer shows a database and its tables, and an integrations layer connects to ERP, accounting, email and devices. A highlighted line runs from a small field gateway into the devices integration and up through every layer to the phone.L4 · INTEGRATIONSERPAccountingEmail · SMSDevicesordersinvoicesalertsModbus · MQTTL3 · DATADBTABLESrequestsapprovalsaudit_logusersassetsreadingsFilesphotos · PDFL2 · SERVICES / APIREST API · v1GET/v1/requestsPOST/v1/approvalsGET/v1/assets/P-101POST/v1/auth/tokenSERVICESAuth · rolesNotificationsScheduled jobsL1 · INTERFACES — WEB · MOBILEops.example.com/requestsRequestsApprovalsAssetsReportsPurchase requests+ NewIDITEMSTATUSPR-0142PR-0141PR-0139Pump seals ×6Site laptopCable traysReviewApprovedDone3 of 18 openP-101LIVE4.2barDischargeGW-01FIELD DEVICE · OPTIONALSAME API,SAME DATAHOSTEDBACK END
Illustrative architecture · interfaces → services → data → integrations

Service map

Five service areas, one practice.

Our software capabilities cover complementary areas, from custom business applications to cloud infrastructure and digital products. Services can be delivered independently or combined to meet specific business and operational needs.

  1. 01 Custom software & business systems

    Workflow tools, portals and internal platforms built around how your organisation actually works, so requests, approvals and records stop living in spreadsheets and inboxes.

    TYPICAL DELIVERABLESWorkflow model · role-based web platform · back-office & customer portals · handover docs

  2. 02 Web & mobile applications

    Responsive web apps and mobile experiences for staff at a desk, customers online and teams working on site, all served by one back end.

    TYPICAL DELIVERABLESInteraction flows · responsive web app · mobile / PWA · back-end services · release plan

  3. 03 Cloud, APIs & integrations

    Hosted systems, databases and APIs that let your software share data with the tools you already use, with authentication and access designed in from the start.

    TYPICAL DELIVERABLESDeployment architecture · databases · REST APIs · authentication · third‑party connectors

  4. 04 Data, monitoring & dashboards

    Reports and operational dashboards for business data or equipment readings, designed around the decision each screen has to support.

    TYPICAL DELIVERABLESData model · collection pipeline · reports · operational dashboards · alert rules

  5. 05 SaaS & digital products

    Software products and subscription-based digital solutions developed to address business needs, simplify operations and improve productivity.

Standalone or connected

Same discipline. Two kinds of system.

Software is a full practice here, not an add-on to engineering projects. Some systems only ever touch people and business data. Others start at a sensor. The method, the code quality and the handover are the same.

Example scenario · not a client project

A · A workflow platform for an office team

Three roles, requester, manager and finance, each act on one stage of a request platform. Approved requests are exported to an accounting system and every step triggers a notification.RQRequestersubmitsMGManagerreviewsFNFinanceover limitRequest platformSubmittedformIn reviewrulesApprovedPO> limit?AUDIT LOG · EVERY STEPEmailnotifyAccountingexport PO
  • UsersRequesters, managers and finance, each seeing only their step
  • We buildRequest forms, approval rules, notifications, an audit log and an accounting export
  • ReplacesA shared spreadsheet and long email chains

Example scenario · not a client project

B · Equipment data feeding a dashboard

A pressure transmitter on a pump line sends readings through a gateway to an API and database, which feed a dashboard that raises a maintenance alert when pressure passes a limit.5.3POST/readingsTLS · DBP-101 pressure5.3barLIMIT 5.0Above limitWork orderraised formaintenancePT-101GATEWAYAPI · DBVALUES ILLUSTRATIVE
  • UsersOperations and maintenance staff checking equipment
  • We buildData collection, an API and database, a dashboard and alert rules
  • WithOur engineering practice, when the field side also needs design
How engineering and software combine

How engagements run

Understand before we implement.

Scope, responsibilities, technical constraints and acceptance criteria are agreed before delivery begins. Each stage ends with something you can review.

Evidence first

Real work, prototypes and concepts, each clearly labelled.

Review selected projects
No.StageWhat happens · what you review
01Discover the operating contextWorkflows, users, existing systems and constraints. → Problem statement and draft scope
02Define scope and technical approachArchitecture, integrations, milestones and acceptance criteria. → Scope, architecture and plan
03Build, verify and documentWorking increments, tested and documented as they are delivered. → A working release per milestone
04Integrate, hand over and supportDeployment, data migration, training and agreed support. → Acceptance tests and handover pack

Start a software project

A process to fix or a product to build? Tell us what it needs to do.

Describe the people, the data and any equipment involved. We will reply with the parts we would build and the questions we need answered first.

Discuss a software project

Inquiries are routed to the software practice lead.